Updating Java paths after upgrading Java

If you upgrade to a newer version of Java where you installed Remedy platform and application components, you must update Java paths at the following locations:

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

After upgrading Java, if you do not update the Java path, you may face some challenges while upgrading 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.

Note

Java SE 8_u45 and later is supported. Older versions as well as Java 9 and 10 are not supported.

If you are using 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 may 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:

Update Smart Reporting Tomcat server with the newer version of Java.
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

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.
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.
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.
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.
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.
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.
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.
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
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
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
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
Update Java reference in any batch file that you are using. For example, update EmailStart.bat or EmailStart.sh to correct Java path.
(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.
If you are using Java 11, perform the following steps for successful installation of Remedy Mid Tier:
1. Navigate to <Apache Tomcat folder>\bin\ and open the tomcat#w.exe file. (# represents the major version number).
2. On the Tomcat Config panel, click the Java tab and remove the following options from the Java Options field:
  1. -XX:+UseParNewGC
Restart the Remedy AR System server.

To update Remedy Mid Tier Tomcat server with the newer version of Java

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

To update Smart Reporting Tomcat server with the newer version of Java

Stop BMC Smart Reporting Tomcat Service.
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)
Press Enter.
In the BMC Smart Reporting Properties window, under the Java tab, select new path for Java Virtual Machine.
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.

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.
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.
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
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

Navigate to <install-directory>\BMC Software\ARSystem\ARSystemInstalledConfiguration.xml.
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 .