manageprofiles parameters for WSRR configuration (per database product)

Use specific manageprofiles command parameters to configure the WSRR database. When you create or augment stand-alone profiles, you can configure the WSRR database using the manageprofile commands. The parameters that you specify differ depending on the database product you are using.

The tables in this topic show the manageprofiles parameters available to configure the WSRR using any supported database product. Parameters associated with database configuration generally have a "-db" prefix; for example -dbType, and -dbDelayConfig. The parameters for the optional separate Service Integration Bus database have a "sib" prefix; for example -sibDbUserId.
Note: If you do not want to use a separate database for either the Activity Logging or Service Integration Bus, ignore all the -act* and -sib* parameters. They default to their -db equivalents and the tables are created in the same database.
Also shown are the equivalent field names for the parameters as they are displayed in the Profile Management Tool.

For a complete list of manageprofiles parameters, including default values, see the topics manageprofiles parameters: deployment manager profiles and manageprofiles parameters: custom profiles.

To view available parameters for database configuration, choose your database product from the following list:
Note:
Sample response files for manageprofiles for a number of different scenarios are provided in the following directory. They can be used as they are, or amended as necessary.
  • For Linux operating systemFor Unix operating system install_root/WSRR/install/profiles-responsefiles
  • For Windows operating system install_root\WSRR\install\profiles-responsefiles

On DB2 Universal or DB2 Express

Table 1 shows the manageprofiles parameters available to configure the WSRR database used by a stand-alone server or deployment manager profile on DB2® Universal or DB2 Express®.

Table 1. Available manageprofiles parameters for configuration of WSRR database using DB2 Universal or DB2 Express
Parameter Related field on Database Configuration pages in Profile Management Tool
N/A Override the destination directory for generated scripts.
-dbCreateNew N/A
-dbDelayConfig Delay running of database scripts (must select if using a remote database).
-dbHostName Database server host name (for example, IP address).
-dbJDBCClasspath Location (directory) of JDBC driver classpath files.
-dbName WSRR database name.
-dbOutputScriptDir Database script output directory.
-dbPassword Password for database authentication.
-dbServerPort Server port.
-dbSchemaName WSRR database schema name.
Note: The -dbSchemaName parameter must always be specified regardless of whether or not you are using separate databases, and has the value of the WSRR database schema name.
-dbSysPassword DB2 instance owner's password.
-dbSysUserId DB2 instance owner .
-dbType Choose a database product. Set the value to DB2_DATASERVER.
-dbUserId User name to authenticate with the database.
Activity Logging parameters  
-actDbHostName (Optional) Activity Logging database server host name (for example, IP address).
-actDbName (Optional) Activity Logging database name.
-actDbPassword (Optional) Password for Activity Logging database authentication.
-actDbSchemaName Activity Logging database schema name.
Note: The -actDbSchemaName parameter must always be specified regardless of whether or not you are using separate databases, and has the value of the Activity Logging schema name.
-actDbServerPort (Optional) Activity Logging database server port.
-actDbUserId (Optional) User name to authenticate with the Activity Logging database.
Service Integration Bus parameters  
-sibDbHostName (Optional) Service Integration Bus database server host name (for example IP address).
-sibDbName (Optional) Service Integration Bus database name.
-sibDbPassword (Optional) Password for Service Integration Bus database authentication.
-sibDbSchemaName Service Integration Bus database schema name.
Note: The -sibDbSchemaName parameter must always be specified regardless of whether or not you are using separate databases, and has the value of the Service Integration Bus schema name.
-sibDbServerPort (Optional) Service Integration Bus database server port.
-sibDbUserId (Optional) User name to authenticate with the Service Integration Bus database.

On DB2 for z/OS

Table 2 shows the manageprofiles parameters available to configure the WSRR database used by a stand-alone server or deployment manager profile on DB2 for z/OS®.

Table 2. Available manageprofiles parameters for WSRR database using DB2 for z/OS
Parameter Related field on Database Configuration pages in Profile Management Tool
N/A Override the destination directory for generated scripts.
-dbConnectionLocation Connection location.
-dbCreateNew (must be set to false, or should not be specified) N/A
-dbDelayConfig Delay running of database scripts (must select if using a remote database).
-dbFunctionPath Database function path for stored procedures.
-dbJDBCClasspath Location (directory) of JDBC driver classpath files.
-dbHostName Database server host name (for example, IP address).
-dbName WSRR database name.
-dbOutputScriptDir Database script output directory.
-dbPassword Password for database authentication.
-dbSchemaName WSRR database schema name.
Note: The -dbSchemaName parameter must always be specified regardless of whether or not you are using separate databases, and has the value of the WSRR database schema name.
-dbServerPort Server port.
-dbStorageGroup (Optional) Storage group name.
-dbType Choose a database product. Set the value to DB2UDBOS390.
-dbUserId User name to authenticate with the database.
Activity Logging parameters  
-actDbHostName (Optional) Activity Logging database server host name (for example, IP address).
-actDbName (Optional) Activity Logging database name.
-actDbPassword (Optional) Password for Activity Logging database authentication.
-actDbSchemaName Activity Logging database schema name.
Note: The -actDbSchemaName parameter must always be specified regardless of whether or not you are using separate databases, and has the value of the Activity Logging schema name.
-actDbServerPort (Optional) Activity Logging database server port.
-actDbSqlid (Optional) Activity Logging Database SQL ID.
Service Integration Bus parameters  
-sibDbHostName (Optional) Service Integration Bus database server host name (for example, IP address).
-sibDbName (Optional) Service Integration Bus database name.
-sibDbPassword (Optional) Password for Service Integration Bus database authentication.
-sibDbSchemaName Service Integration Bus database schema name.
Note: The -sibDbSchemaName parameter should always be specified regardless of whether or not you are using separate databases, and has the value of the Service Integration Bus schema name.
-sibDbServerPort (Optional) Service Integration Bus database server port.
-sibDbUserId (Optional) User name to authenticate with the Service Integration Bus database.

On Oracle

Table 3 shows the manageprofiles parameters available to configure the WSRR database used by a stand-alone server or deployment manager on Oracle.

Table 3. Available manageprofiles parameters for configuration of WSRR database using Oracle
Parameter Related field on Database Configuration pages in Profile Management Tool
N/A Override the destination directory for generated scripts.
-oracleOSUser The operating system ID who owns the oracle installation files. Default is 'oracle'.
-dbCreateNew (must be set to false, or should not be specified) N/A
-dbDelayConfig Delay running of database scripts (must select if using a remote database).
-dbHostName Database server host name (for example, IP address).
-dbJDBCClasspath Location (directory) of JDBC driver classpath files.
-dbName WSRR database name.
-dbOutputScriptDir Database script output directory.
-dbPassword Password for database authentication.
-dbServerPort Server port.
-dbSysPassword The password for the operating system user identified by -dbSysUserId .
-dbSysUserId The oracle database SYSTEM user. Default is 'system'.
-dbType Choose a database product. Set the value to ORACLE.
-dbUserId User name to authenticate with the database.
Activity Logging parameters  
-actDbHostName (Optional) Activity Logging database server host name (for example, IP address).
-actDbName (Optional) Activity Logging database name.
-actDbPassword (Optional) Password for Activity Logging database authentication.
-actDbServerPort (Optional) Activity Logging database server port.
-actDbUserId (Optional) User name to authenticate with the Activity Logging database.
Service Integration Bus parameters  
-sibDbHostName (Optional) Service Integration Bus database server host name (for example, IP address).
-sibDbName (Optional) Service Integration Bus database name.
-sibDbPassword (Optional) Password for Service Integration Bus database authentication.
-sibDbSchemaName Service Integration Bus database schema name.
Note: The -sibDbSchemaName parameter should always be specified regardless of whether or not you are using separate databases, and has the value of the Service Integration Bus schema name.
-sibDbServerPort (Optional) Service Integration Bus database server port.
-sibDbUserId (Optional) User name to authenticate with the Service Integration Bus database.

On Microsoft SQL Server

Table 4 shows the manageprofiles parameters that are available to configure the WSRR database that is used by a stand-alone server or deployment manage profile on Microsoft SQL Server. The supported JDBC driver for this database is the Microsoft SQL Server JDBC Driver, version 1.2.
Note: You cannot create a SQL Server database during profile creation if the database user is to be authenticated using Windows authentication, rather than SQL Server authentication. You can create the tables in an existing SQL Server database using Windows authentication, however.
Table 4. Available manageprofiles parameters for configuration of WSRR database using Microsoft SQL Server
Parameter Related field on Database Configuration pages in Profile Management Tool
N/A Override the destination directory for generated scripts.
-dbHostName Database server host name (for example, IP address).
-dbName WSRR database name.
-dbOutputScriptDir Database script output directory.
-dbPassword Password for database authentication.
-dbSchemaName WSRR database schema name.
Note: The -dbSchemaName parameter should always be specified regardless of whether or not you are using separate databases, and has the value of the WSRR database schema name.
-dbServerName (Optional) Database server name.
-dbServerPort Server port.
-dbType Choose a database product. Set the value to MSSQLSERVER_MICROSOFT.
-dbUserId User name to authenticate with the database.
Activity Logging parameters  
-actDbHostName (Optional) Activity Logging database server host name (for example, IP address).
-actDbName (Optional) Activity Logging database name.
-actDbPassword (Optional) Password for Activity Logging database authentication.
-actDbSchemaName Activity Logging database schema name.
Note: The -actDbSchemaName parameter should always be specified regardless of whether or not you are using separate databases, and has the value of the Activity Logging schema name.
-actDbServerPort (Optional) Activity Logging database server port.
-actDbUserId (Optional) User name to authenticate with the Activity Logging database.
Service Integration Bus parameters  
-sibDbHostName (Optional) Service Integration Bus database server host name (for example, IP address).
-sibDbName (Optional) Service Integration Bus database name.
-sibDbPassword (Optional) Password for Service Integration Bus database authentication.
-sibDbSchemaName Service Integration Bus database schema name.
Note: The -sibDbSchemaName parameter should always be specified regardless of whether or not you are using separate databases, and has the value of the Service Integration Bus schema name.
-sibDbServerPort (Optional) Service Integration Bus database server port.
-sibDbUserId (Optional) User name to authenticate with the Service Integration Bus database.