This documentation supports the 18.08 version of Remedy Deployment.

To view the latest version, select the version from the Product version menu.

Preparing the AR System server before you upgrade BMC Atrium Core and other BMC applications

Prepare the AR System before you upgrade BMC Atrium Core.

In this section

To prepare AR System server before you upgrade

  1. Make sure that the AR System server is correctly licensed.
    BMC Atrium Core requires an AR System server with a multi-server license.
  2. If you want to install the BMC Remedy ITSM Suite applications, and if you are using a different user, make sure that the BMC Atrium Core user is a member of the Administrator group in the BMC Remedy AR System User form.
  3. Disable AR System server encryption temporarily .
    Installation of BMC Atrium Core on an encrypted AR System server is not supported. You can enable encryption after installation.
    1. Log on to the AR System server.
    2. Open the AR System Administration Console.
    3. Choose System > General > Server Information.
    4. From the Server Information form, click the Encryption tab.
    5. In the New Encryption Settings area, choose Disabled in the Security Policy list, and click Apply.
    6. Restart the AR System server.

      Note

      Re-enable encryption after you finish installing all the BMC applications.

  4. Set the size limit for the AR System database.
    If you do not set size limits correctly, the database size limit might be reached.
    To prevent BMC Remedy AR System from reaching the size limit of the database, perform the following changes:

    • For Microsoft Windows using SQL Server — Open SQL Server Enterprise Manager and select the Automatically Grow File option for your AR System database.
    • For UNIX using Oracle — Execute the following SQL statement as the system user:
      ALTER DATABASE DATAFILE 'OracleHome/DATABASE/ARSYS' AUTOEXTEND ON NEXT 100M MAXSIZE UNLIMITED

      Note

      You do not need to commit or restart the server after you make the changes.

  5. Set the JVM heap size for the Tomcat server (this a BMC Remedy Mid Tier setting).
    If you use an existing Tomcat server instance, BMC recommends setting the JVM heap size of Tomcat servers to a minimum value of 1024 MB and a permanent generation size of 256 MB. Otherwise, you might see OutOfMemory errors and a failure to publish web services to the BMC Atrium Core Registry.
    • Setting the JVM heap size for a Windows computer:
      1. Stop the Tomcat server.
      2. Run the tomcat7w application to open the Apache Tomcat6 Properties dialog box. You can find tomcat6w.exe in the C:\Program Files \Apache Software Foundation\Tomcat7.0\bin folder.
      3. Click the Java tab.
      4. Set Maximum Memory Pool to 2048 MB or higher.
      5. In the Java Options list, set XX:MaxPermSize to 256 MB or higher.

        Note

        If you do not find XX:MaxPermSize in this list, look for XX:PermSize. Set this parameter to 256 MB or higher. If you cannot find either of these parameters in the Java Options list, add either XX:PermSize or XX:MaxPermSize using the following syntax:
        -XX:MaxPermSize=256m or -XX:PermSize=256m.

      6. Click Apply and then click OK.
      7. Start the Tomcat server.
    • Setting the JVM heap size for a UNIX computer:
      1. Stop the Tomcat server.
      2. Locate the catalina.sh file in the tomcat\bin directory.
      3. Export the following parameter in the catalina.sh file:
        export CATALINA_OPTS="-Xms1536m -Xmx2048m -XX:PermSize=128m -XX:MaxPermSize=256m"
      4. Start the Tomcat server.
  6. Disable applications running on port 12333.
    To prevent port conflicts with port 12333, disable any applications running on port 12333 before you install. After the installation is complete, programs can resume using port 12333.

  7. For improved performance if you are using the BMC Remedy ITSM Suite applications with the BMC Atrium CMDB, run your BMC Remedy AR System server on a private RPC socket with the following values:
    • Windows:
      • RE-RPC-Socket 390698 (for the Reconciliation Engine)
      • Private-RPC-Socket 390698 10 10    (for the BMC Remedy AR System Server)
    • UNIX:
      • RE-RPC-Socket 390698 (for the Reconciliation Engine)
      • Private-RPC-Socket 390698 6 6 (for the AR System server)

        Note

        You can also use port number 390699, but the port numbers for the BMC Remedy Reconciliation Engine and the AR System server must match.

  8. If you have changed the AR TCP port, update the port number details in the Centralized Configuration and the ARSystemInstalledConfiguration.xml.
  9. Before your upgrade BMC Atrium Core, you must identify indexes for which attributes do not exist and delete them. 
    1. Access the OBJSTR:IndexAttribAttributeDef_join form using Mid Tier and search all attribute names.
    2. Copy an attribute name from the search results.
    3. Open the OBJSTR:AttributeClass_join form and paste the attribute name in the Attribute Name field, and click Search. The Attribute Name field must be populated for the copied attribute. Otherwise, delete the index against which the attribute was listed. 
  10. Ensure that the Atrium Plug-in port and Normalization Engine (NE) plug-in port are the same in the following files:
    1. <arsystem install dir>/conf/ar.cfg. In ar.cfg, look for Server-Plugin-Alias entries.
    2. <atriumcore install dir>/cmdb/plugins/shared/pluginsvr_config.xml
    3. <atriumcore install dir>/AtriumCoreInstalledConfigurations.xml
    4.  <atriumcore install dir>/cmdb/plugins/ne/pluginsvr_config.xml

Where to go from here

Next taskProceed to Improving upgrade performance of BMC Atrium Core.
Up to process

If you have finished upgrading the platform, return to the appropriate upgrade process:

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

Comments