Properties file: wkplc_dbdomain.properties
Each database domain has unique properties. As a result, you can separate the database domains on different database servers if needed. If all the domains are on a single server, then many of the properties are the same, such as the database type (DbType).
Release database properties
- release.DbType
- release.DbName
- Description
- The name of the release database. This value should also appear as the database element in DbUrl.
- For remote IBM DB2 for i, the value must include the host name, such as: hostname/wpsreldb
- For Linux and UNIX-based platforms using IBM DB2, this value is the TCPIP alias.
- For IBM DB2 for i, the value must be unique for this domain.
- Default value
- wpsdb
- Examples
- None available
- release.DbSchema
- Description
- The Release domain database schema name. For IBM DB2 for i, the scheme name must be less than ten characters. Some database management systems have restrictions for schema names. To define a valid schema name, see the documentation of the target database management system for guidance.
- Default value
- release
- Examples
- None available
- release.DbNameOnZos
- release.DataSourceName
- release.DbUrl
- release.DbUser
- release.DbPassword
- release.DbRuntimeUser
- Description
- Optional parameter. WebSphere Portal will use this ID to connect to the release database during day-to-day operations. This is also referred to as the runtime user. If you are not using two seperate IDs, one for configuration and one for runtime, leave this value blank.
- Default value
- No default value
- Examples
- None available
- release.DbRuntimePassword
- release.DBA.DbUser
- release.DBA.DbPassword
- release.DbHome
- Description
- The root location for the database.
- For Oracle Database, enter the location on the remote or local machine for create the tablespaces.
- For Microsoft SQL Server, enter the location locally to store the database files.
- Microsoft SQL Server on Windows Only: This path must use \\ instead of /.
- SQLServer Only:instance in the path below may or may not be there in your installation.
- Default value
- ReplaceWithYourDbHomeDir
- Examples
- Oracle Database: { oracle/product/10.1.0/db_1 }
- release.AdminUrl
- release.DbConfigRoleName
- release.DbRuntimeRoleName
- release.XDbName
- release.DbNode
- release.DbStorageGroup
- release.DbVolumes
- release.DbVcat
- release.DbIndex4KBufferPoolName
- release.Db4KBufferPoolName
- release.Db32KBufferPoolName
- release.TablespaceTrackMod
- release.TablespaceDefine
Community database properties
- community.DbType
- community.DbName
- Description
- The name of the Community domain database. This value should also appear as the database element in DbUrl.
- For Linux and UNIX platforms (non-Windows) using DB2, enter the TCPIP alias for the database.
- For remote IBM DB2 for i, the value should include the host name, such as: hostName/wpscomdb
- Default value
- wpsdb
- Examples
- None available
- community.DbSchema
- Description
- The Community domain database schema name. For IBM DB2 fori, the scheme name must be less than ten characters. Some database management systems have restrictions for schema names. To define a valid schema name, see the documentation of the target database management system for guidance.
- Default value
- community
- Examples
- None available
- community.DbNameOnZos
- community.DataSourceName
- community.DbUrl
- Description
- The wps Community domain database URL. 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.
- Default value
- jdbc:derby:wpsdb;create=true
- Examples
- IBM DB2 using type 2 JDBC drivers: jdbc:db2:wpsdb
- community.DbUser
- community.DbPassword
- 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.
- Default value
- No default value
- Examples
- None available
- community.DbRuntimePassword
- community.DBA.DbUser
- community.DBA.DbPassword
- community.DbHome
- Description
- The root location for the database.
- For Oracle Database, enter the location on the remote or local machine for create the tablespaces.
- For SQL Server, enter the location locally to store the database files.
- For SQL Server Windows Only: This path must use \\ instead of /.
- For SQL Server Only: instance in the path below may or may not be there in your installation.
- Default value
- ReplaceWithYourDbHomeDir
- Examples
- Oracle Database: {oracle /product/10.1.0/db_1 }
- community.AdminUrl
- community.DbConfigRoleName
- community.DbRuntimeRoleName
- community.XDbName
- community.DbNode
- community.DbStorageGroup
- community.DbVolumes
- community.DbVcat
- community.DbIndex4KBufferPoolName
- community.Db4KBufferPoolName
- community.Db32KBufferPoolName
- community.TablespaceTrackMod
- community.TablespaceDefine
Customization database properties
- customization.DbType
- customization.DbName
- Description
- The name of the Customization database. This value should also appear as the database element in customization.DbUrl
The following conditions effect the value for this property:
- Linux and UNIX platforms (non-Windows) when using DB2 only enter the 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
- Default value
- wpsdb
- Examples
- None available
- customization.DbSchema
- Description
- The Customization domain database schema name. For IBM DB2 for i, the scheme name must be less than ten characters. Some database management systems have restrictions for schema names. To define a valid schema name, see the documentation of the target database management system for guidance.
- Default value
- customization
- Examples
- None available
- customization.DbNameOnZos
- customization.DataSourceName
- customization.DbUrl
- Description
- The wps Customization domain database URL. 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 used when establishing connections with the IBM DB2 datasource used by the portal.
- Default value
- jdbc:derby:wpsdb;create=true
- Examples
- Apache Derby database: jdbc:derby:wpsdb;create=true
- customization.DbUser
- customization.DbPassword
- 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.
- Default value
- No default value
- Examples
- None available
- customization.DbRuntimePassword
- customization.DBA.DbUser
- customization.DBA.DbPassword
- customization.DbHome
- Description
- The root location for the database. For Oracle Database, 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 your installation.
- Default value
- ReplaceWithYourDbHomeDir
- Examples
- Oracle Database: { oracle/product/10.1.0/db_1 }
- customization.AdminUrl
- customization.DbConfigRoleName
- customization.DbRuntimeRoleName
- customization.XDbName
- customization.DbNode
- customization.DbStorageGroup
- customization.DbVolumes
- customization.DbVcat
- customization.DbIndex4KBufferPoolName
- customization.Db4KBufferPoolName
- customization.Db32KBufferPoolName
- customization.TablespaceTrackMod
- customization.TablespaceDefine
JCR database properties
- jcr.DbType
- jcr.DbName
- Description
- The name of the JCR database. This value should also appear as the database element in jcr.DbUrl
- For non-Windows platforms when using DB2 only, enter the 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
- Default value
- wpsdb
- Examples
- None available
- jcr.DbSchema
- Description
- The JCR domain database schema name. For IBM DB2 for i, the scheme name must be less than ten characters. Some database management systems have restrictions for schema names. To define a valid schema name, see the documentation of the target database management system for guidance.
- Default value
- jcr
- Examples
- None available
- jcr.DbNameOnZos
- jcr.DataSourceName
- jcr.DbUrl
- Description
- The wps JCR domain database URL.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.
- Default value
- jdbc:derby:wpsdb;create=true
- Examples
- Apache Derby database: jdbc:derby:wpsdb;create=true
- jcr.DbUser
- jcr.DbPassword
- 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.
- Default value
- No default value
- Examples
- None available
- jcr.DbRuntimePassword
- jcr.DBA.DbUser
- jcr.DBA.DbPassword
- jcr.DbHome
- Description
- The root location for the database. For Oracle Database, enter the location on the remote or local machine for create the tablespaces. For SQLServer enter 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 your installation.
- Default value
- ReplaceWithYourDbHomeDir
- Examples
- None available
- jcr.AdminUrl
- jcr.DbConfigRoleName
- jcr.DbRuntimeRoleName
- jcr.XDbName
- jcr.DbNode
- jcr.DbSaPassword
- jcr.DbHost
- jcr.DbDomain
- jcr.DbPort
- jcr.ZosDbPrefix
- jcr.ZosDbMaxTables
- jcr.DbStorageGroup
- jcr.DbVolumes
- jcr.DbVcat
- jcr.DbIndex4KBufferPoolName
- jcr.Db4KBufferPoolName
- jcr.Db32KBufferPoolName
- jcr.TablespaceTrackMod
- jcr.TablespaceDefine
The following properties are required to configure the JCR.
Feedback database properties
- feedback.DbType
- InitializeFeedbackDB
- feedback.DbName
- feedback.DbSchema
- Description
- This value is the Feedback domain database schema name. For IBM DB2 for i, this value must be less than ten characters. Some database management systems have restrictions for schema names. To define a valid schema name, see the documentation of the target database management system for guidance.
- Default value
- FEEDBACK
- Examples
- None available
- feedback.DbNameOnZos
- feedback.DataSourceName
- feedback.DbUrl
- feedback.DbUser
- feedback.DbPassword
- 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.
- Default value
- No default value
- Examples
- None available
- feedback.DbRuntimePassword
- feedback.DBA.DbUser
- feedback.DBA.DbPassword
- feedback.DbHome
- Description
- The root location for the Feedback database.
- For Oracle Database, 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 theinstance in the example path below may or may not exist for your installation.
- Default value
- ReplaceWithYourDbHomeDir
- Examples
- Oracle: oracle/product/10.1.0/db_1
- feedback.AdminUrl
- Description
- This parameter is 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.
- Default value
- ReplaceWithYourAdminUrl
- Examples
- Microsoft SQL Server 2005: jdbc:sqlserver://YourDatabaseServer:1433
- feedback.DbConfigRoleName
- feedback.DbRuntimeRoleName
- feedback.XDbName
- feedback.DbNode
- feedback.DbHostName
- feedback.DbTablespace
- feedback.DbStorageGroup
- feedback.DbVolumes
- feedback.DbVcat
- feedback.Db4KBufferPoolName
- feedback.Db32KBufferPoolName
LikeMinds database properties
- likeminds.DbType
- likeminds.DbName
- likeminds.DbSchema
- Description
- The Likeminds domain database schema name. For IBM DB2 for i, this value must be less than ten characters. Some database management systems have restrictions for schema names. To define a valid schema name, see the documentation of the target database management system for guidance.
- Default value
- likeminds
- Examples
- likeminds
- likeminds.DbNameOnZos
- Description
- This parameter is required for IBM DB2 for z/OS only. 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).
- Default value
- WPSTST02
- Examples
- None available
- likeminds.DataSourceName
- likeminds.DbUrl
- likeminds.DbUser
- likeminds.DbPassword
- likeminds.DbRuntimeUser
- Description
- Optional parameter. WebSphere Portal will use this ID to connect to the Likeminds 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.
- Default value
- No default value
- Examples
- None available
- likeminds.DbRuntimePassword
- likeminds.DBA.DbUser
- likeminds.DBA.DbPassword
- 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.
- Default value
- ReplaceWithYourDbHomeDir
- Examples
- Oracle Database: oracle/product/10.1.0/db_1
- likeminds.AdminUrl
- likeminds.DbConfigRoleName
- likeminds.DbRuntimeRoleName
- likeminds.XDbName
- likeminds.DbNode
- likeminds.DbHostName
- likeminds.DbTablespace
- likeminds.DbStorageGroup
- likeminds.DbVolumes
- likeminds.DbVcat
- likeminds.Db4KBufferPoolName
- likeminds.Db32KBufferPoolName