InfoCenter Home >
7: Multimachine management >
7.2 Managing workloads >
7.2.5 Using workload management - a sample procedure
7.2.5 Using workload management - a sample procedure
The following procedure shows how to implement basic workload management by cloning
application servers and enterprise beans. In this scenario, client requests are
distributed among the clones of an application server on a single machine. (A client
refers to any servlet, Java application, or other program or component that connects the
end user and the enterprise beans being accessed.) In more complex workload management
scenarios, you can distribute clones to remote machines, clone servlets, or configure a
servlet redirector.
- Decide which application server you are going to clone.
- Deploy the enterprise beans that you plan to clone. Optionally, chose the deployment
option to enable workload management for the JAR file.
- After configuring the server and enterprise beans exactly as you want them to be, create
a model of the server. This is the first step in cloning the server. Make sure that the
model includes the enterprise beans that are deployed on the server. It is recommended
that you make the original server instance a clone that is administered through the model.
- Create one or more clones of the server model.
- Start all of the application servers by starting the model.
- If you did not enable workload management when you were deploying the enterprise beans,
use the wlmjar command against the deployed JAR file of the enterprise
bean to produce a WLM-enabled JAR file.
- Add the WLM-enabled JAR file to the class path of the client you want to enable to
exercise workload management.
- If the client is a servlet, also specify the WLM-enabled JAR file in the class path of
the application server on which the servlet resides.
Workload management automatically begins when you start the clones of the application
server.
You need to define a bootstrap host for
stand-alone Java clients -- that is, clients that are located on a different machine from
the application server and have no administrative server for the client. Add the following
line to the Java Virtual Machine (JVM) arguments for the client:
-Dcom.ibm.CORBA.BootstrapHost=machine_name
where machine_name is the name of the machine on which the administrative
server is running.
|
|