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


Installing the execution environment to a dynamic cluster

Next, deploy the execution environment to the dynamic cluster to enable the dynamic cluster to host long-running applications. Do this only once per dynamic cluster, regardless of the number of long-running applications deployed.

About this task

To deploy the execution environment to the dynamic cluster:

Procedure

  1. In the administrative console, select Applications > Install New Application.
  2. Select Remote file system, type <WAS_install_root>/installableApps/LREE.ear, and click Next.
  3. Check the box next to Generate Default Bindings, and click Next.
  4. Check the Use default virtual hostname for Web modules check box, and leave the Host name field as default_host.
  5. Proceed through the installation steps:
    1. Select installation options. Make sure the box next to Deploy enterprise beans is checked. If you plan to set up multiple dynamic clusters to host long-running applications, change the value for application name from LREE to a value that does not conflict with other deployments of LREE.ear. For example, LREE-<application_name>.
    2. In Map modules to servers, select the BatchJobExecutionEnvironmentEJBs and EndpointWebService module.
    3. Choose the dynamic cluster you created in the Create a dynamic cluster for the execution environment section, and click Apply.
    4. Provide options to perform the EJB Deploy. Select the type of database you used for your execution environment database in the Deploy EJB option - Database type field. For Cloudscape, choose CLOUDSCAPE_V5. Type LREESCHEMA for Deploy EJB option - Database schema.
    5. Provide default data source mapping for modules containing 2.x entity beans. Check the box next to BatchJobExecutionEnvironmentEJBs in the table. Select the JNDI name of the data source you defined under To set multiple existing resource JNDI names. Click Apply.
    6. Configure the authorization type and authentication method as needed by your execution environment database. If you use an embedded Cloudscape database, no additional configuration is required.
    7. Select Summary, then click Finish.
  6. Save your changes.

What to do next

By default, the long-running execution environment Web services module is bound to the default_host virtual host of the servers where the long-running execution environment application is installed. To make sure the Web service is available, identify the host names and port numbers used by the application servers that belong to the dynamic cluster where the long-running execution environment is deployed. Then ensure that the default_host virtual host contains a host alias that matches each application server host name and port number.
  1. In the administrative console, select Servers > Application Servers.
  2. Click on the application server.
  3. Under Communications, expand Ports.
  4. Note the port number assigned to WC_defaulthost.
To create the host alias:
  1. In the administrative console navigation tree, select Environment > Virtual Hosts.
  2. Click default_host.
  3. Click Host Aliases.
  4. Click New.
  5. Under Host Name, keep the default *.
  6. Under Port, specify a port.
  7. Click Apply.
  8. If security is enabled, repeat these steps to create host aliases.
  9. Restart server.



Related concepts
Installing the long-running application
Integration of transactional and long-running work
Getting the long-running scheduler WSDL file
Task topic    

Terms of Use | Feedback

Last updated: Oct 16, 2009 11:08:29 AM EDT
http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r0/index.jsp?topic=/com.ibm.websphere.xd.doc/info/scheduler/tbgenv.html