WebSphere Enterprise Service Bus, Version 6.2.0 Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows



< Previous | Next >


Click here to show all collapsed sections.Show all details | Click here to hide all collapsed sections.Hide all details



Tutorial: Building clustered topologies in WebSphere ESB

This tutorial guides you through creating a clustered "gold" topology for WebSphere® ESB using a template-driven approach.

Introduction

With WebSphere ESB you can describe the entire topology that you want to set up by defining a new type of configuration object called a Deployment Environment.

Expand or collapse Show details Hide details

Learning objectives

After you create a cell and federate two empty nodes to it, you will create a deployment environment that serves as a template for the clustered topology.

You will then generate the deployment environment and test the topology.

After completing the lessons in this module you should be able to understand the concepts and know how to do the following tasks:
  • Define the deployment environment
  • Select the type of topology
This tutorial should take approximately 60 minutes to finish. If you explore other concepts related to this tutorial, it could take longer to complete.

Prerequisites

The following software must be installed before you can build the topology:
  • WebSphere Process Server or WebSphere Enterprise Service Bus, at Version 6.1.0 or later.
    Note: The information in this tutorial applies to WebSphere Process Server or WebSphere Enterprise Service Bus Version 6.2.x.
  • A supported version of DB2® (Version 8.2 FP 6 or Version 9.1)



Module 1: Defining the deployment environment

With WebSphere ESB you can describe the entire topology that you want to set up by defining a new type of configuration object called a Deployment Environment.

Expand or collapse Show details Hide details

After completing this module you should be able to understand the concept of a deployment environment and the different types of topologies associated with it, and you should be able to choose the right type of topology for your system.

A deployment environment contains the definition of the entire topology. An entire topology consists of the following elements:
  • Topology type. The type of topology that you want to create.
  • Nodes. The nodes you need to participate with the topology.
  • Clusters. The clusters that are distributed in the topology.
  • Characteristics of databases and schemas. The characteristics of the databases and schemas that are required by the topology, and the credentials that are needed to connect to the databases.
This tutorial takes approximately 60 minutes to finish. If you explore other concepts related to this tutorial, it could take longer to complete.

Lesson : Selecting the type of topology

Select the type of topology, after assessing which type is most appropriate based on your setup.

When you create a deployment environment, you must begin by selecting the type of topology. The Deployment Environment creation wizard allows you to select from the different topologies listed below:
  • Single Cluster. This topology is also known as the "bronze" topology. In this topology, all the functional pieces (user applications, messaging infrastructure, CEI, and support applications) run in the same cluster.
  • Remote Messaging. This topology is also known as the "Silver" topology. In this topology, the messaging engines are configured on their own cluster. User applications, CEI, and support application coexist in the same cluster. In total, you will be creating two clusters. This topology is adequate when you do not plan to make very intensive use of the CEI.
  • Remote Messaging and Remote Support. This topology is also known as the "Gold" topology. In this topology, there are three clusters:
    • Application: A cluster where you can run the user applications.
    • Messaging: A cluster where the messaging infrastructure is configured.
    • Support: A cluster that primarily runs the Common Event Infrastructure (CEI), and also other support applications.
    The Remote Messaging and Remote Support topology is perhaps the most frequently adopted topology because of the flexibility it offers in terms of its potential for scalability.
You can create a deployment environment in any of the following phases:
  • Profile creation time: Powerful for demonstrations or prototyping.
  • Installation time: Use if you choose to also create a profile while installing the product. Powerful for demonstrations or prototyping.
  • After you have federated the nodes to the cell (using the administrative console or a script). Recommended for production implementations because this is the only approach that provides full control over the entire definition of the deployment environment.
The deployment environment definition provides you with a one-click generation button with which you can create the entire clustered topology at once, rather than having to go through a large number of separate and unrelated steps. However, after you have generated the deployment environment, WebSphere ESB maintains no direct relationship between the deployment environment definition and the resources that are generated. This has the following practical implications:
  • After generation, you cannot make a change to the deployment environment definition and regenerate the deployment environment.
  • After generation, if you make a change to a specific resource that was generated (for example, a data source), that change will not be reflected in the deployment environment.
It is a good practice, therefore, to save your configuration after creating the deployment environment and before you generate the environment. This practice allows you to easily restore the initial configuration in case you need to make a change and start again.
For ease of understanding, this tutorial refers to a clustered topology on a single system. However, the steps are much the same if you have multiple, separate systems. The following figure shows the target topology that will be built in the rest of this tutorial.
Figure 1. The target topology
The topology shown in the figure consists of two managed nodes and a deployment manager process
The topology shown in the figure consists of two managed nodes and a deployment manager process. You need to create three clusters, across the two managed nodes:
  • One for the messaging infrastructure
  • One for the WebSphere ESB applications
  • One for the CEI, and other support applications
Each cluster has a member on each of the two nodes, so there are six cluster members. The figure depicts the entire cell as being hosted on a single physical system. However, the procedure for setting up a truly distributed cell, comprised of multiple systems, would not differ significantly from the one shown here.



Module 2: Creating the profiles and federating the nodes

In this module, you will create the deployment manager and custom profiles required for the topology, and you will federate them to the cell. This tutorial follows the approach where the deployment environment is created after federation, because that way you have better control over the configuration of the resources being created.

Expand or collapse Show details Hide details
Important: This tutorial assumes that DB2® UDB is used for all the databases. The tutorial also assumes the following authentication credentials:
  • The DB2 administrator user ID and password (db2admin/xxxxxx in the text).
  • The WebSphere ESB administrator user ID and password (admin/admin in the text).
The tutorial also assumes that the WebSphere ESB product binaries have already been installed, along with the appropriate version of DB2, and that no existing profiles have been created yet.
At the end of this module you will have created and federated profiles for the deployment managers and the two node profiles.
This tutorial takes approximately 50 minutes to finish.

Lesson 2.1: Creating the deployment manager profile

Create a deployment manager profile, using the Profile Management tool.

This lesson guides you through creating the deployment management profile. You will use the Profile Management Tool to create the Deployment Manager Profile.
Important: The Profile Management Tool is not available on the supported 64-bit platforms. On those platforms, you must use the manageprofiles command-line tool to perform these tasks.
Procedure
  1. Click on the Profile management tool from the WebSphere ESB menu or open a command prompt and change directories to INSTALL_ROOT\bin\ProfileManagement and type pmt then press Enter. The Profile Management Tool is displayed.
    Figure 2. Profile Management Tool
    This figure shows the Profile Management Tool
  2. Click Create. The Welcome to the Profile Management tool window is displayed.
    Figure 3. Welcome to the Profile Management Tool
    The figure consists of links to the different online information centers
  3. Click Next. The Environment Selection window is displayed.
    Figure 4. Environment Selection window
    This figure lists the different types of environments you can create
  4. Select WebSphere ESB from the Environments list and click Next. The Profile Type Selection window is displayed.
    Figure 5. Profile Type Selection window
    This figure lists the different types of profiles
  5. Select the Deployment manager profile and click Next. The Profile Creation Options window is displayed.
    Figure 6. Profile Creation Option window
    This figure lists the three different options for creating a profile
  6. Select Advanced profile creation, as shown in the previous figure You do not want to create a deployment environment at this time.
  7. Click Next. The Optional Application window is displayed. Leave the check box for Deploy the administrative console selected.
    Figure 7. Optional Application Deployment
    This figure shows how to install a Web-based administrative console.
  8. Click Next. The Profile Name and Location window is displayed. Leave the defaults for the name of the profile and the directory. You are going to create a profile called Dmgr01.
    Figure 8. Profile Name and Location window
    This figure allows you to specify the Profile Name and Location
  9. Click Next. The Node, Host and Cell Names window is displayed. Leave the defaults for the cell name, host name, and node name. Notice that the node name is <system name>CellManager02. This fictitious node is created to encompass the deployment manager process.
    Figure 9. Node, Host, and Cell names
    This figure gives the names of the nodes, hosts and cells.
  10. Click Next. The Administrative Security window is displayed. Clear the Enable Administrative Security check box. You do not want to enable security at this time.
    Figure 10. Administrative Security
    This figure shows the Administrative Security window which allows you to set up administrative security
  11. Click Next. The Port Value Assignment window is displayed .
    Figure 11. Port Value Assignment
    This image lists the defaults for ports
    Leave the defaults. By default, the console should be available on port 9060 and the SOAP connector on port 8879. If you have other versions of WebSphere Application Server installed on your system, the proposed ports might be different.
  12. Click Next. The Windows Service Definition window is displayed.
    Figure 12. Windows Service Definition
    This screen lets you define the window services you need.
    Clear the Run the deployment manager as a Windows service check box. You are going to stop and start the deployment manager manually from the command line.
  13. Click Next. The Database Configuration window is displayed. Select DB2 Universal Database™ for the database product or leave the defaults. Notice that you can delay the creation of the common database, and that you can change the directory where the database creation scripts are going to be saved. The database name is, by default, WPRCSDB. However, you can change that too. It is important to understand that a cell relies on a single common database.
    Note: This tutorial assumes a local database (not remote). If the database were remote, you would need to delay the execution of the database scripts and you would have to run these scripts manually. DO NOT CHECK Delay execution of database scripts (must select if using remote database).
    Figure 13. Database Configuration window
    This figure provides you options to set up a database.
  14. Click Next. The Database Configuration Part 2 window is displayed format of this window varies depending on the database product you select on the previous step. For DB2 UDB, you need to provide the authentication credentials, the location of the JDBC driver, the driver type, and the host name and port number of the database server process. Specify db2admin for the user, and the password and leave the rest as it is, as shown in the following figure.
    Figure 14. Database Configuration (Part 2) Window
    This figure provides you options to set up a database.
  15. Click Next. The Profile Creation Summary window is displayed. Review the settings then click Create. After a short time you should receive confirmation that the profile was successfully created, as shown in the following figure.
    Figure 15. Profile Creation Complete
    This figure provides confirmation that the profile was successfully created.
  16. Clear the Launch the First steps console check box.
  17. Click Finish. You have now created a profile successfully.

Lesson 2.2: Creating custom profiles for node1 and node2

Creating a custom profile for the Gold topology.

This topic guides you through creating a custom profile for the Gold topology by going through the following steps.
Important: The Profile management tool is not available on the supported 64-bit platforms. On those platforms, you must use the manage profile command line tool, in order to perform these tasks.
Procedure
  1. Click Create. The Welcome to the Profile Management Tool window is displayed.
    Figure 16. Welcome to the Profile Management Tool
    The figure consists of links to the different online information centers
  2. Click Next. The Environment Selection window is displayed.
    Figure 17. Environment Selection windowThis figure lists the different types of environments you can create
  3. Select WebSphere ESB from the Environments list and click Next.
  4. The Profile Type Selection window is displayed. Select the Custom profile, as shown in the following figure.
    Figure 18. Profile Type Selection window
    This figure displays the list of available profile types
  5. Click Next. The Profile Creation Options window is displayed.
  6. Select Advanced Profile Creation. Click Next. The Profile Name and Location window is displayed.
  7. Leave the defaults for the profile name and directory. You are going to create a profile called Custom01.Click Next. The Node and Host Names window is displayed.
  8. Leave the defaults for the node name and host name, but remember the node name. You will add this node to the cell at a later time. The node name should be called system name Node01.
  9. Click Next. The Federation window is displayed. In the Federation window, select the Federate this node later check box. All the fields should become displayed, as shown in the following figure.
    Figure 19. Deferring the federation of the node
    This figure allows you to specify the details of the nodes you want to defer the federation of
  10. In the Database Configuration window select DB2 Universal Database and leave the driver location as the default.
  11. Click Next.
  12. Review the summary, then decide to continue or go back and change something.
    • If everything looks fine, click Create then continue with the remaining steps.
    • If you want to change something, go back and repeat appropriate preceding steps.
    After a short time, you should receive notification that the profile was successfully created.
  13. Clear the Launch the first steps console check box as shown in the following figure.
    Figure 20. Profile Creation Complete window
    This figure confirms that the profile creation is complete
  14. Click Finish.
  15. Create the custom profile for node2. In the welcome screen of the Profile Management tool, click Next, then repeat steps 3 to 14, using Custom02 for the profile name and Node02 for the node name.

Lesson 2.3: Verifying database creation and profile creation

Verify that the database and profiles have been created successfully.

Having created the database and the profiles, you can use commands to verify that the creation processes were successful.
Procedure
  1. Open a command prompt, and type db2cmd. A DB2 command prompt is displayed.
  2. At the DB2 command prompt, type db2 connect to WPRCSDB user db2admin using xxxxxxx. You should successfully connect to the database. Now type db2 list tables. The following table is displayed:
    Table 1.
    Table/View Schema Type Creation time
    APPTIMESTAMP DB2ADMIN T 2007-12-03-17.26.31.265001
    BYTESTORE DB2ADMIN T 2007-12-03-17.26.31.125001
    BYTESTOREOVERFLOW DB2ADMIN T 2007-12-03-17.26.31.234003
    CUSTPROPERTIES DB2ADMIN T 2007-12-03-17.26.31.281001
    FAILEDEVENTBOTYPES DB2ADMIN T 2007-12-03-17.26.32.703003
    FAILEDEVENTDETAIL DB2ADMIN T 2007-12-03-17.26.32.796005
    FAILEDEVENTMESSAGE DB2ADMIN T 2007-12-03-17.26.32.765001
    FAILEDEVENTS DB2ADMIN T 2007-12-03-17.26.32.625002
    MEDIATION_TICKETS DB2ADMIN T 2007-12-03-17.26.35.156002
    PERSISTENTLOCK DB2ADMIN T 2007-12-03-17.26.33.984002
    RELN_METADATA_T DB2ADMIN T 2007-12-03-17.26.36.625002
    SCHEMAVERSIONINFO DB2ADMIN T 2007-12-03-17.25.24.906001
    WSCH_LMGR DB2ADMIN T 2007-12-03-17.26.37.921002
    WSCH_LMPRw DB2ADMIN T 2007-12-03-17.26.37.953002
    WSCH_TASK DB2ADMIN T 2007-12-03-17.26.37.843002
    WSCH_TREG DB2ADMIN T 2007-12-03-17.26.37.890005
    In addition to the tables listed above, there is an additional table in the schema ESBLOG, which is not shown.
  3. Optional: If you want to see a complete list of all the tables in the database, type db2 list tables for all > out.txt. You can then edit the out.txt file, which should contain the table in the ESBLOG schema and the usual catalog tables.
  4. Disconnect from the database, by typing db2 connect reset.
  5. Check that the profiles were created correctly:
    1. In a command prompt, change the current directory to INSTALLROOT\bin.
    2. Type manageprofiles –listProfiles. You should see a list of the three profiles that you just created: DMgr01, Custom01, Custom02.

Lesson 2.4: Federating nodes

Learn how to federate nodes to the cells.

In order to federate nodes to a cell perform the following steps.
Procedure
  1. Start the Deployment Manager process. At a command prompt, change the current directory to INSTALL_ROOT\profiles\DMgr01\bin then type startManager.
  2. When the start up is complete, federate node1 to the cell.
    1. Change the current directory to INSTALL_ROOT\profiles\Custom01\bin
    2. Type the command addNode localhost 8879
    Important: The port number was not needed in the previous command, because the default ports were chosen for the deployment manager. If you did change the port, you would need to specify the actual host name and SOAP connector port number of the Deployment Manager process in the addNode command. The process should complete with a successful completion message, for example:ADMU0003I: Node t60mcNode01 has been successfully federated.
  3. Repeat the federation process for the Custom02 profile.
    1. Change directories to INSTALL_ROOT\profiles\Custom02\bin
    2. Type addNode localhost 8879
    You have now federated the profiles to the cell and are ready to create the deployment environment to represent the clustered topology.



Module 3: Creating a deployment environment

This tutorial guides you through the steps to create the deployment environment that corresponds to the required clustered topology.

Expand or collapse Show details Hide details
Note: The Deployment Environment object is just a description of the topology. When you create one, you do not implicitly create all the resources that are necessary to physically implement the topology. The generation of those resources is a separate step, which we are going to illustrate later in the appropriate section of this tutorial.
At the end of this module you will be able to create a new deployment environment using the console. In order to create this environment you will need to
  1. Select a type of topology.
  2. Add nodes to the topology.
  3. Define the nodes of the three clusters.
  4. Define the databases and schemas
  5. Authenticate the database.

Lesson 3.1: Selecting a type of topology

To create a new deployment environment using the console you need to select the type of topology you want to create. As a part of this tutorial, you will create the Gold topology. To select the Gold topology, you need to go through the following steps

Procedure
  1. Open a Web browser, and direct it to the administrative console. Click Log in to open the console.
  2. On the administrative console of the deployment manager expand Servers >Deployment Environments.
  3. Launch the Deployment Environment Configuration wizard by clicking New on the Deployment Environments page.
    The system displays the first page of the Deployment Environment Configuration wizard with Create a new deployment environment selected.
    Figure 21. Creation of a new deployment environment (initial screen)
    This figure allows you to specify the deployment environment you want to create
  4. Leave the Create a new deployment environment selected, then type MyTopology in the Deployment environment name field.
  5. Select WebSphere ESB from the Runtime capability drop-down list.
  6. Click Next. The Deployment Environment Patterns window is displayed.
    Figure 22. Deployment Environment patterns window
    This figure allows you to you specify the deployment environment you want to create
  7. Click Next then select the Remote Messaging and Remote Support radio button. You are now ready to add nodes to the topology.

Lesson 3.2: Adding the nodes to the topology

This section describes the steps involved in adding the nodes to the topology you want to create.

Procedure
  1. Add the two separate nodes to the deployment environment, by clicking on the check boxes next to them, as shown in the figure.
    Figure 23. Adding Nodes to the topology
    This figure allows you to you specify the details of the nodes you want to add to the topology
  2. Click Next, then define the distribution of the members of the three clusters you want to create. In a Gold topology there are the following three clusters. For each cluster, type the number of members to configure on each node. To ensure failover across the two nodes, assign a member of each cluster to each node.
    1. The Application Deployment Target cluster. This is where you will install the modules you develop.
    2. The Messaging Infrastructure cluster. For the messaging engines.
    3. The Support Infrastructure cluster. For CEI, the Business Rules Manager and System REST services endpoints.
    Each node will run three cluster members as shown in the following figure
    Figure 24. Defining the location of the clusters
    This figure allows you to you specify the location of the clusters
  3. Click Next to display the System REST Service Endpoints panel.
    You can configure service endpoints for Representational State Transfer (REST) application programming interfaces (APIs). If you want widgets to be available in Business Space, you must configure the REST service endpoints for those widgets.
    Figure 25. Configuring System REST Service Endpoints
    System REST Services Endpoints configuration page. Use this page to configure REST services.
    1. Configure a full URL path for all REST services by selecting either https:// or http:// from the Protocol list and then typing the Host Name or Virtual Host in a Load-Balanced Environment and the Port that a client needs to communicate with the server or cluster.
  4. Click Next, to display the Database Settings panel. Before you change the database settings, you need to have an idea of how many databases you are going to need, which schemas go into the various databases, and of the credentials to use for the authentication to those databases. Your database configuration includes the following databases:
    • The common database (WPRCSDB) was created at the time that you created the Deployment Manager. Notice that the deployment environment makes no reference to the WPRCSDB.
    • The Messaging Engine DB (MEDB). You want a single database for the four Messaging Engines (a common configuration). Each messaging engine will have its schema in the database:
      • The CEIME schema for the CEI messaging engine.
      • The SCAAPP and SCASYS schemas for the SCA application and system messaging engines, respectively.
    • The EVENT database for CEI events and for the event catalog.
    The following figure shows the changes to the database and schemas parameters.
    Figure 26. Defining the databases and schemas
    This figure allows you to you define the databases and schemes
    Note: Ensure that the credentials specified for authentication match the db2admin user and password
    Note: Make sure that the Create Tables check box is checked everywhere
    Ensure that all the parameters are correct and match the figures of the previous step.
  5. Click Next. On the Security screen, use the administrator user ID and password. These settings are relevant only if security is turned on, but specify them anyway here, as in the figure:
    Figure 27. Additional Security Settings window
    This feature allows you to you specify additional security settings
    Note: This user ID is typically different from the database administrator's user ID. The user ID that needs to be specified here must be a valid user in the user registry used to authenticate users to the application server.
  6. Click Next. On the Summary panel, review the information and if everything is as expected, click Finish.
    Note: Do not click Finish and Generate at this time. You need to complete some database configuration before you can generate the environment
  7. Save your work.

Lesson 3.3: Reviewing tasks completed so far

Review what you have created so far.

To review what you have created so far
Procedure
  1. The console should now show MyTopology in the list of deployment environments. If you hover your mouse pointer over the Status icon, you can see that the status is now Not configured (as shown in the following figure). This means that the deployment environment exists, but the actual resources have not be generated yet.
    Figure 28. The Deployment Environment state is "Not Yet Configured"
    This figure shows that the Deployment Environment state is Not Yet Configured
  2. Click MyTopology to show a panel that lists a summary of the deployment environment. In particular, the panel shows the status of each of the clusters that belong to it. Because you have not generated any resources yet, the status is Not configured for every element.
    Figure 29. Details of the deployment environment before generating the resources
    This figure shows the Details of the deployment environment prior to generating the resources
    Notice, at the bottom of the panel there is a button that you can use to generate the resources.
  3. Click on Deployment Topology. A panel that describes the topology is displayed. At this time, you should see the green arrows for the nodes (the node agents are up and running), but you should still see that the status of the clusters is Not configured:
    Figure 30. Deployment environment nodes and clusters
    This figure shows the Details of the deployment environment nodes and clusters
  4. Click Cancel then click Data sources. The database configuration screen appears again, showing not only the database names and schema names we defined in the previous step, but also the JNDI name for a number of data sources. At this point, you can still make changes and save those changes in the deployment environment. Any change that you make now will be reflected on the actual resources.
  5. Click Cancel then log off.

Lesson 3.4: Completing the database configuration

In order for the deployment environment generation to succeed, you need to make sure that the database instances exist. In particular, the EVENT database must exist, or the generation will abort with an error that indicates that the database could not be found. In this section we are going to create the instances of all the necessary databases and rely as much as possible on the automatic creation of tables.

To configure the databases we have created so far:
Procedure
  1. Create the EVENT database for the CEI:
    1. Open a command prompt and issue the following command: db2cmd .
    2. On the resulting command prompt, issue: db2 create db EVENT .
      Remember: The EVENT schema and tables will be automatically created when the deployment environment gets generated
  2. Create the Business Space database
    1. On the database command prompt, issue: db2 create db WPRBSDB
  3. Create the BPEDB database.
    1. On the database command prompt, issue: db2 create db BPEDB
  4. Create the Business Process Choreographer Explorer Reporting database.
    1. On the database command prompt, issue: db2 create db OBSVRDB
  5. Create the Messaging Engine database:
    1. On the same command prompt as above, issue: db2 create db MEDB.
    Remember: The Messaging Engines, BPEDB, and Observer's schemas and tables will be automatically created when the clusters start up

Lesson 3.5: Generating and testing the deployment environment

This section will guide you through the steps involved in generating the deployment environment using the administrative console.

To generate the deployment environment, you need to :
Procedure
  1. Generate the resources for the deployment environment by going through the following steps.
    1. Go back to the administrative console. Expand Servers then click Deployment Environments.
    2. Click MyTopology. On the next screen, click Generate Environment.
    3. When the generation is complete (it can take a minute or so), save your work.
    4. Notice that the topology is now configured, and the status is Stopped, as indicated in the following figure.
      Figure 31. Deployment Environment in the Stopped Status
      This figure shows that the Deployment Environment in the Stopped State
    5. Click MyTopology. Now, the status of each of the clusters is Stopped, as shown in the following figure:
      Figure 32. Stopped Clusters in the Deployment Environment
      This figure shows Stopped Clusters in the Deployment Environment
      Notice that you can still click on Deployment Topology and Data sources, but if you make any changes there, those changes will not be reflected on the actual resources that we have already generated.
    6. Look at some of the resources that you have generated. Expand Servers then click Clusters. You should see the three clusters that you have generated, as shown in the following figure.
      Figure 33. Clusters viewed through the Usual Panel for Cluster Management
      This figure shows Clusters viewed through the Usual Panel for Cluster Management
      Each cluster has two cluster members.
    7. Click Servers > Application Servers. You should see the six servers that were generated, as shown in the following figure.
      Figure 34. Cluster Members in the Topology
      This figure shows Clusters in the topology
    8. Make sure the data sources were created. Navigate to Resources > JDBC > Data sources. You should see a list of 10 data sources.
    9. Check the service integration buses. Navigate to Service Integration > Buses. You should see the four buses shown in the following figure.
      Figure 35. SI Buses in the Topology
      This figure shows the service integration buses in the topology
    10. Finally, review the applications that were installed. Navigate to Applications > Enterprise Applications. You should see the following applications; notice that their name bears an indication of where they have been installed:
  2. Now you are ready to start the deployment environment and test some of the functions. Keep in mind that the node agent processes must be up and running for this step to be successful. Important: This step may be difficult to carry out on a single system because of memory constraints (keep in mind that we have the Deployment Manager, two Node Agents, and six application servers running on the same box). We mention these steps for illustration purposes. We suggest that you read through step 2 and then skip to step 3 for an alternative way to test the topology.
    1. Navigate to Servers => Deployment Environments. Check the check box close to MyTopology then click Start.
    2. Very quickly, the status of the Deployment Environment changes to Started, as shown in the following figure.
      Figure 36. The Deployment Environment in the Started Status
      This figure shows The Deployment Environment in the Started Status
    3. Click MyTopology. You will also see that the status of the individual clusters is Started. However, the actual servers take quite a while to start up.
    4. Navigate to Servers > Clusters. Notice that (in all likelihood) the clusters are still in the process of starting (partial start), as shown in the following figure.
      Figure 37. Clusters during startup
      This figure shows the Clusters during startup
    5. Wait a couple of minutes, and then refresh the status of the clusters. Wait until all the three clusters are up and running.
  3. Here is an alternative way to test the topology considering the memory constraints.
    1. Navigate to Servers > Application Servers. All the servers should be stopped now.
    2. Select all the servers that are configured to run on Node 1 then click Start (as shown in the following figure.
      Figure 38. Starting Only Some Members to Cope with Memory Constraints
      This figure shows how to start Only Some Members to Cope with Memory Constraints
    3. Wait a couple of minutes, and then refresh the status of the clusters. Wait until all the three clusters are up and running.
  4. Make sure that the topology is functional. First ensure that the tables for the Messaging Engines have been created.
    1. In a command prompt window, type the following command: db2cmd
    2. In the resulting command prompt window, type the following commands:
      db2 connect to MEDB user db2admin using xxxxxxx
      db2 list tables for all > out.txt 
    3. Edit the file out.txt using a text editor. You should notice that there are a number of tables in the schemas CEIME, BPCME, SCAAPP, SCASYS
      Figure 39. The table in the schema
      This figure shows the table in the schema
    4. Verify that the messaging engines are up and running. In the administrative console, navigate to Service Integration > Buses. Click the name of one of the buses
    5. Click Messaging Engines. The status is inactive, as shown in the following figure.
      Figure 40. Messaging Engine in the Started State
      This figure shows the Messaging Engine in the Started State
Congratulations, you have now generated and tested the deployment environment. In this article, you have learnt how to create a clustered "Gold" topology using a template-driven approach. First, you created the cell and federated two empty nodes to it. Then you created a deployment environment, which is a template for the clustered topology. Finally, after making some adjustments to the databases, you generated the deployment environment and tested the topology.


< Previous | Next >


tutorial Tutorial topic


Terms of use | Feedback





Timestamp icon Last updated: 21 June 2010





http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.doc/doc/ctut_buildingclusteredtopologies.html

Copyright IBM Corporation 2005, 2010. All Rights Reserved.

This information center is powered by Eclipse technology (http://www.eclipse.org).