IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Agent-based services > Centralized Configuration > Centralized Configuration startup > Initiating Centralized Configuration with a service interface request

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

---

Initiating using the Service Interface API (kshsoap)

The Service Interface is an API that allows the creation of a custom interface. Sample HTML files are provided with the agents to demonstrate the function of the Service Interface. The API can also be accessed programmatically using Java, Visual Basic, Perl, HTML and other languages. The Tivoli Enterprise Monitoring Server includes a command line utility called kshsoap that can be used within a script to submit these service interface requests. You can use kshsoap to initiate Centralized Configuration.

Procedure

1. Create a file called request.xml with <UUSER> and <UPASS> elements to specify the credentials that kshsoap requires to connect to the Agent Service Interface. This ID must be defined on the target systems that you plan to submit the request to. As well, the ID must be a member of the Administrative group in the target agent's Access Authorization Group Profile. Example:

   <ConfigurationArtifact>
     <UUSER>root</UUSER>
     <UPASS>{AES256:keyfile:a}ENRUCXLW40LpR0RtGSF97w==</UPASS>
       <ConfigServer
           Name="CENTRAL-CONFIG-SERVER"
           URL="http://winhost:1920///system.winhost_nt/system.winhost_nt/"
           User="Administrator"
           Password="{AES256:keyfile:a}vHBiEqmmvylNPs90Dw1AhQ==" />
       <ConfigFile
           Server="CENTRAL-CONFIG-SERVER"
           Name="cnfglist.xml"
           Path="@PRODUCT@"
           Disp="CNFGLIST"
           Activate="YES" />
   </ConfigurationArtifact>

   The <UUSER> and <UPASS> elements can be replaced by <UNAME> and <UWORD> if you do not want your password encrypted and prefer to enter it in plain text.

2. Create another text file named urls.txt containing the URLs of the Agent Service Interface Request. Example:

   http://linuxhost:1920///linuxhost_lz/linuxhost_lz
   http://unixhost:1920///unixhost_ux/unixhost_ux

3. Use kshsoap to send request.xml to the Service Interfaces listed in urls.txt. On a Windows-based monitoring server, kshsoap.exe is in the install_dir\CMS directory; on a Linux or UNIX-based monitoring server, kshsoap.exe is located in the install_dir/interp/ms/bin directory.

   • install_dir\CMS\kshsoap path_to_file\request.xml path_to_file\urls.txt 

   • install_dir/interp/ms/bin/kshsoap 
     path_to_file/request.xml path_to_file/urls.txt

Parent topic:

Initiating Centralized Configuration with a service interface request

---

+

Search Tips   |   Advanced Search