Installing Connector Components for Operations Manager 2007 R2

Applies To: Operations Manager 2007 R2, Operations Manager 2007 SP1

This section provides instructions for installing Operations Manager 2007 R2 Connector components in the Operations Manager 2007 R2 environment. When both the Connector Service and the Connector Configuration UI components are installed at the same time, the installation must take place on a server on which an Operations Manager 2007 R2 console is installed. That is because the Connector Configuration UI installations are integrated into the Operations Manager 2007 R2 Operations console. If the Connector Configuration UI component is installed separately, the Connector Service component can be installed on any computer with a supported configuration in the domain or in a trusted domain of the Operations Manager 2007 R2 root management server (RMS).

For information about a command-line silent installation, see the end of the To Install Operations Manager 2007 Connector Components section later in this topic.

For the first instance of a Connector service installation on a computer, the Custom Setup page appears after the Welcome and End-User License Agreement pages. By default all components for all Connectors are set to Entire feature will be unavailable. Select the Connectors and components you want to install.

When there is at least one Connector service installed on the computer and you run the installation, the Change, repair, or remove installation page appears after the Welcome page. The Remove button removes all Connectors that are currently installed for the Operations Manager 2007 R2 management group. The Repair button is not enabled for this release. The Change button opens the Custom Setup page with all currently installed Connectors set to Entire feature will be installed on local hard drive. Leave all installed Connectors that you want to keep set to Entire feature will be installed on local hard drive, and also set any other Connector that you want to install to Entire feature will be installed on local hard drive.

To install Operations Manager 2007 Connector components

1. Log in as Administrator or with appropriate permissions, then access and run the SciConnectorSetup_x86.msi file or the SciConnectorSetup_x64.msi file to start the Operations Manager 2007 R2 Connector installer.

   Use the SciConnectorSetup_x86.msi file for computers that are 32-bit systems. Use the SciConnectorSetup_x64.msi file for computers that are non-Itanium 64-bit systems.

   Important

   A user account with the following permissions is necessary for installing Connectors in the Operations Manager 2007 R2 environment.

   • The account must have local admin privileges on the local system and on the local security policies. The account must include granting the logon as a service privilege.

   • The account must have Operations Manager 2007 R2 administrator privileges.

   • The account must have SQL DBO privileges for all databases involved.

   • A domain account with the privileges noted earlier in this topic is necessary when components or functionality are on different systems, such as deployment of High Availability Connectors.

   On the Welcome page, click Next.

2. On the End User License Agreement page, read the information carefully, click I agree, and then click Next to continue.

3. The Custom Setup page shows the selection tree for Connectors and their components. By default, all remote system Connectors and all their components are set to Entire feature will be unavailable. To enable a Connector, click the down arrow next to the Connector name and select to the Connector that you want to install, and select Entire feature will be installed on local hard drive.

   You can set the Connector Configuration UI component to Entire feature will be unavailable and install it later on a different Operations Manager 2007 R2 server. Make sure that the Connector Configuration UI component is installed on a server on which the Operations Manager 2007 R2 console is installed.

   After selecting Connectors to install, the currently selected Connector’s installation location appears in the Installation folder box. Click Browse to make changes.

   Important

   Management Packs for each installed Connector are imported into the Operations Manager 2007 R2 RMS when the Connector Configuration wizard runs. The first instance of a Connector deployment imports the Connectors common library management pack, which is a parent management pack for the individual specific remote system management packs. The specific remote system management packs are imported at each Connector deployment. For more information about Connector management packs, see the Connectors Management Pack Guide for Operations Manager 2007 R2.

   Important

   You can select more than one remote system Connector to install in the same installation session. For information about configuring alert forwarding subscriptions when more than one remote system Connector is installed in an Operations Manager 2007 R2 management group, see Using the Operations Manager 2007 R2 Product Connector Subscription Wizard.

   Click Next after you have set the Connectors and components that you are going to install.

4. On the SQL Server Configuration page, provide the following information:

   • Server Name: An instance of SQL Server within the domain or within a trusted domain of the Operations Manager 2007 R2 RMS.

   • Instance Name (required only for named instances): The name of the instance of a database on the designated instance of a SQL Server. This database name can be the same name as the server and is an optional entry

   • Database Name: Enter a name for the database that you want to be created for Operations Manager 2007 R2 Connectors. There is only one Connectors database for all Connectors in one Operations Manager 2007 R2 management group. Any instances of additional Connectors that are installed in the same Operations Manager 2007 R2 management group for High Availability functionality also use this same database. If any Connector has already been installed, the Connector SQL database already exists. If you do not change the entry, by default a local SQL database named SCInterop is created.

   • SQL Server Port: The default entry is 1433.

   Click Next to continue.

5. On the Configure Connector Service Login and High Availability page, provide the following information:

   • User name: By default this shows the account that is running the Windows Installer. This account must have System Center Data Access and System Center Management Configuration permissions for the Connector management group.

   • Password: The password for the above account.

   • Domain: By default the domain for the computer on which you are installing the Connector Service is displayed. The computer must be in the domain or in a trusted domain of the Operations Manager 2007 R2 RMS.

   • High Availability: Use this check box to designate the installation as a Connector for High Availability installation. For more information about the High Availability feature, see Configuring High Availability

   Click Next to continue.

6. The Ready to install System Center Operations Manager 2007 R2 Connector page appears if the service log-on information is valid. Click Install to continue.

7. The Installing page displays installation progress until the installation of all selected components is complete.

To configure Operations Manager 2007 Connectors

1. After installation of the Connector service is complete, the Configure Connectors page of the Connector Configuration wizard appears. Running the Connector Configuration wizard at installation is optional. However, the Connector Configuration wizard must be run before the Connector service is started. If you do not run the Connector Configuration wizard at installation time, the icon for running the wizard appears on the Start menu of the system where the Connector service was installed.

   The Configure Connectors page has a button for each supported Connector. To configure a Connector that has been installed, click the button for that Connector. The Configure Connectors page returns after each configuration. If multiple Connectors were installed, click each Connector until all installed Connectors are configured.

   When all Connectors are completed, or to skip configuring Connectors, click Done.

2. When the OpsMgr Connector for <EMS> Connector Configuration dialog box appears, provide the following information.

   For the Server names section:

   • Operations Manager server: The name of the Operations Manager 2007 R2 management group RMS.

   • <EMS> provider: The name of the remote system server on which the Interop Provider component will be installed.

     Important

     Do not use an IP address as a server name. Doing so will cause a certificate name mismatch.

   For the WS-Man server credentials section:

   • User name: A user from the remote system server with adequate permissions for Web Services for Management (WS-Man). For Windows-based computers, both local administrator and domain accounts are supported. The domain account must be in the administrators group for the remote system. For UNIX-based computers, the user can be any account with appropriate permissions for the remote system environment.

   • Password: The password for the user.

   Important

   Both Username and Password must be in the range of standard ASCII characters (32-127).

   For configuration of the BMC Remedy ARS Connector, this dialog box also contains a Remedy server credentials section. In this section, provide the following information:

   • Server version: Select V71 or V63 from the Server version list according to the ARS version being used.

   • User name: This is the Remedy user as specified in Appendix A - The BMC Remedy ARS Connector as opsmgr.

   • Password: The password for the user.

   • Authentication: If a credentials authentication system is enabled for Remedy ARS, enter the appropriate string for authentication. If an authentication system is not implemented, leave this field blank.

   • Host name: The server name for the computer on which the BMC Remedy ARS is installed.

   Important

   Both Username and Password must be in the range of standard ASCII characters (32-127).

   Click Configure to continue.

3. The Connector Certificate Retrieval and Installation page appears when configuration of the Connector service is complete.

   The Connector requires the use of certificates to validate the authenticity of the server on which the Interop Provider is running. The Connector does not work until the certificate has been transferred and correctly imported to the server on which Connector is running from the server on which the Interop Provider is running. During the Interop Provider installation, a self-signed certificate is generated and stored in the Interop Provider installation directory. The Connector Certificate Retrieval and Installation wizard retrieves the certificate and automatically installs it on the server on which the Connector is running. Installing the Connector certificate at installation is optional. However, the Connector certificate must be installed on the server on which the Connector is running before the Connector service is started. If you do not install the Interop Provider certificate, the Connector cannot communicate with the server on which the Interop Provider is running.

   Note

   The automatic installation process may be insecure. Verify that the certificate thumbprint returned by the wizard is genuine if you choose to proceed with the automatic import process.

   Note

   The most secure way to transfer the Interop Provider certificate is by manually using physical medium. See Installing a Connector Certificate with the Command-Line Installation.

4. By default, automatic installation is selected. Click Next to continue.

5. When the Connector certificate is installed, click OK to continue.

   Note

   The Interop Provider certificate is valid for three years from the date of installation of the Interop Provider. To replace an expired certificate, you must uninstall the Interop Provider, delete the certificate on the Interop Provider computer, reinstall the Interop Provider service, and then manually install the new certificate on the Connector. See Installing a Connector Certificate with the Command-Line Installation for instructions on how to install the new certificate.

6. Click Finish on the Completed page to exit the setup wizard.

To uninstall the Connector

1. When any Operations Manager 2007 R2 Connectors have been installed on a computer, log on as Administrator to uninstall the Connector. Use the Windows Add or Remove Programs function, or use the Connector installation files, SciConnectorSetup_x86.msi or SciConnectorSetup_x64.msi, to start the Operations Manager 2007 R2 Connectors installation wizard.

2. When one or more Connectors are installed, the installation wizard displays the Change, repair, or remove installation page.

   Click Remove to begin removing all installed Connectors.

   Click Change to remove specific components or specific Connectors.

Installing a Connector with the Command-Line Silent Installation

Use the command-line properties to run the Connector setup .msi file with the Microsoft Windows Installer. This enables unmonitored and scripted installations.

When you run a silent installation on a Windows Server 2008-based server, you must first advertise the application to all user accounts from a non-elevated command prompt. The following code example is the syntax for advertising the application on a Windows Server 2008-based server.

msiexec /jm <.msi-filename>

• <.msi-filename>
  SciConnectorSetup_x86.msi or SciConnectorSetup_x64.msi

The following code example is the syntax for the silent installation command.

msiexec /i <.msi-filename> /qn /l*v connectorinstall.log <REQUIRED-PROPERTIES><REMEDY-PROPERTIES><OPTIONAL-PROPERTIES>

• <.msi-filename>
  SciConnectorSetup_x86.msi or SciConnectorSetup_x64.msi

• <REQUIRED-PROPERTIES>

  • SERVICE_USER="<user-name>" - account used to set up the Connector service.

  • SERVICE_DOMAIN="<domain>" – the domain for the computer on which you are installing the Connector service.

  • SERVICE_PASSWORD=”<password>” – password for the account used to set up the Connector service.

  • SQLSERVER=”<SQL-server-name>” – name of the instance of SQL Server that will hold the Connector database.

  • OPSMGRSERVER=”<OpsMgr-server-name>” – name of the Operations Manager 2007 R2 RMS.

  • PROVIDERSERVER=”<Provider-server-name>” – name of the remote provider server.

  • WSMANUSERNAME=”<WS-Man-user-name>” – account from the remote system to be used for communications.

  • WSMANUSERPASSWORD=”<WS-Man-password>” – password for the remote system communications account.

  • ADDLOCAL=”<Connector>,<ConnectorService>,<ConnectorUI>” – one of the following sets of four properties that identify which Connector to install.

    • OVO,OVOService,OVOUI
      

    • TEC,TECService,TECUI
      

    • Universal,UniversalService,UniversalUI
      

    • Remedy,RemedyService,RemedyUI
      

• <REMEDY-PROPERTIES>

  • REMEDYVERSION="<Remedy-server-version>" – enumerated type specifying the Remedy ARS server version being used. Accepted values are V63 or V71.

  • REMEDYUSERNAME="<Remedy-user-name>" – Remedy ARS remote system communications account as specified in the Operations Manager 2007 R2 console.

  • REMEDYPASSWORD="<Remedy-password>" - password for the Remedy ARS remote system communications account.

  • REMEDYAUTH=”<string>” - if a credentials authentication system has been enabled on the Remedy ARS server, enter the appropriate authentication string. If an authentication system has not been implemented, check with your Remedy system administrator before using this property.

  • REMEDYSERVER="<Remedy-server-name>" – the server name for the computer on which Remedy ARS is installed.

• <OPTIONAL-PROPERTIES>

  • SQLINSTANCE=”<database-instance>” – name of the instance of the database to use. The default instance is used by default.

  • DBNAME=”<database-name>” – name to use for the Connector database. If not specified, SCInterop is used.

  • EMSPORT=”<port-value >” – For TEC Connector only, sets the server listening port. The default value is “0”, which designates using the Port Mapper on UNIX platforms. A TEC administrator can provide a port value for TEC on a Windows operating system, which is typically “5529”.

  • SERVICE_HA=”1” – this property must be set when you are installing a High Availability Connector.

The following is an example of a silent installation command for a Remedy ARS server on an x86 Windows-based system.

msiexec /qn /i SciConnectorSetup_x86.msi /l*v connector.log ADDLOCAL="Remedy,RemedyService,RemedyUI" SERVICE_USER="user-name" SERVICE_DOMAIN="domain" SERVICE_PASSWORD="password" SQLSERVER="SQL-server-name" OPSMGRSERVER="OpsMgr-server-name" PROVIDERSERVER="Provider-server-name" EMSPORT="port-value" WSMANUSERNAME="WS-Man-user-name" WSMANUSERPASSWORD="WS-Man-password" REMEDYVERSION="Remedy-version" REMEDYUSERNAME="Remedy-user-name" REMEDYPASSWORD="Remedy-password" REMEDYAUTH="string" REMEDYSERVER="Remedy-server-name"

If Authorization is not configured on your Remedy ARS server, check with your Remedy system administrator before using the REMEDYAUTH parameter.

The following is an example of a silent installation command for a High Availability Universal Connector on an x86 Windows-based system.

msiexec /i SciConnectorSetup_x86.msi /qn /l*v connectorinstall.log SERVICE_USER="user-name" SERVICE_DOMAIN="domain" SERVICE_PASSWORD=”<password>” SQLSERVER=”<SQL-server-name>” OPSMGRSERVER=”<OpsMgr-server-name>” PROVIDERSERVER=”<Provider-server-name>” WSMANUSERNAME=”<WS-Man-user-name>” WSMANUSERPASSWORD=”<WS-Man-password>” ADDLOCAL=”Universal,UniversalService,UniversalUI” SERVICE_HA=”1”

Installing a Certificate with the Command-Line Installation

Use the command-line application, Scicert.exe, to install the Interop Provider certificate on the Connector server. Installing the Interop Provider certificate enables secure communication between the server on which the Interop Provider is running and the server on which the Connector is running. The file, Scicert.exe, is stored in the Operations Manager 2007 R2 Connector installation directory. The following code example is the syntax for the certificate installation command.

scicert <host> <user> <password> <service name> [silent][test]

• <REQUIRED-PROPERTIES>

  • <host> – the location where the Interop Provider certificate is installed.

  • <user> – the account used for WS-Man communication.

  • <password> – the password for the account used for WS-Man communication.

  • <service name> – enter the name of the service in the form “OpsMgr Universal Connector”.

• <OPTIONAL-PROPERTIES>

  • <silent> – if entered, no command output will be displayed.

  • <test> – if entered, scicert will verify the connection. It will not install a certificate.

Installing for High Availability

The High Availability feature of the Operations Manager 2007 R2 Connector enables failover to secondary Connectors without loss of data. High Availability supports server or communications failure among servers that are configured for High Availability. Data from higher-level failure, such as Operations Manager 2007 R2 root management server (RMS) or total management group failure cannot be recovered with the High Availability feature.

High Availability is enabled by installing the Connector on each server to be configured for High Availability. There is a High Availability check box on the Configure Connector Service Login and High Availability page of the Connector installation wizard that designates an installation as a High Availability installation.

After installation of all Connectors in a High Availability group, use the High Availability tab of the <EMS> Connector Configuration dialog box to configure the failover communications order for those Connectors. For more information about using the High Availability tab of the <EMS> Connector Configuration dialog box, see Configuring High Availability.

On the High Availability page of the <EMS> Connector Configuration dialog box, you can see all the Connectors configured for High Availability. The first Connector is the Active Connector; all other Connectors are in a Passive/Offline state. Passive Connectors are standing by in case the Active Connector fails.