Transfer DB2 for z/OS manually

Transfer DB2 for z/OS manually

You are here

Planning for DB2 for z/OS

Installing DB2 for z/OS

Creating databases and users for DB2 for z/OS

Transfer DB2 for z/OS (Current task) or Transferring between databases manually

Verifying database connections

Before you begin
Before configuring databases, ensure that the following prerequisites are met:

Supported database software is installed.

Databases and users are correctly set up for use by IBM WebSphere Portal.

Password Considerations
For security reasons, you should not store passwords in the wpconfig.properties, wpconfig_dbdomain.properties, and wpconfig_dbtype.properties files. IBM recommends that you edit each of the properties files prior to running a configuration task, inserting the passwords needed for that task. After the task has run, you should delete all passwords from each file. For more information, see Delete passwords from configuration scripts. Alternatively, we can specify the password on the command line using the following syntax:

UNIX:

./WPSconfig.sh task_name -Dpassword_property_key=password_value

Windows:
WPSconfig.bat task_name -Dpassword_property_key=password_value

As with other properties, each password property must have the -D prefix and be set equal to (=) a value. If you have multiple properties in a single command, use a space character between each -Dproperty=value setting. Tips:

The steps for transferring data to another supported database section provides instructions for manually transferring data. Instead of performing the following steps, we can use the configuration wizard, a graphical user interface, to transfer data to another supported database. For more information, refer to Configuring WebSphere Portal with the configuration wizard.

A configuration template might exist to support these instructions. Refer to the portal_server_root/config/helpers directory for available configuration templates. Use the configuration template to update the wpconfig.properties, wpconfig_dbdomain.properties, and wpconfig_dbtype.properties files, as described in Configuration program, according to the property descriptions and recommended values provided here. If you do not want to use a configuration template, follow theses instructions as written.

Steps for transferring data to another supported database
To transfer WebSphere Portal, Member Manager, and Personalization databases to IBM DB2 Universal Database™ for z/OS.

Locate the following files and create a backup copy of each before changing any values:

portal_server_root/config/wpconfig.properties

portal_server_root/config/wpconfig_dbdomain.properties

portal_server_root/config/wpconfig_dbtype.properties

Edit the properties files and enter the values that are appropriate for the environment.
Notes:

The WebSphere Portal database can be used to hold information for applications such as Document Manager, Personalization, Feedback and Likeminds. In this case, the user should similar naming conventions for property values such as release.DbName, jcr.DbName, feedback.DbName, and likeminds.DbName. For example:

releaseDbName=wpsdb

jcr.DbName=jcrdb

feedback.DbName=fdbkdb

likeminds.DbName=lkmddb

Do not change any settings other than those that are specified in these steps. For instructions on working with these files, see Configuration properties reference for a complete properties reference, including default values.

If you are using a remote database, be sure to enter the values for the remote server.

Use / instead of \ for all platforms.

Some values, shown here in italics, might need to be modified to your specific environment.

There might be additional database properties other than those listed here. Only change the properties within this table; skip all other properties.

If you are following the recommended architecture in Planning for DB2, the Value listed for each property in the following table represents the DB2 -specific information that is required to configure WebSphere Portal to DB2.

Depending on which database domain has to be configured, dbdomain may need to be replaced by:

release

customization

community

jcr

feedback

likeminds

wmm

Update the following properties in the file wpconfig_dbdomain.properties.

Database domain properties
Property Value
dbdomain.DbType
The type of database used to store information for WebSphere Portal.
Value type: Alphanumeric text string Recommended value:

DB2 for z/OS and OS/390: db2_zos

dbdomain.DbName Description: The name of the WebSphere Portal domain database and schema.
Notes:

This value is also the database element in the dbdomain.DbUrl property.

Non-Windows platforms when using DB2 only. This value is the TCPIP Alias for the database.

For Oracle, this value should match the 'ORACLE_SID'.

