You use specific manageprofiles command parameters to configure the Common database. Parameters you specify can differ depending on the database product you are using and on the type of profile you are creating.
The tables in this topic show the manageprofiles parameters available to configure the Common database using any supported database product. Parameters associated with Common database configuration generally have a "-db" prefix (-dbType, -dbDelayConfig, etc.). For a complete list of manageprofiles parameters, including default values, see the topic manageprofiles parameters. Example manageprofiles commands used to create or augment various types of profiles can be viewed in the topics Creating profiles with manageprofiles command with Derby or DB2 databases – examples and Augmenting profiles with manageprofiles command with Derby or DB2 databases – examples.
Note that only the -dbType and -dbJDBCClasspath parameters are available for custom profiles. This is because you are simply identifying the type and driver location for the Common database used by the deployment manager to which you will federate the custom profile.
Table 1 shows the manageprofiles parameters available to configure the Common database used by a stand-alone server profile on Derby Embedded.
Table 2 shows the manageprofiles parameters available to configure the Common database used by a stand-alone server, deployment manager, or custom profile on Derby Network Server.
Parameter |
---|
For custom profiles |
-dbType |
-dbJDBCClasspath |
For stand-alone server or deployment manager profiles |
-dbCommonForME (for stand-alone server profiles only) |
-dbCreateNew (must always be true) |
-dbHostName |
-dbName |
-dbOutputScriptDir |
-dbPassword |
-dbServerPort |
-dbType |
-dbUserId |
-fileStoreForME (for stand-alone server profiles only) |
Table 3 shows the manageprofiles parameters available to configure the Common database used by a stand-alone server, deployment manager, or custom profile on DB2 Universal.
Parameter |
---|
For custom profiles |
-dbJDBCClasspath |
-dbType |
For stand-alone server or deployment manager profiles |
-dbCommonForME (for stand-alone server profiles only) |
-dbCreateNew |
-dbDelayConfig |
-dbDriverType |
-dbHostName |
-dbJDBCClasspath |
-dbName |
-dbOutputScriptDir |
-dbPassword |
-dbServerPort |
-dbType |
-dbUserId |
-fileStoreForME (for stand-alone server profiles only) |
Table 4 shows the manageprofiles parameters available to configure the Common database used by a stand-alone server, deployment manager, or custom profile on DB2 Universal Runtime Client.
Parameter |
---|
For custom profiles |
-dbJDBCClasspath |
-dbType |
For stand-alone server or deployment manager profiles |
-dbCommonForME (for stand-alone server profiles only) |
-dbCreateNew |
-dbDelayConfig |
-dbJDBCClasspath |
-dbName |
-dbOutputScriptDir |
-dbPassword |
-dbType |
-dbUserId |
-fileStoreForME (for stand-alone server profiles only) |
Table 5 shows the manageprofiles parameters available to configure the Common database used by a stand-alone server, deployment manager, or custom profile on a database supplied with an i5/OS® operating system.
Parameter |
---|
For custom profiles |
-dbJDBCClasspath |
-dbType |
For stand-alone server or deployment manager profiles |
-dbCommonForME (for stand-alone server profiles only) |
-dbCreateNew |
-dbDelayConfig |
-dbHostName (for Toolbox driver, you need to specify the remote database host name) |
-dbJDBCClasspath |
-dbName |
-dbOutputScriptDir |
-dbPassword |
-dbSchemaName |
-dbType |
-dbUserId |
-fileStoreForME (for stand-alone server profiles only) |
Table 6 shows the manageprofiles parameters available to configure the Common database used by a stand-alone server, deployment manager, or custom profile on DB2 for z/OS v8 or DB2 for z/OS v9.
Parameter |
---|
For custom profiles |
-dbJDBCClasspath |
-dbType |
For stand-alone server or deployment manager profiles |
-dbCommonForME (for stand-alone server profiles only) |
-dbConnectionLocation |
-dbCreateNew (must always be false) |
-dbDelayConfig |
-dbHostName |
-dbJDBCClasspath |
-dbName |
-dbOutputScriptDir |
-dbPassword |
-dbSchemaName |
-dbServerPort |
-dbStorageGroup |
-dbType |
-dbUserId |
-fileStoreForME (for stand-alone server profiles only) |
Table 7 shows the manageprofiles parameters available to configure the Common database used by a stand-alone server, deployment manager, or custom profile on Oracle 9i, Oracle 10g, or Oracle 11g.
Parameter |
---|
For custom profiles |
-dbJDBCClasspath |
-dbType |
For stand-alone server or deployment manager profiles |
-dbCommonForME (for stand-alone server profiles only) |
-dbCreateNew (must always be false) |
-dbDelayConfig |
-dbDriverType |
-dbHostName |
-dbJDBCClasspath |
-dbName |
-dbOutputScriptDir |
-dbPassword |
-dbServerPort |
-dbType |
-dbUserId |
-fileStoreForME (for stand-alone server profiles only) |
Table 8 shows the manageprofiles parameters available to configure the Common database used by a stand-alone server, deployment manager, or custom profile on Informix Dynamic Server.
Parameter |
---|
For custom profiles |
-dbJDBCClasspath |
-dbType |
For stand-alone server or deployment manager profiles |
-dbCommonForME (for stand-alone server profiles only) |
-dbCreateNew |
-dbDelayConfig |
-dbHostName |
-dbInstance |
-dbJDBCClasspath |
-dbLocation (only if -dbCreateNew is true) |
-dbName |
-dbOutputScriptDir |
-dbPassword |
-dbServerPort |
-dbType |
-dbUserId |
-fileStoreForME (for stand-alone server profiles only) |
Parameter |
---|
For custom profiles |
-dbJDBCClasspath |
-dbType |
For stand-alone server or deployment manager profiles |
-dbCommonForME (for stand-alone server profiles only) |
-dbCreateNew |
-dbDelayConfig |
-dbHostName |
-dbJDBCClasspath |
-dbName |
-dbOutputScriptDir |
-dbPassword |
-dbServerPort |
-dbType |
-dbUserId |
-fileStoreForME (for stand-alone server profiles only) |