BPM, Workflow, and Case

BPM, Workflow, and Case

Come for answers. Stay for best practices. All we’re missing is you.

 View Only

Install and Configure IBM Business Automation Workflow 23.0.1 on Premise with Db2 for z/OS

By XIAO LI YU posted Tue November 21, 2023 12:28 AM

  

This document is about how to install and configure IBM Business Automation Workflow (BAW) 23.0.1 on premise with Db2 for z/OS.

1. Prepare your systems for BAW installation

We use Linux to install and configure BAW in our case. For linux system, you may prepare your systems for BAW installation according to document https://www.ibm.com/docs/en/baw/23.x?topic=installation-preparing-linux-systems.

2. Install BAW 23.0.1

  1. Download installer of WAS 8.5.5.23, BAW 22.0.2 and 23.0.1.

  2. Install Installation Manager (IM), sample commands are as below.

    1. cd /root/build/BAW2202/IM

    2. ./installc -c

    3. follow the installation and input values according to your requirement to install IM.

  3. Install BAW 2301, sample commands are as below.

    1. cd /opt/IBM/InstallationManager/eclipse/tools/

    2. ./imcl install com.ibm.bpm.ADV.v85,WorkflowEnterprise.Production com.ibm.websphere.ND.v85,core.feature,ejbdeploy,thinclient,embeddablecontainer,samples,com.ibm.sdk.6_64bit -acceptLicense -installationDirectory /opt/IBM/BPM -repositories /root/build/WAS85523,/root/build/BAW2202/repository,/root/build/workflow.2301.delta.repository.zip -showVerboseProgress -log silentinstall.log

3. Run BPMConfig command to configure BAW 23.0.1

  1. Run BPMConfig to create DE without case management functions, you may refer to document https://www.ibm.com/docs/en/baw/23.x?topic=zos-using-bpmconfig-command

  2. We can only use BPMConfig to create DE without case management functions at first when using Db2 for z/OS.

  3. A sample command is as below.

  4. /opt/IBM/BPM/bin/BPMConfig.sh -create -de /root/sandy/Advanced-PC-SingleCluster-DB2zOS_WithoutCase.properties

4. Run DB scripts on DB2 for z/OS

  1. Download DB scripts from /opt/IBM/BPM/profiles/DmgrProfile/dbscripts.

  2. Modify all createDatabase.sql, createSchema_Advanced.sql, createSchema_Messaging.sql, createTablespace_Advanced.sql, add "CONNECT TO STLEC1;" at the beginning. STLEC1 is location of your DB2 for z/OS.

  3. Modify createProcedure_Advanced.sql, add "CONNECT TO STLEC1@" at the beginning. STLEC1 is location of your DB2 for z/OS.

  4. In our case, on DB2z machine, run all sql files as the order below.

    1. java com.ibm.db2.clp.db2 -tvf /u/sysadm/dbscriptsWithoutCase/PCCell1/DB2zOS/CLLDB/createDatabase.sql

    2. java com.ibm.db2.clp.db2 -tvf /u/sysadm/dbscriptsWithoutCase/PCCell1/DB2zOS/CLLDB/createSchema_Advanced.sql

    3. java com.ibm.db2.clp.db2 -tvf /u/sysadm/dbscriptsWithoutCase/PCCell1.De1/DB2zOS/CMNDB/createDatabase.sql

    4. java com.ibm.db2.clp.db2 -tvf /u/sysadm/dbscriptsWithoutCase/PCCell1.De1/DB2zOS/CMNDB/createTablespace_Advanced.sql

    5. java com.ibm.db2.clp.db2 -tvf /u/sysadm/dbscriptsWithoutCase/PCCell1.De1/DB2zOS/CMNDB/createSchema_Advanced.sql

    6. java com.ibm.db2.clp.db2 -tvf /u/sysadm/dbscriptsWithoutCase/PCCell1.De1/DB2zOS/CMNDB/createSchema_Messaging.sql

    7. java com.ibm.db2.clp.db2 -td@ -f /u/sysadm/dbscriptsWithoutCase/PCCell1.De1/DB2zOS/CMNDB/createProcedure_Advanced.sql

    8. java com.ibm.db2.clp.db2 -tvf /u/sysadm/dbscriptsWithoutCase/PCCell1.De1/DB2zOS/PDWDB/createDatabase.sql

    9. java com.ibm.db2.clp.db2 -tvf /u/sysadm/dbscriptsWithoutCase/PCCell1.De1/DB2zOS/PDWDB/createSchema_Advanced.sql

5. Load the database with system information

Run bootstrap command on BAW machine, here is the sample command:  /opt/IBM/BPM/profiles/DmgrProfile/bin/bootstrapProcessServerData.sh -clusterName SingleCluster

6. Start your environment and verify the installation

  1. Now you've finished configuring BAW functions except case management functions, and you can start BAW to verify your environment. You can verify BAW according to document https://www.ibm.com/docs/en/baw/23.x?topic=workflow-starting-your-environment-verifying-installation.

  2. If you need to use case management functions, you may continue configuring it according to steps below. If you don't need to use case management functions, you don't need to follow the steps below.

7. Configure BAW case management for Db2 for z/OS

  1. If you need to use case management functions, you may continue configuring it according to steps below. If you don't need to use case management functions, you don't need to follow the steps below.

  2. Stop BAW, including DE, node agent and dmgr.

  3. Configure BAW case management for Db2 for z/OS, refer to document https://www.ibm.com/docs/en/baw/23.x?topic=installation-configuring-case-management-db2-zos

  4. Run command to export BPMConfig property file, a sample command is: /opt/IBM/BPM/bin/BPMConfig.sh -export -profile DmgrProfile -outputDir /root/sandy/2302export

  5. Modify generated BPMConfig property file. In our case, BPMConfig property file is /root/sandy/2302export/De1.properties.

  6. Replace the values wherever you see "TO_BE_REPLACED" in the file.

  7. Add case related properties in BPMConfig property file.

  8. Run BPMConfig command to verify DB connections. /opt/IBM/BPM/bin/BPMConfig.sh -validate -db /root/sandy/2302export/De1.properties

  9. Stop BAW, including DE, node agent and dmgr.

  10. Upgrade the deployment environment to add the Case Manager component, by running the following command on the deployment manager. A sample command is: /opt/IBM/BPM/bin/BPMConfig.sh -upgrade -de /root/sandy/2302export/De1.properties -component CaseManager

8. Run DB scripts of case management functions on DB2 for z/OS

  1. Download db scripts from /opt/IBM/BPM/profiles/DmgrProfile/dbscripts_upgrade.

  2. Modify all createDatabase.sql, createSchema_Advanced.sql, createTablespace_Advanced.sql, add "CONNECT TO STLEC1;" at the beginning. STLEC1 is location of your DB2 for z/OS. Except ICNDB/createSchema_Advanced.sql, add "CONNECT TO STLEC1+" at the beginning. 

  3. In our case, on DB2z machine, run all sql files as the order below.

    1. java com.ibm.db2.clp.db2 -tvf /u/sysadm/dbscripts_upgrade/PCCell1.De1/DB2zOS/DOSDB/createDatabase.sql

    2. java com.ibm.db2.clp.db2 -tvf /u/sysadm/dbscripts_upgrade/PCCell1.De1/DB2zOS/DOSDB/createTablespace_Advanced.sql

    3. java com.ibm.db2.clp.db2 -tvf /u/sysadm/dbscripts_upgrade/PCCell1.De1/DB2zOS/ECMDB/createDatabase.sql

    4. java com.ibm.db2.clp.db2 -tvf /u/sysadm/dbscripts_upgrade/PCCell1.De1/DB2zOS/ECMDB/createSchema_Advanced.sql

    5. java com.ibm.db2.clp.db2 -tvf /u/sysadm/dbscripts_upgrade/PCCell1.De1/DB2zOS/ICNDB/createDatabase.sql

    6. java com.ibm.db2.clp.db2 -td+ -f /u/sysadm/dbscripts_upgrade/PCCell1.De1/DB2zOS/ICNDB/createSchema_Advanced.sql. If you meet some exceptions like "Exception in thread "main" java.lang.NoClassDefFoundError: com/ibm/db2/jcc/am/b1", you may solve it by adding classpath of DB2 driver "/usr/lpp/db2/db2c10/jdbc/classes/db2jcc.jar". 

    7. java com.ibm.db2.clp.db2 -tvf /u/sysadm/dbscripts_upgrade/PCCell1.De1/DB2zOS/TOSDB/createDatabase.sql

    8. java com.ibm.db2.clp.db2 -tvf /u/sysadm/dbscripts_upgrade/PCCell1.De1/DB2zOS/TOSDB/createTablespace_Advanced.sql

9. Configure your system for case management

  1. Start dmgr and node agent, do NOT start application server.

  2. Increase transaction timeout and datasource timeout. You may refer to document https://www.ibm.com/docs/en/baw/23.x?topic=cpecm-preparing-run-configuration-tasks.

  3. Better to increase soap timeout of dmgr and application server. Modify ${was_install_root}/profiles/your_profile/properties/soap.client.props file. Increase the value of property com.ibm.SOAP.requestTimeout.

  4. In admin console, create a group, for example, adminGroup2, and add DE admin user (deadmin in our case) to the group.

  5. Restart BAW, including dmgr, node agent and DE.

  6. Run createObjectStoreForContent command. You may refer to document https://www.ibm.com/docs/en/baw/23.x?topic=scripting-createobjectstoreforcontent. Sample commands are as below.

    1. /opt/IBM/BPM/profiles/DmgrProfile/bin/wsadmin.sh -lang jython -user deadmin -password deadmin -host localhost -port 8880

    2. print AdminTask.createObjectStoreForContent(['-clusterName', 'SingleCluster', '-PEWorkflowSystemAdminGroup', 'adminGroup2','-creationUser','deadmin','-password','deadmin'])

  7. Run case configuration tasks. You may refer to document https://www.ibm.com/docs/en/baw/23.x?topic=workflow-configuring-your-system-case-management. If your environment is production environment, you may refer to document https://www.ibm.com/docs/en/baw/23.x?topic=cpecm-preparing-run-configuration-tasks. If your environment is development environment, you may refer to document https://www.ibm.com/docs/en/baw/23.x?topic=management-preparing-run-configuration-tasks

    1. Start or restart BAW.

    2. Go to the install_root/CaseManagement/configure directory.

    3. Run the following command: ./configmgr

    4. Click Open Profile to open the predefined profile for your current development environment. The predefined profile is located in the following directory: dmgr_profile_root/CaseManagement/DE_name/profiles/ICM_dev.

    5. Run tasks one by one. You must run the tasks in the order listed. You don't need to run tasks which are disabled.

10. Verify case management functions in BAW

  1. Now you've finished configuring BAW case management functions, and you can verify your environment.

  2. Restart BAW, including dmgr, node agent and application servers.

  3. Verify case management functions. If your environment is production environment, you may refer to document https://www.ibm.com/docs/en/baw/23.x?topic=cpecm-verifying-business-automation-workflow-applications-in-production-environment. If your environment is development environment, you may refer to document https://www.ibm.com/docs/en/baw/23.x?topic=management-verifying-case-applications-in-development-environment

11. How to drop and clean BAW databases for Db2 for z/OS if needed

  1. If you want to clean BAW databases for Db2 for z/OS, you may follow the steps below. It will drop and clean all BAW databases and data for Db2 for z/OS.

  2. Be careful! Only follow the steps if your BAW env is not needed and need clean up. Do NOT follow the steps if your BAW environment is still in use, otherwise all databases will be dropped and your BAW environment cannot be used!

  3. Get dropDatabase.sql from DB scripts generated by BPMConfig command. In our case, the DB scripts are in /opt/IBM/BPM/profiles/DmgrProfile/dbscripts and /opt/IBM/BPM/profiles/DmgrProfile/dbscripts_upgrade.

  4. add "CONNECT TO STLEC1;" at the beginning of all DB scripts. Add “COMMIT;“ at last if it's not there.

  5. Run all dropDatabase.sql. A sample command is java com.ibm.db2.clp.db2 -tvf /u/sysadm/dbscriptsWithoutCase/PCCell1/DB2zOS/CLLDB/dropDatabase.sql. You need to run it for all databases one by one.

  6. Create DB scripts to drop some sequences. These sequences are used by case management functions. A sample SQL is as below. SYSADM is the user that you use to connect to DB2 z. DOSCT is the value of bpm.de.db.7.schema in your BPMConfig property file. TOSCT is the value of bpm.de.db.6.schema in your BPMConfig property file.

  7. CONNECT TO STLEC1;

     

    DROP SEQUENCE SYSADM.AUDITSEQUENCE;

    DROP SEQUENCE SYSADM.CISEQUENCE;

    DROP SEQUENCE SYSADM.CONTENTQUEUESEQUENCE;

    DROP SEQUENCE SYSADM.REPLSEQUENCE;

    DROP SEQUENCE SYSADM.SCFSEQUENCE;

     

    DROP SEQUENCE DOSCT.AUDITSEQUENCE;

    DROP SEQUENCE DOSCT.CISEQUENCE;

    DROP SEQUENCE DOSCT.CONTENTQUEUESEQUENCE;

    DROP SEQUENCE DOSCT.REPLSEQUENCE;

    DROP SEQUENCE DOSCT.SCFSEQUENCE;

     

    DROP SEQUENCE TOSCT.AUDITSEQUENCE;

    DROP SEQUENCE TOSCT.CISEQUENCE;

    DROP SEQUENCE TOSCT.CONTENTQUEUESEQUENCE;

    DROP SEQUENCE TOSCT.REPLSEQUENCE;

    DROP SEQUENCE TOSCT.SCFSEQUENCE;

     

    COMMIT;

  8. Run command to drop the sequences. A sample command is java com.ibm.db2.clp.db2 -tvf /u/sysadm/dropSequence.sql.

  9. Now you've finished clean all BAW databases and data for Db2 for z/OS.

0 comments
42 views

Permalink