Configuring Servers for Communications

  • Article

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

You can use the <EMS> Connector Configuration dialog box to configure Operations Manager 2007 R2 and remote system servers for communications with the Connector. The <EMS> Connector Configuration dialog box has the following tabs for configuring Connector environment servers.

  • <EMS> Server (where <EMS> is a placeholder for the specific remote system name)

  • Operations Manager

<EMS> Server Configuration

You can use the <EMS> Server tab of the <EMS> Connector Configuration dialog box to configure remote system servers for communications with the Connector.

The <EMS> Server tab has the following sections and elements.

Enterprise Management System (EMS) Server Communication Order

  • Move Up
    Moves the selected server name up in the list.
  • Move Down
    Moves the selected server name down in the list.
  • Remove Server
    Removes the selected server name from the list.
  • Add Server
    Adds to the list a remote system server that has an Interop Provider installed. Polling and other Connector communications are first attempted with the top server on the list. The communication attempts continue down the list and loop through the list according to the server settings in the lower section of the tab. Server names must be derived from other sources.

Warning

Each remote system server in this list must have an Interop Provider installed or communications attempts will fail.

Warning

Do not use the name localhost; spell out the host name.

Settings in the following sections of the tab apply or appear for the selected server.

Web Services for Management (WS-Man) Server Credentials

  • User name
    For Windows operating systems, the user must be the local administrator the for the remote system environment on the server that is being added. For UNIX or Linux, the account can be any user with appropriate permissions for the remote system environment.

  • Password
    Enter the password for the designated user for Web services on the remote system server that is being added.

    Important

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

  • WS-Man port
    TCP port 1270 is set by default and cannot be changed.

  • Validate WS-Man
    Click Validate WS-Man to check the connection with the EMS Server.

    The Connector service and the Operations console must reside on the same server, and the certificate for the EMS Provider must be current. If the Connector service is on another server, or if you have modified the EMS and have not imported its new certificate, Validate WS-Man will not validate the connection.

    Note

    Only the first EMS server in the list is validated. Selecting a different server will have no effect on validation.

The following are the sections of the <EMS> Server tab that have unique sets of elements for each Connector.

OVO Server

  • Polling interval (seconds)
    Set a value, in seconds, to determine the time between Interop Provider polling of the remote system server for acknowledgements or updated events. Default=30
  • Receive updates from Operations Manager
    Select this check box to enable the forwarding of updated Operations Manager 2007 R2 alerts to HP Operations Manager.
  • Send updates to Operations Manager
    Select this check box to enable the forwarding of updated remote system events to Operations Manager 2007 R2.
  • Convert host name to IP address
    Select this check box to automatically convert the host name entered in the list to an IP address.

TEC Server Settings

  • Polling interval (seconds)
    Set a value, in seconds, to determine the time between Interop Provider polling of the remote system server for acknowledgements or updated events. Default=30
  • Server listening port
    Set to 0 for to use the Port Mapper for TEC on a UNIX platform. Otherwise set as noted by the TEC administrator, typically 5529 for TEC on Windows operating systems. Default=0
  • Receive updates from Operations Manager
    Select this check box to enable the forwarding of updated Operations Manager 2007 R2 alerts to IBM Tivoli Console.
  • Send updates to Operations Manager
    Select this check box to enable the forwarding of updated remote system events to Operations Manager 2007 R2.

EMS Server with the Universal Connector

  • Polling interval (seconds)
    Set a value, in seconds, to determine the time between Interop Provider polling of the remote system server for acknowledgements or updated events. Default=30

  • File format for provider
    Select the drop down value of XML for forwarding alerts as XML files. Select EVT for forwarding alerts as text properties files. Default=XML

    Note

    Alerts forwarded to the Interop Provider on Windows remote systems are validated for XML format, alerts forwarded to the Interop Provider on UNIX remote systems are validated for EVT text format. For more information about Universal Connector alert messaging formats, see Using the Universal Connector.

  • Receive updates from Operations Manager
    Select this check box to enable the forwarding of updated Operations Manager 2007 R2 alerts to the active remote system.
  • Send updates to Operations Manager
    Select this check box to enable the forwarding of updated remote system events to Operations Manager 2007 R2.

Remedy Settings

  • Password
    Enter the password for the user.

    Important

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

  • Authentication
    If a credentials authentication system is enabled for Remedy ARS, enter the appropriate string for authentication.
  • Host name
    This field contains the server name for the computer on which the BMC Remedy ARS is installed.

Remedy server settings

  • Polling interval (seconds)
    Set a value, in seconds, to determine the time between Interop Provider polling of the remote system server for acknowledgements or updated events. Default=30
  • Receive updates from Operations Manager
    Select this check box to enable the forwarding of updated Operations Manager 2007 R2 alerts to IBM Tivoli Console.
  • Send updates to Operations Manager
    Select this check box to enable the forwarding of updated remote system events to Operations Manager 2007 R2.

Operations Manager Server Configuration

You can use the Operations Manager tab of the Connector Configuration dialog box to configure the Operations Manager 2007 R2 root management server (RMS) that communicates with the Connector. Because one Operations Manager 2007 R2 management group can have only one RMS, there can be no other Connector RMS to add to the list. Use this list to reconfigure communications when an Operations Manager 2007 R2 management group has been reconfigured with a new RMS.

Warning

Listing an Operations Manager 2007 R2 RMS of a different management group causes forwarding of alerts from a different Operations Manager 2007 R2 database.

The Operations Manager tab has the following sections and elements.

Operations Manager server communication order

  • Move Up
    Moves the selected server name up in the list.
  • Move Down
    Moves the selected server name down in the list.
  • Remove Server
    Removes the selected server name from the list.

  • Add Server
    Adds an Operations Manager 2007 R2 server that communicates with the Connector. Polling and other Connector communications are first attempted with the top server on the list. The communication attempts continue down the list and loop through the list according to the server settings in the lower section of this Operations Manager tab. Server names must be derived from other sources.

    Warning

    Do not use the name localhost; spell out the host name or use an IP address. Only Operations Manager 2007 R2 root management servers (RMSs) can communicate with servers of remote systems.

Settings in the following section of the tab apply or appear for the selected server.

Operations Manager Server Settings

  • Polling interval (seconds)
    Set the number of seconds between polling for new and updated Operations Manager 2007 R2 alerts. Default=30

  • Forward historical alerts (hours old)
    Set the number of hours to go back and look for alerts to be sent to the remote system. Default = 0 (indicating that no historical alerts are sent upon starting or restarting the Connector service)

    Warning

    If the Connector service is turned off and turned back on while the Forward Historical alerts setting is 0, all alerts that occur when the service is inactive will not be forwarded to the remote system.

  • Maximum field size
    Set the maximum number of characters that can be sent as data for each field. Default=2000
  • Maximum delivery attempts
    Set the number of attempts to send Operations Manager 2007 R2 alerts if transmission fails. Default=5 (Set to 0 for infinite.)
  • Number of polls to wait for response
    Set the number of polls to hold an alert in cache. Multiply the Server polling interval by the Number of polls to wait for total cache holding period. For example, default settings hold an alert in cache for five minutes. Default=10
  • Send updates for closed alerts only
    Select this check box to forward alert updates to the remote system server only when Operations Manager 2007 R2 alert status is set to closed.