Value type: Alphanumeric text string
Notes:

For DB2 and DB2 for z/OS, this value cannot exceed 8 characters and can only contain letters and numbers. Refer to the database documentation for more information.

For DB2, this value must be different from the value of dbdomain.XDbName.

If you change the name of the WebSphere Portal data source due to a database migration, manually update this property in the portal_server_root/config/wpconfig_dbdomain.properties file to maintain the proper resource reference mapping.

Default value for all domains: wpsdb
dbdomain.DbNameOnZos
Description: The name of the WebSphere Portal database on DB2 for z/OS.
Value type: Alphanumeric text string Default:

Release: WPSTST02

Customization: WPSTST02

Community: WPSTST02

JCR: WPSTST02

WMM: WPSTST02

Feedback: WPSTST02

LikeMinds: WPSTST02

dbdomain.DbUrl
The database URL used to access the WebSphere Portal database with JDBC. The value must conform to standard JDBC URL syntax.
The database element of this value should match the value of dbdomain.DbName.
Value type: Alphanumeric text string, conforming to standard JDBC URL syntax Recommended:

DB2 for z/OS (local): jdbc:db2:location

DB2 for z/OS (remote): jdbc:db2:wpsdb

dbdomain.DbUser
Description: The user ID for the database administrator.
Notes:

For SQL Server and non-wmm databases only, unless you are the system administrator, the values for dbdomain.DbUser and dbdomain.DbSchema must be the same.

For Oracle and SQL Server servers, this value must be set to FEEDBACK, which corresponds to the user FEEDBACK in the database. If the user you are using is an administrative user that has authority over the FEEDBACK schema, the administrative user should be entered for the dbdomain.DbUser property.

Value type: Alphanumeric text string Default:

Release: db2admin

Community: db2admin

Customization: db2admin

JCR: db2admin

WMM: db2admin

Feedback: db2admin

LikeMinds: db2admin

Recommended: wpsdbusr (for databases other than DB2 )
dbdomain.DbPassword
Description: The password for the database administrator.
A value must be set for this property; it cannot be empty.
Value type: Alphanumeric text string
Default value for all domains: ReplaceWithYourDbAdminPwd
dbdomain.XDbName
Description: The database loop back alias that needs to be set if you plan to use the create-local-database-db2 task.
Notes:

For DB2, this value must be different from the value of dbdomain.DbName.

Value type: Alphanumeric text string Default:

Release: wps6TCP

Community: wps6TCP

Customization: wps6TCP

WMM: wps6TCP

JCR: wps6TCP

Feedback: fdbk6TCP

LikeMinds: lmdb6TCP

dbdomain.DbNode
Description: The value for the node database.
Required for non-Windows platforms when using DB2 only.
Value type: Alphanumeric text string Default values:

Release: wpsNode

Community: wpsNode

Customization: wpsNode

JCR: wpsNode

WMM: wpsNode

Feedback value: pznNode

LikeMinds value: pznNode

dbdomain.DbSchema
The schema name of the database domain.
Notes:

This property is not used on Member Manager, which only uses the dbdomain.DbUser name as the schema.

Follow the documentation of the target database management system in order to define a valid schema name as restrictions apply for some database management systems.

For SQL Server only, unless you are the system administrator, the values for dbdomain.DbUser and dbdomain.DbSchema must be the same.

For Oracle and SQL Server servers, the value must be set to FEEDBACK.

Value type: Alphanumeric text string
Default: dbdomain
dbdomain.DataSourceName
Description: The name of the data store that WebSphere Portal uses to communicate with its databases.
Notes:

If the DbUser, DbUrl, and DbPassword are not the same across domains, this value must differ from the DataSourceName of the other domains.

The value for dbdomain.DataSourceName should not be set to the same value as dbdomain.DbName.

Value type: Alphanumeric text string Default values:

Release: wpsdbDS

Community: wpsdbDS

Customization: wpsdbDS

JCR: JCRDS

WMM: wpsdbDS

Feedback: feedback5

LikeMinds: lmdbDS

DB2 Content Manager Runtime Edition properties
Property Value
jcr.DbHost Description: The hostname of the system hosting the DB2 Content Manager Runtime Edition database.
Required for DB2 for z/OS and OS/390 only.
Value type: Alphanumeric text string
jcr.DbDomain Description: The domain of the system hosting the DB2 Content Manager Runtime Edition database.
Required for DB2 for z/OS and OS/390 only.
Value type: Alphanumeric text string
jcr.ZosDbPrefix Description: Common prefix of Node Type database names for the DB2 Content Manager Runtime Edition database.
Required for DB2 for z/OS and OS/390 only.
Recommended: Set this value according to your own environment, to match the value used when executing the commands to create the database found in the file Creating the DB2 Content Manager Runtime Edition database.
Default: ICM
jcr.ZosDbMaxTables Description: Maximum number of User Defined Tables to be stored in a particular Node Type DB in the DB2 Content Manager Runtime Edition database.
Required for DB2 for z/OS and OS/390 only.
Recommended: 400.
Default: 400
jcr.DbStorageGroup Description: The storage group for the DB2 Content Manager Runtime Edition database.
Required for DB2 for z/OS and OS/390 only.
Recommended: Set this value according to your own environment, to match the value used when executing the commands to create the database found in the file Creating the DB2 Content Manager Runtime Edition database.
Default: WPSSG
jcr.DbVolumes Description: The volumes for the DB2 Content Manager Runtime Edition database.
Required for DB2 for z/OS and OS/390 only.
Recommended: Set this value according to your own environment, to match the value used when executing the commands to create the database found in the file Creating the DB2 Content Manager Runtime Edition database.
Default: *
jcr.DbVcat Description: The VCAT for the DB2 Content Manager Runtime Edition database.
Required for DB2 for z/OS and OS/390 only.
Recommended: Set this value according to your own environment, to match the value used when executing the commands to create the database found in the file Creating the DB2 Content Manager Runtime Edition database.
Default: DSN810
jcr.Db4KBufferPoolName Description: The 4K bufferpool name for the DB2 Content Manager Runtime Edition database.
Required for DB2 for z/OS and OS/390 only.
Recommended: Set this value according to your own environment, to match the value used when executing the commands to create the database found in the file Creating the DB2 Content Manager Runtime Edition database.
Default: BP0
jcr.Db32KBufferPoolName Description: The 32K bufferpool name for the DB2 Content Manager Runtime Edition database.
Required for DB2 for z/OS and OS/390 only.
Recommended: Set this value according to your own environment, to match the value used when executing the commands to create the database found in the file Creating the DB2 Content Manager Runtime Edition database.
Default: BP32K
jcr.DbPort Description: Port number of the DB2 Content Manager Runtime Edition database, if not on the local system (required for Driver Type 4 only).
Required for DB2 for z/OS and OS/390 only.
Recommended: Set this value according to your own environment.
Default: 446

Personalization and Feedback Database properties
Property Value
feedback.DbTablespace
The name of the Feedback database table space.
Required only if running on DB2 for z/OS, or if using DB2 for z/OS as a remote database.
Recommended: fdbkdbts
Default: fdbkdbts

LikeMinds Database properties
Property Value
likeminds.DbTablespace
The name of the LikeMinds database table space.
Required only if running on DB2 for z/OS, or if using DB2 for z/OS as a remote database.
Recommended: lmdbts
Default: lmdbts

Update the following properties in the file wpconfig_dbtype.properties.

Database type properties
Property Value
DbSafeMode
This only applies to database-specific tasks. If this property is set to true, database-specific tasks, such as create/modify/drop database, will not be performed. The property should be used if a pre-configured database (from a previous installation) already exists. If the property is set to false, the database will be updated and the pre-existing database configuration will be overwritten.
Recommended: false
Default: false
db2_zos.DbDriver
The name of class that SqlProcessor will use to import SQL files.
Recommended: COM.ibm.db2.jdbc.app.DB2Driver
Windows and UNIX Default: COM.ibm.db2j.jdbc.DB2Driver (Cloudscape )
db2_zos.JdbcProvider
The name of the JDBC provider that WebSphere Portal uses to communicate with its databases.
Recommended: wpsdbJDBC_db2_zos
Default: wpsdbJDBC_db2_zos
db2_zos.DbLibrary
The directory and name of the.zip or.jar file that contains the JDBC driver class
Recommended: microsoftJDBC/lib/jar
In UNIX environments, use a colon (:) instead of a semi-colon (;) to separate multiple paths.
Windows and UNIX Default value: <SQLLIB>/jcc/classes/db2jcc.jar:<SQLLIB>/jcc/classes/db2jcc_license_cisuz.jar:<SQLLIB>/jcc/classes/db2jcc_javax.jar

Update the following properties in the file wpconfig.properties.

WebSphere Application Server properties
Property Description
WasPassword
The password for WebSphere Application Server security authentication.
If a value is specified for WasPassword, a value must also be specified for WasUserid. If WasPassword is left blank, WasUserid must also be left blank.
Value type: Alphanumeric text string
Recommended: Set this value according to your own environment.
Default: ReplaceWithYourWASUserPwd

Save the file.

Open a command prompt, and change to the directory portal_server_root/config.

Perform this step only if WebSphere Portal is on UNIX. Use the following steps to export the db2instance environment in the profile:

In your.bashrc,.dshrc, or.profile file, add
if [ -f /home/db2inst1/sqllib/db2profile ]; then. /home/db2inst1/sqllib/db2profile; fi

Reopen all the shells.

Enter the following commands to validate configuration properties.

UNIX:

./WPSconfig.sh validate-database-connection-wps -DDbPassword=password

./WPSconfig.sh validate-database-connection-jcr -DJcrDbPassword=password

./WPSconfig.sh validate-database-connection-feedback -DFeedbackDbPassword=password

./WPSconfig.sh validate-database-connection-likeminds -DLikemindsDbPassword=password

./WPSconfig.sh validate-database-connection-wmm -DWmmDbPassword=password

./WPSconfig.sh validate-database-driver

Windows :

WPSconfig.bat validate-database-connection-wps -DDbPassword=password

WPSconfig.bat validate-database-connection-jcr -DJcrDbPassword=password

WPSconfig.bat validate-database-connection-feedback -DFeedbackDbPassword=password

WPSconfig.bat validate-database-connection-likeminds -DLikemindsDbPassword=password

WPSconfig.bat validate-database-connection-wmm -DWmmDbPassword=password

WPSconfig.bat validate-database-driver

From the same command prompt as the previous steps, change to the directory portal_server_root/config.

If WebSphere Portal is on UNIX, export the DB2 user profile that you created when installing DB2 onto the administrative user using the following command. This gives that administrative user rights over DB2.
. /home/db2inst1/sqllib/db2profile
where db2inst1 represents your database instance
You must complete this step before running database tasks and before enabling security in order to create a suitable JDBC driver.

Stop both server1 and the WebSphere Portal server.

Enter the following command:

UNIX:

./stopServer.sh server1 -user admin_userid -password admin_password

Windows:
stopServer.bat server1 -user admin_userid -password admin_password

i5/OS:
stopServer -profileName profile_root -user admin_userid -password admin_password
...where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal is installed; for example, wp_profile.

...where server1 is the name of the WebSphere Application Server administrative server, and profile_root is the name given to the WebSphere Application Server profile in use.

Enter the following command:

UNIX:

./stopServer.sh WebSphere_Portal -user admin_userid -password admin_password

