|
|
This section describes the setup of the WebSphere cluster. Although it is not recommended for performance reasons to separate the Web and EJB containers, this is necessary for the example to work (split-JVM environment). Therefore, we deploy the Web and EJB modules of Trade 6 into different clusters. The required steps are:
| 1. | Create two cells with at least one node in each. |
|
|
| 2. | Create a cluster in each cell. Both clusters have to have the same name. If you install an application that splits across multiple clusters for the Web and EJB modules (as is the case in this example), create the additional clusters as well. |
|
|
|
|
Note that you could also create the cluster and cluster members using the trade.jacl script used to set up the Trade 6 resources in the next step. However, with the split-JVM environment we are setting up, it is easier to create the clusters using the Administrative Console. The trade.jacl script asks for cluster and cluster member names and only creates a new cluster and cluster members if they do not exist in the cell yet.
| 3. | Set up the Trade 6 resources by running the trade.jacl script with the configure option. Run the script on the primary and backup cell. |
|
Follow the directions that are included in the Trade 6 download package for setup and installation, or see Chapter 8 of IBM WebSphere V6 Scalability and Performance Handbook, SG24-6392 for instructions on how to use the trade.jacl script. |
| 4. | Install Trade 6 using the Administrative Console. Consider this: |
| a. On the Map modules to servers step (Step 2), map the TradeEJB module to wascluster01 and map TradeWeb to wascluster02. |
| b. Make sure the right database is selected on the Provide options to perform the EJB Deploy step (Step 3). |
| c. On the Map EJB references to beans step (Step 9), update the EJB references. This enables them to contact the EJBs installed on the EJB cluster. You must change the JNDI names of the ejb/Trade reference bindings in the TradeWeb module to their fully qualified JNDI names, for example: |
cell/clusters/<EJB_Cluster_Name>/ejb/TradeEJB
In our environment, the correct fully qualified JNDI name is:
cell/clusters/wascluster01/ejb/TradeEJB
So add cell/clusters/wascluster01/ to the beginning of the existing names for the ejb/Trade, ejb/Quote, ejb/LocalQuote, and ejb/LocalAccountHome settings.
Cell names: wascell02 and wascell03
