Creating a custom Java administrative client program using WebSphere Application Server administrative Java APIs

Why and when to perform this task

This section describes how to develop a Java program using the WebSphere Application Server administrative APIs for accessing the WebSphere administrative system. For more information, view the JMX Javadoc .

When you develop and run administrative clients that use various JMX connectors and that have security enabled, use the following guidelines. When you follow these guidelines, you guarantee the behavior among different implementations of JMX connectors. Any programming model that strays from these guidelines is unsupported.

  1. Create and use a single administrative client before you create and use another administrative client.
  2. Create and use an administrative client on the same thread.
  3. Use one of the following ways to specify a user ID and password to create a new administrative client::
    • Specify a default user ID and password in the property file.
    • Specify a user ID and password other than the default. Once you create an administrative client with a nondefault user ID and password, specify the nondefault user ID and password when you create subsequent administrative clients.

Steps for this task

  1. Develop an administrative client program.
  2. Build the administrative client program by compiling it with javac and providing the location of the necessary JAR files in the classpath argument.

    For example, if your installation directory is /DeploymentManager a typical command would look like the following example:

    (split for publication)
    javac -classpath 
    /DeploymentManager/lib/admin.jar;/DeploymentManager/lib/wsexception.jar;
    /DeploymentManager/lib/jmxc.jar 
    MyAdminClient.java
    (split for publication)
  3. If your administrative client uses Simple Object Access Protocol (SOAP) as its Connector, you must configure Java Secure Socket Extension (JSSE) as your transport layer. WebSphere Application Server uses Secure Sockets Layer (SSL) and Transport Layer Security (TLS) with the Java Secure Sockets Extension (JSSE) and System SSL packages.
    Create digital certificates for the user ID used to run your administrative client. If you want to use System Authorization Facility (SAF) to create digital certificates and store them in a SAF keyring, refer to Warning: no string named [tsec_definsslsec] found.. (You can save the name of the keyring you create for use in the next step.)
  4. Update the soap.client.props file being used by your administrative client with the name of the SAF keyring. Refer to the second step in Warning: no string named [tsec_racfjssekeyringzos] found. for directions on updating the soap.client.props file.
  5. Run the administrative client program by setting up the run-time environment so that the program can find all of the prerequisites.
    Many of the batch or script files in the bin directory under the installation root perform a similar function. The following is an example of a batch file that runs an administrative client program named MyAdminClient:
    @echo off
    
    binDir=`dirname "$0"`       
    . "$binDir/setupCmdLine.sh"
    
    "$JAVA_HOME/bin/java" "$CLIENTSOAP" "-Dwas.install.root=$WAS_HOME"
    "-Dwas.repository.root=$CONFIG_ROOT" -Dcom.ibm.CORBA.BootstrapHost=$COMPUTERNAME 
    -classpath "$WAS_CLASSPATH;/DeploymentManager/classes;/DeploymentManager/lib/admin.jar;
    /DeploymentManager/lib/wasjmx.jar" MyAdminClient $@
    




Searchable topic ID:   txml_customjava
Last updated: Jun 21, 2007 9:56:50 PM CDT    WebSphere Application Server for z/OS, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/tjmx_customjava.html

Library | Support | Terms of Use | Feedback