document.doc

Creation of IBM WPS (Websphere Process Server) custom server profile with capabilities Custom Database* configuration for CEI event Upgrade / Augment WPS server profile to IBM WBM (Websphere Business Monitor). WBM is the product

for BAM (aka Business Activity Monitoring) of enterprise application. Custom Database* configuration for WBM server (i,e for BAM) so that the Application Monitor data may

be used for reporting using third party products like Actuate e.Report.

* In this case, IBM DB2 v 9.1 used as the custom database. It may be replaced with any other database products like Oracle, Informix, Microsoft SQL server etc.

Software Requirement1. IBM Websphere Integration Developer(WID) v6.1.2 2. IBM Websphere Process Server(WPS) v 6.1.23. IBM Websphere Business Monitor(WBM) v 6.1.24. IBM DB2 v9.1 (may install any other database as per your requirement)

Target Audience IBM WID-WPS developer, IBM WBM developer Application Designer and Architects. Software Installation Group Server Admin

Table of Content

1. About IBM WPS (Websphere Process Server)...............................................................................22. About IBM WBM (Websphere Business Monitor).........................................................................23. Create new IBM WPS custom server profile (& Configure DB2 database for CEI events)...........3

3.1. Look into the CEI database........................................................................................................224. Augment WPS profile with WBM capabilities (& configure DB2 database for Monitor model) 23

4.1. Look into the Monitor database.................................................................................................345. Sample Application test on the server...........................................................................................35

5.1. Import the applications..............................................................................................................355.2. Choose the correct server and deploy the modules...................................................................355.3. Run sample test cases and check the monitor data....................................................................375.4. Check the data in database and extract report...........................................................................38

Date Document Version

Change Summery Author Remark

19th Jan 2009 0.1 (Draft) Initial Document Satya Sidhartha

Change Log

1. About IBM WPS (Websphere Process Server)

1

document.doc

IBM® WebSphere® Process Server is a high-performance business engine to help form processes that meet your business goals Built on open standards; it deploys and executes processes that orchestrate services (people, information, systems, and trading partners) within your service-oriented architecture (SOA) or non-SOA infrastructure.

Extends the value of core applications and databases by centralizing business processes and sharing them across the enterprise, enabling businesses to maximize resources and increase ROI

Ensures compliance with regulations and internal requirements by that business operations run precisely as documented

Ensures process integrity to accommodate transaction intensive processes, while providing the scalability, reliability and flexibility needed for future business needs

Strong support for human workflow and enables rapid process changes, providing business agility and enabling you to leverage resources efficiently.

More about product at http://www-01.ibm.com/software/integration/wps/Help and documentation at http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/topic/com.ibm.websphere.wps.612.doc/welcome_wps.html

2. About IBM WBM (Websphere Business Monitor)

IBM WebSphere® Business Monitor is business activity monitoring (BAM) software that allows you to measure business process performance, monitor in-flight and completed processes, and report on business operations.

Provides business users access to near real-time business process information and KPIs through Web 2.0 dashboards, desktop and mobile devices.

Empowers business users to create new dashboards, KPIs and subscribe to business alerts without involving IT

Provides a comprehensive realtime view of operational processes through a high performance business activity monitoring solution for processes and applications running in disparate environments

Accelerates continuous process improvement and business innovation through a tight integration with other IBM BPM products

Enables business users to manage staff workload for better resource planning. Offers multidimensional analyses for trend analysis and problem identification

More about the product at http://www-01.ibm.com/software/integration/wbimonitor/Help and documentation at http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/index.jsp?topic=/com.ibm.btools.help.monitor.doc/home.html

3. Create new IBM WPS custom server profile (& Configure DB2 database for CEI events)

To create a new server profile, you must have installed the WPS server on your machine. When you install IBM WID, the process server gets installed by default.

Note-: By default, WPS servers use internal Derby database for CEI Event logging, Monitoring (if any) and other process related data.

2

document.doc

To create a new server profile, go to the C:\IBM\WID61\pf\wps\firststeps folder and double click on the file firststeps.bat. Assuming C:\IBM\WID61 as the installation directory for WID.

3

document.doc 4

document.doc 5

document.doc 6

document.doc 7

document.doc 8

document.doc 9

document.doc 10

document.doc 11

document.doc 12

document.doc 13

document.doc 14

document.doc 15

document.doc 16

document.doc 17

document.doc 18

document.doc 19

document.doc 20

document.doc 21

document.doc

After successful profile creation, it will display message like this.

3.1.Look into the CEI database

Now you may have a look into the CEI database created by new WPS profile on DB2 database.Use these connection properties to connect to the event database.

Driver class name------: com.ibm.db2.jcc.DB2DriverUser name----------------: db2admin (or username you have provided)Password------------------: Welcome1 (or password you have provided)Connection URL---------: jdbc:db2://localhost:50000/EVENT (replace localhost with IP of the DB2 server and port as well)

Here you can see around 33 tables being created. Among which the CEI_T_CBE_MAP table contains a listing of all of the CBE (Common Base Events or simply events) properties and what tables they can be found in. The CEI_T_EVENT (here it’s CEI_T_EVENT00) table contains all of the simple or top-level property data of a CBE.

Note-: CEI_T_EVENT00 table gets populated with CBE (i.e. events) only when you deploy application emitting event onto this server profile.

22

document.doc

4. Augment WPS profile with WBM capabilities (& configure DB2 database for Monitor model)

The profile created in the above step is a Websphere Process Server(WPS) profile. In order to deploy business monitoring application you must have Websphere Business Monitoring(WBM) capabilities.

So you must Augment the WPS server to WBM profile as well. After successful augmentation, the profile would be capable to deploy both process server module as well as the BAM enabled monitor models modules.

For that you have to install the Websphere Business Monitor (WBM, here v6.1.2) and integrate it with the WID installation. After successful installation, the server view of WID will look like this.

To create a new server profile, go to the C:\IBM\WID61\pf\wps\firststeps folder and double click on the file firststeps.bat. Assuming C:\IBM\WID61 as the installation directory for WID.

(Picture# -: )

23

document.doc 24

document.doc 25

document.doc 26

document.doc 27

document.doc 28

document.doc 29

document.doc 30

document.doc 31

document.doc 32

document.doc 33

document.doc

4.1.Look into the Monitor database

Now you may have a look into the CEI database created by new WPS profile on DB2 database.Use these connection properties to connect to the event database.

Driver class name------: com.ibm.db2.jcc.DB2DriverUser name----------------: db2admin (or username you have provided)Password------------------: Welcome1 (or password you have provided)Connection URL---------: jdbc:db2://localhost:50000/MONITOR (replace localhost with IP of the DB2 server and port as well)

34

document.doc

5. Sample Application test on the server

5.1.Create the applications

You may now create IBM WPS and WBM compliant applications and deploy them onto the newly created server. Note the WPS application should emit CBE or simply events (Which are stored into the EVENT database on DB2 as per this configuration). The events should be consumed by WBM server (using Triggers and Matrics) so that they will be persisted in MONITOR database (Here configured to DB2).

5.2.Choose the correct server and deploy the modulesNow choose the server which we have created with custom database configuration.

35

document.doc

Now we can deploy both process server modules and Business Monitor modules on this server. Right click on “WebSphere Business Monitor Server v6.1 on WebSphere Process Server” and click on “Add and Remove Projects”. Select deploy both the modules.

36

document.doc

5.3.Run sample test cases and check the monitor data.If you test run the module, the module will emit CBE events and those events get stored into EVENT

database tables. As we have also enabled BAM using the IBM WBM, those events also goes to MONITOR database. (The database structure is diff for both and the later one is more suitable for reporting purpose while the former one is more suitable for event logging purpose).

To test, open assembly diagram of the Clawback_Process_Merge, select the Clawback_Eligibility component, right click on that and choose the “Test Component” option.

37

document.doc

You may run couple of test cases similar to this so that the database could be populated with more data.

5.4.Check the data in database and extract reportNow check the MONITOR database for the process monitoring data.

38

document.doc 39