Completing the BMC Remedy AR System upgrade
After you have finished Upgrading BMC Remedy AR System, perform the following postupgrade tasks.
|1.||Set the Java heap size.|
As a starting point, set the Java heap size to a minimum of 16 GB for a medium environment. After upgrading, you should monitor the memory usage to ensure that Java does not run out of memory. For complete recommendations, see Hardware requirements.
|2.||Update Java paths after upgrading.||If you have upgraded to the newer version of Java after upgrading to BMC Remedy Action Request (AR) System and BMC Atrium Core, manually update the Java paths as directed. |
|3.||Enable LDAP plug-ins for SSL connections postupgrade.||(Applicable only if upgrading from a version prior to 9.0) To enable LDAP plug-ins for SSL connections in configured networks after an upgrade, you must add an LDAP certificate to the certificate database for SSL communication.|
|4.||Update the armonitor configuration file for the plugin server.||You must update the armonitor configuration file for the plugin server to troubleshoot issues if the plug-in server runs out of memory.|
|5.||(Optional) Enable Call Home to monitor the upgrade.|
Enable the Call Home functionality to trace the upgrade sequence of plug-ins, tools, and components. This functionality is available after you upgrade BMC Remedy AR System sever. It tracks the sequence of upgrade activities performed by various plugins, tools, and components.
|6.||(Optional) Migrate configurations for the components in the Centralized Configuration||When you upgrade, all configurations in the Centralized Configuration are moved under global level configurations with the out-of-the-box value. Manage these configurations either by using the Server Group Configuration screen of the Remedy Management Console or by using the Configuration utility.|