Windows:
stopServer.bat WebSphere_Portal -user admin_userid -password admin_password

i5/OS:
stopServer WebSphere_Portal -profileName profile_root -user admin_userid -password admin_password
...where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal is installed; for example, wp_profile.

To transfer the database, perform this step:

Enter the following commands to run the configuration task.

UNIX:

./WPSconfig.sh database-transfer -Drelease.DbPassword=password -Dcustomization.DbPassword=password -Dcommunity.DbPassword=password -Djcr.DbPassword=password -Dwmm.DbPassword=password -Dfeedback.DbPassword=password -Dlikeminds.DbPassword=password

Windows:
WPSconfig.bat database-transfer -Drelease.DbPassword=password -Dcustomization.DbPassword=password -Dcommunity.DbPassword=password -Djcr.DbPassword=password -Dwmm.DbPassword=password -Dfeedback.DbPassword=password -Dlikeminds.DbPassword=password

After running this task, a message indicating success should result. Check the log files to verify that this task was successful. If the configuration fails, verify the values in the wpconfig_dbdomain.properties file, and then repeat this step.

From the command line processor, reset the check pending status on the WebSphere Portal table spaces listed here. CHECK DATA is a DB2 batch utility that is invoked through JCL or through the DB2 utility panels. Type the following utility commands to check pending status:
check data tablespace releasenameonzos.TS320A check data tablespace releasenameonzos.TS280A check data tablespace releasenameonzos.TS300A check data tablespace releasenameonzos.TS2110A check data tablespace releasenameonzos.TS830A check data tablespace communitynameonzos.TS4010B check data tablespace communitynameonzos.TS280B check data tablespace communitynameonzos.TS2110B check data tablespace customizationnameonzos.TS2110C check data tablespace jcrdbnameonzos.EVTSGATH check data tablespace jcrdbnameonzos.ICMSFQ04 check data tablespace jcrdbnameonzos.TS2110D

...where releasenameonzos, communitynameonzos, and customizationnameonzos are the names of the WebSphere Portal databases, and jcrdbnameonzos is the name of the JCR database. Refer to the Utility Guide and Reference for DB2 for z/OS for additional details.

After transferring to WebSphere Portal, you should run the RUNSTATS utility as shown in the following example:
LISTDEF JCRDBZOS INCLUDE TABLESPACE JCRDBZOS.* BASE RUNSTATS TABLESPACE LIST JCRDBZOS INDEX(ALL) KEYCARD TABLE(ALL) LISTDEF JCRDB01 INCLUDE TABLESPACE JCRDB01.* BASE RUNSTATS TABLESPACE LIST JCRDB01 INDEX(ALL) KEYCARD TABLE(ALL) ...

Start the WebSphere Application Server.

Verify that the WebSphere Portal application server is running by opening the following URL in a browser: http://hostname.companyname.com:port/wps/portalif, where hostname.companyname.com is the fully qualified host name of the machine where WebSphere Portal is running and port is the transport port that is created by WebSphere Application Server.

Next steps
You have completed this step. Continue to the next step:

Verifying database connections

Parent topic:
Transferring all domains

Database domain properties
Property	Value
dbdomain.DbType	The type of database used to store information for WebSphere Portal. Value type: Alphanumeric text string Recommended value: DB2 for z/OS and OS/390: db2_zos
dbdomain.DbName	Description: The name of the WebSphere Portal domain database and schema. Notes: This value is also the database element in the dbdomain.DbUrl property. Non-Windows platforms when using DB2 only. This value is the TCPIP Alias for the database. For Oracle, this value should match the 'ORACLE_SID'. Value type: Alphanumeric text string Notes: For DB2 and DB2 for z/OS, this value cannot exceed 8 characters and can only contain letters and numbers. Refer to the database documentation for more information. For DB2, this value must be different from the value of dbdomain.XDbName. If you change the name of the WebSphere Portal data source due to a database migration, manually update this property in the portal_server_root/config/wpconfig_dbdomain.properties file to maintain the proper resource reference mapping. Default value for all domains: wpsdb
dbdomain.DbNameOnZos	Description: The name of the WebSphere Portal database on DB2 for z/OS. Value type: Alphanumeric text string Default: Release: WPSTST02 Customization: WPSTST02 Community: WPSTST02 JCR: WPSTST02 WMM: WPSTST02 Feedback: WPSTST02 LikeMinds: WPSTST02
dbdomain.DbUrl	The database URL used to access the WebSphere Portal database with JDBC. The value must conform to standard JDBC URL syntax. The database element of this value should match the value of dbdomain.DbName. Value type: Alphanumeric text string, conforming to standard JDBC URL syntax Recommended: DB2 for z/OS (local): jdbc:db2:location DB2 for z/OS (remote): jdbc:db2:wpsdb
dbdomain.DbUser	Description: The user ID for the database administrator. Notes: For SQL Server and non-wmm databases only, unless you are the system administrator, the values for dbdomain.DbUser and dbdomain.DbSchema must be the same. For Oracle and SQL Server servers, this value must be set to FEEDBACK, which corresponds to the user FEEDBACK in the database. If the user you are using is an administrative user that has authority over the FEEDBACK schema, the administrative user should be entered for the dbdomain.DbUser property. Value type: Alphanumeric text string Default: Release: db2admin Community: db2admin Customization: db2admin JCR: db2admin WMM: db2admin Feedback: db2admin LikeMinds: db2admin Recommended: wpsdbusr (for databases other than DB2 )
dbdomain.DbPassword	Description: The password for the database administrator. A value must be set for this property; it cannot be empty. Value type: Alphanumeric text string Default value for all domains: ReplaceWithYourDbAdminPwd
dbdomain.XDbName	Description: The database loop back alias that needs to be set if you plan to use the create-local-database-db2 task. Notes: For DB2, this value must be different from the value of dbdomain.DbName. Value type: Alphanumeric text string Default: Release: wps6TCP Community: wps6TCP Customization: wps6TCP WMM: wps6TCP JCR: wps6TCP Feedback: fdbk6TCP LikeMinds: lmdb6TCP
dbdomain.DbNode	Description: The value for the node database. Required for non-Windows platforms when using DB2 only. Value type: Alphanumeric text string Default values: Release: wpsNode Community: wpsNode Customization: wpsNode JCR: wpsNode WMM: wpsNode Feedback value: pznNode LikeMinds value: pznNode
dbdomain.DbSchema	The schema name of the database domain. Notes: This property is not used on Member Manager, which only uses the dbdomain.DbUser name as the schema. Follow the documentation of the target database management system in order to define a valid schema name as restrictions apply for some database management systems. For SQL Server only, unless you are the system administrator, the values for dbdomain.DbUser and dbdomain.DbSchema must be the same. For Oracle and SQL Server servers, the value must be set to FEEDBACK. Value type: Alphanumeric text string Default: dbdomain
dbdomain.DataSourceName	Description: The name of the data store that WebSphere Portal uses to communicate with its databases. Notes: If the DbUser, DbUrl, and DbPassword are not the same across domains, this value must differ from the DataSourceName of the other domains. The value for dbdomain.DataSourceName should not be set to the same value as dbdomain.DbName. Value type: Alphanumeric text string Default values: Release: wpsdbDS Community: wpsdbDS Customization: wpsdbDS JCR: JCRDS WMM: wpsdbDS Feedback: feedback5 LikeMinds: lmdbDS

