Page tree
Skip to end of metadata
Go to start of metadata

Perform these tasks on the BMC Remedy AR System Server if the Integration for BMC Remedy Service Desk - AR System module is already installed.

Before you begin

  • Back up the data for the version that you are upgrading from.
  • If you are using BMC Impact Integration for Remedy AR System (BMC II for AR System), you must uninstall it before upgrading to this version of Integration for BMC Remedy Service Desk .

Note

BMC II for Remedy AR System is the earlier integration product that provided integration between a BMC Impact Solutions cell and the BMC Remedy AR System server. It populates a form on the BMC Remedy AR System server but does not create incidents in BMC Remedy Service Desk.

  • When you upgrade from Integration for BMC Remedy Service Desk 7.1.00 or Integration for BMC Remedy Service Desk 7.2.00, the installer moves the Integration for BMC Remedy Service Desk files to the installationDirectory/integrations/ibrsd directory and migrates all internal folder structures and configurations. Although the upgrade procedure migrates the earlier configurations, back up your installationDirectory/server/ibrsd folder as a precaution.
  • When you upgrade BMC ProactiveNet CMDB extensions, all 'Server-Plugin-Alias' entries in the ar.cfg file located at the BMCARSystem\Conf directory are removed. These alias entries are necessary to have the ITSM stack functional. Therefore, you must take a backup of the ar.cfg file before running the upgrade and merge the contents of the backed up ar.cfg file with the new ar.cfg file post-upgrade. 

To upgrade the Integration for BMC Remedy Service Desk - AR System module

  1. Navigate to the Integrations\Atrium_CMDB\CMDB_Extensions\Windows\Disk1 directory in the installation package.
    • If you have an installation DVD, copy the contents to a directory with write permission, and navigate to the directory.
    • If you have downloaded the installation files, navigate to the directory.
  2. Run setup.exe.
  3. On the Welcome page, click Next.
  4. On the license agreement page, click Next.
  5. On the Directory Selection page, retain the default directory, or click Browse to select a different directory, and click Next.
  6. On the BMC Remedy AR System Server/Atrium CMDB User Inputs page, provide the following details, and click Next.


  7. On the SIM NOTIFY Plugin User Inputs page, enter the port number on which the SIM NOTIFY server is listening for incoming connections of clients (for example, BMC ProactiveNet Publishing Server) that subscribe for notifications. The default port number is 1840.

    Note

    This port is different from the AR Server port. Configure your firewall to allow this port so that BMC ProactiveNet Publishing Server can connect to it.

  8. In the BMC ProactiveNet Impact Manager User Input Information screen, complete the following fields and click Next.

    Field

    Description

    Impact Manager Name

    Name of the primary ProactiveNet Cell.

    Impact Manager Host Name

    Host name of the primary ProactiveNet Cell.

    Impact Manager Port

    Port number of the ProactiveNet Cell. The default port is 1828.

    Secondary Impact Manager Name

    Name of the secondary ProactiveNet Cell.

    Secondary Impact Manager Port

    Port number of the secondary ProactiveNet Cell.

    Impact Manager Encryption Key

    Encryption key of the ProactiveNet Cell. The default encryption key is mc.

  9. On the CMDB User permissions information page, select the Deploy IBRSD Workflow check box to enable the integration workflows.
  10. On the Installation Preview page, click Install.
    The installer displays the progress of the installation.
  11. On the Installation Result Summary page, click Next.
  12.  On the Installation Summary page, click View Log to view the installation logs or click Finish to complete the installation.
  13. Restart Apache Tomcat as described in To restart Apache Tomcat on Microsoft Windows.

After successfully upgrading BMC ProactiveNet CMDB Extensions, start the AR System server.