Content Platform Engine, Database: DB2 for z/OS Operating systems: AIX, HP-UX, Linux, Linux on System z, Solaris

Ensuring visibility of data source properties (IBM DB2 for z/OS)

You need to set a JVM argument or edit the Engine.properties file on the Content Platform Engine server so that Content Platform Engine can read the data source properties in the IBM® DB2® for z/OS® database.

About this task

There are two alternative methods to ensure that Content Platform Engine can read the data source properties in the IBM DB2 for z/OS database:

Method 1: Set the value of a JVM argument on the Content Platform Engine server.
Method 2: Specify the IBM DB2 for z/OS data source properties in the Engine.properties file.

You can use method 1 if both of the following conditions hold:

You are not deploying Content Platform Engine in an environment where WebSphere® security domains are in use.
The Content Platform Engine server is able to read the data source properties.

You must use method 2 if at least one of the following conditions holds:

You are deploying Content Platform Engine in an environment where WebSphere security domains are in use.
The Content Platform Engine server is not able to read the data source properties.

Procedure

To ensure visibility of data source properties:

If you are using method 1, set the following JVM argument on the Content Platform Engine server:
```
-Dcom.filenet.engine.init.BGThreadsAsBootstrapId=false
```

If you are using method 2, note that the Engine.properties file must be in the WebSphere directory that holds the FileNet directory where server-specific P8 log files and other directories that are needed at runtime reside. In a typical installation, this WebSphere directory is .../WebSphere/AppServer/profiles/AppSrv01.

The Engine.properties file must contain three properties settings for each IBM DB2 for z/OS data source. For example, the following data source property settings are required for the non-XA (FNGCDDS) and XA (FNGCDDSXA) data sources for the global configuration database (GCD):

FNGCDDS.zOSDatabaseName=X50DBASE
FNGCDDS.zOSDefaultSTOGROUP=ECCADMSTG
FNGCDDS.zOSSTOGROUPOptions=PRIQTY 10 SECQTY 5

FNGCDDSXA.zOSDatabaseName=X50DBASE
FNGCDDSXA.zOSDefaultSTOGROUP=ECCADMSTG
FNGCDDSXA.zOSSTOGROUPOptions=PRIQTY 10 SECQTY 5

As another example, the following data source property settings are required for the non-XA (OBJECTSTORE1DS) and XA (OBJECSTORE1DSXA) data sources for an object store database:

OBJECTSTORE1DS.zOSDatabaseName=CEDBASE
OBJECTSTORE1DS.zOSDefaultSTOGROUP=ECCADMSTG
OBJECTSTORE1DS.zOSSTOGROUPOptions=PRIQTY 10 SECQTY 5

OBJECTSTORE1DSXA.zOSDatabaseName=CEDBASE
OBJECTSTORE1DSXA.zOSDefaultSTOGROUP=ECCADMSTG
OBJECTSTORE1DSXA.zOSSTOGROUPOptions=PRIQTY 10 SECQTY 5

Each data source property is described in the following table:

Table 1. Data source property descriptions
Property name	Description
`zOSDatabaseName`	The string-valued custom property that represents the name of the actual database being targeted.
`zOSDefaultSTOGROUP`	The string-valued custom property that represents the default storage group to be used when issuing index-creation statements. A storage group on IBM DB2 for z/OS is analogous to an index tablespace on DB2 or Oracle Database, and to a filegroup on Microsoft SQL Server. If you do not specify this property, the Content Platform Engine server can still function, but the IBM DB2 for z/OS database then uses its system-defined default, which is probably not appropriate.
`zOSSTOGROUPOptions`	Storage groups on IBM DB2 for z/OS can have a number of optional parameters. You need this string-valued custom property in order to specify various options to the `'USING STOGROUP'` clause in SQL statements.