Building a WebSphere Business Events Infrastructure, Part 1: Augmenting a Business Space in a WebSphere Business Events clustered infrastructure

This series covers recommendations and techniques for implementing a highly available, highly scalable WebSphere Business Events infrastructure. Part 1 provides a step-by-step guide to augmenting a Business Space in a WebSphere Business Events clustered environment. This content is part of the IBM Business Process Management Journal.

Paul Faulkner, Senior IT Specialist, IBM

Paul Faulkner photoPaul Faulkner is a Certified IT Specialist with IBM Software Services for WebSphere, specializing in system integration. Paul has designed and implemented complex integration patterns, including policy-driven Enterprise Service Bus (ESB) and solutions involving complex business event processing. Paul has over 20 years experience in IT with the majority of time spent developing middleware solutions. He has presented at multiple conferences. You can contact Paul at pfaulkn@us.ibm.com.



Wilson Fievre (wilsonf@us.ibm.com), Senior IT Solution Architect, IBM

Wilson Fievre is a Senior IT Solution Architect with IBM Software Services for WebSphere, where he focuses on Enterprise Integration Middleware Technology (Messaging) and Service-Oriented Architecture (SOA). Wilson is an active contributor to WebSphere Message Broker, and the author of the WebSphere Message Broker Transaction Tracking Monitor solution that led to the WebSphere Message Broker Event Monitor component. He has over 17 years of industry experience in defining and implementing technical architectures, leading development teams through complete project lifecycles, software development, consulting and mentoring, and is a frequent conference presenter.



19 January 2011

Introduction

The content of this article is based on IBM studies and research to implement a complex event processing solution for a Fortune 500 company. The article is Part 1 of a series that discuss topics associated with the best approaches and techniques for implementing a highly available, highly scalable WebSphere Business Events infrastructure using WebSphere MQ Server V7 as the messaging backbone to interact with WebSphere Message Broker.

When configuring and setting up Websphere Business Events (hereafter called Business Events), one of the steps is to augment the Business Events profile with Business Space. The Business Events Information Center provides instructions on how to augment a Business Events profile with Business Space for a standalone Business Events server. In this article, we'll describe the steps required to augment a Business Space in a Business Events clustered environment.

All sample commands demonstrated in this article are based on WebSphere Business Events V7.0.1 and WebSphere Application Server V7.0.0.7.


Infrastructure overview

Figure 1 shows an example of a highly available and scalable Business Events infrastructure cluster configured horizontally with two physical machines. The Business Events data store and Business Space tables are configured remotely and reside in third machine.

Figure 1. Business Events infrastructure cluster example
Business Events infrastructure cluster example

The Business Events cluster resides inside a WebSphere Application Server (hereafter Application Server) cell. A Business Events Service Integration Bus with one active message engine uses WebSphere MQ as the JMS provider. The Business Events cluster is augmented with Business Space.

The following sections detail the steps for augmenting Business Events with Business Space.


Prerequisites and set-up

These instructions assume you have previously installed the Business Events runtime into an Application Server cluster called WBECluster. You can define the cluster with a name of your choice, just make sure to change the properties in the instructions below to reflect the name used.

Note: Defining a cluster is beyond the scope of this document. Refer to the WebSphere Application Server Information Center or the WebSphere Business Events Information Center for more information.


Step 1: Augment the Deployment Manager profile with the Business Space template for Business Events

  1. Log in to the machine hosting your Deployment Manager as root
  2. Make a backup copy of the following file.
    /opt/IBM/WBE701/WAS/BusinessSpace/config.bspace/MetadataFiles/BSpace_DB2-distributed.properties
  3. Modify the original file as follows, substituting your implementation-specific information for the items in italics.
    # ====> Set wasHome to the WAS install root directory <====
    wasHome=/opt/IBM/WBE701/WAS 
    … 
    #====> Set databaseUser to the user ID of a user with database privileges <==== 
    databaseUser=db2inst1
    …
    # Properties used to create the data source 
    # - serverName
    # ====> Set serverName to the name of the database server host<====
    serverName=your DB server name 
    # - Set portNumber to the database server port
    portNumber=60000
    … 
    #====> Set db2universal_jdbc_driver_path to appropriate directory<====
    db2universal_jdbc_driver_path=/opt/IBM/WBE701/WAS/universalDriver_wbi/lib
    # - universal_jdbc_driver_path identifies the location of db2jcc_license_cu.jar # 
    ====> Set universal_jdbc_driver_path to the appropriate directory<====
    universal_jdbc_driver_path=/opt/IBM/WBE701/WAS/universalDriver/lib
  4. From the Application Server install/bin directory, issue the following command:
    ./manageprofiles.sh -augment -profileName Dmgr01
    -templatePath
    "/opt/IBM/WBE701/WAS/profileTemplates/BusinessSpace/dmgr.bspace"
    -cellName conaix11Cell01 -nodeName
    conaix11CellManager01 -bspacedbDesign
    /opt/IBM/WBE701/WAS/BusinessSpace/config.bspace/MetadataFiles/BSpace_DB2-
    distributed.properties -dbDelayConfig true
  5. You should see the following response:
    NSTCONFSUCCESS: Profile augmentation succeeded.

Note that we are opting to delay the database configuration (-dbDelayConfig true). This is necessary because our business space database is in a remote location.


Step 2: Install Business Space components

  1. Log in to the machine hosting your Deployment Manager.
  2. From the Application Server install/bin directory, start the the administration configuration tool by issuing the command: wsadmin.sh.
  3. Issue the following command to install the Business Space components: $AdminTask installBusinessSpace {-clusterName WBECluster}
  4. Save the changes by typing the command: $AdminConfig save.
  5. Issue the following command to configure the database scripts and JDBC resources:
    $AdminTask configureBusinessSpace {-clusterName WBECluster -bspacedbDesign
    /opt/IBM/WBE701/WAS/BusinessSpace/config.bspace/MetadataFiles/BSpace_DB2-distributed.properties}
  6. Save the changes by entering the command: $AdminConfig save.
  7. Type quit to exit the administration tool.

Step 3: Verify the installation

  1. Change to the Deployment Manager profile directory. You should now see both a BusinessSpace directory and a dbscripts directory.
  2. The dbscripts directory contains several scripts and SQL configuration files that are required to build the Business Space Parms database on the remote database server, as shown below:
    [root@conaix11]/opt/IBM/WBE701/WAS/profiles/Dmgr01/dbscripts/BusinessSpace/
    WBECluster/DB2/BSPACE> ls -l
    total 160
    -rw-r--r--    1 root     system         2351 Sep 17 15:00 configBusinessSpaceDB.bat
    -rwxr-xr-x    1 root     system         2638 Sep 17 15:00 configBusinessSpaceDB.sh
    -rw-r--r--    1 root     system         1945 Sep 17 15:00 createDBTables.bat
    -rwxr-xr-x    1 root     system         1574 Sep 17 15:00 createDBTables.sh
    -rw-r--r--    1 root     system          984 Sep 17 15:00 createDatabase.sql
    -rw-r--r--    1 root     system         3044 Sep 17 15:00 createGrant.sql
    -rw-r--r--    1 root     system         1099 Sep 17 15:00 createSchema.sql
    -rw-r--r--    1 root     system        18997 Sep 17 15:00 createTable.sql
    -rw-r--r--    1 root     system         1881 Sep 17 15:00 createTables_BusinessSpace
    .sql
    -rw-r--r--    1 root     system         2119 Sep 17 15:00 createTablespace.sql
    -rw-r--r--    1 root     system         1122 Sep 17 15:00 dropSchema.sql
    -rw-r--r--    1 root     system         2082 Sep 17 15:00 dropTable.sql
    -rw-r--r--    1 root     system         1926 Sep 17 15:00 migrateSchema.bat
    -rw-r--r--    1 root     system         2232 Sep 17 15:00 migrateSchema.sh
    -rw-r--r--    1 root     system         1509 Sep 17 15:00 upgradeSchemaTables.bat
    -rw-r--r--    1 root     system         1270 Sep 17 15:00 upgradeSchemaTables.sh
  3. Copy the dbscripts directory to the server that hosts your databases.
  4. Log in to your Deployment Manager administrative console and verify that the Business Space applications have been deployed, as shown in Figure 2.
    Figure 2. Verify Business Space application deployment
    Verify Business Space application deployment
  5. Also in the administrative console, verify that the JDBC resources have been defined, as shown in Figure 3.
    Figure 3. Verify that JDBC resources are defined
    Verify that JDBC resources are defined

Step 4: Configure the database

  1. If you didn't already do so, copy the dbscripts files to your database server.
  2. Log in to the database server using an ID authorized to create databases.
  3. Run the configBusinessSpaceDB script using the createDB option to automatically create the database:
    /home/db2inst1/scripts/BSPACE> ./configBusinessSpaceDB.sh createDB. You'll be prompted to provide the user ID and password of the database manager.
  4. To apply the changes, restart each of the WebSphere Application Servers on which Business Space is running.
  5. After restarting the Application Servers, you should notice that all the Business Space applications are now running in the administrative console, as shown in Figure 4.
    Figure 4. Business Space applications running in the console
    Business Space applications running in the console

This concludes the configuration process for Business Space. You can now log in to your business space and utilize the Business Events widgets. The standard location to log in to Business Space (assuming Security is not configured) is http://hostname:9080/mum/resources/bootstrap/login.jsp


Troubleshooting

Following are some potential errors and recommendations for how to correct them.

Errors during augment step

Error:
<message>[C:\Program Files\WBE701\WAS\profileTemplates\BusinessSpace\dmgr.bspace] is not a valid profile template.</message>

Solution:
Ensure that your path name is correct and the dmgr.bspace template is present.

Error:
<message>Current mode is:augment. It is possible that the augmenting template(s) being applied to [WbeSrv01] have already been applied or that the profile WbeSrv01 does not exist.</message>

Solution:
Verify that the BSpace_DB2-distributed.properties file has been modified to accurately represent your environment.

Errors during the install business space components step

Error:
WASX7015E: Exception running command: ">$AdminTask installBusinessSpace {-clusterName myCluster}"; exception information: com.ibm.bsf.BSFException: error while eval'ing Jacl expression

Solution:
Verify that the cluster name specified is correct and has been created without any issues. Verify that the cluster starts without errors.


Conclusion

You've now learned the detailed steps required to augment a Business Space in a WebSphere Business Events clustered environment!

Resources

Comments

developerWorks: Sign in

Required fields are indicated with an asterisk (*).


Need an IBM ID?
Forgot your IBM ID?


Forgot your password?
Change your password

By clicking Submit, you agree to the developerWorks terms of use.

 


The first time you sign into developerWorks, a profile is created for you. Information in your profile (your name, country/region, and company name) is displayed to the public and will accompany any content you post, unless you opt to hide your company name. You may update your IBM account at any time.

All information submitted is secure.

Choose your display name



The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerWorks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

Required fields are indicated with an asterisk (*).

(Must be between 3 – 31 characters.)

By clicking Submit, you agree to the developerWorks terms of use.

 


All information submitted is secure.

Dig deeper into WebSphere on developerWorks


static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=WebSphere, Business process management
ArticleID=608277
ArticleTitle=Building a WebSphere Business Events Infrastructure, Part 1: Augmenting a Business Space in a WebSphere Business Events clustered infrastructure
publish-date=01192011