Creating a Decision Server Events runtime in WebSphere Operational Decision Management V7.5, Part 1: Configuring a standalone environment

This two-part series describes how to create a Decision Server Events environment in WebSphere® Operational Decision Management V7.5. Part 1 takes you through the steps for building a standalone environment. Part 2 will go through the steps for building a highly available and scalable environment. This content is part of the IBM Business Process Management Journal.

Share:

Shenfu (Mike) Fan (sfan@us.ibm.com), Certified IT Architect and IT Specialist, IBM

Photo of Shenfu (Mike) FanShenfu (Mike) Fan is a Senior Managing Consultant with IBM Software Services for WebSphere (ISSW). He is primarily focused on architectural design, development, and implementation of enterprise application integration solutions using WebSphere products that include WebSphere Message Broker, WebSphere MQ, WebSphere Business Events, WebSphere Service Registry and Repository, WebSphere ESB, and others.


developerWorks Contributing author
        level

Tim Galvin (tgalvin@us.ibm.com), Software Developer, IBM

Tim Galvin photoTim Galvin is a Software Developer with the IBM WebSphere Business Events development team in the Littleton Software Lab in MA. He previously worked as a senior consultant, leading customers in the architecture, design, and implementation of WebSphere Business Events solutions.



12 December 2012

Also available in Chinese

Introduction

WebSphere Operational Decision Management (hereafter called ODM) enables businesses to respond to real-time data with intelligent, automated decisions. It consists of two complementary components, Decision Server Rules and Decision Server Events. Depending on business data types and business requirements, Decision Server Events can be used to provide decision management services. Because Decision Server Events is the new version of WebSphere Business Events, WebSphere Business Events V7 users may want to migrate their solutions to ODM to leverage new tools and features.

You can configure either a standalone or highly available and scalable Decision Server events environment. A standalone environment using a single server is the simplest topology to configure and manage. However, this topology should only be used in a development or test environment because it is not highly available or scalable. In this article, we'll step through the process of installing and configuring a standalone Decision Server events environment, including Business Space.

To benefit from this article, readers should have a fundamental understanding of WebSphere ODM and WebSphere Application Server products. For more information on these products, see Resources.


Creating a Decision Server Events runtime

We're going to build a standalone Decision Server Events runtime (hereafter called event runtime) on a Windows® XP machine. The event runtime is a shared, secured location that contains assets such as data connections, business objects, events, and actions. WebSphere MQ is used for the JMS provider and DB2® for the event runtime repository. Though ODM, MQ and DB2 are all installed on one machine for the sake of simplicity, in the real world, MQ and DB2 servers may be hosted on different machines for performance reasons. Table 1 lists the prerequisite software and installation information.

Table 1. Software installation information
SystemParameterValue
WebSphere ODMVersion
Host
Install_Dir
WAS_Dir
UserID
7.5
localhost
C:\IBM\WODM75
C:\IBM\WODM75\WAS
admin
WebSphere MQVersion
Host
Install_Dir
UserID
7.0.1
localhost
C:\IBM\MQV70
admin
DB2Version
Host
Install_Dir
Server_Port
UserID
9.7
localhost
C:\IBM\SQLLIB
50000
admin

Before creating the event runtime, you need to create a database and a queue manager as follows:

  1. Create a database called DSEDB1 by entering the following DB2 Command Line Processor (CLP) command:
    db2 create database DSEDB1 using codeset UTF-8 territory us PAGESIZE 32768
  2. Create a queue manager DSEQM1 along with a listener and pub/sub JMS objects using the following commands:
    crtmqm DSEQM1
    strmqm DSEQM1
    echo DEFINE LISTENER('DSEQM1_TCP') TRPTYPE(TCP) PORT(2414) CONTROL(QMGR) 
    	| runmqsc DSEQM1
    runmqsc DSEQM1 < C:\IBM\MQV70\java\bin\MQJMS_PSQ.mqsc

After the database and queue manager are successfully created, follow the steps below to build a standalone event runtime by creating a new Decision Server events application server profile using the Profile Management tool:

  1. Run pmt.bat in the directory C:\IBM\WODM75\WAS\bin\ProfileManagement to open the Profile Management tool.
  2. On the Welcome page, click Launch Profile Management Tool and then click Create.
  3. On the Environment Selection page, select Application server profile augmented with WebSphere Operational Decision Management Decision Server events under WebSphere Operational Decision Management, as shown in Figure 1.
    Figure 1. Select the environment
    Select the environment

    It is worth mentioning that the profile augmentation with Operational Decision Management Decision Server Events has a dependency on WebSphere eXtreme Scale profile augmentation which is invoked automatically. Generally you don't have to worry about that, unless there is some issue with the WebSphere eXtreme Scale installation.

  4. On the Profile Creation Options page, select Typical profile creation.
  5. On the WebSphere Decision Server Events Installation Location page, specify a fully-qualified ODM product installation location, as shown in Figure 2.

    Figure 2. Specify product installation location
    Specify product installation location
  6. On the Administrative Security page, enable administrative security and provide a user name and password, as shown in Figure 3.
    Figure 3. Enable administrative security
    Enable administrative security
  7. On the Database Configuration page, select the database manager IBM DB2(R) Universal Database. Then specify a database name of DSEDB1, make sure that the location for the JDBC driver file is correct, and provide a user name and password, as shown in Figure 4.
    Figure 4. Configure database
    Configure database
  8. On the Messaging Provider Configuration page, select the messaging provider WebSphere MQ JMS messaging, provide a queue manager name, host name and port number, and select Bindings for WebSphere MQ transport type, as shown in Figure 5.
    Figure 5. Configure messaging provider
    Configure messaging provider
  9. On the Profile Creation Summary page, click Create to create the new profile.
  10. After the profile creation is completed, click Finish, and exit the Profile Management tool.

To verify that the event runtime is successfully created, start the application server and open the administrative console. You should see the following:

  • A WebSphere application server server1 under Servers =>Server Types => WebSphere application servers.
  • A WebSphere enterprise application wberuntimeear under Applications => Application Types => WebSphere enterprise applications.
  • A data source Event Runtime Datasource under Resources => JDBC => Data sources
  • A set of JMS objects, such as topic connection factory WbeTopicConnectionFactory under Resources => JMS => Topic connection factories, topics eventTopic and actionTopic under Resources => JMS => Topics, and an activation specification wbe_events under Resources => JMS => Activation specifications.
  • A set of custom properties under Resources => Resource Environment => Resource environment entries => WbeSrv01 => Custom properties, as shown in Figure 6.
    Figure 6. The event runtime custom properties
    The event runtime custom properties

In DB2 Control Center, open the DSEDB1 database. You should see a set of tables for the event runtime repository, as shown in Figure 7.

Figure 7. Tables for the event runtime repository
Tables for the event runtime repository

Configuring Business Space

ODM provides a set of Decision Server events widgets for users to perform the event logic tests. In order to use these widgets, you need to configure the Business Space in which the widgets run.

You create a standalone Business Space environment by augmenting the WODMSrv01 profile using the Profile Management tool as follows:

  1. Run pmt.bat under the C:\IBM\WODM75\WAS\bin\ProfileManagement directory to open the Profile Management tool.
  2. On the Welcome page, click Launch Profile Management Tool.
  3. Select the WODMSrv01 profile and click Augment, as shown in Figure 8.
    Figure 8. Select the profile to augment
    Select the profile to augment
  4. On the Augment Selection page, select Standalone Business Space powered by WebSphere, as shown in Figure 9.

    Figure 9. Select the augment to apply to the profile
    Select the augment to apply to the profile
  5. On the Profile Augmentation Options page, select Advanced profile augmentation.
  6. On the Administrative Security page, enable administrative security and specify the user name and password.
  7. On the Database Design page, click Next to continue.
  8. On the Database Configuration page (Part 1), select DB2 Universal Database as the database product, and change the database name from the default of BSPACE to DSEDB1, as shown in Figure 10. The Business Space shares the DSEDB1 database with the event runtime repository.
    Figure 10. Configure the database - Part 1
    Configure the database - Part 1
  9. On the Database Configuration page (Part 2), enter the user name/password, and the database server host name, as shown in Figure 11.
    Figure 11. Configure the database - Part 2
    Configure the database - Part 2
  10. On the Profile Augmentation Summary page, click Augment.
  11. After the profile augmentation is complete, click Finish, then exit the Profile Management tool.

In the administrative console, under Applications => Application Types => WebSphere enterprise applications, you should see the following applications installed for Business Space:

  • BSpaceEAR_VMXP03Node01_server1
  • BSpaceForms_VMXP03Node01_server1
  • BSpaceHelp_VMXP03Node01_server1
  • PageBuilder2_VMXP03Node01_server1
  • mm.was_VMXP03Node01_server1

In DB2 Control Center, open the DSEDB1 database. You should see a set of tables for Business Space, as shown in Figure 12.

Figure 12. Tables for Business Space
Tables for Business Space

Installing Decision Server events widgets

The following widgets are available for Decision Server events:

  • Event Tester widget
  • Event Capture widget
  • Event Replay widget

To install the event widgets, start the application server if it is not already started, and run the following commands:

