IBM BPM, V8.0.1, All platforms > Install IBM BPM > IBM BPM Advanced for z/OS: Process Server > Configure IBM BPM Advanced for z/OS: Process Server
Create the databases
Before the IBM BPM for z/OS instance can function, one or more supporting databases must be configured and the database objects defined.
If this is your first IBM BPM for z/OS installation, start with a stand-alone configuration with a DB2 for z/OS database to become familiar with using DB2.
You can then create an ND configuration that uses a DB2 database, which is a more complex procedure.
- DB2 for z/OS authorization prerequisites
Before you create the IBM BPM databases, you must ensure that the required authorizations are granted for your DB2 for z/OS version. Also ensure that the appropriate storage groups and buffer pools are assigned, and configure clustering if necessary.- Create databases in the DB2 for z/OS subsystem
When you use the database design tool (DbDesignGenerator.sh) to define your database configuration, you can generate the database scripts that are required for creating the databases for the IBM BPM components.- Create the messaging engine data stores
If the messaging engine data stores have not already been created, use the database design tool to generate the database scripts that the database administrator will use to create the tables for the messaging engine data stores.
- Adding the DB2 for z/OS libraries to the Servant and Adjunct JCL
If you are using Type 2 connection pool data sources to access the database, the SDSNEXIT, SDSNLOAD, and SDSNLOD2 data sets must be available to the WebSphere Application Server. If the DB2 for z/OS system does not run with SDSNEXIT, SDSNLOAD, and SDSNLOD2 in LNKLST, update your WebSphere Servant and Adjunct JCL so that the STEPLIB statement includes the customized DB2 SDSNEXIT, the SDSNLOAD, and the SDSNLOD2.
- Granting table privileges to the JCA authentication alias user ID
If the schema name you are using is not the same as the JCA authentication alias user ID, you must grant a subset of DB2 for z/OS privileges to the JCA authentication alias user ID.