InfoCenter Home > 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 clientTo enable stand-alone Java applications to participate in workload management, do the following:
The rest of this section describes this setup procedure in more detail. Copy the JAR files to client machineThe following JAR files must be copied from a machine where WebSphere Application Server is installed to the machine where the client application runs:
Install the SDK on the client machineWorkload management for stand-alone clients is supported for the Java 2 SDK, version IBM 1.2.2. If the machine where the client application runs is not currently using this version of the SDK, you must install it. See the SDK installation instructions for details. Add the JAR files to the CLASSPATH variable on the client machineAdd the names of the JAR files to the CLASSPATH variable on the machine where the client application runs. For example: CLASSPATH=D:\WebSphere\jars\_wlm_deployedBean.jar;D:\WebSphere\jars\ujc.jar;%CLASSPATH% Add the directories containing the SDK executable files to the PATH variable on the client machineAdd the directories containing the executable files of the SDK to the PATH variable on the machine where the client application runs. For example: PATH=C:\WebSphere\SDK\bin;C:\WebSphere\jdk\jre\bin;%PATH% Run the client applicationTo enable the client application to participate in workload management, start it with the following system parameters:
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 clientEnabling workload management with security requires additional steps to be performed:
The rest of this section describes this setup procedure in more detail. Copy the files to the client machineThe following files must be copied from a machine where WebSphere Application Server is installed to the machine where the client application runs:
Install the SDK on the client machineWorkload management with security supports the same version of the SDK as workload management alone: Java 2 SDK, version IBM 1.2.2. To install it, follow the SDK installation instructions. Add the JAR files to the CLASSPATH variable on the client machineAdd the names of the JAR files to the CLASSPATH environment variable on the machine where the client application runs. For example: CLASSPATH=D:\WebSphere\jars\_wlm_deployedBean.jar;D:\WebSphere\jars\ujc.jar; D:\WebSphere\jars\sslight.jar;%CLASSPATH% Add the directories containing the SDK executable files to the PATH variable on the client machineAdd the directories containing the executable files of the SDK to the PATH variable on the machine where the client application runs. For example: PATH=C:\WebSphere\SDK\bin;C:\WebSphere\jdk\jre\bin;%PATH% Set up the server to enable Java client accessA WebSphere administrator must create an application that specifies which enterprise beans require authorization and security checking by using the appropriate administration console wizards. The administrator must set the security permissions for all clients of the application to allow access to the read, write, remove, create, execute, and finder methods of the enterprise beans. See article 6.6.18.1, Securing applications, for details on setting up security. Run the client applicationTo enable the client application to participate in workload management, start it with the following system parameters:
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 |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|