Installing Connector Components for Remote Systems

  • Article

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

This section provides instructions for installing the Operations Manager 2007 R2 Connector component for all supported remote systems. The Interop Provider is the only component for installation in a Windows remote system environment. In a UNIX remote system environment, an additional component called the Interop Core is installed along with the Interop Provider.

If multiple Connectors are installed in one Operations Manager 2007 R2 environment to connect to various remote systems, an Interop Provider must be installed independently on each remote system.

Important

The scenario of multiple Remedy Interop Providers for a single Remedy system is not supported. If Remedy Connectors are installed on multiple Operations Manager 2007 R2 servers to communicate with a Remedy system, communication must be through a single Provider installation.

Important

For installation of the Interop Provider for a remote system in a Windows-based environment, the user account must have local admin privileges for the server on which the Interop Provider is installed. For installation of the Interop Provider for a remote system in a UNIX or Linux environment, the user account must have root privileges for the given remote system.

To install the Interop Provider on Windows-based computers

  1. Log on with the privilege level necessary for installing in the given remote system environment, and then access and run the SciProviderSetup.msi file to begin the Interop Provider Setup Wizard. On the Welcome page, click Next.

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

  3. The Select Provider page lists the Interop Providers that are supported by the Operations Manager 2007 R2 Connectors. By default, the Interop Universal Provider is selected. Select the Interop Provider that you want to install, and then click Next.

  4. On the Custom Setup page, ensure that the Interop Provider for the Connector you are installing is selected. In all cases the Universal Connector Interop Provider component is also available for installation at the same time. After selections are completed, click Next.

  5. Click Next on the Ready to install Microsoft Operations Manager 2007 Interop Providers page to begin installing the Interop Provider. A progress bar is displayed during the installation.

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

    Note

    For Interop Provider installations for the BMC Remedy ARS Connector, a system reboot is required after installation.

Important

If the Interop Provider is installed after the Connector Service is installed and started, the Interop Provider install overwrites the configuration values that are sent by the Connector Service. For example, the File Format for Provider value that is set in the Universal Connector Configuration dialog box is set to the Interop Provider installation default value of “.evt”. If the Interop Provider is installed after the Connector Service is installed, stop and restart the Connector Service after the Interop Provider installation.

To uninstall the Interop Provider on Windows-based computers

  1. From the Start menu, click Control Panel, and open Add or Remove Programs.

  2. Select System Center Operations Manager 2007 Interop Provider, and then click Remove.

How to Install the Interop Provider on UNIX or Linux Systems

Installation of the Interop Provider component for a supported remote system that is deployed on a UNIX platform requires two installation pieces. First, the Interop Core must be installed and then the Interop Provider is installed. There is a unique pair of packages of the Interop Core and Interop Provider for each supported UNIX or Linux platform and supported remote system.

The following are the UNIX and Linux installation packages that are on the Operations Manager 2007 R2 Connector media. Under each supported operating-system processor-architecture combination, the Interop Core package file is listed, followed by the Interop Provider packages that are available for that platform. The Interop Provider packages are identified by the “ovo”, “tec”, or “unv” designation in the filename.

  • IBM AIX 5L 5.3, Technology Level 6, SP5 (PowerPC)

    scx-<build-number>.aix.5.ppc.lpp.gz (Interop Core package)

scinterop-<build-number>.aix.5.3.ppc-tec.lpp.gz

scinterop-<build-number>.aix.5.3.ppc-unv.lpp.gz

  • HP-UX 11i v2 (IA64)

    scx-<build-number>.hpux.11iv2.ia64.depot.Z (Interop Core package)

scinterop-<build-number>.hpux.11iv2.ia64-ovo.depot.Z

scinterop-<build-number>.hpux.11iv2.ia64-unv.depot.Z

  • HP-UX 11i v2 (PA-RISC)

    scx-<build-number>.hpux.11iv2.parisc.depot.Z (Interop Core package)

scinterop-<build-number>.hpux.11iv2.parisc-ovo.depot.Z

scinterop-<build-number>.hpux.11iv2.parisc-unv.depot.Z

  • HP-UX 11i v3 (IA64)

    scx-<build-number>.hpux.11iv3.ia64.depot.Z (Interop Core package)

scinterop-<build-number>.hpux.11iv3.ia64-ovo.depot.Z

scinterop-<build-number>.hpux.11iv3.ia64-unv.depot.Z

  • HP-UX 11i v3 (PA-RISC)

    scx-<build-number>.hpux.11iv3.parisc.depot.Z (Interop Core package)

scinterop-<build-number>.hpux.11iv3.parisc-ovo.depot.Z

scinterop-<build-number>.hpux.11iv3.parisc-unv.depot.Z

  • Solaris 10 (SPARC)

    scx-<build-number>.solaris.10.sparc.pkg.gz (Interop Core package)

scinterop-<build-number>.solaris.10.sparc-ovo.pkg.gz

