The following topics provide information that you can use to prepare your environment for installing BMC Service Resolution 3.5 Service Pack 1:
Verify installation of supported products
Before you install BMC Service Resolution 3.5 Service Pack 1, ensure that you have installed licensed versions of all of the supported products. For more information, see Supported-products-and-versions.
Note
If you have installed Remedy ITSM Service Pack 2 Patch 001 (8.1.02.001), you do need to install the BMC CMDB Extensions, which are available out of the box in this patch.
Install TrueSight Infrastructure Management or ProactiveNet
Before you install BMC Service Resolution 3.5 Service Pack 1, you must first install a supported version of TrueSight Infrastructure Management or ProactiveNet.
For information about installing TrueSight Infrastructure Management or ProactiveNet:
SeeInstallingin the TrueSight Operations Management 11.0 online documentation.
Before installing the TrueSight Infrastructure Management component, you must have installed Remedy Single Sign-On and TrueSight Presentation Server. The TrueSight Operations Management installation documentation describes how to plan for the deployment and to install these components.
SeeInstallingin the ProactiveNet 9.6 online documentation.
Install Remedy ITSM 8.1 or later
Install Remedy ITSM 8.1 or later and ensure that it is integrated with TrueSight Infrastructure Management/ProactiveNet.
Install the BMC Service Resolution 3.5 Service Pack 1 on the Remedy ITSM server. See Installing the service pack on Remedy ITSM server.
Install BMC CMDB Extensions
If you are integrating Infrastructure Management with Atrium CMDB, you must install the BMC CMDB Extensions and components before configuring the TrueSight Infrastructure Management or ProactiveNet Server to integrate with the CMDB. Install BMC CMDB Extensions on the same computer where the Atrium CMDB is installed.
View CMDB Extensions installation procedure with latest version of TrueSight Operations Management
The referenced document [confluencePage:page:tsomd110.Installing the BMC CMDB Extensions to enable integration with Atrium CMDB] was not found.
View CMDB Extensions installation procedure with ProactiveNet 9.6
When you install ProactiveNet CMDB Extensions, the following BMC software is installed:
- BMC Impact Model Designer
- Integration for BMC Remedy Service Desk - AR System
Install ProactiveNet CMDB Extensions on the same computer where BMC Atrium CMDB is installed. In a server group environment, install ProactiveNet CMDB Extensions on all the servers in the server group. Ensure that all servers are added to the group list. For more information about the server group environment, see the online documentation of BMC Remedy Action Request System.
- Before you begin with the installation, ensure that you have administrator privileges on Remedy Action Request System.
As an administrator, ensure that you have the following permissions:
- Administrator
- Incident Config
- Incident Master
- Incident Viewer
- Incident Submitter
- Contact Organization Admin
- Contact Location Admin
- Contact People Admin
- Contact Support Admin
- Config Group Mapping Admin
- Config Categorization Admin
For information about adding permissions, see Adding-roles-and-permissions.
- BMC recommends that you run the Remedy AR System and BMC Atrium Core Heath check before proceeding with the installation.
- Ensure that you enable Administrative Operations on the AR Server. For information about enabling Administrative Operations, see the online documentation of BMC Remedy Action Request System.
- Ensure that the Enable Multiple Assign Groups setting is enabled for all AR Servers. To do this, in AR Server, in the Server Information page, on the Configuration tab, select the Enable Multiple Assign Groups check box.
- Ensure that you increase the timeout to 600 seconds and enable unqualified search in the Server Information page of AR Server.
Ensure that you have installed the following applications on the Remedy Action Request System server:
The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.
Note
For a successful installation, ensure that your system has a minimum of 3 GB of free memory. If this requirement is not met, importing workflows to BMC Atrium CMDB may fail.
- On Linux or Solaris operating system, ensure that the following libraries are present in the /usr/lib folder:
- 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.
- Run setup.exe.
- On the Welcome page, click Next.
- On the license agreement page, click Next.
- On the Directory Selection page, retain the default directory, or click Browse to select a different directory, and click Next.
On the BMC Remedy AR System Server/Atrium CMDB User Inputs page, provide the following details, and click Next.
The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.
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.
In the BMC ProactiveNet Impact Manager User Input Information screen, complete the following fields and click Next.
| |
---|
| Name of the primary ProactiveNet Cell. |
| Host name of the primary ProactiveNet Cell. |
| 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. |
- On the CMDB User permissions information page, select the Deploy IBRSD Workflow check box to enable the integration workflows.
- On the Installation Preview page, click Install.
The installer displays the progress of the installation. - On the Installation Result Summary page, click Next.
- On the Installation Summary page, click View Log to view the installation logs or click Finish to complete the installation.
- Restart Apache Tomcat as described in To restart Apache Tomcat on Microsoft Windows.
Note
- Install the ProactiveNet Extensions by the user using which you installed AR Server, it may be either root or non-root user.
- Ensure that you have writable permission for the ar.conf file.
- Navigate to the Integrations/Atrium_CMDB/CMDB_Extensions<operating system>/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.
Apply executable rights to all the installation files by running the following command:
chmod -R 755 installationDirectoryFolderName
installationDirectoryFolderName is the name of the folder that contains all the installation files.
For example, chmod -R 755 Disk1
- Run setup.bin.
- Follow step 3 through step 10 as described in To install BMC ProactiveNet CMDB Extensions on Microsoft Windows.
- Restart Apache Tomcat as described in To restart Apache Tomcat on Linux/Solaris.
When integrating with an Action Request Server Group, you must install the ProactiveNet CMDB Extensions on:
- The primary administrative server - Installing on the primary administrative server creates the necessary forms, workflow, and data. It also deploys the Impact Model Designer on the primary server.
- Each server that has the reconciliation function enabled - Installing on each server is necessary to install the BPPM Notify ARDBC plugin and iBRSD plugin. For more information, see Configuring-the-Notify-ARDBC-plug-in.
Note
On a Linux computer, to integrate Infrastructure Management 10.0.500 with Remedy ITSM 9.1, before installing the BMC CMDB Extensions, ensure that you have ncurses version 5 library installed. If it is not installed, run the following command to install the package:
yum install libncurses.so.5
When you finish installing the BMC CMDB Extensions, you must restart Apache Tomcat.
Restarting Apache Tomcat on Microsoft Windows | - On a command prompt, type services.msc.
- Right-click Apache Tomcat Tomcat6, and click Restart.
|
Restarting Apache Tomcat on Linux or Solaris | - Navigate to tomcat_home/bin.
- Run the following command to stop Apache Tomcat:
./shutdown.sh
- Run the following command to restart Apache Tomcat:
./startup.sh
|
Publish CIs
If you are using Remedy ITSM 9.1 and TrueSight Presentation Server 10.1 and if you encounter issue when publishing configuration items (CIs), contact BMC Support for the latest hotfix.
Back up Remedy AR System objects
As part of the BMC Service Resolution 3.5 installation, certain Remedy AR System forms, active links, and filters are modified. You must back up all Remedy Action Required System (Remedy AR System) objects before you install BMC Service Resolution 3.5, in case you later need to roll back the installation. You can either set up your system to perform this backup automatically, or you can perform a manual backup.
To manually back up Remedy AR System objects
Log on to Remedy Developer Studio as an administrator, and back up the following modified objects:
- HPD:CFG-Rules
- HPD:Help Desk
- HPD:Help Desk Classic
- HPD:IncidentProcessControl
- INT:BPPMDetails
- INT:OutBoundStaging
- INT:EventBuffering
Create an outage record
To successfully create an outage record, you need the eiframework.jar file.
- If you are using Remedy ITSM 9.0 and later and Oracle as the database and TrueSight Presentation Server 10.1, download this attachment and replace it in the BMC_ProactiveNet_HOME/pw/integrations/eventintegrator folder.
- If you are using ProactiveNet 9.5 SP2, download this attachment, unzip it, and rename it to eiframework.jar. Replace the file in the BMC_ProactiveNet_HOME/pw/integrations/eventintegrator folder.
Disable the filter
If you are using Remedy ITSM 9.1 or later, for the BMC Service Resolution 3.5.01 features to work, ensure that you disable the "BiiARS_HPD:OutBoundStagingForm_INCIDENTINFO!" Filter in Remedy Developer Studio.
Ensure sufficient disk space for installation
Ensure that the default %TEMP% directory has sufficient space for the installation. If not, increase the available space or change the temporary location. (The installer does not use the InstallAnywhere framework and is not affected by the IATEMPDIR system variable.)
Where to go from here
Downloading-the-installation-files