Siebel System Monitoring and Diagnostics Guide > Monitoring Siebel Server Run-Time Operations > Process of Monitoring Siebel Application Server Operations Across an Enterprise >

Preparing to Monitor Siebel Application Server Operations Across an Enterprise

Before beginning your application server monitoring operations across an enterprise, perform the following procedure.

This task is a step in Process of Monitoring Siebel Application Server Operations Across an Enterprise.

To prepare for monitoring application server operations across an enterprise

1. Make sure:
   • The appropriate JDK (Java Development Kit) is installed and the installation path is set in the user environment variables.
   • One or more Siebel Servers are running
   • The Siebel Management Server and a Management Agent or Agents are running

     For more information about what version of JDK to use, see Siebel System Requirements and Supported Platforms on Oracle Technology Network. For information about setting user environment variables and Siebel Server, see Siebel System Administration Guide. For more information about the Siebel Management Server and Management Agents, see Siebel Installation Guide for the operating system you are using and Siebel Application Deployment Manager Guide.

2. Create a working Java directory from which you can monitor operations.

   For example, you might create a source folder in the D directory (D:\src).

   NOTE:  It is recommended that you create this directory in the same location where JDK is installed.

3. Copy the siebelmgr.jar file from <management agent root directory>\lib to D:\src.

   This file provides the communication between the server and management agent as well as the notification of messages from the server to the agent.

   For example, you might copy from D:\SP1_08_CORE\ses\siebsrvr\mgmtagent\lib.

4. Copy the siebeljmxapi.jar file from management server root dir\lib to D:\src.

   This file connects the server to the management agent and converts the various queries received into something the agent can understand.

   For example, you might copy from D:\DiagTool\lib.

5. Create the following files using the code in Sample Files for Monitoring Siebel Application Servers and save the files to the Java directory you created in Step 2:
   • key1.txt
   • 1srvr.xml
   • 2srvr.xml
   • Enterprise.java
   • Server.java
   • Component.java
6. Edit the appropriate sample XML file (1srvr.xml or 2srvr.xml) by performing the following:
   1. Generate an encrypted password to include in your XML file by executing the following command:

   java -cp <dir1>\siebelmgr.jar com.siebel.management.util.Decoder <dir2> <key_file> <clear_text_password>

   where:

   • dir1 is the directory where the siebelmgr.jar is located.
   • dir2 is the directory where the security.properties file is located.
   • key_file is a file containing a continuous string of characters that represents your chosen key, and that character string is used as the encryption key. For example, the key_file might contain the following string:

     Mississippi123

   • clear_text_password is the encrypted password.

     For example, you might execute the following command:

   D:\src>java -cp D:\src\siebelmgr.jar com.siebel.management.util.Decoder D:\DiagTool\security\ D:\src\key1.txt MyPassword)

   As a result, the following output is generated:

   XQj12uTtvi8 (the encrypted base64 encoded password for MyPassword)

   2. Make sure the enterprise name, Siebel Server name, user name, connect string (URL), and password are correct for your specific deployment.

      For more information about which XML file to use and how to use it, Sample Files for Monitoring Siebel Application Servers.

7. Create the following files using the code in Sample Files for Monitoring Siebel Application Servers and save the files to the Java directory you created in Step 2:
   • Enterprise.java
   • Server.java
   • Component.java
8. Edit the appropriate sample Java file (Enterprise.java, Server.java, or Component.java), making sure the enterprise and component names are correct for your specific deployment.

You are now ready to begin monitoring application server operations at the enterprise, server, or component level. For more information, see:

• Monitoring Enterprise Operations for Siebel Application Servers Across an Enterprise
• Monitoring Server Operations for Siebel Application Servers Across an Enterprise
• Monitoring Component Operations for Application Servers Across an Enterprise