All execution environments and long-running applications are deployed to dynamic
clusters just like transactional applications. The dynamic cluster is the
deployment target for the Java 2 Platform Enterprise Edition (J2EE) Enterprise
Archive (EAR) files for both the execution environment and
your long-running application.
Before you begin
Deploy each long-running application to
its own dynamic cluster to provide the grid placement logic the greatest flexibility
in managing instances of your long-running applications.
About this task
Define a dynamic cluster to create a deployment target for a new
long-running application.
Creating a node group
and dynamic cluster causes WebSphere Extended Deployment to create an application
server for the dynamic cluster on each node in the node group. Perform the
following steps for each application server created for the dynamic cluster
you created. If you add nodes to the node group later, repeat these steps
for the newly-created application servers.
- In the administrative console, select Server > Dynamic Clusters.
- Click New.
- Type an appropriate name for the dynamic cluster. For example, LongRunningApplicationDC.
- In the Map to node group menu, select the node group in which to create
the dynamic cluster.
- In the Default application server template menu, select defaultXD.
- Set other dynamic cluster properties as appropriate for the dynamic cluster.
- Click Next, then Finish.
- If you want WebSphere Extended Deployment to automatically start and stop
instances of this dynamic cluster as needed, select Automatic in the
menu, click the box for the dynamic cluster you created, then click Set
mode.
Results
Creating a node group and dynamic cluster causes WebSphere Extended
Deployment to create an application server for the dynamic cluster on each
node in the node group.
What to do next
Perform the following steps for each application server created for
the dynamic cluster you created. If you add nodes to the node group, repeat
these steps for the newly-created application servers.
- In the administrative console, select Servers > Application servers.
- Click on the name of the application server in the dynamic cluster. The
application server's name will be in the form dynamicclustername_nodename.
- Select Container Services > Startup beans service.
- Check the box next to Enable service at server startup and click OK.
- Repeat for other application servers in the dynamic cluster.
- Create host aliases for any dynamic cluster instances elsewhere for both
the long-running scheduler and the long-running execution environment.
Creating host aliases is critical if you do not use the setupLongRunning.py script
to set up the environment.
- In the administrative console, click Environment > Virtual Hosts.
- Click default_host > Host Aliases >New.
- Under Host Name, type a virtual host name, or *.
- Under Port, type the WC_defaulthost port.
- Click Apply.
- If security is enabled, repeat these steps to create
host aliases based on the WC_defaulthost_secure port.
- Restart the server.
- Save your changes.
- Set job capacity for endpoints:
- Click Servers > Dynamic clusters.
- Click the dynamic cluster for the execution environment.
- Under Additional Properties, click Custom Properties > New.
enter
- In the Name field, type com.ibm.websphere.longrun.EndPointCapacity.
- In the Value field, type an integer value,
for example, 10, that represents the job capacity per endpoint.
The default maximum job capacity per endpoint is 2.
- Click Apply and save the configuration.