scinterop-<build-number>.solaris.10.sparc-tec.pkg.gz

scinterop-<build-number>.solaris.10.sparc-unv.pkg.gz

  • Red Hat Enterprise Linux Server release 5.1 (Tikanaga)

    scx-<build-number>.rhel.5.x86.rpm (Interop Core package)

MSFTscinteropUnv-<build-number>.rhel.5.x86.rpm

  • SUSE Linux Enterprise Server 10 SP1 (i586)

    scx-<build-number>.sles.10.x86.rpm (Interop Core package)

MSFTscinteropUnv-<build-number>.suse.10.x86.rpm

After selecting the appropriate package files for installation, copy the files to the /tmp directory on the UNIX platform. After the package files are copied to the /tmp directory, there are two more steps for installation with each package.

  1. Uncompress or unzip the package file.

  2. Unpack and install files from the package.

The following procedures show the commands for performing these steps on each supported operating system. All samples use the Universal Connector packages for the examples. To install a Connector other than the example provided, replace the string “Unv” with the following case specific identities for the appropriate Connectors:

“Ovo”   for HP Operation Manager Connector (formerly HP OpenView Operations)

“Tec”    for IBM Tivoli Enterprise Console Connector

The last command in each case is the Interop Provider uninstall command.

IBM AIX 5L 5.3, Technology Level 6, SP5 (PowerPC)

  1. To unzip, unpack, and install the Interop Core:

    gzip -d /tmp/scx-<build-number>.aix.5.pcc.lpp.gz

installp -X -d /tmp/scx-<build-number>.aix.5.ppc.lpp scx.rte

  2. To unzip, unpack, and install the Interop Provider:

    gzip –d /tmp/scinterop-<build-number>.aix.5.3.pcc-unv.lpp.gz

installp -X -d /tmp/scinterop-<build-number>.aix.5.3.ppc-unv.lpp MSFTscinteropUnv.rte

  3. To uninstall:

    installp –u MSFTscinteropUnv.rte

installp –u scx.rte

HP-UX 11i v3 (IA64)

  1. To unzip, unpack, and install the Interop Core:

    uncompress /tmp/scx-<build-number>.hpux.11iv3.ia64.depot.Z

swinstall -s /tmp/scx-<build-number>.hpux.11iv3.ia64.depot scx

  2. To unzip, unpack, and install the Interop Provider:

    uncompress /tmp/scinterop-<build-number>.hpux.11iv3.ia64-unv.depot.Z

swinstall -s /tmp/scinterop-<build-number>.hpux.11iv3.ia64-unv.depot scx

  3. To uninstall:

    swremove MSFTscinteropUnv

swremove scx

HP-UX 11i v3 (PA-RISC)

  1. To unzip, unpack, and install the Interop Core:

    uncompress /tmp/scx-<build-number>.hpux.11iv3.parisc.depot.Z

swinstall -s /tmp/scx-<build-number>.hpux.11iv3.parisc.depot scx

  2. To unzip, unpack, and install the Interop Provider:

    uncompress /tmp/scinterop-<build-number>.hpux.11iv3.parisc-unv.depot.Z

swinstall -s /tmp/scinterop-<build-number>.hpux.11iv3.parisc-unv.depot –x ask=true MSFTscinteropUnv

  3. To uninstall:

    swremove MSFTscinteropUnv

swremove scx

Solaris 10 (SPARC)

  1. To unzip, unpack, and install the Interop Core:

    gzip –d /tmp/scx-<build-number>.solaris.10.sparc.pkg.gz

pkgadd -d /tmp/scx-<build-number>.solaris.10.sparc.pkg MSFTscx

  2. To unzip, unpack, and install the Interop Provider:

    gzip –d /tmp/scinterop-<build-number>.solaris.10.sparc-unv.pkg.gz

pkgadd -d /tmp/scinterop-<build-number>.solaris.10.sparc-unv.pkg MSFTscinteropUnv

  3. To uninstall:

    pkgrm MSFTscinteropUnv

pkgrm MSFTscx

Red Hat Enterprise Linux Server release 5.1 (Tikanaga)

  1. To install the Interop Core:

    rpm -i scx-<build number>.rhel.5.x86.rpm

  2. To install the Interop Provider:

    rpm –i MSFTscinteropUnv-<build number>.rhel.5.x86.rpm

  3. To uninstall:

    rpm –e MSFTscinteropUnv

rpm –e scx

SUSE Linux Enterprise Server 10 SP1 (i586)

  1. To install the Interop Core:

    rpm -i scx-<build number>.sles.10.x86.rpm

  2. To install the Interop Provider:

    rpm –i MSFTscinteropUnv-<build number>.suse.10.x86.rpm

  3. To uninstall:

    rpm –e MSFTscinteropUnv

rpm –e scx

Note

When the Interop Provider installation is complete on UNIX or Linux, the Interop Provider is running.