Process Integrator Deployment on IBM Webspher Application Server Cluster

Transcription

1 White Paper Process Integrator Deployment on IBM Webspher Application Server Cluster A user guide for deploying Process integrator on websphere application server cluster 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

2 Copyright 201X EMC Corporation. All Rights Reserved. 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. Part Number : H

3 Table of Contents About this Document... 4 Audience... 4 Introduction... 4 Installing Process Integrator WAR file in Cluster Setup... 5 Using a script to set Listener table attributes Conclusion References

4 About this Document This guide outlines the ideal way to successfully install and configure Documentum Process Integrator on IBM WebSphere Application Server 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 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 clustered environment: Deploying Documentum Business Activity Monitor on IBM Websphere Application Server Cluster. 4

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. 5. Select the bps.war file and click Next 5

6 6. Select Detailed Show all installation option and parameters Option and Click on Next 7. Click on Continue button 6

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

8 9. Select the bps.war by clicking checkbox and also select Cluster1 and Webserver1 Click Apply 8

9 10. Click Next 9

10 11. Enter the JDK Source Level as 15 click Next 10

11 12. Click Next 11

12 13. Click Next button 12

13 14. Click Next 13

14 15. Click Next 14

15 16. Click Next 15

16 17. Enter the Context root as bps and click Next 16

17 18. Click Finish 17

18 19. click on save link 18

19 20. Click on bps link 21. Click on Manage modules 19

20 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 20

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 21

22 26. Edit dfc.properties 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> 27. Edit bps_template.xml file as below <?xml version="1.0"?> <config xmlns:xsi=" <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> <property name="mail.imap.partialfetch" value="false"/> <property name="mail.debug" value="false"/> </config_properties> <connections> <docbase-connection> <docbase> Docbase name </docbase> <user> Docbase user</user> <password> Docbase user password </password> <domain/> </docbase-connection> </connections> </config> 22

23 28. 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_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 29. Navigate to location <IBM Installed Directory> \WebSphere\AppServer\profiles\AppSrv02\installedApps\TCMQAW2K3ORA040Cell01\bps.ear \bps.war\web-inf\classes 23

24 30. Edit dfc.properties 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> 31. Edit bps_template.xml file as below <?xml version="1.0"?> <config xmlns:xsi=" <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> <property name="mail.imap.partialfetch" value="false"/> <property name="mail.debug" value="false"/> </config_properties> <connections> <docbase-connection> <docbase> Docbase name </docbase> <user> Docbase user</user> <password> Docbase user password </password> <domain/> </docbase-connection> </connections> </config> 24

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 25

26 33. Open Admin console of Dmgr 34. Start the bps application by selecting the check box 35. Access the URLs a. <App Server 01 host> : <http port>/bps/inbound_details.jsp Example : 26

27 b. <App Server 02 host> : <http port>/bps/inbound_details.jsp Example : c. <HTTP Server host> : <http port>/bps/inbound_details.jsp Example : To View the Listeners started for the processes use specific Application server host and port for example : To access listener page : a. <App Server 01 host> : <http port>/bps/lsnrs.jsp Example : b. <App Server 02 host> : <http port>/bps/lsnrs.jsp Example : 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 "%JAVA%" -classpath %DFC_CONFIG_DIR%;..\lib\bpm_infra.jar;..\lib\bpmcommons.jar;..\lib\bpmutil.jar;..\lib\dfc.jar com.documentum.bps.utils.setattributesinlistenertable %1 %2 %3 %4 27

28 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, , 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: #ProcessName::ActivityName::<Preferred Instance Name>::<Run In All Instances> #<Name of Process>::<name of activity>::<preferred instance name> #<Name of Process>::<name of activity>::<preferred instance name>::<run In All Instances> 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> 28

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. deploy-business-activity-monitor-server-wp.pdf 29