×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')

This documentation supports the 20.02 version of Remedy Deployment.
To view an earlier version, select the version from the Product version menu.

Remedy Deployment 20.02 ... Upgrading Upgrading the platform Upgrading BMC Remedy AR System Completing the BMC Remedy AR System upgrade

Updating Java paths after upgrading Java

You must update the Java paths in your environment after you upgrade your Java version. After upgrading Java, if you do not update the Java path, you might face some challenges while upgrading Remedy components from an older version. For example, if you do not update the Java path and upgrade from the version 7.x or 8.x, BMC Atrium Tomcat service is deleted from the services console.  

This topic describes the steps to update Java paths for the following scenarios:

Related topics

Completing the BMC Remedy AR System upgrade

Upgrading BMC Remedy AR System

To update Java paths after upgrading Java to OpenJDK versions 16 or 17

If you are upgrading your Java version to OpenJDK versions 16 or 17 perform the following steps:

  1. Update the Tomcat configuration settings:
    1. Stop the Tomcat service that supports the Mid Tier application.
    2. Navigate to C:\Program Files\Apache Software Foundation\Tomcat 9.0\bin\Tomcat9w.exe.
    3. Run the Tomcat9w.exe file as Administrator.

    4. On the Tomcat Config panel, under the Java tab, change the path for Java Virtual Machine to the OpenJDK 16 or 17 path.
      For example:

      C:\Program Files\Java\jdk-17\bin\server\jvm.dll
    5. Edit the Java Options and remove the following entry if present:
       -XX:PermSize=256m
    6. Click Save.
    7. Edit the <ARSystemServerInstallDir>/midtier/filedeployer/conf/armonitor.cfg file.
    8. Update the Java path to the latest Java path and save the file.
    9. Start the Tomcat service that supports the Mid Tier application.

  2. Stop the AR System and Mid Tier services.
  3. Add the following parameters In arserver.config file:
    (Windows): ARSystemServerInstallDir\arserver.config
    (Linux): ARSystemServerInstallDir/bin/arserver.conf
    1. On the server where Remedy Action Request System is installed, open the arserver.config file or the arserver.conf file in a text editor.

    2. Add the following parameters:

      jvm.option.28 = -XX:+UseG1GC

#jvm options for jdk17 support
jvm.option.36 = -XX:+UseStringDeduplication
jvm.option.37 = -XX:MaxGCPauseMillis=200
jvm.option.38 = --add-opens=java.base/java.lang=ALL-UNNAMED
jvm.option.39 = --add-opens=java.base/java.util=ALL-UNNAMED
jvm.option.40 = --add-opens=java.base/java.io=ALL-UNNAMED
jvm.option.41 = --add-opens=java.base/java.util.concurrent=ALL-UNNAMED
jvm.option.42 = --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED
jvm.option.43 = --add-opens=java.base/java.net=ALL-UNNAMED

      Important

      The jvm.option numbers may vary in your file. Make sure that the jvm.option is added with an unique number.

    3. Remove the following parameter, if present:

      jvm.option.28 = -XX:+UseConcMarkSweepGC
    4. Save the edited file.

  4. Add the following command in the ARJavapluginServer process command and Carte Server Process command:

    --add-opens java.base/sun.net.www.protocol.jar=ALL-UNNAMED

    For example,

    ${BMC_JAVA_HOME}/java -Xmx1024m --add-opens java.base/sun.net.www.protocol.jar=ALL-UNNAMED -classpath /opt/bmc/ARSystem/pluginsvr:/opt/java/lib/bmcext/*:/opt/bmc/ARSystem/pluginsvr/arpluginsvr990_build000.jar:/opt/bmc/ARSystem/api/lib/arcmnapp990_build000.jar com.bmc.arsys.pluginsvr.ARPluginServerMain -x platform-admin-0 -i /opt/bmc/ARSystem
    ${BMC_JAVA_HOME}/java  -XX:+UnlockExperimentalVMOptions -XX:+EnableJVMCI --module-path=/opt/bmc/ARSystem/diserver/data-integration/lib/graal --upgrade-module-path=/opt/bmc/ARSystem/diserver/data-integration/lib/graal/compiler.jar:/opt/bmc/ARSystem/diserver/data-integration/lib/graal/compiler-management.jar  -Xmx1024m -cp /opt/bmc/ARSystem/diserver/data-integration:/opt/bmc/ARSystem/diserver/data-integration/lib/* -Dorg.mortbay.util.URI.charset=UTF-8 -Djava.library.path= -DKETTLE_HOME=/opt/bmc/ARSystem/diserver -DKETTLE_REPOSITORY= -DKETTLE_USER= -DKETTLE_PASSWORD= -DKETTLE_PLUGIN_PACKAGES= -DKETTLE_LOG_SIZE_LIMIT= -DKETTLE_MAX_LOG_SIZE_IN_LINES=5000 -DKETTLE_DISABLE_CONSOLE_LOGGING=Y -DKETTLE_COMPATIBILITY_MERGE_ROWS_USE_REFERENCE_STREAM_WHEN_IDENTICAL=Y -DKETTLE_LENIENT_STRING_TO_NUMBER_CONVERSION=Y --add-opens java.base/sun.net.www.protocol.jar=ALL-UNNAMED org.pentaho.di.www.Carte platform-admin-0.platform-admin 20000 -i /opt/bmc/ARSystem
  5. Update the JAVA_PATH configurations:
    1. Navigate to the <JRE_HOME>\conf\security\ folder and open the java.security file.

    2.  Edit the file and add the following code after security.provider.13=SunPKCS11:

      security.provider.14=org.bouncycastle.jce.provider.BouncyCastleProvide
    3. Save the file.
    4. Navigate to the OpenJDK 11 lib folder by using this path - <JRE_11_HOME>/lib.
    5. Copy the bmcext folder.
    6. Paste the bmcext folder in the new OpenJDK 16 or 17 lib folder. The path for the new location is <JRE_HOME>/lib/.
    7. Navigate to the OpenJDK 11 bin folder by using this path - <JRE_11_HOME>/bin.
    8. Copy the msvcr100.dll file.
    9. Paste the msvcr100.dll file in the new OpenJDK 16 or 17 bin folder. The path for the new location is <JRE_HOME>/bin/.

  6. If you are using OpenJDK version 11 or later, verify if the --add-opens java.base/java.lang=ALL-UNNAMED parameter is present.
    If not, add the parameter by performing the following steps:

    1. For Windows:
      1. Navigate to ARSystemServerInstallDir\Conf\armonitor.cfg file.

      2. Edit the file and add the --add-opens java.base/java.lang=ALL-UNNAMED parameter as shown in the following code:

        "C:\Program Files\Java\jdk-17\bin\java" -Xmx512m  -classpath "C:\Program Files\BMC Software\AtriumCore\cmdb\plugins\ne;C:\Program Files\BMC Software\AtriumCore\cmdb\plugins;C:\Program Files\BMC Software\AtriumCore\cmdb\sdk\bin\arpluginsvr91_build009.jar;C:\Program Files\BMC Software\AtriumCore\cmdb\sdk\bin\arapi91_build009.jar;C:\Program Files\BMC Software\AtriumCore\cmdb\sdk\bin\arutil91_build009.jar;C:\Program Files\BMC Software\AtriumCore\cmdb\sdk\bin\arlogger-9.1.10-SNAPSHOT.jar;C:\Program Files\BMC Software\AtriumCore\cmdb\sdk\bin\cmdbapi91.jar;;C:\Program Files\Java\jdk-17\lib\bmcext\*" --add-opens java.base/java.lang=ALL-UNNAMED com.bmc.arsys.pluginsvr.ARPluginServerMain -x clm-XYZ-XXXXX -i "C:\Program Files\BMC Software\ARSystem"
      3. Save the file.

    2. For Linux:
      1. Navigate to BMC_ATRIUM_CORE_HOME/cmdb/server/bi/normeng.sh file.

      2. Edit the file and add the --add-opens java.base/java.lang=ALL-UNNAMED parameter as shown in the following code:

        exec java -Xmx512m --add-opens java.base/java.lang=ALL-UNNAMED com.bmc.arsys.pluginsvr.ARPluginServerMain -x clm-XYZ-XXXXX -i /data/bmc/ARSystem $*
      3. Save the file.

  7. Set the Java Path in Environment Variables:
    1. In the search box, type 'Edit the system environment variables' and navigate to Advanced System Settings > Environment Variables.
    2. Under the User variables section, update the Path variable with the latest Java path. 
    3. Also update the path in the following location:
      env variable "%_PENTAHO_JAVA_HOME%\bin" , JAVA_HOME
    4. Under the System variables section, update the JAVA_HOME variable with the latest Java path.

  8. (OpenJDK 16 only) Set the Environment Variables:
    1. In the search box, type 'Edit the system environment variables' and navigate to Advanced System Settings > Environment Variables.
    2. Under the System variables section, set the following parameters:

      Variable Name= JDK_JAVA_OPTIONS

      Variable Value= --illegal-access=permit

  9. In Microsoft Windows Registry, update the JVM Library path with the current path:
    1. Open the Microsoft Windows Registry Editor.
    2. Update Registry reference of JVM Library to the newly installed Java path at the following locations:
      • HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > BMC Remedy Action Request System<server_name> > Parameter 
      • HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > BMC Remedy Email Engine > Parameter 
      • HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > BMC Remedy Flashboards Server > Parameter
      • HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > BMC Remedy MidTier File Deployer > Parameter 

  10. Update the Java paths with the latest Java path for the following AR System clients:
    1. In Remedy Developer Studio:
      • Navigate to Developer Studio Directory and edit devstudio.ini to update the latest Java path. 
        Example: C:\Program Files\Java\jre1.8.0_161\bin\javaw.exe

    2. In Remedy Data Import Tool:
      • Navigate to Data Import Tool Directory and edit dataimporttool.ini to update the latest Java path. 
        Example: C:\Program Files\Java\jre1.8.0_161\bin\javaw.exe

  11. Update the Java path with the current Java path in the following files for Windows:
    1. AR System:

      • <AR_System_Install_Dir>\BMC Software\ARSystem\Conf\armonitor.cfg

      • <AR_System_Install_Dir>\BMC Software\ARSystem\arserver.config

      • <AR_System_Install_Dir>\BMC Software\ARSystem\pluginsvr\pluginsvr_config.xml

      • <AR_System_Install_Dir>\BMC Software\ARSystem\AREmail\EmailStart.bat

      • <AR_System_Install_Dir>\BMC Software\ARSystem\AREmail\EmailStop.bat

      • <AR_System_Install_Dir>\BMC Software\ARSystem\arserverstop.config

      • <AR_System_Install_Dir>\BMC Software\ARSystem\produse.config

      • <AR_System_Install_Dir>\BMC Software\ARSystem\arconnectconfig.config

      • <AR_System_Install_Dir>\BMC Software\ARSystem\approval\bin\approval-utils.bat

      • <AR_System_Install_Dir>\BMC Software\ARSystem\diserver\data-integration\set-pentaho-env.bat

      • <AR_System_Install_Dir>\BMC Software\ARSystem\diserver\data-integration\ngie\bin\aimt.cmd

      • <AR_System_Install_Dir>\BMC Software\ARSystem\diserver\data-integration\ngie\bin\devtoprod.cmd

      • <AR_System_Install_Dir>\BMC Software\ARSystem\diserver\data-integration\ngie\bin\sampleJobImport.cmd

      • <AR_System_Install_Dir>\BMC Software\ARSystem\artools\arexport.bat

      • <AR_System_Install_Dir>\BMC Software\ARSystem\artools\pdp.bat

      • <AR_System_Install_Dir>\BMC Software\ARSystem\artools\seqdeploymentcli.bat

    2. BMC CMDB:

      • <CMDB_Install_Dir>\BMC Software\AtriumCore\cmdb\sdk\bin\deputil.cmd

      • <CMDB_Install_Dir>\BMC Software\AtriumCore\cmdb\sdk\bin\nesim.cmd

      • <CMDB_Install_Dir>\BMC Software\AtriumCore\cmdb\sdk\bin\run_cmdbjavadriver.bat

      • <CMDB_Install_Dir>\BMC Software\AtriumCore\cmdb\sdk\bin\vzUtil.cmd

      • <CMDB_Install_Dir>\BMC Software\AtriumCore\cmdb\sdk64\bin\nesim.cmd

      • <CMDB_Install_Dir>\BMC Software\AtriumCore\cmdb\sdk64\bin\deputil.cmd

      • <CMDB_Install_Dir>\BMC Software\AtriumCore\cmdb\sdk64\bin\run_cmdbjavadriver.bat

      • <CMDB_Install_Dir>\BMC Software\AtriumCore\cmdb\sdk64\bin\vzUtil.cmd

      • <CMDB_Install_Dir>\BMC Software\AtriumCore\cmdb\utils\CMDBArchive\runcmdbarchiveutil.cmd

      • <CMDB_Install_Dir>\BMC Software\AtriumCore\cmdb\utils\DashboardDataGenerator\rundashboardutil.cmd

      • <CMDB_Install_Dir>\BMC Software\AtriumCore\wsc\atriumws91\lib\atriumwsenv


    3. Mid Tier:
      • <AR_System_Install_Dir>\BMC Software\ARSystem\midtier\filedeployer\statusCheck.bat
      • <AR_System_Install_Dir>\BMC Software\ARSystem\midtier\filedeployer\conf\armonitor
    4. Tomcat:
      • <Tomcat_home_directory>\conf\catalina.properties

  12. Update the Java path with the current Java path in the following files for Linux:
    1. AR System:

      • /etc/arsystem/armonitor.conf

      • /<AR_System_Install_Dir>/bmc/ARSystem/bin/arserverd.conf

      • /<AR_System_Install_Dir>/bmc/ARSystem/bin/produse.config

      • /<AR_System_Install_Dir>/bmc/ARSystem/bin/arserverstopd.conf

      • /<AR_System_Install_Dir>/bmc/ARSystem/bin/arconnectconfig.config

      • /<AR_System_Install_Dir>/bmc/ARSystem/pluginsvr/pluginsvr_config.xml

      • /<AR_System_Install_Dir>/bmc/ARSystem/AREmail/emaild.sh

      • /<AR_System_Install_Dir>/bmc/ARSystem/diserver/data-integration/set-pentaho-env.sh

      • /<AR_System_Install_Dir>/bmc/ARSystem/diserver/data-integration/ngie/bin/aimt.sh

      • /<AR_System_Install_Dir>/bmc/ARSystem/diserver/data-integration/ngie/bin/devtoprod.sh

      • /<AR_System_Install_Dir>/bmc/ARSystem/diserver/data-integration/ngie/bin/sampleJobImport.sh

      • /<AR_System_Install_Dir>/bmc/ARSystem/approval/bin/approval-utils.sh

      • /<AR_System_Install_Dir>/bmc/ARSystem/artools/seqdeploymentcli.sh

      • /<AR_System_Install_Dir>/bmc/ARSystem/artools/pdp.sh

      • /<AR_System_Install_Dir>/bmc/ARSystem/artools/arexport.sh

      • /<AR_System_Install_Dir>/bmc/ARSystem/flashboards/server.sh

      • /<AR_System_Install_Dir>/bmc/ARSystem/bin/arsystem

    2. BMC CMDB:

      • /<CMDB_Install_Dir>/bmc/AtriumCore/cmdb/utils/CMDBArchive/runcmdbarchiveutil.sh

      • /<CMDB_Install_Dir>/bmc/AtriumCore/cmdb/utils/DashboardDataGenerator/rundashboardutil.sh

      • /<CMDB_Install_Dir>/bmc/AtriumCore/cmdb/sdk/bin/nesim.sh

      • /<CMDB_Install_Dir>/bmc/AtriumCore/cmdb/sdk/bin/run_cmdbjavadriver.sh

      • /<CMDB_Install_Dir>/bmc/AtriumCore/cmdb/sdk/bin/vzUtil.sh

      • /<CMDB_Install_Dir>/bmc/AtriumCore/cmdb/server/bin/atriumplugin.sh

      • /<CMDB_Install_Dir>/bmc/AtriumCore/cmdb/server/bin/normeng.sh

      • /<CMDB_Install_Dir>/bmc/AtriumCore/wsc/atriumws91/lib/atriumwsenv

    3. Mid Tier:

      • /data/bmc/ARSystem/midtier/filedeployer/conf/armonitor.conf

      • /data/bmc/ARSystem/midtier/filedeployer/filedeployer.sh

      • /data/bmc/ARSystem/midtier/filedeployer/statusCheck.sh

    4. Tomcat:

      • <Tomcat_home_directory>/conf/catalina.properties

      • <Tomcat_home_directory>/bin/catalina.sh

      • <Tomcat_home_directory>/bin/shutdown.sh

      • <Tomcat_home_directory>/bin/startup.sh

      • <Tomcat_home_directory>/bin/bmcAtriumSetenv.sh

  13. Restart all the services.

To update Java paths after upgrading Java to versions earlier than OpenJDK 16

If you upgrade to a version of Java earlier than OpenJDK version 16, you must update the Java paths on the environments where you installed the Remedy platform and application components.

You must update the Java paths in the following locations:

  • armonitor.cfg
  • arserver.config
  • produse.config
  • arserverstop.config
  • arconnectconfig.config
  • Microsoft Windows Registry
  • Remedy Developer Studio
  • ARSystemInstalledConfiguration.xml 

Notes

Java SE 8_u45 and later is supported.

Java SE versions earlier than 8-u45, Java 9, and Java 10 are not supported.

For Java 11, the following JVM parameters are not supported:

  • -XX:+UseParNewGC

  • -XX:+PrintGCDetails

  • -XX:+PrintGCDateStamps
  • -XX:+PrintGCCause

For more information on the supported JVM parameters, see Configuration checklist for Remedy Platform Open link .


Remedy Smart Reporting might not work successfully if the following conditions are true:

  • Java is upgraded to newer version where Remedy Smart Reporting is installed and Tomcat server is not upgraded to the newer version of Java.

  • Remedy Smart Reporting is installed on a stand-alone machine and BMC Remedy ARSystemInstalledConfiguration.xml file is not updated with the newer version java.

For Remedy Smart Reporting to work, you must perform the following steps:

  1. Update Smart Reporting Tomcat server with the newer version of Java.
  2. Update Java home path in ARSystemInstalledConfiguration.xml file. 

Important

If Remedy Smart Reporting and Remedy AR System are installed on the same machine, when you update the Java path for Remedy AR System in ARSystemInstalledConfiguration.xml file, the updates are applicable for Remedy Smart Reporting also. So, you need not update java path for Remedy Smart Reporting in ARSystemInstalledConfiguration.xml file.

To update Java paths

  1. In armonitor.cfg:
    (Windows): ARSystemServerInstallDir\Conf\armonitor.cfg
    (Linux): /etc/arsystem/serverName/armonitor.conf
    1. On the server where Remedy Action Request System is installed, open the armonitor.cfg file or the armonitor.conf file in a text editor.

    2. Find and replace references to the Java 7 path with the latest Java path.

    3. Update the BMC_JAVA_HOME parameter with the latest Java path.
    4. Save the edited file.

  2. In File Deployer folder:
    (Windows): ARSystemServerInstallDir\midtier\filedeployer\conf\armonitor.cfg
    (Linux): /etc/arsystem/serverName/midtier/filedeployer/armonitor.conf
    1. On the server where Remedy Action Request System is installed, in the filedeployer folder, open the armonitor.cfg file or the armonitor.conf file in a text editor.

    2. Find and replace references to the older Java path with the latest Java path.

    3. Save the edited file.

  3. In arserver.config:
    (Windows): ARSystemServerInstallDir\arserver.config
    (Linux): ARSystemServerInstallDir/bin/arserverd.conf
    1. On the server where Remedy Action Request System is installed, open the arserver.config file or the arserverd.config file in a text editor.

    2. Update the following parameter to the latest bin directory path:
      jvm.search.path.1=FILE_SYSTEM=<<Latest bin directory path>>

    3. If you are using Java 11, remove the following unsupported JVM parameter:

      • -XX:+UseParNewGC
    4. If you are using Java 11 and do not have Remedy Encryption Performance Security or Remedy Encryption Premium Security installed, you must add the following parameter:
      jvm.option.n=-Dorg.apache.activemq.broker.BouncyCastlePosition=100
      Where n is the order of the parameter. If you do not add this parameter, SOAP-based HTTPS connections might fail. 
    5. Save  the edited file.

  4. In produse.config:
    (Windows): ARSystemServerInstallDir\produse.config
    (Linux): ARSystemServerInstallDir/bin/produse.config
    1. On the server where Remedy Action Request System is installed, open the produse.config file or the produse file in a text editor.
    2. Update the following parameter to the latest bin directory path:
      jvm.search.path.1=FILE_SYSTEM=<<Latest bin directory path>>
    3. Save the edited file.

  5. In arserverstop.config:
    (Windows): ARSystemServerInstallDir\arserverstop.config
    (Linux): ARSystemServerInstallDir/bin/arserverstopd.conf
    1. On the server where Remedy Action Request System is installed, open the arserverstop.config file or the arserverstopd.conf file in a text editor.
    2. Update the following parameter to the latest bin directory path:
      jvm.search.path.1=FILE_SYSTEM=<<Latest bin directory path>>
    3. Save the edited file.

  6. In arconnectconfig.config:
    (Windows): ARSystemServerInstallDir\arconnectconfig.config
    (Linux): ARSystemServerInstallDir/bin/arconnectconfig.config
    1. On the server where Remedy Action Request System is installed, open the arconnectconfig.config file or the arconnectconfig file in a text editor.
    2. Update the following parameter to the latest bin directory path:
      jvm.search.path.1=FILE_SYSTEM=<<Latest bin directory path>>
    3. Save the edited file.

  7. In pluginsvr_config.xml:
    (Windows): ARSystemServerInstallDir\pluginsvr\pluginsvr_config.xml
    (Linux): ARSystemServerInstallDir/pluginsvr/pluginsvr_config.xml
    1. On the server where Remedy Action Request System is installed, open the pluginsvr_config.xml file in a text editor.
    2. Update the <ftsJavaPath> tag to the latest bin directory path:
        <ftsJavaPath>C:/Program Files/Java/jre1.8.0_101/bin/java</ftsJavaPath>
    3. Save the edited file.

  8. In Microsoft Windows Registry:
    1. Open the Microsoft Windows Registry Editor.
    2. Update Registry reference of JVM Library to the newly installed Java path at the following locations:
      • HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > BMC Remedy Action Request System<server_name> > Parameter 
      • HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > BMC Remedy Email Engine > Parameter 
      • HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > BMC Remedy Flashboards Server > Parameter
      • HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > BMC Remedy MidTier File Deployer > Parameter 
      • HKEY_LOCAL_MACHINE > SOFTWARE >WOW6432Node>Apache Software Foundation >Procrun 2.0>BMCSmartReporting>Parameters>Java
      For example, C:\Program Files\Java\jre1.8.0_45\bin\server\jvm.dll

  9. In Remedy Developer Studio:
    • Go to Developer Studio Directory and edit devstudio.ini to update the latest Java path. 
      Example: C:\Program Files\Java\jre1.8.0_161\bin\javaw.exe

  10. In Remedy Data Import Tool:
    • Go to Data Import Tool Directory and edit dataimporttool.ini to update the latest Java path. 
      Example: C:\Program Files\Java\jre1.8.0_161\bin\javaw.exe

  11. Update the ARSystemInstalledConfiguration.xml file to the latest version of Java. During your next upgrade, the installer fetches the value of Java version from the ARSystemInstalledConfiguration.xml file if the Java path is not updated in the installer panel.

    Windows:<install-directory>\BMC Software\ARSystem\ARSystemInstalledConfiguration.xml 

    UNIX:/opt/bmc/ARSystem/ARSystemInstalledConfiguration.xml


  12. Update Java reference in any batch file that you are using. For example, update EmailStart.bat or EmailStart.sh to the correct Java path.

  13. (Optional) Perform the following steps:

    1. Right-click Computer > Properties > Advanced System Settings > Environment Variables.
    2. Under the User variables section, update the Path variable with the latest Java path. 
    3. Under the System variables section, update the JAVA_HOME variable with the latest Java path.
       

  14. Restart the Remedy AR System server.

To update the Java path for Remedy Mid Tier Tomcat server

  1. Stop the Remedy Mid Tier Tomcat Service.
  2. Navigate to <Apache Tomcat folder>\bin\ and open the tomcat#w.exe file. (# represents the major version number).
  3. On the Tomcat Config panel, under the Java tab, select new path for Java Virtual Machine.



  4. If you are using Java 11, remove the following options from the Java Options field:
    -XX:+UseParNewGC

  5. Start the Remedy Mid Tier Tomcat Service.

To update the Java path for Smart Reporting Tomcat server

  1. Stop BMC Smart Reporting Tomcat Service. 
  2. On the Command line interface (CLI), navigate to <SmartReportingInstallDir>/appserver/bin and type the command tomcat#w.exe //ES/BMCSmartReporting.
    (# represents the Tomcat version installed on your computer)

  3. Press Enter.

  4. In the BMC Smart Reporting Properties window, under the Java tab, select new path for Java Virtual Machine. 

  5. Edit the <ARSystemServerInstallDir>/midtier/filedeployer/conf/armonitor.cfg file.
  6. Update the Java path to the latest Java path and save the file.

  7. Start the BMC Smart Reporting Tomcat Service.

To update the binaries for Remedy Encryption Security

If you are using Remedy Encryption Security, you must update the binary files located under the new Java path.

  1. Stop the Tomcat service on the machine on which your non-Remedy application is installed. The term non-Remedy application refers to the third party or user applications that use the Remedy AR System API to communicate with the AR System servers.
  2. Navigate to the <JRE_HOME>/lib/security/ folder and perform the following steps to back up the existing Java files that are being used by the non-Remedy application:
    1. Rename java.security to java.security.backup.
    2. Rename local_policy.jar to local_policy.jar.backup
    3. Rename US_export_policy.jar to US_export_policy.jar.backup.
  3. From your Remedy Mid Tier server that is already encryption enabled, copy the following files to your JRE folder on the non-Remedy machine:
    1. java.security
    2. local_policy.jar
    3. US_export_policy.jar
  4. Start the Tomcat service on the computer where non-BMC application is installed.

To update the Java home path in the Linux environment

You must update the Java home path in the following files for Linux environment:

  • armonitor.conf
  • arserverd.conf
  • arsystem.sh
  • pluginsvr_config.xml
  • emaild.sh
  • arcmdb.sh
  • arrecond.sh
  • normeng.sh
  • atriumplugin.sh
  • slmbrsvc.sh

To update Java home path in ARSystemInstalledConfiguration.xml file for Remedy Smart Reporting on a stand-alone machine

  1. Navigate to <install-directory>\BMC Software\ARSystem\ARSystemInstalledConfiguration.xml. 
  2. Update Java Home Path property value in XML with newer version Java and Save.

     <property>

      <name>BMC_JAVA_JRE_<<64 or 32>>_BIT_HOME_PATH</name> 

      <value>C:\Program Files\Java\jre<<new java version>></value>

    </property>


To update Remedy Single Sign-On server with the newer version of Java

To update the Java version of your Remedy Single Sign-On (RSSO) server, you must perform the steps mentioned in the knowledge article on BMC Communities Remedy Single Sign On - Procedure for upgrading Java for RSSO Open link .



Was this page helpful? Yes No Submitting... Thank you
Last modified by Maithili Deshpande on Apr 12, 2024
remedy_it_service_management upgrading remedy_ar_system post-upgrade updating_java_path

Comments

  1. Francois Seegers

    There is no mention of settings specific to using OpenJDK?

    Jun 01, 2020 10:35
    1. Himanshu Raul

      Hi Francois,

      Thank you for your comment on the documentation. We are working on creating a knowledge article for the settings specific to OpenJDK. We will update the documentation with the link to the KA soon.

      Regards,

      Himanshu

      Jun 30, 2020 11:50
  2. Sharvan Singh

    It would be good to add the non supported parameters for different versions in this document only. We were facing issue after Java upgrade which got resolved by following https://communities.bmc.com/docs/DOC-121311

    Oct 29, 2020 04:04
    1. Himanshu Raul

      Hi Sharvan,

      Thank you for your feedback on the documentation. We have updated the topic and added a link to the Knowledge article  Configuration checklist for Remedy Platform Open link . The topic describes the parameters which are supported and not supported for Java 11.

      Regards,

      Himanshu

      Nov 04, 2020 11:54

Log in or register to comment.

Setting the Java heap size
Enabling Call Home to collect diagnostics
© Copyright 1991-2021 BMC Software, Inc. © Copyright 1991-2021 BladeLogic, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.