Remedy - Server - Additional Java path includes 'bmcext' in the armonitor.cfg from ARS 19.02

Version 3
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    Remedy AR System Server


    AR System Server


    BMC Remedy AR System Server version 19.02 and onwards


    This path was added to some processes inside the armonitor.cfg file:  <C:\Program Files\Java\jre1.8.0_XXX\lib\bmcext\*.jar>
    For example in the Plugin Server:

    Until version 18.08 the line was similar to this:
    "%BMC_JAVA_HOME%\java" -Xmx1024m -classpath "<C:\Program Files\BMC Software\ARSystem\pluginsvr;C> ...

    Now it has an extra path in version 19.02:
    "%BMC_JAVA_HOME%\java" -Xmx3072m -classpath "<d:\Program Files\BMC Software\ARSystem\pluginsvr;C:\Program Files\Java\jre1.8.0_XXX\lib\bmcext\*.jar>;
    Or in the File Deployer:

       "%BMC_JAVA_HOME%\java" -classpath "<C:\Program Files\BMC Software\ARSystem\arfiledeployer-9.1.04-SNAPSHOT.jar>"    
       "%BMC_JAVA_HOME%\java" -classpath "<C:\Program Files\Java\jre1.8.0_XXX\lib\bmcext\*.jar;d:\Program Files\BMC Software\ARSystem\arfiledeployer-9.1.07-SNAPSHOT.jar>"  

    Sometimes the path doesn't exist, it goes until <C:\Program Files\Java\jre1.8.0_XXX\lib\> but there's no bmcext folder inside.




      Starting with version 19.02, AR System now supports Java 11.
    Up until Java 8, the security installer (i.e. premium security, performance security and AWS installer) copies the required JAR files which are used for encryption into the <JAVA_home>/lib/ext folder, extension class loader was responsible to load all the JARs at runtime and add it to the classpath.
    However as of Java 9 onwards, the extension mechanism is obsolete and deprecated. This means that there is no such folder name called “ext”, so, it creates the folder called “bmcext” inside the <JAVA_HOME>/lib/bmcext, and copies all the required JARs into it.
    Starting from Java 9, JDK doesn’t load any JARs implicitly which are part of the “ext” folder because the “ext” folder has been deprecated. Therefore, it is the responsibility of individual components to load the JARs explicitly.
    So the product installer adds this in armonitor.cfg (-classpath "C:\tools\jdk-11.0.2\lib\bmcext\*.jar ). It just sets the “bmcext” directory in the $JAVA_HOME and then copies the JARs needed there and the code explicitly imports them as needed.

    For AR System this path will be used only if customer is working with Java 11 or higher, nevertheless the configuration should remain as it is. 


    Article Number:


    Article Type:


      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles