Process Integrator Deployment on IBM Webspher Application Server Cluster

(1)

White Paper

Abstract

This paper describes how to deploy EMC Documentum Process Integrator on Websphere application server clustered setup. Process Integrator provides inbound messaging capabilities to applications based on the Documentum platform, enabling them to exchange documents and information with people outside the organization. February 2012

Process Integrator Deployment on IBM

Webspher Application Server Cluster

A user guide for deploying Process integrator on websphere

application server 7.0.0.9 cluster

(2)

EMC believes the information in this publication is accurate of its publication date. The information is subject to change without notice.

The information in this publication is provided “as is.” EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

VMware is a registered trademark of VMware, Inc. All other trademarks used herein are the property of their respective owners.

(3)

About this Document

This guide outlines the ideal way to successfully install and configure DocumentumProcess Integrator on IBM WebSphere Application Server 7.0.0.9 clustered environment to enable high availability and load balancing. The volume of incoming requests is high in a production environment and can be handled in an efficient manner if Process Integrator application is deployed in a clustered environment.

Audience

This white paper is intended for administrators and developers who deploy Process Integrator on IBM Websphere application server clustered setup. This document contains step by step procedure to Deploy and configure the Process Integrator in Clustered setup for achieving High availability and load balancing.

Introduction

This guide discusses how high availability and load balancing can be achieved for Process Integrator when it is deployed on IBM WebSphere Application Server 7.0 clustered environment.

The process of installing and configuring IBM WebSphere Application Server 7.0 on a single machine in a clustered environment involves the following steps:

 Installing IBM WebSphere Application Server Network Deployment 7.0  Installing IBM Update Installer for WebSphere 7.0.0.9

 Installing IBM HTTP Server

 Configuring IBM WebSphere Application Server in a cluster

 Deploying and Configuring Documentum Process Integrator in a cluster

Please refer the following while paper for installing and configuring IBM WebSphere Application Server 7.0.0.9 clustered environment:

Deploying Documentum Business Activity Monitor on IBM Websphere Application Server Cluster.

http://powerlink.emc.com/km/live1/en_US/Offering_Technical/White_Paper/h8260-deploy-business-activity-monitor-server-wp.pdf

(5)

Installing Process Integrator WAR file in Cluster Setup

Download Process Integrator (bps.war) file for WAS(IBM JDK) from Download center . 1. ave the bps.war file in one of the temp folder

2. Open admin console for Deployment manager

3. Expand Applications, Application Type and Click Websphere enterprise applications 4. Click on Install Button.

(6)

6 Process Integrator Deployment guide on IBM WAS cluster 6. Select Detailed –Show all installation option and parameters Option and Click on Next

(7)

8. Select “Precompile javaserver pages files” Enter the application name as “bps” Click NEXT

(8)

8 Process Integrator Deployment guide on IBM WAS cluster 9. Select the bps.war by clicking checkbox and also select Cluster1 and Webserver1

(9)

(10)

10 Process Integrator Deployment guide on IBM WAS cluster 11. Enter the JDK Source Level as 15 click Next

(11)

(12)

12 Process Integrator Deployment guide on IBM WAS cluster 13. Click Next button

(13)

(14)

14 Process Integrator Deployment guide on IBM WAS cluster 15. Click Next

(15)

(16)

16 Process Integrator Deployment guide on IBM WAS cluster 17. Enter the Context root as bps and click Next

(17)

(18)

18 Process Integrator Deployment guide on IBM WAS cluster 19. click on save link

(19)

20. Click on bps link

(20)

20 Process Integrator Deployment guide on IBM WAS cluster 22. Click on bpw.war link

23. Select “Class Loaded with local class loader first(Parent last)” option from class loader order mad Click OK

(21)

24. Click on save link 25. Navigate to location <IBM Installed Directory>

\WebSphere\AppServer\profiles\AppSrv01\installedApps\TCMQAW2K3ORA040Cell01\bps.ear \bps.war\WEB-INF\classes

(22)

22 Process Integrator Deployment guide on IBM WAS cluster 26. Edit dfc.properties file as below

27. Edit bps_template.xml file as below dfc.data.dir=c:/dfc_data_dir01

dfc.globalregistry.repository=<Docbase name> dfc.globalregistry.password=<Encrypted password> dfc.globalregistry.username=<Global registry user name> dfc.docbroker.host[0]=<docbroker host ip/name>

dfc.docbroker.port[0]= <docbroker port>

<?xml version="1.0"?> <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <polling_interval>30</polling_interval> <message_store_home_dir>C:\\dfc_data_dir01\\message_store</message_store_hom e_dir> <instance_name>bps1</instance_name> <ha_enabled>TRUE</ha_enabled> <config_properties>

</config_properties> <connections>

<docbase-connection>

<docbase> Docbase name </docbase> <user> Docbase user</user>

<password> Docbase user password </password> <domain/>

</docbase-connection> </connections>

(23)

28. Edit the log4j.properties file as below 29. Navigate to location log4j.rootCategory=WARN, A1, F1 log4j.category.MUTE=OFF #--- CONSOLE --- log4j.appender.A1=org.apache.log4j.ConsoleAppender log4j.appender.A1.threshold=ERROR log4j.appender.A1.layout=org.apache.log4j.PatternLayout log4j.appender.A1.layout.ConversionPattern=%d{ISO8601} %5p [%t] [%c] - %m%n #--- FILE --- log4j.appender.F1=org.apache.log4j.RollingFileAppender log4j.appender.F1.File=C:/dfc_data_dir01/logs/bps-all.log log4j.appender.F1.MaxFileSize=5MB log4j.appender.F1.layout=org.apache.log4j.PatternLayout log4j.appender.F1.layout.ConversionPattern=%d{ISO8601} %5p [%t] [%c] - %m%n #---bps--- log4j.logger.com.documentum.bpm=WARN, bpsappender log4j.logger.com.documentum.bps=WARN, bpsappender

#--- if you like to enable debugging for any specific package e.g. ftp --- #log4j.logger.com.documentum.bps.ftp=DEBUG, bpsappender log4j.additivity.com.documentum.bpm=false log4j.additivity.com.documentum.bps=false log4j.appender.bpsappender=org.apache.log4j.RollingFileAppender log4j.appender.bpsappender.File=C:/dfc_data_dir01/logs/bps.log log4j.appender.bpsappender.MaxFileSize=2MB log4j.appender.bpsappender.layout=org.apache.log4j.PatternLayout log4j.appender.bpsappender.layout.ConversionPattern=%d{ISO8601} %5p [%t] [%c] - %m%n

#---if you like to turn off logging from a specific package --- #log4j.logger.com.documentum.bps.dql.inbound.runtime.DQLPoller=OFF

(24)

24 Process Integrator Deployment guide on IBM WAS cluster 30. Edit dfc.properties file as below

31. Edit bps_template.xml file as below dfc.data.dir=c:/dfc_data_dir02

dfc.globalregistry.repository=<Docbase name> dfc.globalregistry.password=<Encrypted password> dfc.globalregistry.username=<Global registry user name> dfc.docbroker.host[0]=<docbroker host ip/name>

dfc.docbroker.port[0]= <docbroker port>

<?xml version="1.0"?> <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <polling_interval>30</polling_interval> <message_store_home_dir>C:\\dfc_data_dir02\\message_store</message_store_hom e_dir> <instance_name>bps2</instance_name> <ha_enabled>TRUE</ha_enabled> <config_properties>

</config_properties> <connections>

<docbase-connection>

<docbase> Docbase name </docbase> <user> Docbase user</user>

<password> Docbase user password </password> <domain/>

</docbase-connection> </connections>

(25)

32. Edit the log4j.properties file as below log4j.rootCategory=WARN, A1, F1 log4j.category.MUTE=OFF #--- CONSOLE --- log4j.appender.A1=org.apache.log4j.ConsoleAppender log4j.appender.A1.threshold=ERROR log4j.appender.A1.layout=org.apache.log4j.PatternLayout log4j.appender.A1.layout.ConversionPattern=%d{ISO8601} %5p [%t] [%c] - %m%n #--- FILE --- log4j.appender.F1=org.apache.log4j.RollingFileAppender log4j.appender.F1.File=C:/dfc_data_dir02/logs/bps-all.log log4j.appender.F1.MaxFileSize=5MB log4j.appender.F1.layout=org.apache.log4j.PatternLayout log4j.appender.F1.layout.ConversionPattern=%d{ISO8601} %5p [%t] [%c] - %m%n #---bps--- log4j.logger.com.documentum.bpm=WARN, bpsappender log4j.logger.com.documentum.bps=WARN, bpsappender

