Configuring the HP Operations management server system

The following RPC communication from the HP Operations management server to the managed nodes is affected:

RPC Client	RPC Server	Direction	Explanation
`ovpmad`	`opcctla`	Mgmt Server Mgd Node	Deployment of policies (started by management server).
`OvEpMsgActSrv`	`opcctla`	Mgmt Server Mgd Node	Action requests, Control requests, Heartbeat polling, ...
`opcragt`	`opcctla`	Mgmt Server Mgd Node	Start/ stop/ status and other opcragt requests.

On the management server, you can configure all settings using the Server Configuration dialog box.

In the console tree, right-click Operations Manager, and then click ConfigureServer.... The Server Configuration dialog box appears.
Click Namespaces, and then click Message Action Server General. A list of values appears.
After you have changed a value, restart the OvEpMessageActionServer service for the change to take effect.

RPC Servers

On the HPOM for Windows management server system, the RPC service (endpoint mapper) must be running because it is required by the operating system and other applications. However, it is possible not to register the HP Operations RPC server at the endpoint mapper by setting the value DCE RPC server port registration to false.

Then the RPC clients on managed node systems must have a server port configuration, so that agents can contact the RPC server on the management server system without querying the endpoint mapper.

Configuration values for RPC server on the management server

Value	Type	Default	Explanation
DCE RPC server port registration	Boolean	True	Selects whether to register RPC interfaces with endpoint mapper. If set to false for the message action server, all managed nodes must have a dedicated server port configuration to be able to reach the HP Operations management server. If true, managed nodes can send messages in the usual way, but managed nodes with configured RPC server ports will use those and will not perform an endpoint mapper lookup.
DCE RPC server port	Integer	0	Specifies exactly one port to be used by the RPC server. The value 0 means that the DCE runtime will assign a port.

The Message and Action server implements two interfaces, the RPC interface of the Message Receiver and the interface of the Distribution Manager, which is actually a link to the message receiver so that HPOM for Windows provides the same interfaces as HPOM for UNIX. Therefore the value of DCE RPC server port applies to both of these interfaces.

RPC Clients

The RPC clients ovpmad and OvEpMsgActSrv on the management server system share the same settings.

Configuration values for RPC clients on the management server

Value	Type	Default	Explanation
DCE RPC server port specification file	String	none	Complete path pointing to a server port specification file as described below. Do NOT use " " when specifying the path. Example: `c:\Program Files\ports`
DCE RPC server port lookup	Boolean	True	Whether to perform an endpoint mapper lookup if no matching port for a managed node is found in the server port specification file.

Related Topics: