This documentation applies to the 8.1 version of Remedy ITSM Deployment, which is in "End of Version Support." You will not be able to leave comments.

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

Preparing your operating system and your server before you upgrade BMC Atrium Core

This topic provides the following information:

Preparing for upgrading from any version of BMC Atrium Core

Important

Perform the upgrade during off-peak hours when no major activity (such as running a data exchange or a reconciliation job) is underway on the AR System server. 

  1. Before you upgrade the AR System server, create a backup of your AR System server database.

    The backup preserves your data and lets you restore your previous environment if you encounter errors while upgrading.

  2. Upgrade your AR System server before you upgrade BMC Atrium Core to version 8.1.00. 
  3. Upgrade the AR System server.

    Important

    • If you created functional indexes at the database level of the AR System server, you must first save the information about these indexes and then proceed to remove them before you upgrade the AR System server. You can create the indexes again after you upgrade the AR System server.
    • If you are using AR System server 7.1.00 or earlier, upgrade your AR System server to version 7.5.00 and then upgrade to version 8.1.00. For more information about upgrading to AR System server 7.5.00, see the BMC Remedy Action Request System 7.5.00 Installation Guide.
  4. Fix issues that the AR System server might have encountered.
    Open the arerror.log file and search for issues particularly related to the database and network that might have occurred. Fix these issues before upgrading BMC Atrium Core.
  5. Configure the AR System thread settings before you upgrade BMC Atrium Core.
  6. If you have jobs that are defined against deprecated classes, the jobs do not successfully upgrade and errors might occur. To overcome these errors, delete all the rules defined on deprecated classes.

    Note

    Job definitions are not upgraded automatically, but after your upgrade is complete, you can create new jobs in the BMC Atrium Core Console.

  7. Make sure that you have no classes in a Change Pending state.
    The upgrade stops if there are pending activities.
  8. Depending upon the version you are upgrading from, perform the required actions:

    VersionAction
    You are using a version of BMC Remedy ITSM earlier than 7.0.3 patch 009Create a backup of your database and upgrade to BMC Remedy ITSM 7.0.3 patch 009 or later and then proceed with the upgrade
    You are upgrading from a version earlier than 7.5.00

    Choose a new installation directory when you upgrade.

    Note: The AtriumCore directory must not be below the BMC_AR_SYSTEM_HOME directory. For example, if you used /usr/arsystem/cmdb to install an earlier version, use a different path, like /usr/AtriumCore for the upgrade.
    Additionally, you must remove the BMC Atrium Core libraries in the the PATH environment variable. To do this, you can remove the mid tier location and the old BMC Atrium Core installation directory location from PATH and LD_LIBRARY_PATH.

    You are upgrading from version 7.5.00 or later

    Provide the current installation directory when you upgrade, but make sure that the AtriumCore directory is not under BMC_AR_SYSTEM_HOME. If the AtriumCore directory is under the BMC_AR_SYSTEM_HOME directory, you might encounter the following error in the atriumcore_install_log.txt file:

    LOG EVENT {Description=[SET PROPERTY VALIDATION_ERROR_RESULT],
    Detail=INVALID_INSTALL_DIR_PATH_ATRIUM[String:BMC Atrium Core]]}
    SEVERE,com.bmc.install.product.atriumfoundation.task.
    AtriumFoundationPathValidationTask,
    LOG EVENT {Description=[INVALID_INSTALL_DIR_PATH_ATRIUM
    [String:BMC Atrium Core]],Detail=[INVALID_INSTALL_DIR_PATH_ATRIUM]}
    You used the command-line version Best Practice Conversion Utility (BPCU) before upgrading your applications or server components to version 7.6.04

    The Customization Type of some BMC Atrium CMDB classes might have changed from Unmodified to Custom.

    Set the Customization Type of these BMC Atrium CMDB classes to Unmodified before you upgrade BMC Atrium CMDB. To do this, you must install a utility that converts the custom classes to Unmodified.
    For more information about installing this utility and converting the customization type to Unmodified, see the following comment on the BMC Communities web page: Unsupported BMC Remedy Developer Studio plug-in to Convert Base objects to Custom and Custom objects to Base

Commenting out the entries in the armonitor and ar configuration files

If you are upgrading from BMC Atrium Core 7.5.00, comment out the entries in the ar monitor and ar configuration files.
If you are using a UNIX computer, you must comment out:

  • arcmdbd.sh and arrecond.sh entries in the armonitor.conf file
  • libcmdbconsolefilterapi21.sl and cmdbsvr21.sl entries in the ar.conf file.
    If you are using a Windows computer, you must comment out arcmdbh.exe and arrecond.exe entries in the armonitor.cfg file.

To comment out the arrecond and arcmdbh entries in the armonitor file

  1. Navigate to the following location on the BMC Remedy AR System server:
    • (Windows) AR_install_directory\Conf
    • (UNIX) /etc/arsystem/<server_name>
  2. Open the armonitor.conf file (UNIX) or the armonitor.cfg file (Windows) in a text editor.
  3. In the armonitor.conf file, locate the lines that include arcmdbd.sh and arrecond.sh.
    In the armonitor.cfg file, locate the lines that include arcmdbd.exe and arrecond.exe.
  4. Add the number sign (#) at the start of the line.
  5. Save the file.

To comment out libcmdbconsolefilterapi21.sl and cmdbsvr21 entries in the ar.conf file

  1. Open the ar.conf file.
  2. Locate the lines that include the following:
    • Plugin: /usr/arsystem/norad/cmdb/server/bin/libcmdbconsolefilterapi21.sl
    • Load-Shared-Library: cmdbsvr21.sl
  3. Add the number sign (#) at the start of the line.
  4. Save the file.

Performing a complete health check of AR System server and BMC Atrium CMDB

After you upgrade AR System server, perform a health check of your AR System server and the AR System server database. To do this, you must instantiate the AR System server in the consistency checker mode. The consistency checker mode performs activities like status checks, maintenance, and validation of the AR System server database.
For more information, see  Running the database consistency checker  in BMC Remedy AR System documentation.

After you finish the health check of the AR System server, you must perform a complete health check of BMC Atrium CMDB.

Note

Before you upgrade, you must verify that the class definitions in your data model are correct. Class definitions in your data model are verified when you perform a health check of BMC Atrium CMDB.

To perform a complete health check of AR System server and BMC Atrium CMDB

Manually verify the data model by following the steps in this section:

  1. From the BMC Atrium CMDB Maintenance tool, run the health check.
  2. Examine the arerror.log and cmdbengdebug.log files for any errors about starting the cmdbEngine.
    Search for the string cmdbEngine to find errors. When the cmdbEngine is started, it validates the class definitions. The following example shows the error message that you might view in arerror.log:

    *Mon Dec 11 16:10:18 2006 390600 : The specified super class with given classId is not found. : Class ID: OB005056C00008PlV3RQU3oZAAHO8C, Super Class ID: OB005056C00008F1V3RQd#IYAAD90C (ARERR 120132)*
  3. Perform the following steps to verify that all classes in your data model are active:
    1. In a browser, open the OBJSTR:Class form in Search mode.
    2. Choose View > Advanced Search Bar.
    3. In the Advanced Search Bar at the bottom of the window, specify the following query:

      *'OSStatus' != "Active" OR 'Pending ID' != "0" OR 'System Status*' != "Active" OR 'Record Status' != "Active" OR 'Status' != "Active"*

      If this query returns any rows, it means that those classes were either not correctly created or were not correctly deleted.

    4. Check the classes listed in the result window to investigate the issue.
  4. Perform the following steps to verify that all attributes for the classes are Active.
    1. In a browser, open the Attribute Definitions form in Search mode.
    2. Choose View > Advanced Search Bar.
    3. In the Advanced Search Barat the bottom of the window, specify the following query:

      *'OSStatus' != "Active" OR 'Pending ID' != "0" OR 'Record Status' != "Active"*

      If this query returns any rows, it means that those attributes were either not correctly created or not correctly deleted.

  5. Run cmdbdriver from the server.
    For information, see  cmdbdriver program  in BMC Atrium Core documentation.

    Note

    On a UNIX computer, you might need to open the arcmdbd.sh file and set LD_LIBRARY_PATH to the path where the BMC Atrium CMDB files and directories are installed.

  6. Type the glc command to get the list of classes.
  7. Accept default values for all prompts displayed for this command.
    A list of classes is displayed.

    Note

    If the cmdbdriver program generates an AR 91 RPC call failed error, verify that the cmdbEngine is running. This error might also occur if the class definitions in the your data model are incorrect.

  8. In a browser, open the Application Pending form and make sure that there are no records with Change Pending status.
  9. Perform a clean-up of all the reconciliation jobs and AIE data exchanges that have a pending status, and set the status of AIE data exchanges and reconciliation jobs to Inactive.
  10. Make sure that the ARDBC.Notify plugin is running.

Important

If you find that the ARDBC.Notify plugin is not running, from the ar.conf or the ar.cfg file, set the following parameters to match your environment: Plugin, BMC-ARDBC-NOTIFY-Server-Port, BMC-ARDBC-NOTIFY-Protocol-V1-Encrypt, BMC-ARDBC-NOTIFY-Event-Cache, and BMC-ARDBC-NOTIFY-Verify-Log.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments