InfoCenter Home >
7: Multimachine management >
7.2 Managing workloads >
7.2.8 Workload management for stand-alone Java clients

7.2.8 Workload management for stand-alone Java clients

Stand-alone Java applications (Java applications that do not run under WebSphere Application Server), J2EE clients, administrative agents, and other types of Java applications can participate in WebSphere workload management. This extends the benefits of workload management (such as load balancing and failover support) to Java applications that run on machines where WebSphere Application Server is not installed. The Java client can optionally participate in WebSphere security.

Enabling workload management for a stand-alone Java client

To enable stand-alone Java applications to participate in workload management, do the following:

  1. Create a stand-alone Java client module by using the Application Assembly Tool (AAT).
  2. Install the client module by using the administrative console or a command-line interface such as wscp.
  3. Install the Websphere client Java Archive (JAR) files and the Java 2 SDK by using the WebSphere client installation CD.
  4. Start the stand-alone Java client application with the following system parameters:
    • com.ibm.ejs.wlm.BootstrapNode=admin_server_node
    • com.ibm.CORBA.BootstrapHost=admin_server_node
    • com.ibm.CORBA.BootstrapPort=900

    where admin_server_node is the name of the machine where the WebSphere administrative server is located. You can specify either the short name, the IP address, or the fully qualified name of the machine. For example:

    java -Dcom.ibm.ejs.wlm.BootstrapNode=greenland
    -Dcom.ibm.CORBA.BootstrapHost=greenland.rh1.ibm.com
    -Dcom.ibm.CORBA.BootstrapPort=900 WlmApp

Enabling workload management and security for a stand-alone Java client

Enabling workload management with security requires additional steps to be performed:

  1. Create a standalone Java client module by using the Application Assembly Tool (AAT).
  2. Install the client module by using the administrative console or a command-line interface such as wscp.
  3. Install the Websphere client Java Archive (JAR) files and the Java 2 SDK by using the WebSphere client installation CD.
  4. Copy the product_installation_root/properties/sas.client.props file to the WebSphere/properties directory. This file contains security configuration properties.
  5. Copy the product_installation_root/lib/sslight.jar file to the WebSphere/jars directory.
  6. Copy the product_installation_root/lib/ujc.jar file to the WebSphere/jars directory.
  7. Start the stand-alone Java client application with the following system parameters:
    • com.ibm.CORBA.ConfigURL=file:/C:/Websphere/properties/sas.client.props
    • com.ibm.ejs.wlm.BootstrapNode=admin_server_node
    • com.ibm.CORBA.BootstrapHost=admin_server_node
    • com.ibm.CORBA.BootstrapPort=900

    where admin_server_node is the name of the machine where the WebSphere administrative server is located. You can specify either the short name, the IP address, or the fully qualified name of the machine. For example:

    java -Dcom.ibm.CORBA.ConfigURL=file:/C:/Websphere/properties/sas.client.props
    -Dcom.ibm.ejs.wlm.BootstrapNode=greenland
    -Dcom.ibm.CORBA.BootstrapHost=greenland.rh1.ibm.com
    -Dcom.ibm.CORBA.BootstrapPort=900 WlmApp
Go to previous article: Run-time exceptions and failover strategies for workload management Go to next article: Problem Determination

 

 
Go to previous article: Run-time exceptions and failover strategies for workload management Go to next article: Problem Determination