HP Operations Manager for Windows

Configuration Examples


NoteNOTE:
Keys used in the examples below are abbreviations, for example PORT_MSGR on the managed node stands for OPC_COMM_PORT_MSGR. On the management server, you can set the necessary registry keys using the Server Configuration dialog. See the Variable Reference for the exact names.

Example 1

In this example the control agents of nodes A and C do not register with the DCE endpoint mapper, therefore management server X uses entries in the port specification file to contact the control agents.

On the managed nodes, node A reads the port of its management server from the variables PORT_MSGR and PORT_DISTM in the opcinfo file. Node B still uses the endpoint mapper lookup when contacting its management server, as it has not been configured otherwise. Therefore the management server has to register its RPC server at the endpoint mapper (which is the default).

RPC clients perform the following steps when connecting to an RPC server. A key to the diagram can be found below.

Example 2

In this flexible management scenario with two servers "X" and "Y", the RPC clients on the node A read the ports necessary to contact both management servers from the port specification file. The ports are different for management servers "X" and "Y".

"Y" is an HPOM for UNIX management server and uses the opcinfo file to specify the ports used by the server processes.

"X" is an HPOM for Windows management server and uses the registry to specify the port used by the Message and Action server process.

Related Topics: