Co Author - Aparna Bulusu (apbulusu@in.ibm.com)
Introduction :
In the traditional environment of Business Automation Workflow, there might be a need for more than one project areas for the grouping and better management of the projects. The default project area in the Development environment is dev_env_connection_definition and in the production environment is target_env. The following steps help in creating another project area which is the secondary or regular project area.
Step1. Create the DataBase artifacts. They are the database schema, bufferpools, storage groups, table spaces
Step2. Create the DataSources in the application server. They are the jdbc datasources.
Step3. Create the Object store in Content Platform Engine. After creating the object store install the Process Engine Extensions Add-on.
Step4. Create the Connection Point.
Step5. Convert the Object store created in step 3 to a Target Object store. This can be done using the Business Automation Workflow case configuration application - BAWAdmin
Step6. Create the Project area. This can be done using BAWAdmin.
Step7. Register the project area created in Step6. This can be done using BAWAdmin.
After the completion of all the steps the application server needs to be restarted.
Note: The following steps are for DB2 database and Red Hat Enterprise Linux 9.2 operating system for a development environment. They are only for reference. Depending on the development and production environment volumes and configuration needs they can be modified accordingly.
Step1. Create the DataBase artifacts.
1a. Create the required directories for the database
mkdir -p /home/db2inst1/DBDIR/CPEDB/SalesTOS/datafs1
mkdir -p /home/db2inst1/DBDIR/CPEDB/SalesTOS/datafs2
mkdir -p /home/db2inst1/DBDIR/CPEDB/SalesTOS/datafs3
mkdir -p /home/db2inst1/DBDIR/CPEDB/SalesTOS/indexfs1
mkdir -p /home/db2inst1/DBDIR/CPEDB/SalesTOS/indexfs2
mkdir -p /home/db2inst1/DBDIR/CPEDB/SalesTOS/lobfs1
chmod 777 -R /home/db2inst1/DBDIR/CPEDB
Save the above text with the name createdirsfordb.sh (you can give your desired name instead of SalesTOS) ensure that the script has root execute permissions and run it.
1b. Create the required artifacts at the Database level for the Object store.
-- Connect to db
CONNECT TO CPEDB;
-- Create Schema
SET SCHEMA SALESTOS;
-- Create 256MB GCD buffer pool
CREATE Bufferpool SALESTOS_DATA_BP IMMEDIATE SIZE AUTOMATIC PAGESIZE 32K;
CREATE Bufferpool SALESTOS_INDX_BP IMMEDIATE SIZE AUTOMATIC PAGESIZE 32K;
-- Create additional buffer pools
CREATE Bufferpool SALESTOS_LOB_BP IMMEDIATE SIZE AUTOMATIC PAGESIZE 32K;
CREATE Bufferpool SALESTOS_TEMP_BP IMMEDIATE SIZE AUTOMATIC PAGESIZE 32K;
CREATE Bufferpool SALESTOS_SYS_BP IMMEDIATE SIZE AUTOMATIC PAGESIZE 32K;
CREATE STOGROUP SALESTOSDATA_SG ON '/home/db2inst1/DBDIR/CPEDB/SalesTOS/datafs1', '/home/db2inst1/DBDIR/CPEDB/SalesTOS/datafs2', '/home/db2inst1/DBDIR/CPEDB/SalesTOS/datafs3';
CREATE STOGROUP SALESTOSINDX_SG ON '/home/db2inst1/DBDIR/CPEDB/SalesTOS/indexfs1', '/home/db2inst1/DBDIR/CPEDB/SalesTOS/indexfs2';
CREATE STOGROUP SALESTOSLOB_SG ON '/home/db2inst1/DBDIR/CPEDB/SalesTOS/lobfs1';
-- Create tablespaces
CREATE LARGE TABLESPACE SALESTOS_DATA_TS PAGESIZE 32 K MANAGED BY AUTOMATIC STORAGE USING STOGROUP SALESTOSDATA_SG EXTENTSIZE 16 OVERHEAD 10.5 PREFETCHSIZE 16 TRANSFERRATE 0.14 BUFFERPOOL SALESTOS_DATA_BP DROPPED TABLE RECOVERY ON;
CREATE LARGE TABLESPACE SALESTOS_IDX_TS PAGESIZE 32 K MANAGED BY AUTOMATIC STORAGE USING STOGROUP SALESTOSINDX_SG EXTENTSIZE 16 OVERHEAD 10.5 PREFETCHSIZE 16 TRANSFERRATE 0.14 BUFFERPOOL SALESTOS_INDX_BP DROPPED TABLE RECOVERY ON;
CREATE LARGE TABLESPACE SALESTOS_LOB_TS PAGESIZE 32 K MANAGED BY AUTOMATIC STORAGE USING STOGROUP SALESTOSLOB_SG EXTENTSIZE 16 OVERHEAD 10.5 PREFETCHSIZE 16 TRANSFERRATE 0.14 BUFFERPOOL SALESTOS_LOB_BP DROPPED TABLE RECOVERY ON;
CREATE USER TEMPORARY TABLESPACE SALESTOS_TEMP_TS PAGESIZE 32 K MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 16 OVERHEAD 10.5 PREFETCHSIZE 16 TRANSFERRATE 0.14 BUFFERPOOL SALESTOS_TEMP_BP;
CREATE SYSTEM TEMPORARY TABLESPACE SALESTOS_SYSTMP_TS PAGESIZE 32 K MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 16 OVERHEAD 10.5 PREFETCHSIZE 16 TRANSFERRATE 0.14 BUFFERPOOL SALESTOS_SYS_BP;
GRANT USE OF TABLESPACE SALESTOS_DATA_TS TO user db2inst1;
GRANT USE OF TABLESPACE SALESTOS_IDX_TS TO user db2inst1;
GRANT USE OF TABLESPACE SALESTOS_LOB_TS TO user db2inst1;
GRANT USE OF TABLESPACE SALESTOS_TEMP_TS TO user db2inst1;
Save the above content as createdbartifactories.sql
(you can give your desired name instead of SalesTOS)
Ensure that the application server and the database is started.
login as db2inst1 for db2 database
su - db2inst1
run the above sql file
db2 -tvmf createdbartifactories.sql
Please note in the steps for creating datasources, the following additional properties are required if you are using external CPE. https://www.ibm.com/docs/en/baw/24.0.x?topic=system-adding-case-second-project-area-user
Step2. Create the DataSources in the application server.
Create the data source in websphere application server admin console.
-login to WAS
-Go to Resources > JDBC > Data Sources
2.a at the same scope of jdbc/FNTOSDS create a new datasource
Ensure that you fill the values in the wizard as shown in summary below -
click finish.
2.b Create another datasource for XA with the following entries
click finish
Once the XA database is created, restart the websphere by logging in as root.
Step3. Create the Object store in Content Platform Engine. After creating the object store install the Process Engine Extensions Add-on.
Goto the Domain > Right click on Object store > New object store
Next > New Database connection > create a new db connection
Give the new display name , next > JNDI and JNDI XA Datasource names fill as created in WAS
Example Summary:
Name Value
Display name : DB configuration for SalesTOS
Site : Initial Site
JNDI data source : jdbc/FNTOSDSSALES
JNDI XA data source : jdbc/FNTOSDSXASales
Fill in the following details for creating the object store and click finish
Example Summary
Name Value
Display name : SalesTOS
Symbolic name : SalesTOS
Description : SalesTOS
Database connection : DB configuration for SalesTOS
Schema : SALESTOS
Force case-insensitive search : False
Compress database tables and indexes : False
Customize the schema creation script : False
Storage area type : Database
Administrators uid=deadmin,0=defaultWIMFileBasedRealm
3a.After the Object store in created, install the following add-on
Add-ons 5.2.1 Base Content Engine Extensions, 5.2.1 Process Engine Extensions
Set the user group permissions.
Step4. Create the Connection Point.
Enter the name of table space that was created during the creation of DB tables.
Step5. Convert the Object store created in step 3 to a Target Object store.
Using BAWAdmin, convert the Object store created above into a Target object store
Go to the Domain > Object stores > SalesTOS > right click and convert to target object store, Environment you gave select development for the development environment
Step6. Create the Project area.
Go to > dos > ProjectAreas > Define
click finish
Step7. Register the project area created in Step6. This can be done using BAWAdmin.
In BAWAdmin Go to dos > ProjectArea > Right click on SalesProjectArea > Register
Review the project area registration properties
Project area: SalesProjectArea
Desktop: IBM Business Automation Workflow
Case operations user name: deadmin
IBM Business Automation Workflow process server name: c83491v1.fyre.ibm.com (host name of the process server)
IBM Business Automation Workflow process server port: 9443
Use secured protocol: true
IBM Business Automation Workflow process server context root:
IBM Case Manager context root:
JMS user name:
JMS Topic Connection Factory Name:
JMS Topic Name:
Index number of primary shards:
Index number of shards replicas:
Restart the Websphere application server.