Enabling and configuring the SOAP server on a monitoring server

The Web Services Simple Object Access Protocol (SOAP) server is an application server plug-in that receives and sends XML data, and provides XML SOAP interfaces into the Tivoli Management Services components and the monitoring agents. The SOAP server is installed with each monitoring server and is enabled during configuration of the hub monitoring server. During configuration, you specify the list of non-local hub monitoring servers with which the local SOAP server can communicate.

Before you begin

ICSF password encryption is required for SOAP Server. For more information on the SOAP server and SOAP server security, see SOAP server.

Note: If you enable the SOAP server while configuring the hub, at least one of the communication protocols you specify must be either IP*.*PIPE or IP*.UDP. The communication protocols for the SOAP server are automatically initialized to the protocol values set for the runtime environment.

About this task

Use the following parameters to enable the SOAP server.

KDS_TEMS_SOAP_SERVER_FLAG: This parameter determines whether to enable the Web Services Simple Object Access Protocol (SOAP) server. The default is Y.
KDS_TEMS_HTTP_PORT_NUM: This parameter contains the HTTP port number for communications with the SOAP server. The default is 1920.

For a hub monitoring server, SOAP server configuration creates a KSHXHUBS member in the rhilev.rte.RKANPARU library. The KSHXHUBS member contains a table of hub monitoring servers, an aliasing mechanism for identifying the hub monitoring servers with which the local SOAP server can communicate. Use the following parameters to create the table:

KDS_PH: Table BEGIN and END delimiter.
KDS_PH01_ROW: First row delimiter.
KDS_PH01_TEMS_NAME_NODEID: This parameter defines the TEMS name (node ID) of the hub monitoring server. If you have overridden the RTE_TEMS_NAME_NODEID global CMS_NODEID value, adjust the KDS_PH01_TEMS_NAME_NODEID parameter to the same value.
KDS_PH01_TEMS_RTE: This parameter contains the name of the runtime environment where the hub is configured.
KDS_PH01_TEMS_COMM_PROTOCOL1: This parameter contains the communication protocol to be used by the SOAP server.
KDS_PH01_TEMS_TCP_HOST: If this is a high-availability hub, this parameter must be set to the DVIPA
KDS_PH01_TEMS_TCP_PORT_NUM: This parameter defines the TCP port number of the SOAP server.
KDS_PH01_TEMS_VTAM_NETID: This parameter defines the VTAM® network identifier for the SOAP server.
KDS_PH01_TEMS_VTAM_APPL_GLB_BKR: This parameter defines the VTAM® applid for the global location broker of the SOAP server.
KDS_PH01_TEMS_VTAM_LU62_DLOGMOD: This parameter defines the LU6.2 logmode entry required by the SOAP server for SNA communication.
KDS_PH01_TEMS_ALIAS_NAME: This parameter contains the monitoring server name (node ID) that identifies a non-local hub monitoring server to the SOAP server. For best results, accept the default name.
KDS_PH01_TEMS_USER_QUERY: This parameter defines the user ID with query access to the SOAP server.
KDS_PH01_TEMS_SYSV_FLAG: This parameter determines whether system variables are to be enabled for the SOAP server.
KDS_PH01_TEMS_KSH_SECURE: This parameter defines the security status of the SOAP server.

To create the access list for the SOAP server, use the following parameters:

KDS_PU: Table BEGIN and END delimiter
KDS_PU01_ROW: First row delimiter

KDS_PU01_TEMS_NAME_NODEID
KDS_PU01_TEMS_USER_ID
KDS_PU01_TEMS_USER_QUERY
KDS_PU01_TEMS_USER_UPDATE
KDS_PU: Table END delimiter

For more information about SOAP server security, see SOAP server configuration and security. For more information about the parameters, see Tivoli Enterprise Monitoring Server (KDS) parameters.