C:\IBM\WODM75\WAS\AppServer\profiles\WODMSrv01\bin>wsadmin -lang jython -conntype NONE
wsadmin>AdminTask.installBusinessSpaceWidgets(['-nodeName','VMXP03Node01',
                                               '-serverName','server1',
                                               '-widgets','C:/IBM/WODM75/WODM/widgets'])
wsadmin>AdminConfig.save()
wsadmin>exit

In the administrative console, under Applications => Application Types => WebSphere enterprise applications, you should see the following applications for the event widgets installed:

  • capturereplaywidgets_VMXP03_server1
  • cahrtwidgets_VMXP03_server1
  • testerwidget_VMXP03_server1

Installing the WBETester application

In order to run the Event Tester widget, you need to install the WBETester application by running the following script.

C:\IBM\WODM75\WODM\config\was>standalone_install_ute.bat admin

Note: admin is the primary administrative user for WebSphere Application Server.

Since the script uses properties in the setenv files, before running the script, you need to verify setenv.bat in the C:\IBM\WODM75\WODM\config\was directory, and modify it if necessary to ensure that the application server and MQ settings are specified as listed below.

set WASHOME=C:\IBM\WODM75/WAS/AppServer
set WASADMINHOST=localhost
set WASBOOTSTRAPPORT=2809
set WASPROFILE=WODMSrv01
set WASSERVER=server1
set WBEHOME=C:\IBM\WODM75\WODM
set WASWCPORT=9080
set MQMANAGERNAME=DSEQM1
set MQPORT=2414
set MQTRANSTYPE=BINDINGS

You also need to verify the setenv.bat file in the C:\IBM\WODM75\WODM\config\db directory and make sure that the database settings are specified as listed below:

set DBTYPE=DB2_Universal
set DBHOST=localhost
set DBPORT=50000
set DBNAME=DSEDB1
set JDBCDRIVERPATH=C:\IBM\SQLLIB\java\db2jcc.jar
set WBEHOME=C:\IBM\WODM75\WODM

After you run the standalone_install_ute script, the wbetesterear application is installed and the event runtime property called as.director.bet.inst is created and set to true. If wbetesterear is not installed, when you start Business Space you'll see an error indicating that the event runtime is unavailable.

In addition, to use Business Space widgets to monitor events, actions, filters, and data in real time, you need to make sure that the event runtime is configured to record history by setting the following event runtime properties:

as.director.server.history.enableModule = true
as.director.server.history.enableRecording = true

Refer to Configuring the event runtime to record history in the WebSphere Operational Decision Management Information Center for more information.


Verifying the event runtime environment

Start the application server and complete the following steps to verify the event runtime environment:

  1. Download the MeterReadings event project from the ODM Information Center. In the MeterReadings project, the current and previous values of meter readings are compared. If the latest meter reading is less than the previous one, an action is triggered.
  2. Open the Event Designer and import the project into the Event Explorer, as shown in Figure 13.
    Figure 13. Import the event project
    Import the event project
  3. On the Event runtimes tab, right-click in the view to open the New runtime connection menu. Provide connection information and click Finish to create a runtime connection, as shown in Figure 14.
    Figure 14. Create new runtime connection
    Create new runtime connection
  4. Right-click the MeterReadings event project to open the context menu and click Deploy, as shown in Figure 15.
    Figure 15. Deploy an event project
    Deploy an event project
  5. Select Deploy all assets and click Next.
  6. Select to use the known runtime localhost:9080 and then click Finish. You should see the message "Successfully deployed project to runtime". The deployed event project objects are shown in Figure 16.
    Figure 16. Deployed event project in runtime
    Deployed event project in runtime
  7. Open the Business Space and select the Event Testing widget.
  8. Click Select Event Template to get the New meter reading event template.
  9. Enter 12345 for the customer ID and 1000 for the meter reading field.
  10. Click Send Event to send the event, as shown in Figure 17.
    Figure 17. Send an event
    Send an event
  11. Send another event with the same customer ID and a meter reading of 800.
  12. Open the Action tab. You should see an action like that in Figure 18. This means that the event flow was successfully processed by the event runtime.
    Figure 18. Generated action
    Generated action

Conclusion

In this article, we walked you through the steps to create a standalone Decision Server events environment for development or test purposes, including creating the event runtime, Business Space and event widgets. We also ran a simple test to verify the environment by sending events and receiving actions through the Event Testing widget on Business Space.

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 Business process management on developerWorks


static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Business process management, WebSphere
ArticleID=851048
ArticleTitle=Creating a Decision Server Events runtime in WebSphere Operational Decision Management V7.5, Part 1: Configuring a standalone environment
publish-date=12122012