WebSphere Extended Deployment, Version 6.0.x
             Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS


Creating a node group and dynamic cluster to host the long-running scheduler

The long-running scheduler is a Java 2 Platform Enterprise Edition (J2EE) application. The WebSphere Extended Deployment Operations Optimization component is required to host the job scheduler in a dynamic cluster. To make the long-running scheduler highly available, deploy it to a dynamic cluster within your WebSphere Extended Deployment environment. Only unclustered application servers or static clusters are supported if you deploy Compute Grid without the Operations Optimization component.

Before you begin

Determine which nodes in your cell host the long-running scheduler. The administrative console, application clients, J2EE applications and Web service requests access the long-running scheduler. The flong-running scheduler must access the long-running scheduler database, and the nodes that host execution environments.

Privileges for the long-running scheduler differ, depending on the various roles. Roles include monitor, operator, configurator, and administrator. If you are a user with either a monitor or an operator role, you can only view the long-running scheduler information. If you have the role of configurator or administrator, you have all the configuration privileges for the long-running scheduler.

About this task

See Getting started with business grid to understand how the long-running scheduler fits into the overall architecture of business grid functions.

Procedure

  1. In the administrative console, select System administration > Node groups.
  2. Click New.
  3. Type an appropriate name for the node group. For example, LongRunningSchedulerNG .
  4. Click OK.
  5. Select the node group that you created from the table.
  6. Select Node group members, then click Add.
  7. Check the boxes next to the nodes that host the long-running scheduler, then click Add.
  8. In the administrative console, select Servers > Dynamic Clusters.
  9. Click New.
  10. Type an appropriate name for the dynamic cluster. For example, LongRunningSchedulerDC.
  11. In the Map to node group menu, select the node group that you created.
  12. In the Default application server template menu, select defaultXD.
  13. Make sure Keep one instance started at all times is selected.
  14. Select Limit the number of instances that can start, then type 1 in the text field. For a high availability environment, use a dynamic cluster with the minimum and maximum, both set to 1, automatic mode, and an on demand router in front of the dynamic cluster.
  15. Click Next, then Finish.
  16. If you want WebSphere Extended Deployment to automatically manage the location of your long-running scheduler, select Automatic from the mode menu, check the box for the dynamic cluster that you created, and click Set mode.

Results

The following example shows the steps you need to perform only for static or dynamic cluster members added after the job scheduler has been assigned to a host. When the job scheduler is assigned a host, WebSphere Extended Deployment automatically performs the following steps for cluster members already in a cluster.

Example

  1. In the administrative console, select Servers > Application servers.
  2. Click the name of the application server in the dynamic cluster. The application server's name will be in the form dynamicclustername_nodename.
  3. Select Container Services > Startup beans service.
  4. Check the box next to Enable service at server startup and click OK.
  5. Repeat for other application servers in the dynamic cluster.
  6. Save your changes.
  7. In the administrative console, select Environment > Virtual Hosts.
  8. Click grid_host.
  9. Click Host Aliases.
  10. Click New.
  11. Under Host Name, type a virtual host name, or *.
  12. Under Port, type the WC_gridhost port.
  13. Click Apply.
  14. If security is enabled, repeat these steps to create host aliases based on the WC_grid_host_secure port.
  15. Restart server.



Related concepts
Configuring the long-running scheduler
Related reference
Administrative roles and privileges
Task topic    

Terms of Use | Feedback

Last updated: Nov 30, 2007 4:00:35 PM EST
http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r0/index.jsp?topic=/com.ibm.websphere.xd.doc/info/scheduler/tbgcrtende.html