#--- if you like to enable debugging for any specific package e.g. ftp --- #log4j.logger.com.documentum.bps.ftp=DEBUG, bpsappender log4j.additivity.com.documentum.bpm=false log4j.additivity.com.documentum.bps=false log4j.appender.bpsappender=org.apache.log4j.RollingFileAppender log4j.appender.bpsappender.File=C:/dfc_data_dir02/logs/bps.log log4j.appender.bpsappender.MaxFileSize=2MB log4j.appender.bpsappender.layout=org.apache.log4j.PatternLayout log4j.appender.bpsappender.layout.ConversionPattern=%d{ISO8601} %5p [%t] [%c] - %m%n

#---if you like to turn off logging from a specific package --- #log4j.logger.com.documentum.bps.dql.inbound.runtime.DQLPoller=OFF

(26)

26 Process Integrator Deployment guide on IBM WAS cluster 33. Open Admin console of Dmgr

34. Start the bps application by selecting the check box

35. Access the URLs

a. http:// <App Server 01 host> : <http port>/bps/inbound_details.jsp Example : http://localhost:9082/bps/inbound_details.jsp

(27)

b. http:// <App Server 02 host> : <http port>/bps/inbound_details.jsp Example : http://localhost:9083/bps/inbound_details.jsp

c. http:// <HTTP Server host> : <http port>/bps/inbound_details.jsp Example : http://localhost:80/bps/inbound_details.jsp

To View the Listeners started for the processes use specific Application server host and port for example :

To access listener page :

a. http:// <App Server 01 host> : <http port>/bps/lsnrs.jsp Example : http://localhost:9082/bps/lsnrs.jsp

b. http:// <App Server 02 host> : <http port>/bps/lsnrs.jsp Example : http://localhost:9083/bps/lsnrs.jsp

Using a script to set Listener table attributes

NOTE : Since HTTP server configured for load balancing, the incoming requests are routed to the application servers depending on the algorithm configured in HTTP server.

User should configure the HTTP and Web service inbound Listeners in process Integrator to run in all instances.

1. Download bpsInboundTools .zip for windows and .tar file for Unix 2. Extract the compressed file into a temp folder

3. Locate the setValuesInListenerTable .bat/.sh file in the bin directory in temp folder. The script contains the following text:

echo off

REM ** Point the DFC_CONFIG_DIR to the same location as the one pointed to by Inbound Framework **

REM ** Point JAVA to the java executable ** set DFC_CONFIG_DIR=

set JAVA= echo on

(28)

28 Process Integrator Deployment guide on IBM WAS cluster 4. In this script Set following

Set the DFC_CONFIG_DIR to the directory containing the [dfc.properties] Set JAVA to the java executable directory.

5. Create the listener text file.

The template file setValues_listener_template.txt, located in bin directory should be edited to contain the settings for the process name, activity name, preferred instance and

run_in_all_instances fields.

Preferred Instance Name is the name of the instance that is designated as the preferred instance for the listener. Run In All Instances is set to true or false. If specified as true, the listener can run in any running instance. If not specified, default is false and the listener can run only in one inbound instance.

Note: Do not run listeners for asynchronous protocols on multiple Process Integrator

instances. The run_in_all_instances value must remain 0 for asynchronous protocols listeners like FTP, email, DQL, DB, and JMS. Two listeners must not pick up the same message.

The format for specifying the preferred instance and the run in all instances settings are:

In each line of the text file, specify each HTTP/ Web service inbound activity for which the preferred instance needs to be run in all instances and save the file.

For example:

Process1::HTTP_Inbound_Activity1::bps1::true Process2::Webservice_Inbound_Activity2:bps1::true 6. Run the script file as below

For windows:

setValuesInListenerTable.bat <docbase><user><password><full path to the setValues_listener_template text file>

For Unix:

./setValuesInListenerTable.sh <docbase><user><password><full path to the setValues_listener_template text file>

#ProcessName::ActivityName::<Preferred Instance Name>::<Run In All Instances> #<Name of Process>::<name of activity>::<preferred instance name>

(29)

Conclusion

This guide endeavors to provide detailed steps with screen shots to Deploy Documentum Process Integrator on IBM Cluster, configure Process integrator to work with IBM Webspher cluster environment.

References

` The following web resources provide additional, relevant information.

 Process Integrator Deployment guide

 Process Integrator Development guide

 Deploying Documentum Business Activity Monitor on IBM Websphere Application Server Cluster.