Error: Invalid spaceKey on retrieving a related space config.

Updating Java paths after upgrading Java

If you upgrade to a newer version of Java where you installed BMC 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
  • BMC 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.


BMC Remedy Smart Reporting may not work successfully if the following conditions are true

  • Java is upgraded to newer version where BMC Remedy Smart Reporting is installed and Tomcat server is not upgraded to the newer version of Java.
  • BMC 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 BMC 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

Note: If BMC Remedy Smart Reporting and BMC AR System are installed on the same machine, when you update the Java path for AR in ARSystemInstalledConfiguration.xml file, the updates are applicable for BMC Remedy Smart Reporting also. So, you need not update java path for BMC 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 BMC 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 Java 8_u45 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.config
    1. On the server where BMC 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>>


  4. In produse.config:
    (Windows): ARSystemServerInstallDir\produse.config
    (Linux): ARSystemServerInstallDir/bin/produse
    1. On the server where BMC 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/arserverstoped
    1. On the server where BMC Remedy Action Request System is installed, open the arserverstop.config file or the arserverstoped 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
    1. On the server where BMC 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 thee edited file.

  7. In pluginsvr_config.xml:
    (Windows): ARSystemServerInstallDir\pluginsvr\pluginsvr_config.xml
    (Linux): ARSystemServerInstallDir/bin/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 
      For example, C:\Program Files\Java\jre1.8.0_45\bin\server\jvm.dll

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


  10. In BMC 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 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. 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

  15. Restart the BMC Remedy AR System server.

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

  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. Start the Remedy Mid Tier Tomcat Service.

Update Smart Reporting Tomcat server with the newer version of Java

  1. Stop BMC Smart Reporting Tomcat Service. 
  2. On the Command line interface (CLI), navigate to <SmartReportingInstallDir>/appserver/bin and type the command tomcat7w.exe //ES/BMCSmartReporting.

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

  5. Start the BMC Smart Reporting Tomcat Service.

Update the binaries for BMC Remedy Encryption Security

If you are using BMC 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-BMC Remedy application is installed. The term non-BMC 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-BMC 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 BMC Remedy Mid Tier server that is already encryption enabled, copy the following files to your JRE folder on the non-BMC 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.

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

Update Java home path in ARSystemInstalledConfiguration.xml file for BMC 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>

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Martin Noack

    Is it possible to use environment variables in the mentioned config files so that we don't have to modify each of the files but simply change the environment variable value?

    May 06, 2019 05:05
    1. Himanshu Raul

      Hi Martin,

      Thank you for the feedback on the documentation. It is not possible to use the environment variables in the mentioned config files because they are not just environment variables everywhere. The variables get converted to actual hardcoded value in some places. Hence it is not a change that can be done in a single place at this time.

      Regards,

      Himanshu

      May 30, 2019 04:35
  2. Amir Sedighi

    Please include dataimporttool.ini in this doc

    Aug 01, 2019 02:39
    1. Himanshu Raul

      Hi Amir,

      Thank you for your comment. We have updated the topic with the steps to update the Java path in the Data Import Tool.

      Regards,

      Himanshu

      Aug 02, 2019 04:13