DB2 Content Manager Runtime Edition properties
Property	Value
jcr.DbHost	Description: The hostname of the system hosting the DB2 Content Manager Runtime Edition database. Required for DB2 for z/OS and OS/390 only. Value type: Alphanumeric text string
jcr.DbDomain	Description: The domain of the system hosting the DB2 Content Manager Runtime Edition database. Required for DB2 for z/OS and OS/390 only. Value type: Alphanumeric text string
jcr.ZosDbPrefix	Description: Common prefix of Node Type database names for the DB2 Content Manager Runtime Edition database. Required for DB2 for z/OS and OS/390 only. Recommended: Set this value according to your own environment, to match the value used when executing the commands to create the database found in the file Creating the DB2 Content Manager Runtime Edition database. Default: ICM
jcr.ZosDbMaxTables	Description: Maximum number of User Defined Tables to be stored in a particular Node Type DB in the DB2 Content Manager Runtime Edition database. Required for DB2 for z/OS and OS/390 only. Recommended: 400. Default: 400
jcr.DbStorageGroup	Description: The storage group for the DB2 Content Manager Runtime Edition database. Required for DB2 for z/OS and OS/390 only. Recommended: Set this value according to your own environment, to match the value used when executing the commands to create the database found in the file Creating the DB2 Content Manager Runtime Edition database. Default: WPSSG
jcr.DbVolumes	Description: The volumes for the DB2 Content Manager Runtime Edition database. Required for DB2 for z/OS and OS/390 only. Recommended: Set this value according to your own environment, to match the value used when executing the commands to create the database found in the file Creating the DB2 Content Manager Runtime Edition database. Default: *
jcr.DbVcat	Description: The VCAT for the DB2 Content Manager Runtime Edition database. Required for DB2 for z/OS and OS/390 only. Recommended: Set this value according to your own environment, to match the value used when executing the commands to create the database found in the file Creating the DB2 Content Manager Runtime Edition database. Default: DSN810
jcr.Db4KBufferPoolName	Description: The 4K bufferpool name for the DB2 Content Manager Runtime Edition database. Required for DB2 for z/OS and OS/390 only. Recommended: Set this value according to your own environment, to match the value used when executing the commands to create the database found in the file Creating the DB2 Content Manager Runtime Edition database. Default: BP0
jcr.Db32KBufferPoolName	Description: The 32K bufferpool name for the DB2 Content Manager Runtime Edition database. Required for DB2 for z/OS and OS/390 only. Recommended: Set this value according to your own environment, to match the value used when executing the commands to create the database found in the file Creating the DB2 Content Manager Runtime Edition database. Default: BP32K
jcr.DbPort	Description: Port number of the DB2 Content Manager Runtime Edition database, if not on the local system (required for Driver Type 4 only). Required for DB2 for z/OS and OS/390 only. Recommended: Set this value according to your own environment. Default: 446

Database type properties
Property	Value
DbSafeMode	This only applies to database-specific tasks. If this property is set to true, database-specific tasks, such as create/modify/drop database, will not be performed. The property should be used if a pre-configured database (from a previous installation) already exists. If the property is set to false, the database will be updated and the pre-existing database configuration will be overwritten. Recommended: false Default: false
db2_zos.DbDriver	The name of class that SqlProcessor will use to import SQL files. Recommended: COM.ibm.db2.jdbc.app.DB2Driver Windows and UNIX Default: COM.ibm.db2j.jdbc.DB2Driver (Cloudscape )
db2_zos.JdbcProvider	The name of the JDBC provider that WebSphere Portal uses to communicate with its databases. Recommended: wpsdbJDBC_db2_zos Default: wpsdbJDBC_db2_zos
db2_zos.DbLibrary	The directory and name of the.zip or.jar file that contains the JDBC driver class Recommended: microsoftJDBC/lib/jar In UNIX environments, use a colon (:) instead of a semi-colon (;) to separate multiple paths. Windows and UNIX Default value: <SQLLIB>/jcc/classes/db2jcc.jar:<SQLLIB>/jcc/classes/db2jcc_license_cisuz.jar:<SQLLIB>/jcc/classes/db2jcc_javax.jar