wkplc_dbdomain.properties file reference

wkplc_dbdomain.properties file reference

JCR Properties
The following properties are required to configure the JCR.
jcr.priqtyl
Description: Required only for IBM DB2 for z/OS and OS/390. The primary quantity to be allocated for the tablespaces assigned to user tables in JCR.
Value: Numeric
Examples: No examples are available.
Default: 50000

jcr.secqtyl
Description: Required only for IBM DB2 for z/OS and OS/390. Secondary quantity to be allocated for the tablespaces being assigned to user tables in JCR.
Value: Numeric
Examples: No examples are available.
Default: 10000

jcr.blobBufferpool
Description: Required only for IBM DB2 for z/OS and OS/390. The name of the bufferpool in which the BLOB tablespaces is created. If it is not specified, then the default value specified in the database is used.
Value: No values are available.
Examples: No examples are available.
Default: BP32K1

jcr.bp4ktables
Description: Required only for IBM DB2 for z/OS and OS/390. The name of 4K bufferpools separated by comma used by JCR for user tables.
Value: char
Examples: BP1,BP2
Default: BP1

jcr.bp4kindexes
Description: Required only for IBM DB2 for z/OS and OS/390. The name of 4K bufferpools separated by comma used by JCR to create indexes on user tables.
Value: char
Examples: BP1,BP2
Default: BP1

jcr.bp8ktables
Description: Required only for IBM DB2 for z/OS and OS/390. The name of 4K bufferpools separated by comma used by JCR for user tables.
Value: char
Examples: BP8K1,BP8K2
Default: BP8K1

jcr.bp16ktables
Description: Required only for IBM DB2 for z/OS and OS/390. The name of 4K bufferpools separated by comma used by JCR for user tables.
Value: char
Examples: BP16K1,BP16K2
Default: BP16K1

jcr.bp32ktables
Description: Required only for IBM DB2 for z/OS and OS/390. The name of 4K bufferpools separated by comma used by JCR for user tables.
Value: char
Examples: BP32K1,BP32K2
Default: BP32K1

Personalization Feedback Database Properties

feedback.DbType
Description: The type of database that WebSphere Portal will use for the feedback database.
Value: Valid database types include:
IBM DB2 Database: db2
IBM DB2 for i: db2_iseries
IBM DB2 for z/OS: db2_zos
Oracle Database: oracle
Microsoft SQL Server 2005: sqlserver2005
Microsoft SQL Server 2008: sqlserver2005
IBM Derby: derby

Examples: db2
Default: derby

InitializeFeedbackDB
Description: Determines how to handle the Personalization feedback database during database transfer from Derby to another DB type.
Value: Valid values include:
true: to transfer data from a Derby database
false: to redirect the feedback DataSource to a preexisting database

Examples: No examples are available.
Default: true

feedback.DbName
Description: The name of the feedback database. The value should be the same as the database element in feedback.DbUrl value
Value: The following conditions effect the value for this property:
If WebSphere Portal is configured to use IBM DB2 for i, this value must be unique for this domain.
If WebSphere Portal is configured to use a remote IBM DB2 database for IBM i, the value must include the host name, such as: hostName/wpsfdbdb
If WebSphere Portal is installed on Linux and UNIX-based platforms and configured to use IBM DB2, this value is the TCPIP Alias for the database.

Examples: No examples available.
Default: wpsdb

feedback.DbSchema
Description: Feedback domain database schema name. To determine a valid schema name, see the documentation for the database that you are using. Schema name restrictions apply for some databases.
Value: A valid schema name. If you are using IBM DB2 for i, the value must be less than 10 characters.
Examples: No examples available.
Default: FEEDBACK

feedback.DbNameOnZos
Description: Required for IBM DB2 for z/OS only.
Value: string The following conditions effect the value for this property:
If WebSphere Portal is installed on z/OS and is configured to use IBM DB2 for z/OS, the value must be the same as the feedback.DbName value.
If WebSphere Portal is configured to use a remote IBM DB2 for z/OS database, the value should be the same as the name of the remote Feedback database.

Examples: No examples available.
Default: WPSTST02

feedback.DataSourceName
Description: The name of the datasource to use for the feedback database.
Value: The following reserved names cannot be used for this value: releaseDS, communityDS, customizationDS, jcrDS, lmdbDS, feedback
Examples: No examples available.
Default: wpdbDS

feedback.DbUrl
Description: The feedback database URL.
Value: The database element of this value should match the value of DbName. The following conditions effect the value for this property:
For IBM DB2 for i when WebSphere Portal is installed on a UNIX platform, add ;prompt=false to the URL unless X11 DISPLAY is set and active.
For IBM DB2 for z/OS, the database element of this value should match the location name of the database to be used when establishing connections with the IBM DB2 datasource used by portal.

Examples: Use one of the following examples with values specific to database:
Derby database: jdbc:derby:wpsdb;create=true
IBM DB2 with type 2 drivers: jdbc:db2:wpsdb
IBM DB2 with type 4 drivers: jdbc:db2:// <YourDatabaseServer> :50000/wpsdb:returnAlias=0; Where the port is usually 50000 (Windows) or 50001 (Linux)
IBM DB2 for i with type 2 drivers: jdbc:db2:*LOCAL/wpsdb;metadata source=1
IBM DB2 for i with type 4 drivers: jdbc:as400: <hostName> /wpsdb;metadata source=1
Remote IBM DB2 for i with type 4 drivers: jdbc:as400: <hostName> /wpsdb;metadata source=1;prompt=false
IBM DB2 for z/OS: jdbc:db2: <location>
Remote IBM DB2 for z/OS with type 2 drivers: jdbc:db2:wpsdb
Remote IBM DB2 for z/OS with type 4 drivers: jdbc:db2:// <YourDatabaseServer> : <port> / <location>
Thin Oracle Database with type 4 drivers and thin client: jdbc:oracle:thin:@ <YourDatabaseServer> :1521:wpsdb
Microsoft SQL Server 2005 and 2008: jdbc:sqlserver:// <YourDatabaseServer> :1433;SelectMethod=cursor;DatabaseName=wpsdb
DataDirect SQL Server 2005 and 2208: jdbc:datadirect:sqlserver:// <YourDatabaseServer> :1433;DatabaseName=wpsdb

Default: jdbc:derby:wpsdb;create=true

feedback.DbUser
Description: Thhe database administrator user ID.
Value: A valid database user ID.
Examples: No examples available
Default: db2admin

feedback.DbPassword
Description: The database password for the administrator user ID.
Value: A valid database password.
Examples: No examples available
Default: ReplaceWithYourDbAdminPwd

feedback.DbRuntimeUser
Description: Optional parameter. WebSphere Portal will use this ID to connect to the feedback database during day-to-day operations. If WebSphere Portal can connect using the same ID used during configuration, the feedback.DbUser value, then leave this value blank.
Value: A valid database user ID.
Examples: No examples available.
Default: no default

feedback.DbRuntimePassword
Description: The password for the database runtime user ID.
Value: A valid database password.
Examples: No examples available
Default: ReplaceWithYourDbRuntimePwd

feedback.DBA.DbUser
Description: The DBA user ID for privileged access operations during creation of this database type.
Value: A valid database ID.
Examples: No examples available.
Default: db2admin

feedback.DBA.DbPassword
Description: The password for the privileged DBA user ID used to access operations during creation of the feedback database.
Value: A valid database password
Examples: No examples available.
Default: ReplaceWithYourDBAPwd

feedback.DbHome
Description: The root location for the feedback database. For Oracle, this is the location on the remote or local database server where the tablespaces are created. For SQL Server, this is the local location where the database files are stored. For SQL Server on Windows the path must use two back slashes (//) instead of a forward slash (/). For SQL Server the <instance> in the example path below may or may not exist for installation.
Value: No values is available.
Examples: Use the following example that is appropriate for database:
Oracle: <oracle> /product/10.1.0/db_1
SQL Server: C://Microsoft SQL Server// <instance> //MSSQL

Default: ReplaceWithYourDbHomeDir

feedback.AdminUrl
Description: Required for SQL Server only. This value is the SQL Server URL without a database attached. This value is used to connect to SQL Server for DBA operations.
Value: No values are available.
Examples: Use the appropriate Administrator URL example for database
Microsoft SQL Server 2005: jdbc:sqlserver:// <YourDatabaseServer> :1433
DataDirect SQL Server 2005: jdbc:datadirect:sqlserver:// <YourDatabaseServer> :1433
Microsoft SQL Server 2008: jdbc:sqlserver:// <YourDatabaseServer> :1433
DataDirect SQL Server 2008: jdbc:datadirect:sqlserver:// <YourDatabaseServer> :1433

Default: ReplaceWithYourAdminUrl

feedback.DbConfigRoleName
Description: Required for Oracle Database only. The name of the role created and assigned to the configuration database user (feedback.DbUser).
Value: A database role name
Examples: No examples available.
Default: WP_PZN_CONFIG_USERS

feedback.DbRuntimeRoleName
Description: Required for Oracle Database only. The name of the role created and assigned to the runtime database user (feedback.DbRuntimeUser).
Value: A database role name
Examples: No examples are available,
Default: WP_PZN_RUNTIME_USERS

feedback.XDbName
Description: Required for Linux and UNIX-based platforms when using a IBM DB2 database. Required for a local IBM DB2 Database using a type 2 JDBC driver. The feedback database alias that needs to be set if you want to call create-database
Value: valid database name
Examples: No examples available,
Default: fdbk6TCP

feedback.DbNode
Description: Required for Linux and UNIX-based platforms when using IBM DB2. The node for the feedback database The value is required if you want to run the create-database task.
Value: No values are available.
Examples: No examples available.
Default: pznNode

feedback.DbHostName
Description: Required for Microsoft SQL Server 2005 and 2008 only. The host name of the feedback database.
Value: No values available.
Examples: No examples available.
Default: myserver

feedback.DbTablespace
Description: Required for IBM DB2 for z/OS only. The name of the feedback database tablespace.
Value: No values are available.
Examples: No examples are available.
Default: fdbkdbts

feedback.DbStorageGroup
Description: Required for IBM DB2 for z/OS only. The storage group for the feedback database.
Value: No values are available.
Examples: No examples are available.
Default: WPSSG

feedback.DbVolumes
Description: Required for IBM DB2 for z/OS only. The volumes for the feedback database.
Value: No values are available.
Examples: No examples are available.
Default: *

feedback.DbVcat
Description: Required for IBM DB2 for z/OS only. The VCAT for the WebSphere Portal feedback database.
Value: No values available.
Examples: No examples available.
Default: DSN810

feedback.Db4KBufferPoolName
Description: Required for IBM DB2 for z/OS only. The 4K bufferpool name for the feedback database.
Value: No values are available.
Examples: No examples are available.
Default: BP2

feedback.Db32KBufferPoolName
Description: Required for IBM DB2 for z/OS only. The 32K bufferpool name for the feedback database.
Value: No values available.
Examples: No examples available.
Default: BP32K1

LikeMinds Database Properties

likeminds.DbType
Description: The type of database to be used for the Likeminds database.
Value: Use on of the following valid database types:
IBM DB2 Database: db2
IBM DB2 for i: db2_iseries
IBM DB2 for z/OS: db2_zos
Oracle Database: oracle
Microsoft SQL Server 2005: sqlserver2005
Microsoft SQL Server 2008: sqlserver2005
IBM Derby: derby

Examples: db2
Default: derby

likeminds.DbName
Description: The name of the Likeminds database. Should also appear as the database element in likeminds.DbUrl
Value: The following conditions effect the value for this property:
For IBM DB2 databases on Linux and UNIX-based platforms, this value is the TCPIP Alias for the database.
For IBM DB2 for i, the database name must be unique for this domain
For IBM DB2 for i database that are installed on a remote server the valude must include the host name, such as: hostName/wpslkmdb

Examples: wplsdb
Default: wpsdb

likeminds.DbSchema
Description: The Likeminds domain database schema name. To determine a valid schema name, see the documentation for the database that you are using. Schema name restrictions apply for some databases.
Value: A valid schema name. For IBM DB2 i, this value must be less than 10 characters.
Examples: likeminds
Default: likeminds

likeminds.DbNameOnZos
Description: Required for IBM DB2 for z/OS only.
Value: The following conditions effect the value for this property:
If the database type is IBM DB2 for z/OS (db2_zos) and the database is remote, this value is the name of the remote Likeminds domain database.
If WebSphere Portal is installed on z/OS with a local database (database type is db2_zos), this value must be the same value as the database name (DbName).

Examples: No examples are available.
Default: WPSTST02

likeminds.DataSourceName
Description: The name of the datasource that will be used for the Likeminds domain.
Value: The following reserved names must not be specified: releaseDS, communityDS, customizationDS, jcrDS, lmdbDS, feedback
Examples: No examples are available.
Default: wpdbDS

likeminds.DbUrl
Description: The Likeminds domain database URL.
Value: The following conditions effect the value for this property:
The database element of this value should match the value of DbName property.
For IBM DB2 for i when WebSphere Portal is installed on a UNIX platform, add ;prompt=false to the URL unless X11 DISPLAY is set and active.
For IBM DB2 for z/OS, the database element of this value should match the location name of the database to be used when establishing connections with the IBM DB2 datasource used by the portal.

Examples: Use one of the following examples with values specific to database.
Derby database: jdbc:derby:wpsdb;create=true
IBM DB2 with type 2 drivers: jdbc:db2:wpsdb
IBM DB2 with type 4 drivers: jdbc:db2:// <YourDatabaseServer> :50000/wpsdb:returnAlias=0; Where the port is usually 50000 (Windows) or 50001 (Linux)
IBM DB2 for i with type 2 drivers: jdbc:db2:*LOCAL/wpsdb;metadata source=1
IBM DB2 for i with type 4 drivers: jdbc:as400: <hostName> /wpsdb;metadata source=1
Remote IBM DB2 for i with type 4 drivers: jdbc:as400: <hostName> /wpsdb;metadata source=1;prompt=false
IBM DB2 for z/OS: jdbc:db2: <location>
Remote IBM DB2 for z/OS with type 2 drivers: jdbc:db2:wpsdb
Remote IBM DB2 for z/OS with type 4 drivers: jdbc:db2:// <YourDatabaseServer> : <port> / <location>
Thin Oracle Database with type 4 drivers and thin client: jdbc:oracle:thin:@ <YourDatabaseServer> :1521:wpsdb
Microsoft SQL Server 2005 and 2008: jdbc:sqlserver:// <YourDatabaseServer> :1433;SelectMethod=cursor;DatabaseName=wpsdb
DataDirect SQL Server 2005 and 2208: jdbc:datadirect:sqlserver:// <YourDatabaseServer> :1433;DatabaseName=wpsdb

Default: jdbc:derby:wpsdb;create=true

likeminds.DbUser
Description: The database administrator user ID.
Value: Alphanumeric text string
Examples: No examples are available
Default: db2admin

likeminds.DbPassword
Description: The database administrator password.
Value: Alphanumeric text string
Examples: No examples are available.
Default: ReplaceWithYourDbAdminPwd

likeminds.DbRuntimeUser
Description: Optional parameter. WebSphere Portal will use this ID to connect to the feedback database during day-to-day operations. WebSphere Portal can connect using the same ID used during configuration, the likeminds.DbUser value, then leave this value blank.
Value: A valid database user ID.
Examples: No examples available.
Default: no default is available

likeminds.DbRuntimePassword
Description: The passwrod for the database runtime user.
Value: Alphanumeric text string
Examples: No examples are available.
Default: ReplaceWithYourDbRuntimePwd

likeminds.DBA.DbUser
Description: The DBA user ID for privileged access operations during creation of this database type.
Value: A valide database ID.
Examples: No examples are available.
Default: db2admin

likeminds.DBA.DbPassword
Description: The password for priviledged access operations during creation of this database type.
Value: Alphanumeric text string
Examples: No examples are available.
Default: ReplaceWithYourDBAPwd

likeminds.DbHome
Description: The root location for the database. For Oracle Database this is the location on the remote or local server where the tablespaces are created For SQL Server this is the location locally to store the database files.
Value: A valid installation path for the database. The following conditions effect the value for this property:
For SQL Server on Windows, this path must use // instead of /.
In the SQL Server example, <instance> may or may not be included in the installation path

Examples: The following are examples:
Oracle Database: <oracle> /product/10.1.0/db_1
SQL Server: C://Microsoft SQL Server// <instance> //MSSQL

Default: ReplaceWithYourDbHomeDir

likeminds.AdminUrl
Description: Required for SQL Server only. This value is the SQL Server URL without a database attached. This value is used to connect to SQL Server for DBA operations.
Value: A valid database server URL
Examples: The following are examples:
Microsoft SQL Server 2005: jdbc:sqlserver:// <YourDatabaseServer> :1433
DataDirect SQL Server 2005: jdbc:datadirect:sqlserver:// <YourDatabaseServer> :1433
Microsoft SQL Server 2008: jdbc:sqlserver:// <YourDatabaseServer> :1433
DataDirect SQL Server 2008: jdbc:datadirect:sqlserver:// <YourDatabaseServer> :1433

Default: ReplaceWithYourAdminUrl

likeminds.DbConfigRoleName
Description: Required for Oracle only The role that will be created and assigned to the configuration database user (likeminds.DbUser).
Value: string
Examples: No examples are available.
Default: WP_PZN_CONFIG_USERS

likeminds.DbRuntimeRoleName
Description: Required for Oracle only Name of the role that will be created and assigned to the runtime database user (likeminds.DbRuntimeUser).
Value: No values are available,
Examples: No examples are available,
Default: WP_PZN_RUNTIME_USERS

likeminds.XDbName
Description: Required for Linux and UNIX-based platforms when using an IBM DB2 Database. Required Windows platforms using a local IBM DB2 database using Type 2 JDBC drivers. The Likeminds database alias used when running the create-database task.
Value: No values are available,
Examples: No examples are available,
Default: lmdb6TCP

likeminds.DbNode
Description: Required for Linux and UNIX-based platforms when using an IBM DB2 Database. The node for the Likeminds domain database used when running the create-database task.
Value: No values are available.
Examples: No examples are available.
Default: pznNode

likeminds.DbHostName
Description: Required only for Microsoft SQL Server 2005 and 2008. The host name of the Likeminds database.
Value: No values are available.
Examples: No examples are available.
Default: myserver

likeminds.DbTablespace
Description: Required only for IBM DB2 for z/OS. The name of the Likeminds database table space.
Value: No values are available.
Examples: No examples are available.
Default: lmdbts

likeminds.DbStorageGroup
Description: Required only for IBM DB2 for z/OS. The storage group for the WebSphere Portal Likeminds database.
Value: No values are available.
Examples: No examples are available.
Default: WPSSG

likeminds.DbVolumes
Description: Required only for BM DB2 for z/OS. The volumes for the WebSphere Portal Likeminds database.
Value: No values are available.
Examples: No examples are available.
Default: *

likeminds.DbVcat
Description: Required only for IBM DB2 for z/OS. The VCAT for the Likeminds database.
Value: No values are available.
Examples: No examples are available.
Default: DSN810

likeminds.Db4KBufferPoolName
Description: Required only for IBM DB2 for z/OS. The 4K bufferpool name for the Likeminds database.
Value: No values are available.
Examples: No examples are available.
Default: BP2

likeminds.Db32KBufferPoolName
Description: Required only for IBM DB2 for z/OS. The 32K bufferpool name for the Likeminds database.
Value: No values are available.
Examples: No examples are available.
Default: BP32K1

Release Database Properties

release.DbType
Description: Type of database to be used for the WebSphere Portal Release domain.
Value: The following are valid database types:
IBM DB2: db2
IBM DB2 for i: db2_iseries
IBM DB2 for z/OS: db2_zos
Derby: derby
Microsoft SQL Server 2005: sqlserver2005
Microsoft SQL Server 2008: sqlserver2005
Oracle Database: oracle

Examples: derby
Default: derby

release.DbName
Description: Name of the release database
Value: Should also appear as the database element in DbUrl. The following conditions effect the value for this property:
For Linux and UNIX-based platforms using IBM DB2, this value is the TCPIP Alias.
For IBM DB2 for i, this value must be unique for this domain

Examples: For remote IBM DB2 for i the value must include the host name, such as: hostname/wpsreldb
Default: wpsdb

release.DbSchema
Description: WebSphere Portal Release domain database schema name. 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.
Value: A valid schema name. For IBM DB2 for i, this value must be less than 10 characters
Examples: No examples are available.
Default: release

release.DbNameOnZos
Description: Required for DB2 for z/OS only
Value: The following conditions effect the value for this property:
If running db2_zos as remote database, this value is the name of the remote WebSphere Portal database.
If portal is running on z/OS with db2_zos, set this value equal to DbName.

Examples: No examples are available.
Default: WPSTST02

release.DataSourceName
Description: Name of datasource to be used for WebSphere Portal Release Domain
Value: The following reserved names must not be specified: releaseDS, communityDS, customizationDS, jcrDS, lmdbDS, feedback
Examples: No examples are available.
Default: wpdbDS

release.DbUrl
Description: This value is the wps release domain database URL.
Value: The database element of this value should match the value of DbName property.
For IBM DB2 for i when WebSphere Portal is installed on a UNIX platform, add ;prompt=false to the URL unless X11 DISPLAY is set and active.
For IBM DB2 for z/OS, the database element of this value should match the location name of the database to be used when establishing connections with the IBM DB2 datasource used by the portal.

Examples: Use one of the following examples with values specific to database.
Derby database: jdbc:derby:wpsdb;create=true
IBM DB2 with type 2 drivers: jdbc:db2:wpsdb
IBM DB2 with type 4 drivers: jdbc:db2:// <YourDatabaseServer> :50000/wpsdb:returnAlias=0; Where the port is usually 50000 (Windows) or 50001 (Linux)
IBM DB2 for i with type 2 drivers: jdbc:db2:*LOCAL/wpsdb;metadata source=1
IBM DB2 for i with type 4 drivers: jdbc:as400: <hostname> /wpsdb;metadata source=1
Remote IBM DB2 for i with type 4 drivers: jdbc:as400: <hostname> /wpsdb;metadata source=1;prompt=false
DB2 for z/OS: jdbc:db2: <location>
Remote DB2 for z/OS with type 2 drivers: jdbc:db2:wpsdb
Remote DB2 for z/OS with type 4 drivers: jdbc:db2:// <YourDatabaseServer> : <port> / <location>
Thin Oracle Database with type 4 drivers and thin client: jdbc:oracle:thin:@ <YourDatabaseServer> :1521:wpsdb
Microsoft SQL Server 2005 and 2008: jdbc:sqlserver:// <YourDatabaseServer> :1433;SelectMethod=cursor;DatabaseName=wpsdb
DataDirect SQL Server 2005 and 2208: jdbc:datadirect:sqlserver:// <YourDatabaseServer> :1433;DatabaseName=wpsdb

Default: jdbc:derby:wpsdb;create=true

release.DbUser
Description: Database administrator user ID.
Value: Alphanumeric text string
Examples: No examples are available.
Default: db2admin

release.DbPassword
Description: Database administrator password
Value: No values are available
Examples: No examples are available
Default: ReplaceWithYourDbAdminPwd

release.DbRuntimeUser
Description: Optional parameter. WebSphere Portal will use this ID to connect to the release database during day-to-day operations. If WebSphere Portal can connect using the same ID used during configuration, the release.DbUser value, then leave this value blank.
Value: Alphanumeric text string.
Examples: No examples are available.
Default: no default is available

release.DbRuntimePassword
Description: Database runtime user password.
Value: Alphanumeric text string
Examples: No examples are available.
Default: ReplaceWithYourDbRuntimePwd

release.DBA.DbUser
Description: DBA user for privledged access operations during creation of this database type.
Value: Alphanumeric text string
Examples: No examples are available.
Default: db2admin

release.DBA.DbPassword
Description: DBA password for privledged access operations during creation of this database type
Value: Alphanumeric text string
Examples: No examples are available.
Default: ReplaceWithYourDBAPwd

release.DbHome
Description: Root location for the database. For Oracle this is the location on the remote or local machine for create the tablespaces. For SQLServer this is the location locally to store the database files. SQLServer Windows Only: This path must use // instead of /. SQLServer Only: <instance> in the path below may or may not be there in installation.
Value: The following are possible values:
Oracle: { <oracle> /product/10.1.0/db_1 }
SQLServer: { C://Microsoft SQL Server// <instance> //MSSQL }

Examples: No examples are available.
Default: ReplaceWithYourDbHomeDir

release.AdminUrl
Description: Required for SQL Server only. This value is the SQL server URL without a database attached. This value is used to connect to SQL Server for DBA operations.
Value: No value information is available.
Examples: The following are examples:
DataDirect SQL Server 2005 and 2008: jdbc:datadirect:sqlserver://:1433
Microsoft SQL Server 2005 and 2008: jdbc:sqlserver://:1433

Default: ReplaceWithYourAdminUrl

release.DbConfigRoleName
Description: Required for Oracle only. Name of the role that will be created and assigned to the config database user (release.DbUser).
Value: No values are available
Examples: No examples are available
Default: WP_BASE_CONFIG_USERS

release.DbRuntimeRoleName
Description: Required for Oracle only Name of the role that will be created and assigned to the runtime database user (release.DbRuntimeUser).
Value: No values are available.
Examples: No examples are available.
Default: WP_BASE_RUNTIME_USERS

release.XDbName
Description: Required for Non-Windows platforms when using DB2. Required only for local DB2 database using Type 2 JDBC driver. Release database alias that needs to be set if you want to call create-database task.
Value: No values are available
Examples: No values are available
Default: wps6TCP

release.DbNode
Description: Required for Non-Windows platforms when using DB2. Node for the WebSphere Portal release domain database and needs to be set if you want to call the create-database task.
Value: No values are available.
Examples: No examples are available.
Default: wpsNode

release.DbStorageGroup
Description: Required for DB2 for z/OS only. Storage group for the WebSphere Portal release database.
Value: No values are available
Examples: No examples are available.
Default: WPSSG

release.DbVolumes
Description: Required for DB2 for z/OS only. Volumes for the WebSphere Portal release database.
Value: No values are available.
Examples: No examples are available.
Default: *

release.DbVcat
Description: Required for DB2 for z/OS only. This value is the VCAT for the WebSphere Portal release database.
Value: No values are available.
Examples: No examples are available.
Default: DSN810

release.DbIndex4KBufferPoolName
Description: Required for DB2 for z/OS only. This value is the 4K bufferpool name for the WebSphere Portal release database. This bufferpool is dedicated for the indices.
Value: No values are available.
Examples: No examples are available.
Default: BP3

release.Db4KBufferPoolName
Description: Required for DB2 for z/OS only. This value is the 4K bufferpool name for the WebSphere Portal release database.
Value: No values are available.
Examples: No examples are available.
Default: BP2

release.Db32KBufferPoolName
Description: Required for DB2 for z/OS only. This value is the 32K bufferpool name for the WebSphere Portal release database.
Value: No values are available.
Examples: No examples are available.
Default: BP32K1

release.TablespaceTrackMod
Description: Required for DB2 for z/OS only. Sets the TRACKMOD attribute of all tablespaces to the specified value. See the DB2 for z/OS documentation about attribute TRACKMOD before changing this value.
Value: YES NO
Examples: No examples are available.
Default: YES

release.TablespaceDefine
Description: Required for DB2 for z/OS only. Sets the DEFINE attribute of all tablespaces to the specified value. See the DB2 for z/OS documentation about attribute DEFINE before changing this value.
Value: YES NO
Examples: No examples are available
Default: NO

Community Database Properties

community.DbType
Description: Type of database to be used for the WebSphere Portal Community domain.
Value: The following are valid database types:
IBM DB2: db2
IBM DB2 for i: db2_iseries
IBM DB2 for z/OS: db2_zos
Derby: derby
Microsoft SQL Server 2005: sqlserver2005
Microsoft SQL Server 2008: sqlserver2005
Oracle Database: oracle

Examples: db2
Default: derby

community.DbName
Description: Name of the WebSphere Portal Community domain database. Should also appear as the database element in DbUrl. Non-Windows platforms when using DB2 only, this value is the TCPIP Alias for the database.
Value: No values are available
Examples: For remote IBM DB2 for i the value should include the host name, such as: hostName/wpscomdb
Default: wpsdb

community.DbSchema
Description: Community domain database schema name. Follow the documentation of the database management system that you are using in order to determine a valid schema name. Restrictions apply for some database management systems.
Value: A valid schema name. For IBM DB2 for i, this value must be less than 10 characters.
Examples: No examples are available.
Default: community

community.DbNameOnZos
Description: Required for DB2 for z/OS only.
Value: The following conditions effect the value for this property:
If WebSphere Portal is configured to use a remote DB2 for z/OS database, the value should be the name of the remote Community domain database.
If WebSphere Portal is installed on z/OS and is configured to use DB2 for z/OS, the value must be set equal to the value in the community.DbName parameter.

Examples: No examples are available.
Default: WPSTST02

community.DataSourceName
Description: Name of the datasource to use for the WebSphere Portal Community domain.
Value: The following reserved names must not be specified: releaseDS, communityDS, customizationDS, jcrDS, lmdbDS, feedback
Examples: No examples are available.
Default: wpdbDS

community.DbUrl
Description: This value is the wps community domain database URL.
Value: The database element of this value should match the value of DbName property.
For IBM DB2 for i when WebSphere Portal is installed on a UNIX platform, add ;prompt=false to the URL unless X11 DISPLAY is set and active.
For IBM DB2 for z/OS, the database element of this value should match the location name of the database to be used when establishing connections with the IBM DB2 datasource used by the portal.

Examples: IBM DB2 using type 2 JDBC drivers: jdbc:db2:wpsdb
Derby database: jdbc:derby:wpsdb;create=true
IBM DB2 with type 2 drivers: jdbc:db2:wpsdb
IBM DB2 with type 4 drivers: jdbc:db2:// <YourDatabaseServer> :50000/wpsdb:returnAlias=0; Where the port is usually 50000 (Windows) or 50001 (Linux)
IBM DB2 for i with type 2 drivers: jdbc:db2:*LOCAL/wpsdb;metadata source=1
IBM DB2 for i with type 4 drivers: jdbc:as400: <hostname> /wpsdb;metadata source=1
Remote IBM DB2 for i with type 4 drivers: jdbc:as400: <hostName> /wpsdb;metadata source=1;prompt=false
DB2 for z/OS: jdbc:db2: <location>
Remote DB2 for z/OS with type 2 drivers: jdbc:db2:wpsdb
Remote DB2 for z/OS with type 4 drivers: jdbc:db2:// <YourDatabaseServer> :port/location
Thin Oracle Database with type 4 drivers and thin client: jdbc:oracle:thin:@ <YourDatabaseServer> :1521:wpsdb
Microsoft SQL Server 2005 and 2008: jdbc:sqlserver:// <YourDatabaseServer> :1433;SelectMethod=cursor;DatabaseName=wpsdb
DataDirect SQL Server 2005 and 2208: jdbc:datadirect:sqlserver:// <YourDatabaseServer> :1433;DatabaseName=wpsdb

Default: jdbc:derby:wpsdb;create=true

community.DbUser
Description: Database user ID.
Value: Alphanumeric text string
Examples: No examples are available.
Default: db2admin

community.DbPassword
Description: Database administrator password.
Value: Alphanumeric text string
Examples: No examples are available.
Default: ReplaceWithYourDbAdminPwd

community.DbRuntimeUser
Description: Optional parameter. WebSphere Portal will use this ID to connect to the community database during day-to-day operations. If WebSphere Portal can connect using the same ID used during configuration, the community.DbUser value, then leave this value blank.
Value: Alphanumeric text string.
Examples: No examples are available.
Default: no default is available

community.DbRuntimePassword
Description: Database runtime user password.
Value: Alphanumeric text string
Examples: No examples are available.
Default: ReplaceWithYourDbRuntimePwd

community.DBA.DbUser
Description: Database administrator user for privileged access operations during creation of this database type.
Value: No values are available.
Examples: No examples are available.
Default: db2admin

community.DBA.DbPassword
Description: Database administrator user password for privileged access operations during creation of this database type.
Value: Alphanumeric text string
Examples: No examples are available.
Default: ReplaceWithYourDBAPwd

community.DbHome
Description: Root location for the database. For Oracle this is the location on the remote or local machine for create the tablespaces. For SQLServer this is the location locally to store the database files. For SQLServer Windows Only: This path must use // instead of /. For SQLServer Only: <instance> in the path below may or may not be there in installation.
Value: Use the following value that is appropriate for database:
Oracle: { <oracle> /product/10.1.0/db_1 }
SQLServer: { C://Microsoft SQL Server// <instance> //MSSQL }

Examples: No examples are available.
Default: ReplaceWithYourDbHomeDir

community.AdminUrl
Description: Required for SQL Server only. Sqlserver URL without a database attached. This value is used to connect to SQL Server for DBA operations.
Value: No values are available.
Examples: The following are examples:
DataDirect SQL Server 2005 and 2008: jdbc:datadirect:sqlserver://:1433
Microsoft SQL Server 2005 and 2008: jdbc:sqlserver://:1433

Default: ReplaceWithYourAdminUrl

community.DbConfigRoleName
Description: Required for Oracle only Name of the role that will be created and assigned to the config database user (community.DbUser)
Value: No values are available
Examples: No examples are available
Default: WP_BASE_CONFIG_USERS

community.DbRuntimeRoleName
Description: Required for Oracle only Name of the role that will be created and assigned to the runtime database user (community.DbRuntimeUser)
Value: No values are available
Examples: No examples are available
Default: WP_BASE_RUNTIME_USERS

community.XDbName
Description: Required for Non-Windows platforms when using DB2. Required only for local DB2 database using Type 2 JDBC driver Community database alias that needs to be set if you want to call create-database
Value: No values are available
Examples: No examples are available
Default: wps6TCP

community.DbNode
Description: Required for Non-Windows platforms when using DB2. Node for the WebSphere Portal Community domain database and needs to be set if you want to call the create-database task.
Value: No values are available.
Examples: No examples are available.
Default: wpsNode

community.DbStorageGroup
Description: Required for DB2 for z/OS only. Storage group for the WebSphere Portal community database.
Value: No values are available.
Examples: No examples are available.
Default: WPSSG

community.DbVolumes
Description: Required for DB2 for z/OS only. Volumes for the WebSphere Portal community database.
Value: No values are available.
Examples: No examples are available.
Default: *

community.DbVcat
Description: Required for DB2 for z/OS only. This value is the VCAT for the WebSphere Portal community database.
Value: No values are available.
Examples: No examples are available.
Default: DSN810

community.DbIndex4KBufferPoolName
Description: Required for DB2 for z/OS only. This value is the 4K bufferpool name for the WebSphere Portal community database. This bufferpool is dedicated for the indices.
Value: No values are available.
Examples: No examples are available.
Default: BP3

community.Db4KBufferPoolName
Description: Required for DB2 for z/OS only. This value is the 4K bufferpool name for the WebSphere Portal community database.
Value: No values are available.
Examples: No examples are available.
Default: BP2

community.Db32KBufferPoolName
Description: Required for DB2 for z/OS only. This value is the 32K bufferpool name for the WebSphere Portal community database.
Value: No values are available.
Examples: No examples are available.
Default: BP32K1

community.TablespaceTrackMod
Description: Required for DB2 for z/OS only. Sets the TRACKMOD attribute of all tablespaces to the specified value. Refer to the DB2 for z/OS documentation about attribute TRACKMOD before changing this value.
Value: YES NO
Examples: No examples are available.
Default: YES

community.TablespaceDefine
Description: Required for DB2 for z/OS only. Sets the DEFINE attribute of all tablespaces to the specified value. Refer to the DB2 for z/OS documentation about attribute DEFINE before changing this value.
Value: YES NO
Examples: No examples are available.
Default: NO

Customization Database Properties

customization.DbType
Description: Type of database to be used for the WebSphere Portal Customization domain.
Value: The following are valid database types:
IBM DB2: db2
IBM DB2 for i: db2_iseries
IBM DB2 for z/OS: db2_zos
Derby: derby
Microsoft SQL Server 2005: sqlserver2005
Microsoft SQL Server 2008: sqlserver2005
Oracle Database: oracle

Examples: derby
Default: derby

customization.DbName
Description: Name of the WebSphere Portal Customization database. Should also appear as the database element in customization.DbUrl
Value: The following conditions effect the value for this property:
Non-Windows platforms when using DB2 only. TCPIP Alias for the database.
For IBM DB2 for i, this value must be unique for this domain.
For remote DB2 database for IBM i the value must include the host name, such as: hostname/wpscstdb

Examples: No examples are available.
Default: wpsdb

customization.DbSchema
Description: WebSphere Portal Customization domain database schema name. Follow the documentation of the database management system that you are using in order to determine a valid schema name. Restrictions apply for some database management systems.
Value: A valid schema name. For IBM DB2 for i, this value must be less than 10 characters.
Examples: No examples are available.
Default: customization

customization.DbNameOnZos
Description: Required for DB2 for z/OS only.
Value: If running db2_zos as remote database, this value is the name of the remote WebSphere Portal Customization domain database.
If portal is running on z/OS with db2_zos, this value must be set equal to DbName.

Examples: No examples are available.
Default: WPSTST02

customization.DataSourceName
Description: The name of datasource to be used for WebSphere Portal Customization domain
Value: The following reserved names must not be specified: releaseDS, communityDS, customizationDS, jcrDS, lmdbDS, feedback
Examples: No examples are available.
Default: wpdbDS

customization.DbUrl
Description: This value is the wps customization domain database URL.
Value: The database element of this value should match the value of DbName property.
For IBM DB2 for i when WebSphere Portal is installed on a UNIX platform, add ;prompt=false to the URL unless X11 DISPLAY is set and active.
For IBM DB2 for z/OS, the database element of this value should match the location name of the database to be used when establishing connections with the IBM DB2 datasource used by the portal.

Examples: Use one of the following examples with values specific to database.
Derby database: jdbc:derby:wpsdb;create=true
IBM DB2 with type 2 drivers: jdbc:db2:wpsdb
IBM DB2 with type 4 drivers: jdbc:db2:// <YourDatabaseServer> :50000/wpsdb:returnAlias=0; Where the port is usually 50000 (Windows) or 50001 (Linux)
IBM DB2 for i with type 2 drivers: jdbc:db2:*LOCAL/wpsdb;metadata source=1
IBM DB2 for i with type 4 drivers: jdbc:as400: <hostname> /wpsdb;metadata source=1
Remote IBM DB2 for i with type 4 drivers: jdbc:as400: <hostname> /wpsdb;metadata source=1;prompt=false
DB2 for z/OS: jdbc:db2: <location>
Remote DB2 for z/OS with type 2 drivers: jdbc:db2:wpsdb
Remote DB2 for z/OS with type 4 drivers: jdbc:db2:// <YourDatabaseServer> : <port> / <location>
Thin Oracle Database with type 4 drivers and thin client: jdbc:oracle:thin:@ <YourDatabaseServer> :1521:wpsdb
Microsoft SQL Server 2005 and 2008: jdbc:sqlserver:// <YourDatabaseServer> :1433;SelectMethod=cursor;DatabaseName=wpsdb
DataDirect SQL Server 2005 and 2208: jdbc:datadirect:sqlserver:// <YourDatabaseServer> :1433;DatabaseName=wpsdb

Default: jdbc:derby:wpsdb;create=true

customization.DbUser
Description: Database administrator user ID.
Value: Alphanumeric text string
Examples: No examples are available
Default: db2admin

customization.DbPassword
Description: Database administrator password.
Value: Alphanumeric text string
Examples: No examples are available.
Default: ReplaceWithYourDbAdminPwd

customization.DbRuntimeUser
Description: Optional parameter. WebSphere Portal will use this ID to connect to the customization database during day-to-day operations. If WebSphere Portal can connect using the same ID used during configuration, the customization.DbUser value, then leave this value blank.
Value: Alphanumeric text string
Examples: No examples available.
Default: no default is available

customization.DbRuntimePassword
Description: Database runtime user password.
Value: Alphanumeric text string
Examples: No examples are available.
Default: ReplaceWithYourDbRuntimePwd

customization.DBA.DbUser
Description: The value is the DBA user for privledged access operations during creation of this database type.
Value: Alphanumeric text string
Examples: No examples are available.
Default: db2admin

customization.DBA.DbPassword
Description: Password for privledged access operations during creation of this database type.
Value: Alphanumeric text string
Examples: No examples are available.
Default: ReplaceWithYourDBAPwd

customization.DbHome
Description: Root location for the database. For Oracle this is the location on the remote or local machine for create the tablespaces. For SQLServer this is the location locally to store the database files. SQLServer Windows Only: This path must use // instead of /. SQLServer Only: <instance> in the path below may or may not be there in installation.
Value: Oracle: { <oracle> /product/10.1.0/db_1 }
SQLServer: { C://Microsoft SQL Server// <instance> //MSSQL }

Examples: No examples are available.
Default: ReplaceWithYourDbHomeDir

customization.AdminUrl
Description: Required for SQL Server only. Sqlserver URL without a database attached. This value is used to connect to SQL Server for DBA operations.
Value: No values are available.
Examples: The following are examples:
DataDirect SQL Server 2005 and 2008: jdbc:datadirect:sqlserver://:1433
Microsoft SQL Server 2005 and 2008: jdbc:sqlserver://:1433

Default: ReplaceWithYourAdminUrl

customization.DbConfigRoleName
Description: Required for Oracle only Name of the role that will be created and assigned to the config database user (customization.DbUser).
Value: No values are available.
Examples: No examples are available.
Default: WP_BASE_CONFIG_USERS

customization.DbRuntimeRoleName
Description: Required for Oracle only Name of the role that will be created and assigned to the runtime database user (customization.DbRuntimeUser).
Value: No values are available,
Examples: No examples are available,
Default: WP_BASE_RUNTIME_USERS

customization.XDbName
Description: Required for Non-Windows platforms when using DB2. Required only for local DB2 database using Type 2 JDBC driver. Customization database alias that needs to be set if you want to call create-database
Value: No values are available,
Examples: No examples are available,
Default: wps6TCP

customization.DbNode
Description: Required for Non-Windows platforms when using DB2. Node for the WebSphere Portal Customization domain database and needs to be set if you want to call create-database.
Value: No values are available
Examples: No examples are available
Default: wpsNode

customization.DbStorageGroup
Description: Required for DB2 for z/OS only. Storage group for the WebSphere Portal customization database.
Value: No values are available.
Examples: No examples are available.
Default: WPSSG

customization.DbVolumes
Description: Required for DB2 for z/OS only. Volumes for the WebSphere Portal customization database.
Value: No values are available.
Examples: No examples are available.
Default: *

customization.DbVcat
Description: Required for DB2 for z/OS only. This value is the VCAT for the WebSphere Portal customization database.
Value: No values are available.
Examples: No examples are available.
Default: DSN810

customization.DbIndex4KBufferPoolName
Description: Required for DB2 for z/OS only. This value is the 4K bufferpool name for the WebSphere Portal customization database. This bufferpool is dedicated for the indices.
Value: No values are available.
Examples: No examples are available.
Default: BP3

customization.Db4KBufferPoolName
Description: Required for DB2 for z/OS only. This value is the 4K bufferpool name for the WebSphere Portal customization database.
Value: No values are available.
Examples: No examples are available.
Default: BP2

customization.Db32KBufferPoolName
Description: Required for DB2 for z/OS only. This value is the 32K bufferpool name for the WebSphere Portal customization database.
Value: No values are available.
Examples: No examples are available.
Default: BP32K1

customization.TablespaceTrackMod
Description: Required for DB2 for z/OS only. Sets the TRACKMOD attribute of all tablespaces to the specified value. Refer to the DB2 for z/OS documentation about attribute TRACKMOD before changing this value.
Value: YES NO
Examples: No examples are available.
Default: YES

customization.TablespaceDefine
Description: Required for DB2 for z/OS only. Sets the DEFINE attribute of all tablespaces to the specified value. Refer to the DB2 for z/OS documentation about attribute DEFINE before changing this value.
Value: YES NO
Examples: No examples are available
Default: NO

JCR Database Properties

jcr.DbType
Description: Type of database to be used for the WebSphere Portal JCR domain.
Value: The following are valid database types:
IBM DB2: db2
IBM DB2 for i: db2_iseries
IBM DB2 for z/OS: db2_zos
Derby: derby
Microsoft SQL Server 2005: sqlserver2005
Microsoft SQL Server 2008: sqlserver2005
Oracle Database: oracle

Examples: derby
Default: derby

jcr.DbName
Description: Name of the WebSphere Portal JCR database. Should also appear as the database element in jcr.DbUrl
Value: Non-Windows platforms when using DB2 only. TCPIP Alias for the database.
For IBM DB2 for i, this value must be unique for this domain
For remote IBM DB2 for i the value must include the host name, such as: hostname/wpscstdb

Examples: No examples are available.
Default: wpsdb

jcr.DbSchema
Description: WebSphere Portal JCR domain database schema name. Follow the documentation of the database management system that you are using in order to determine a valid schema name. Restrictions apply for some database management systems.
Value: A valid schema name. For IBM DB2 for i, this value must be less than 10 characters.
Examples: No examples are available.
Default: jcr

jcr.DbNameOnZos
Description: Required for DB2 for z/OS only.
Value: The following conditions effect the value for this property:
If running db2_zos as remote database, this value is the name of the remote WebSphere Portal JCR domain database.
If portal is running on z/OS with db2_zos, this value must be set equal to DbName.

Examples: No examples are available.
Default: WPSTST02

jcr.DataSourceName
Description: Name of datasource to be used for WebSphere Portal JCR domain.
Value: The following reserved names must not be specified: releaseDS, communityDS, customizationDS, jcrDS, lmdbDS, feedback
Examples: No examples are available.
Default: wpdbDS

jcr.DbUrl
Description: This value is the wps JCR domain database URL.
Value: The database element of this value should match the value of DbName property.
For IBM DB2 for i when WebSphere Portal is installed on a UNIX platform, add ;prompt=false to the URL unless X11 DISPLAY is set and active.
For IBM DB2 for z/OS, the database element of this value should match the location name of the database to be used when establishing connections with the IBM DB2 datasource used by the portal.

Examples: Use one of the following examples with values specific to database.
Derby database: jdbc:derby:wpsdb;create=true
IBM DB2 with type 2 drivers: jdbc:db2:wpsdb
IBM DB2 with type 4 drivers: jdbc:db2:// <YourDatabaseServer> :50000/wpsdb:returnAlias=0; Where the port is usually 50000 (Windows) or 50001 (Linux)
IBM DB2 for i with type 2 drivers: jdbc:db2:*LOCAL/wpsdb;metadata source=1
IBM DB2 for i with type 4 drivers: jdbc:as400: <hostName> /wpsdb;metadata source=1
Remote IBM DB2 for i with type 4 drivers: jdbc:as400: <hostName> /wpsdb;metadata source=1;prompt=false
DB2 for z/OS: jdbc:db2: <location>
Remote DB2 for z/OS with type 2 drivers: jdbc:db2:wpsdb
Remote DB2 for z/OS with type 4 drivers: jdbc:db2:// <YourDatabaseServer> : <port> / <location>
Thin Oracle Database with type 4 drivers and thin client: jdbc:oracle:thin:@ <YourDatabaseServer> :1521:wpsdb
Microsoft SQL Server 2005 and 2008: jdbc:sqlserver:// <YourDatabaseServer> :1433;SelectMethod=cursor;DatabaseName=wpsdb
DataDirect SQL Server 2005 and 2208: jdbc:datadirect:sqlserver:// <YourDatabaseServer> :1433;DatabaseName=wpsdb

Default: jdbc:derby:wpsdb;create=true

jcr.DbUser
Description: Database administrator user ID.
Value: Alphanumeric text string
Examples: No examples are available
Default: db2admin

jcr.DbPassword
Description: Database administrator password.
Value: Alphanumeric text string
Examples: No examples are available.
Default: ReplaceWithYourDbAdminPwd

jcr.DbRuntimeUser
Description: Optional parameter. WebSphere Portal will use this ID to connect to the JCR database during day-to-day operations. If WebSphere Portal can connect using the same ID used during configuration, the jcr.DbUser value, then leave this value blank.
Value: Alphanumeric text string
Examples: No examples available.
Default: no default is available

jcr.DbRuntimePassword
Description: Database runtime user password.
Value: Alphanumeric text string
Examples: No examples are available.
Default: ReplaceWithYourDbRuntimePwd

jcr.DBA.DbUser
Description: The value is the DBA user for privledged access operations during creation of this database type.
Value: Alphanumeric text string
Examples: No examples are available.
Default: db2admin

jcr.DBA.DbPassword
Description: Password for privledged access operations during creation of this database type.
Value: Alphanumeric text string
Examples: No examples are available.
Default: ReplaceWithYourDBAPwd

jcr.DbHome
Description: Root location for the database. For Oracle this is the location on the remote or local machine for create the tablespaces. For SQLServer this is the location locally to store the database files. SQLServer Windows Only: This path must use // instead of /. SQLServer Only: <instance> in the path below may or may not be there in installation.
Value: Oracle: { <oracle> /product/10.1.0/db_1 }
SQLServer: { C://Microsoft SQL Server// <instance> //MSSQL }

Examples: No examples are available.
Default: ReplaceWithYourDbHomeDir

jcr.AdminUrl
Description: Required for SQL Server only. Sqlserver URL without a database attached. This value is used to connect to SQL Server for DBA operations.
Value: No values are available.
Examples: The following are examples:
DataDirect SQL Server 2005 and 2008: jdbc:datadirect:sqlserver://:1433
Microsoft SQL Server 2005 and 2008: jdbc:sqlserver://:1433

Default: ReplaceWithYourAdminUrl

jcr.DbConfigRoleName
Description: Required for Oracle only Name of the role that will be created and assigned to the config database user (jcr.DbUser).
Value: No values are available.
Examples: No examples are available.
Default: WP_JCR_CONFIG_USERS

jcr.DbRuntimeRoleName
Description: Required for Oracle only Name of the role that will be created and assigned to the runtime database user (jcr.DbRuntimeUser).
Value: No values are available,
Examples: No examples are available,
Default: WP_JCR_RUNTIME_USERS

jcr.XDbName
Description: Required for Non-Windows platforms when using DB2. Required only for local DB2 database using Type 2 JDBC driver. This value is the JCR database alias that needs to be set if you want to call create-database
Value: No values are available,
Examples: No examples are available,
Default: wps6TCP

jcr.DbNode
Description: Required for Non-Windows platforms when using DB2. Node for the WebSphere Portal JCR domain database and needs to be set if you want to call the create-database task.
Value: No values are available.
Examples: No examples are available.
Default: wpsNode

jcr.DbSaPassword
Description: Optional for MS SQL Server 2005. This value is the SQL Server System Administrator password.
Value: Alphanumeric text string
Examples: No examples are available.
Default: ReplaceWithYourDbAdminPwd

jcr.DbHost
Description: Required for DB2 for z/OS. Host name (only) of remote system hosting the DB2 Content Manager Runtime Edition database.
Value: No values are available.
Examples: No examples are available.
Default: ReplaceWithYourDbHost

jcr.DbDomain
Description: Required for DB2 for z/OS. Domain (not including host name) of the remote system hosting the DB2 Content Manager Runtime Edition database.
Value: No values are available.
Examples: No examples are available.
Default: yourco.com

jcr.DbPort
Description: Required for DB2 for z/OS. This value is the port number of DB2 Content Manager Runtime Edition database on the remote system.
Value: numeric
Examples: No examples are available.
Default: 446

jcr.ZosDbPrefix
Description: Required for DB2 for z/OS. Common prefix of Node Type database names for DB2 Content Manager Runtime Edition.
Value: No values are available.
Examples: No examples are available.
Default: ICM

jcr.ZosDbMaxTables
Description: Required for DB2 for z/OS. Maximum number of User Defined Tables to be stored in a particular Node Type DB in the DB2 Content Manager Runtime Edition database.
Value: numeric
Examples: No examples are available.
Default: 400

jcr.DbStorageGroup
Description: Required for DB2 for z/OS only. Storage group for the WebSphere Portal JCR database.
Value: No values are available.
Examples: No examples are available.
Default: WPSSG

jcr.DbVolumes
Description: Required for DB2 for z/OS only. Volumes for the WebSphere Portal JCR database.
Value: No values are available.
Examples: No examples are available.
Default: *

jcr.DbVcat
Description: Required for DB2 for z/OS only. This value is the VCAT for the WebSphere Portal JCR database.
Value: No values are available.
Examples: No examples are available.
Default: DSN810

jcr.DbIndex4KBufferPoolName
Description: Required for DB2 for z/OS only. This value is the 4K bufferpool name for the WebSphere Portal JCR database. This bufferpool is dedicated for the indices.
Value: No values are available.
Examples: No examples are available.
Default: BP3

jcr.Db4KBufferPoolName
Description: Required for DB2 for z/OS only. This value is the 4K bufferpool name for the WebSphere Portal JCR database.
Value: No values are available.
Examples: No examples are available.
Default: BP2

jcr.Db32KBufferPoolName
Description: Required for DB2 for z/OS only. This value is the 32K bufferpool name for the WebSphere Portal JCR database.
Value: No values are available.
Examples: No examples are available.
Default: BP32K1

jcr.TablespaceTrackMod
Description: Required for DB2 for z/OS only. Sets the TRACKMOD attribute of all tablespaces to the specified value. Refer to the DB2 for z/OS documentation about attribute TRACKMOD before changing this value.
Value: YES NO
Examples: No examples are available.
Default: YES

jcr.TablespaceDefine
Description: Required for DB2 for z/OS only Sets the DEFINE attribute of all tablespaces to the specified value. See the DB2 for z/OS documentation about attribute DEFINE before changing this value.
Value: YES NO
Examples: No examples are available
Default: NO

Parent
Configuration properties reference
corrected buffer pool sizes minor chages/typos

+
Search Tips | Advanced Search