WebSphere Portal 6.1.5 wkplc_comp.properties file reference

About the Workplace Component Configuration properties file

The following are general notes about the properties file:

• Do NOT enclose any value in quotes
  
• Windows paths must use /, instead of a \
  
• Windows long paths are okay
  
• Properties are immutable;after they are set they cannot be overridden
  
• Precedence is as follows in descending order
  
• Properties set on command line are read first -DMyNode=somenode
  
• Properties set in properties file are read next
  
• Properties set in buildfile file are read last.
  

=Personalization properties (prereq.pzn.properties)=
The personalization data is loaded from:
AIX: /usr/IBM/WebSphere/PortalServer/pzn/prereq.pzn/prereq.pzn.properties
i5/OS: /QIBM/UserData/WebSphere/PortalServer/pzn/prereq.pzn/prereq.pzn.properties
Linux, HP-UX, Solaris: /opt/IBM/WebSphere/PortalServer/pzn/prereq.pzn/prereq.pzn.properties
Windows: C:/IBM/wp615/WebSphere/PortalServer/pzn/prereq.pzn/prereq.pzn.properties

Examples for DbType and DbUrl

DbType
Description: The type of database to be used for WebSphere Portal
Values: The following values apply to all the Personalization properties:
DB2: { db2 }
Oracle: { oracle }
MS SQL Server 2005: { sqlserver2005 }
Derby: { derby }
DB2 for iSeries: { db2_iseries }
DB2 for z/OS: { db2_zos }

DbUrl
Description: The wps database URL. The database element of this value should match the value of DbName.
Values: Example values are provided for each database.
For 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 DB2 datasource used by WebSphere Portal
Derby: { jdbc:derby:wpsdb;create=true }
DB2 (type 2): { jdbc:db2:wpsdb }
DB2 (type 4): { jdbc:db2://:/wpsdb:returnAlias=0; }
where the port is usually 50000 (Windows) or 50001 (Linux).
DB2 for i5/OS (type 2): { jdbc:db2:*LOCAL/wpsdb }
DB2 for i5/OS (type 4): { jdbc:as400:/wpsadb }
DB2 for z/OS { jdbc:db2: }
DB2 for z/OS (remote, type 2): { jdbc:db2:wpsdb }
DB2 for z/OS (remote, type 4): { jdbc:db2://:/ }
Oracle (type 4, thin): { jdbc:oracle:thin:@:1521:wpsdb }
SQL Server 2005 (Microsoft): { jdbc:sqlserver://:1433;SelectMethod=cursor;DatabaseName=wpsdb }
SQL Server 2005 (DataDirect): { jdbc:datadirect:sqlserver://:1433;DatabaseName=wpsdb }

AdminUrl
Description: The database URL for SQL Server administation
SQL Server 2005 (Microsoft): { jdbc:sqlserver://:1433}
SQL Server 2005 (DataDirect): { jdbc:datadirect:sqlserver://:1433}

Personalization feedback database properties

feedback.DbType
Description: The type of database to be used for the Feedback database.
Value: The database server you are using.
Examples: Valid example values are provided above in the "Examples for DbType and DbUrl" section.
Default: derby


InitializeFeedbackDB
Description: Determines how to handle the Personalization feedback database during database transfer from Derby to another DB type. Set this value to true to transfer data from Derby or set this value to false to redirect the feedback DataSource to a preexisting database.
Value: true false
Example: none available
Default: true

feedback.DbName
Description: The name of the feedback database. This value should also appear as the database element in feedback.DbUrl
Value:
When WebSphere Portal is configured to use DB2 for i5/OS, this value must be unique for this domain.
When WebSphere Portal is installed on Linux and UNIX-based platforms and configured to use a DB2 database, this value is the TCPIP Alias for the database.
When WebSphere Portal is configured to use a remote DB2 database for iSeries, the value must be: /wpsfdbdb
Example: none available
Default: wpsdb

feedback.DbSchema
Description: The Feedback 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:
For DB2 database for i5/OS, this value must be less than 10 characters.
Example: none available
Default: FEEDBACK

feedback.DbNameOnZos
Description: This parameter is required for DB2 for z/OS only. If WebSphere Portal is configured to use a remote DB2 for z/OS database, the value should be the name of the remote Feedback 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 feedback.DbName parameter.
Value: none available
Example: none available
Default: WPSTST02

feedback.DataSourceName
Description: The name of datasource to use for the Feedback database.
Value: none available
Example: none available
Default: wpdbDS

feedback.DbUrl
Description: The Feedback database URL.
Value: URL
Example: Valid example values are provided above in the "Examples for DbType and DbUrl" section.
Default: jdbc:derby:wpsdb;create=true

feedback.DbUser
Description: The database user ID.
Value: none available
Example: none available
Default: db2admin

feedback.DbPassword
Description: The database password.
Value: none available
Example: none available
Default: ReplaceWithYourDbAdminPwd

feedback.DBA.DBUser
Description: The database administrator user for privileged access operations during creation of this database type.
Value: none available
Example: none available
Default: db2admin

feedback.DBA.DbPassword
Description: The database administrator user password for privileged access operations during creation of this database type.
Value: none available
Example: none available
Default: ReplaceWithYourDbAPwd

feedback.DbHome
Description: This is the root location for the database. This value is used to specify the location (remote or locally) to create the tablespaces for Oracle.
Value: Use the following value that is appropriate for your 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: in the path below may or may not be there in your installation.
Oracle: { /product/10.1.0/db_1 }
SQLServer: { C:\\Microsoft SQL Server\\\\MSSQL }
Example: none available
Default: ReplaceWithYourDbHomeDir

feedback.AdminUrl
Description: This parameter is required for SQL Server only. This is used to connect to SQL Server for DBA operations.
Value: The value is the SQL Server URL without a database attached.
Example: Valid example values are provided above in the "AdminUrl" section.
Default: ReplaceWithYourAdminUrl

feedback.XDbName
Description: The name of the Feedback database. This parameter is required for Non-Windows platforms when using DB2. This parameter is also required for local DB2 database using a Type 2 JDBC driver.
Value: none available
Example: none available
Default: fdbk6TCP

feedback.DbNode
Description: This parameter is required for Non-Windows platforms when using DB2. This value is the node for the Feedback database and needs to be set if you want to call the create-database task.
Value: none available
Example: none available
Default: pznNode

feedback.DbHostName
Description: This parameter is required for MS SQL Server 2005 only. This value is the host name of the Feedback database.
Value: none available
Example: none available
Default: myserver

feedback.DbTablespace
Description: This parameter is required for DB2 for z/OS only. This value is the name of the feedback database table space.
Value: none available
Example: none available
Default: fdbkdbts

feedback.DbStorageGroup
Description: This parameter is required for DB2 for z/OS only. This value is the storage group for the WebSphere Portal feedback database.
Value: none available
Example: none available
Default: WPSSG

feedback.DbVolumes
Description: This parameter is required for DB2 for z/OS only. This value is the volumes for the WebSphere Portal feedback database.
Value: none available
Example: none available
Default: *

feedback.DbVcat
Description: This parameter is required for DB2 for z/OS only. This value is the VCAT for the WebSphere Portal feedback database.
Value: none available
Example: none available
Default: DSN810

feedback.Db4KBufferPoolName
Description: This parameter is required for DB2 for z/OS only. This value is the 4K buffer pool name for the WebSphere Portal feedback database.
Value: none available
Example: none available
Default: BP2

feedback.Db32KBufferPoolName
Description: This parameter is required for DB2 for z/OS only. This value is the 32K bufferpool name for the WebSphere Portal feedback database.
Value: none available
Example: none available
Default: BP32K

source.feedback.DbType
Description: The type of database to use for the Feedback database.
Value: See the examples for DbType and DbUrl above.
Example: none available
Default: derby

source.feedback.DbName
Description: The name of the Feedback database.
Value:
This value should also appear as the database element in feedback.DbUrl
Non-Windows platforms when using DB2 only: This value is the TCPIP Alias for the database.
For DB2 database for i5/OS: this value must be unique for this domain
For remote DB2 database for i5/OS: /wpsfdbdb
Example: none available
Default: wpsdb

source.feedback.DbSchema
Description: The Feedback 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: none available
Example: none available
Default: FEEDBACK

source.feedback.DbNameOnZos
Description: This parameter is required for DB2 for z/OS only
Value:
If running db2_zos as remote database, this value is the name of the remote Feedback database.
If portal is running on z/OS with db2_zos, this value must be set equal to the value in the DbName parameter.
Example: none available
Default: WPSTST02

source.feedback.DataSourceName
Description: The name of the datasource to use for the Feedback database.
Value: none available
Example: none available
Default: wpdbDS

source.feedback.DbUrl
Description: The Feedback database URL.
Value: Database URL
Example: Valid example values are provided above at the beginning of this section.
Default: jdbc:derby:wpsdb;create=true

source.feedback.DbUser
Description: The database administrator user ID.
Value: none available
Example: none available
Default: db2admin

source.feedback.DbPassword
Description: The database administrator password.
Value: none available
Example: none available
Default: ReplaceWithYourDbAdminPwd

source.feedback.XDbName
Description: This parameter is required for Non-Windows platforms when using DB2 only and only for local DB2 database using Type 2 JDBC driver. This value is the name of the Feedback database.
Value: none available
Example: none available
Default: fdbk6TCP

source.feedback.DbNode
Description: This parameter is required for Non-Windows platforms when using DB2 only. This value is the node for the Feedback database and needs to be set if you want to call the create-database task.
Value: none available
Example: none available
Default: pznNode

source.feedback.DbHostName
Description: This parameter is required for MS SQL Server 2005 only. This value is the host name of the Feedback database.
Value: none available
Example: none available
Default: myserver

source.feedback.DbTablespace
Description: This parameter is required for DB2 for z/OS only. This value is the name of the feedback database tablespace.
Value: none available
Example: none available
Default: fdbkdbts

source.feedback.DbStorageGroup
Description: This parameter is required for DB2 for z/OS only. This value is the storage group for the WebSphere Portal feedback database.
Value: none available
Example: none available
Default: WPSSG

source.feedback.DbVolumes
Description: This parameter is required for DB2 for z/OS only. This value is the volumes for the WebSphere Portal feedback database
Value: none available
Example: none available
Default: *

source.feedback.DbVcat
Description: This parameter is required for DB2 for z/OS only. This value is the VCAT for the WebSphere Portal feedback database
Value: none available
Example: none available
Default: DSN810

source.feedback.Db4KBufferPoolName
Description: This parameter is required for DB2 for z/OS only. This value is the 4K bufferpool name for the WebSphere Portal feedback database
Value: none available
Example: none available
Default: BP2

source.feedback.Db32KBufferPoolName
Description: This parameter is required for DB2 for z/OS only. This value is the 32K bufferpool name for the WebSphere Portal feedback database
Value: none available
Example: none available
Default: BP32K

1. 
   

END: Personalization Feedback Database Properties

1. 
   

LikeMinds Database Properties

Examples for DbType and DbUrl

DbType: The type of database to be used for WebSphere Portal
DB2: { db2 }
Oracle: { oracle }
MS SQL Server 2005: { sqlserver2005 }
derby: { derby }
DB2 for iSeries: { db2_iseries }
DB2 for z/OS: { db2_zos }

DbUrl: The wps database URL
Note: The database element of this value should match the value of DbName
Note: For DB2 Type 4 driver use jdbc:db2://:/wpsdb:returnAlias=0;
The port is usually 50000 (Windows) or 50001 (Linux).
Note: On z/OS, the database element of this value should match the location name of the database to be used when establishing connections with the DB2 datasource used by WebSphere Portal
derby: { jdbc:derby:wpsdb;create=true }
db2 (type 2): { jdbc:db2:wpsdb }
db2 (type 4): { jdbc:db2://:50000/wpsdb:returnAlias=0; }
db2_iseries (type 2): { jdbc:db2:*LOCAL/wpsdb }
db2_iseries (type 4): { jdbc:as400:/wpsdb }
db2_zos: { jdbc:db2: }
db2_zos (remote, type 2): { jdbc:db2:wpsdb }
db2_zos (remote, type 4): { jdbc:db2://:/ }
oracle: { jdbc:oracle:thin:@:1521:wpsdb }
sqlserver: { jdbc:microsoft:sqlserver://:1433;DatabaseName=wpsdb }
sqlserver2005: { jdbc:datadirect:sqlserver://:1433;DatabaseName=wpsdb }

Properties

likeminds.DbType
Description: The type of database used for the LikeMinds database.
Value: The database server you are using.
Example: Valid example values are provided above in the "Examples for DbType and DbUrl" section.
Default: derby

likeminds.DbName
Description: The name of the LikeMinds database
Value:
This value should also appear as the database element in the likeminds.DbUrl parameter.
Non-Windows platforms when using DB2 only: This value is the TCPIP Alias for the database.
For DB2 database for iSeries, this value must be unique for this domain
For remote DB2 database for iSeries: /wpslkmdb
Example: none available
Default: wpsdb

likeminds.DbSchema
Description: The LikeMinds 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: For DB2 database for iSeries, this value must be less than 10 characters.
Example: none available
Default: likeminds

likeminds.DbNameOnZos
Description: This parameter is required for DB2 for z/OS only.
Value:
If running db2_zos as remote database, the name of the remote LikeMinds database.
If portal is running on z/OS with db2_zos, this value must be set equal to the DbName parameter.
Example: none available
Default: WPSTST02

likeminds.DataSourceName
Description: The name of datasource to use for the LikeMinds database.
Value: none available
Example: none available
Default: wpdbDS

likeminds.DbUrl
Description: The Likeminds database URL.
Value: URL
Example: Valid example values are provided above in the "Examples for DbType and DbUrl" section.
Default: jdbc:derby:wpsdb;create=true

likeminds.DbUser
Description: The database administrator user ID.
Value: none available
Example: none available
Default: db2admin

likeminds.DbPassword
Description: The database administrator password.
Value: none available
Example: none available
Default: ReplaceWithYourDbAdminPwd

likeminds.DBA.DbUser
Description: DBA user for privileged access operations during creation of this database type.
Value: none available
Example: none available
Default: db2admin

likeminds.DBA.DbPassword
Description: DBA password for privileged access operations during creation of this database type
Value: none available
Example: none available
Default: ReplaceWithYourDBAPwd

likeminds.DbHome
Description: This is the root location for the database.
Value:
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: in the path below may or may not be there in your installation.
Oracle: { /product/10.1.0/db_1 }
SQLServer: { C:\\Microsoft SQL Server\\\\MSSQL }
Used to specify the location (remote or locally) to create the tablespaces for Oracle
Example: none available
Default: ReplaceWithYourDbHomeDir

likeminds.AdminUrl
Description: This parameter is required for SQL Server only. This is used to connect to SQL Server for DBA operations
Value: The value is the SQL Server URL without a database attached.
Example: Valid example values are provided above in the "AdminUrl" section.
Default: ReplaceWithYourAdminUrl

likeminds.XDbName
Description: This parameter is required for Non-Windows platforms when using DB2 and is also required only for local DB2 database using Type 2 JDBC driver. This value is the name of the LikeMinds database.
Value: none available
Example: none available
Default: lmdb6TCP

likeminds.DbNode
Description: This parameter is required for Non-Windows platforms when using DB2. This value is the node for the LikeMinds database and needs to be set if you want to call the create-database task.
Value: none available
Example: none available
Default: pznNode

likeminds.DbHostName
Description: This parameter is required for MS SQL Server 2005 only. This value is the host name of the LikeMinds database.
Value: none available
Example: none available
Default: myserver

likeminds.DbTablespace
Description: This parameter is required for DB2 for z/OS only. This value is the name of the LikeMinds database tablespace.
Value: none available
Example: none available
Default: lmdbts

likeminds.DbStorageGroup
Description: This parameter is required for DB2 for z/OS only. This value is the storage group for the WebSphere Portal likeminds database.
Value: none available
Example: none available
Default: WPSSG

likeminds.DbVolumes
Description: This parameter is required for DB2 for z/OS only. This value is the volumes for the WebSphere Portal likeminds database
Value: none available
Example: none available
Default: *

likeminds.DbVcat
Description: This parameter is required for DB2 for z/OS only. This value is the VCAT for the WebSphere Portal likeminds database
Value: none available
Example: none available
Default: DSN810

likeminds.Db4KBufferPoolName
Description: This parameter is required for DB2 for z/OS only. This value is the 4K bufferpool name for the WebSphere Portal likeminds database
Value: none available
Example: none available
Default: BP2

likeminds.Db32KBufferPoolName
Description: This parameter is required for DB2 for z/OS only. This value is the 32K bufferpool name for the WebSphere Portal likeminds database
Value: none available
Example: none available
Default: BP32K

source.likeminds.DbType
Description: The type of database to use for the LikeMinds database.
Value: See examples for DbType and DbUrl above.
Example: none available
Default: derby

source.likeminds.DbName
Description: The name of the Feedback database.
Value:
This value should also appear as the database element in likeminds.DbUrl
Non-Windows platforms when using DB2 only: This value is the TCPIP Alias for the database.
For DB2 database for i5/OS: this value must be unique for this domain
For remote DB2 database for i5/OS: /wpsfdbdb
Example: none available
Default: wpsdb

source.likeminds.DbSchema
Description: The Likeminds 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: none available
Example: none available
Default: likeminds

source.likeminds.DbNameOnZos
Description: This parameter is required for DB2 for z/OS only
Value:
If running db2_zos as remote database, this value is the name of the remote Likeminds database.
If portal is running on z/OS with db2_zos, this value must be set equal to the value in the DbName parameter.
Example: none available
Default: WPSTST02

source.likeminds.DataSourceName
Description: The name of the datasource to use for the Likeminds database.
Value: none available
Example: none available
Default: wpdbDS

source.likeminds.DbUrl
Description: The Likeminds database URL.
Value: Database URL
Example: Valid example values are provided above at the beginning of this section.
Default: jdbc:derby:wpsdb;create=true

source.likeminds.DbUser
Description: The database administrator user ID.
Value: none available
Example: none available
Default: db2admin

source.likeminds.DbPassword
Description: The database administrator password.
Value: none available
Example: none available
Default: ReplaceWithYourDbAdminPwd

source.likeminds.XDbName
Description: This parameter is required for Non-Windows platforms when using DB2 only and only for local DB2 database using Type 2 JDBC driver. This value is the name of the Likeminds database.
Value: none available
Example: none available
Default: lmdb6TCP

source.likeminds.DbNode
Description: This parameter is required for Non-Windows platforms when using DB2 only. This value is the node for the Likeminds database and needs to be set if you want to call the create-database task.
Value: none available
Example: none available
Default: pznNode

source.likeminds.DbHostName
Description: This parameter is required for MS SQL Server 2005 only. This value is the host name of the Likeminds database.
Value: none available
Example: none available
Default: myserver

source.likeminds.DbTablespace
Description: This parameter is required for DB2 for z/OS only. This value is the name of the Likeminds database tablespace.
Value: none available
Example: none available
Default: lmdbts

source.likeminds.DbStorageGroup
Description: This parameter is required for DB2 for z/OS only. This value is the storage group for the WebSphere Portal Likeminds database.
Value: none available
Example: none available
Default: WPSSG

source.likeminds.DbVolumes
Description: This parameter is required for DB2 for z/OS only. This value is the volumes for the WebSphere Portal Likeminds database
Value: none available
Example: none available
Default: *

source.likeminds.DbVcat
Description: This parameter is required for DB2 for z/OS only. This value is the VCAT for the WebSphere Portal Likeminds database
Value: none available
Example: none available
Default: DSN810

source.likeminds.Db4KBufferPoolName
Description: This parameter is required for DB2 for z/OS only. This value is the 4K bufferpool name for the WebSphere Portal likeminds database
Value: none available
Example: none available
Default: BP2

source.likeminds.Db32KBufferPoolName
Description: This parameter is required for DB2 for z/OS only. This value is the 32K bufferpool name for the WebSphere Portal likeminds database
Value: none available
Example: none available
Default: BP32K

1. 
   

END: LikeMinds Database Properties

1. 
   

=WP.EAR PROPERTIES=

WP.EAR loaded from:
AIX: /usr/IBM/WebSphere/PortalServer/installer/wp.ear/wp.ear.properties
i5/OS: /QIBM/UserData/WebSphere/PortalServer/installer/wp.ear/wp.ear.properties
Linux, HP-UX, Solaris: /opt/IBM/WebSphere/PortalServer/installer/wp.ear/wp.ear.properties
Windows: C:/IBM/wp615/WebSphere/PortalServer/installer/wp.ear/wp.ear.properties

WpsDefaultHome
Description: The WebSphere Portal default home URL
Value: URL
Example:
http://:// With "portal" in the URL: http://localhost:80/wps/portal
Default: portal

WpsPersonalizedHome
Description: The WebSphere Portal personalized home.
Value: URL
Example:
http://:// With "myportal" in the URL: http://localhost:80/wps/myportal
Default: myportal

1. END WP.EAR PROPERTIES #
   

1. BEGIN WP.DB.IMPL PROPERTIES #
   

WP.DB.IMPL loaded from: /opt/IBM/WebSphere/PortalServer/base/wp.db.impl/wp.db.impl.properties
AIX: /usr/IBM/WebSphere/PortalServer/base/wp.db.impl/wp.db.impl.properties
i5/OS: /QIBM/UserData/WebSphere/PortalServer/base/wp.db.impl/wp.db.impl.properties
Linux, HP-UX, Solaris: /opt/IBM/WebSphere/PortalServer/base/wp.db.impl/wp.db.impl.properties
Windows: C:/IBM/wp615/WebSphere/PortalServer/base/wp.db.impl/wp.db.impl.properties

1. 
   

Examples for DbType and DbUrl

1. 
   

1. DbType: The type of database to be used for WebSphere Portal
   
2. DB2: { db2 }
   
3. Oracle: { oracle }
   
4. MS SQL Server 2005: { sqlserver2005 }
   
5. Derby: { derby }
   
6. DB2 for iSeries: { db2_iseries }
   
7. DB2 for z/OS: { db2_zos }
   

1. DbUrl: The wps database URL
   
2. Note: The database element of this value should match the value of DbName
   
3. Note: For DB2 Type 4 driver use jdbc:db2://:/wpsdb:returnAlias=0;
   
4. The port is usually 50000 (Windows) or 50001 (Linux).
   
5. Note: On z/OS, the database element of this value should match the location
   
6. name of the database to be used when establishing connections with
   
7. the DB2 datasource used by WebSphere Portal
   
8. derby: { jdbc:derby:wpsdb;create=true }
   
9. db2 (type 2): { jdbc:db2:wpsdb }
   
10. db2 (type 4): { jdbc:db2://:50000/wpsdb:returnAlias=0; }
    
11. db2_iseries (type 2): { jdbc:db2:*LOCAL/wpsdb }
    
12. db2_iseries (type 4): { jdbc:as400:/wpsdb }
    
13. db2_zos: { jdbc:db2: }
    
14. db2_zos (remote, type 2): { jdbc:db2:wpsdb }
    
15. db2_zos (remote, type 4): { jdbc:db2://:/ }
    
16. oracle (type 4, thin): { jdbc:oracle:thin:@:1521:wpsdb }
    
17. sqlserver2005 (Microsoft): { jdbc:sqlserver://:1433;SelectMethod=cursor;DatabaseName=wpsdb }
    
18. sqlserver2005 (DataDirect): { jdbc:datadirect:sqlserver://:1433;DatabaseName=wpsdb }
    

1. AdminUrl: The database URL for sqlserver administation
   
2. sqlserver2005 (Microsoft): { jdbc:sqlserver://:1433}
   
3. sqlserver2005 (DataDirect): { jdbc:datadirect:sqlserver://:1433}
   

1. 
   

Examples for DbType and DbUrl

1. 
   

1. 
   

Release Database Properties

1. 
   

release.DbType
Description: The type of database to be used for the Release database.
Value: The database server you are using.
Examples: Valid example values are provided above in the "Examples for DbType and DbUrl" section.
Default: derby

release.DbName
Description: The name of the feedback database. This value should also appear as the database element in release.DbUrl
Value:
When WebSphere Portal is configured to use DB2 for i5/OS, this value must be unique for this domain.
When WebSphere Portal is installed on Linux and UNIX-based platforms and configured to use a DB2 database, this value is the TCPIP Alias for the database.
When WebSphere Portal is configured to use a remote DB2 database for iSeries, the value must be: /wpsreldb
Example: none available
Default: wpsdb

release.DbSchema
Description: The Release 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. For DB2 database for iSeries, this value must be less than 10 characters.
Value:
For DB2 database for iSeries, this value must be less than 10 characters.
Example: none available
Default: release

release.DbNameOnZos
Description: This parameter is required for DB2 for z/OS only. If WebSphere Portal is configured to use a remote DB2 for z/OS database, the value should be the name of the remote Feedback 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 release.DbName parameter.
Value: none available
Example: none available
Default: WPSTST02

release.DataSourceName
Description: The name of datasource to use for the Release domain.
Value: none available
Example: none available
Default: wpdbDS

release.DbUrl
Description: The wps release domain URL.
Value: URL
Example: Valid example values are provided above in the "Examples for DbType and DbUrl" section.
Default: jdbc:derby:wpsdb;create=true

release.DbUser
Description: The database user ID.
Value: none available
Example: none available
Default: db2admin

release.DbPassword
Description: The database administrator password
Value: none available
Example: none available
Default: ReplaceWithYourDbAdminPwd

release.DBA.DbUser
Description: The database administrator user for privileged access operations during creation of this database type.
Value: none available
Example: none available
Default: db2admin

release.DBA.DbPassword
Description: The database administrator user password for privileged access operations during creation of this database type.
Value: none available
Example: none available
Default: ReplaceWithYourDBAPwd

release.DbHome
Description: This is the root location for the database. This value is used to specify the location (remote or locally) to create the tablespaces for Oracle.
Value: Use the following value that is appropriate for your 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: in the path below may or may not be there in your installation.
Oracle: { /product/10.1.0/db_1 }
SQLServer: { C:\\Microsoft SQL Server\\\\MSSQL }
Example: none available
Default: ReplaceWithYourDbHomeDir

release.AdminUrl
Description: This parameter is required for SQL Server only. This is used to connect to SQL Server for DBA operations.
Value: The value is the SQL Server URL without a database attached.
Example: Valid example values are provided above in the "AdminUrl" section.
Default: ReplaceWithYourAdminUrl

release.XDbName
Description: The release database alias that needs to be set if you want to call the create-database task. This parameter is required for Non-Windows platforms when using DB2. This parameter is also required for local DB2 database using a Type 2 JDBC driver.
Value: none available
Example: none available
Default: wps6TCP

release.DbNode
Description: This parameter is required for Non-Windows platforms when using DB2. This value is the node for the WebSphere Portal release domain database and needs to be set if you want to call the create-database task.
Value: none available
Example: none available
Default: wpsNode

release.DbStorageGroup
Description: This parameter is required for DB2 for z/OS only. This value is the storage group for the WebSphere Portal release database.
Value: none available
Example: none available
Default: WPSSG

release.DbVolumes
Description: This parameter is required for DB2 for z/OS only. This value is the volumes for the WebSphere Portal release database.
Value: none available
Example: none available
Default: *

release.DbVcat
Description: This parameter is required for DB2 for z/OS only. This value is the VCAT for the WebSphere Portal release database.
Value: none available
Example: none available
Default: DSN810

release.DbIndex4KBufferPoolName
Description: This parameter is 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: none available
Example: none available
Default: BP3

release.Db4KBufferPoolName
Description: This parameter is required for DB2 for z/OS only. This value is the 4K bufferpool name for the WebSphere Portal release database.
Value: none available
Example: none available
Default: BP2

release.Db32KBufferPoolName
Description: This parameter is required for DB2 for z/OS only. This value is the 32K bufferpool name for the WebSphere Portal release database.
Value: none available
Example: none available
Default: BP32K

release.TablespaceTrackMod
Description: This parameter is required for DB2 for z/OS only. This value 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
Example: none available
Default: YES

source.release.DbType
Description: The type of database to use for the WebSphere Portal Release domain.
Value: See the examples for DbType and DbUrl above.
Example: none available
Default: derby

source.release.DbName
Description: The name of the Feedback database.
Value:
This value should also appear as the database element in release.DbUrl
Non-Windows platforms when using DB2 only: This value is the TCPIP Alias for the database.
For DB2 database for i5/OS: this value must be unique for this domain
For remote DB2 database for i5/OS: /wpsreldb
Example: none available
Default: wpsdb

source.release.DbSchema
Description: The 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: none available
Example: none available
Default: release

source.release.DbNameOnZos
Description: This parameter is 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 database.
If portal is running on z/OS with db2_zos, this value must be set equal to the value in the DbName parameter.
Example: none available
Default: WPSTST02

source.release.DataSourceName
Description: The name of the datasource to use for the WebSphere Portal Release domain.
Value: none available
Example: none available
Default: wpdbDS

source.release.DbUrl
Description: The wps release domain database URL.
Value: Database URL
Example: Valid example values are provided above at the beginning of this section.
Default: jdbc:derby:wpsdb;create=true

source.release.DbUser
Description: The database administrator user ID.
Value: none available
Example: none available
Default: db2admin

source.release.DbPassword
Description: The database administrator password.
Value: none available
Example: none available
Default: ReplaceWithYourDbAdminPwd

source.release.XDbName
Description: This parameter is required for Non-Windows platforms when using DB2 only and only for local DB2 database using Type 2 JDBC driver. This value is the name of the release database alias that needs to be set if you want to call the create-database task.
Value: none available
Example: none available
Default: wps6TCP

source.release.DbNode
Description: This parameter is required for Non-Windows platforms when using DB2 only. This value is the node for theWebSphere Portal Release domain database and needs to be set if you want to call the create-database task.
Value: none available
Example: none available
Default: wpsNode

source.release.DbStorageGroup
Description: This parameter is required for DB2 for z/OS only. This value is the storage group for the WebSphere Portal release database.
Value: none available
Example: none available
Default: WPSSG

source.release.DbVolumes
Description: This parameter is required for DB2 for z/OS only. This value is the volumes for the WebSphere Portal release database
Value: none available
Example: none available
Default: *

source.release.DbVcat
Description: This parameter is required for DB2 for z/OS only. This value is the VCAT for the WebSphere Portal release database
Value: none available
Example: none available
Default: DSN810

source.release.DbIndex4KBufferPoolName
Description: This parameter is 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: none available
Example: none available
Default: BP3

source.release.Db4KBufferPoolName
Description: This parameter is required for DB2 for z/OS only. This value is the 4K bufferpool name for the WebSphere Portal release database.
Value: none available
Example: none available
Default: BP2

source.release.Db32KBufferPoolName
Description: This parameter is required for DB2 for z/OS only. This value is the 32K bufferpool name for the WebSphere Portal release database.
Value: none available
Example: none available
Default: BP32K

1. 
   

END: Release Database Properties

1. 
   

1. 
   

Community Database Properties

1. 
   

community.DbType
Description: The type of database to be used for the WebSphere Portal Community domain.
Value: The database server you are using.
Examples: Valid example values are provided above in the "Examples for DbType and DbUrl" section.
Default: derby

community.DbName
Description: The name of the community domain database. This value should also appear as the database element in community.DbUrl
Value:
When WebSphere Portal is configured to use DB2 for i5/OS, this value must be unique for this domain.
When WebSphere Portal is installed on Linux and UNIX-based platforms and configured to use a DB2 database, this value is the TCPIP Alias for the database.
When WebSphere Portal is configured to use a remote DB2 database for iSeries, the value must be: /wpscomdb
Example: none available
Default: wpsdb

community.DbSchema
Description: The 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:
For DB2 database for iSeries, this value must be less than 10 characters.
Example: none available
Default: community

community.DbNameOnZos
Description: This parameter is required for DB2 for z/OS only. 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.
Value: none available
Example: none available
Default: WPSTST02

community.DataSourceName
Description: The name of datasource to use for the WebSphere Portal Community domain database.
Value: none available
Example: none available
Default: wpdbDS

community.DbUrl
Description: The WebSphere Portal Community domain database URL.
Value: URL
Example: Valid example values are provided above in the "Examples for DbType and DbUrl" section.
Default: jdbc:derby:wpsdb;create=true

community.DbUser
Description: The database user ID.
Value: none available
Example: none available
Default: db2admin

community.DbPassword
Description: The database password.
Value: none available
Example: none available
Default: ReplaceWithYourDbAdminPwd

community.DBA.DbUser
Description: The database administrator user for privileged access operations during creation of this database type.
Value: none available
Example: none available
Default: db2admin

community.DBA.DbPassword
Description: The database administrator user password for privileged access operations during creation of this database type.
Value: none available
Example: none available
Default: ReplaceWithYourDBAPwd

community.DbHome
Description: This is the root location for the database. This value is used to specify the location (remote or locally) to create the tablespaces for Oracle.
Value: Use the following value that is appropriate for your 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: in the path below may or may not be there in your installation.
Oracle: { /product/10.1.0/db_1 }
SQLServer: { C:\\Microsoft SQL Server\\\\MSSQL }
Example: none available
Default: ReplaceWithYourDbHomeDir

community.AdminUrl
Description: This parameter is required for SQL Server only. This is used to connect to SQL Server for DBA operations.
Value: The value is the SQL Server URL without a database attached.
Example: Valid example values are provided above in the "AdminUrl" section.
Default: ReplaceWithYourAdminUrl

community.XDbName
Description: The name of the community database alias that needs to be set if you want to call the create-database task. This parameter is required for Non-Windows platforms when using DB2. This parameter is also required for local DB2 database using a Type 2 JDBC driver.
Value: none available
Example: none available
Default: wps6TCP

community.DbNode
Description: This parameter is required for Non-Windows platforms when using DB2. This value is the node for the WebSphere Portal Community domain database and needs to be set if you want to call the create-database task.
Value: none available
Example: none available
Default: wpsNode

community.DbStorageGroup
Description: This parameter is required for DB2 for z/OS only. This value is the storage group for the WebSphere Portal community database.
Value: none available
Example: none available
Default: WPSSG

community.DbVolumes
Description: This parameter is required for DB2 for z/OS only. This value is the volumes for the WebSphere Portal community database.
Value: none available
Example: none available
Default: *

community.DbVcat
Description: This parameter is required for DB2 for z/OS only. This value is the VCAT for the WebSphere Portal community database.
Value: none available
Example: none available
Default: DSN810

community.DbIndex4KBufferPoolName
Description: This parameter is 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: none available
Example: none available
Default: BP3

community.Db4KBufferPoolName
Description: This parameter is required for DB2 for z/OS only. This value is the 4K bufferpool name for the WebSphere Portal community database.
Value: none available
Example: none available
Default: BP2

community.Db32KBufferPoolName
Description: This parameter is required for DB2 for z/OS only. This value is the 32K bufferpool name for the WebSphere Portal community database.
Value: none available
Example: none available
Default: BP32K

community.TablespaceTrackMod
Description: This parameter is required for DB2 for z/OS only. This value 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
Example: none available
Default: YES

source.community.DbType
Description: The type of database to be used for the WebSphere Portal Community domain.
Value: The database server you are using.
Examples: Valid example values are provided above in the "Examples for DbType and DbUrl" section.
Default: derby

source.community.DbName
Description: The name of the community database. This value should also appear as the database element in community.DbUrl
Value:
When WebSphere Portal is configured to use DB2 for i5/OS, this value must be unique for this domain.
When WebSphere Portal is installed on Linux and UNIX-based platforms and configured to use a DB2 database, this value is the TCPIP Alias for the database.
When WebSphere Portal is configured to use a remote DB2 database for iSeries, the value must be: /wpscomdb
Example: none available
Default: wpsdb

source.community.DbSchema
Description: The 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:
For DB2 database for iSeries, this value must be less than 10 characters.
Example: none available
Default: community

source.community.DbNameOnZos
Description: This parameter is required for DB2 for z/OS only. 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.
Value: none available
Example: none available
Default: WPSTST02

source.community.DataSourceName
Description: The name of datasource to use for the WebSphere Portal Community domain database.
Value: none available
Example: none available
Default: wpdbDS

source.community.DbUrl
Description: The WebSphere Portal Community domain database URL.
Value: URL
Example: Valid example values are provided above in the "Examples for DbType and DbUrl" section.
Default: jdbc:derby:wpsdb;create=true

source.community.DbUser
Description: The database user ID.
Value: none available
Example: none available
Default: db2admin

source.community.DbPassword
Description: The database password.
Value: none available
Example: none available
Default: ReplaceWithYourDbAdminPwd

source.community.XDbName
Description: The name of the community database alias that needs to be set if you want to call the create-database task. This parameter is required for Non-Windows platforms when using DB2. This parameter is also required for local DB2 database using a Type 2 JDBC driver.
Value: none available
Example: none available
Default: wps6TCP

source.community.DbNode
Description: This parameter is required for Non-Windows platforms when using DB2. This value is the node for the WebSphere Portal Community domain database and needs to be set if you want to call the create-database task.
Value: none available
Example: none available
Default: wpsNode

source.community.DbStorageGroup
Description: This parameter is required for DB2 for z/OS only. This value is the storage group for the WebSphere Portal community database.
Value: none available
Example: none available
Default: WPSSG

source.community.DbVolumes
Description: This parameter is required for DB2 for z/OS only. This value is the volumes for the WebSphere Portal community database.
Value: none available
Example: none available
Default: *

source.community.DbVcat
Description: This parameter is required for DB2 for z/OS only. This value is the VCAT for the WebSphere Portal community database.
Value: none available
Example: none available
Default: DSN810

source.community.DbIndex4KBufferPoolName
Description: This parameter is 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: none available
Example: none available
Default: BP3

source.community.Db4KBufferPoolName
Description: This parameter is required for DB2 for z/OS only. This value is the 4K bufferpool name for the WebSphere Portal community database.
Value: none available
Example: none available
Default: BP2

source.community.Db32KBufferPoolName
Description: This parameter is required for DB2 for z/OS only. This value is the 32K bufferpool name for the WebSphere Portal community database.
Value: none available
Example: none available
Default: BP32K

1. 
   

END: Community Database Properties

1. 
   

1. 
   

Customization Database Properties

1. 
   

customization.DbType
Description: The type of database to be used for the WebSphere Portal Customization domain.
Value: The database server you are using.
Examples: Valid example values are provided above in the "Examples for DbType and DbUrl" section.
Default: derby

customization.DbName
Description: The name of the WebSphere Portal Customization database. This value should also appear as the database element in customization.DbUrl
Value:
When WebSphere Portal is configured to use DB2 for i5/OS, this value must be unique for this domain.
When WebSphere Portal is installed on Linux and UNIX-based platforms and configured to use a DB2 database, this value is the TCPIP Alias for the database.
When WebSphere Portal is configured to use a remote DB2 database for iSeries, the value must be: /wpscstdb
Example: none available
Default: wpsdb

customization.DbSchema
Description: The 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:
For DB2 database for iSeries, this value must be less than 10 characters.
Example: none available
Default: customization

customization.DbNameOnZos
Description: This parameter is required for DB2 for z/OS only. If WebSphere Portal is configured to use a remote DB2 for z/OS database, the value should be the name of the remote Customization 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 customization.DbName parameter.
Value: none available
Example: none available
Default: WPSTST02

customization.DataSourceName
Description: The name of datasource to use for the WebSphere Portal Customization domain database.
Value: none available
Example: none available
Default: wpdbDS

customization.DbUrl
Description: The WebSphere Portal Customization domain database URL.
Value: URL
Example: Valid example values are provided above in the "Examples for DbType and DbUrl" section.
Default: jdbc:derby:wpsdb;create=true

customization.DbUser
Description: The database user ID.
Value: none available
Example: none available
Default: db2admin

customization.DbPassword
Description: The database password.
Value: none available
Example: none available
Default: ReplaceWithYourDbAdminPwd

customization.DBA.DbUser
Description: The database administrator user for privileged access operations during creation of this database type.
Value: none available
Example: none available
Default: db2admin

customization.DBA.DbPassword
Description: The database administrator user password for privileged access operations during creation of this database type.
Value: none available
Example: none available
Default: ReplaceWithYourDBAPwd

customization.DbHome
Description: This is the root location for the database. This value is used to specify the location (remote or locally) to create the tablespaces for Oracle.
Value: Use the following value that is appropriate for your 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: in the path below may or may not be there in your installation.
Oracle: { /product/10.1.0/db_1 }
SQLServer: { C:\\Microsoft SQL Server\\\\MSSQL }
Example: none available
Default: ReplaceWithYourDbHomeDir

customization.AdminUrl
Description: This parameter is required for SQL Server only. This is used to connect to SQL Server for DBA operations.
Value: The value is the SQL Server URL without a database attached.
Example: Valid example values are provided above in the "AdminUrl" section.
Default: ReplaceWithYourAdminUrl

customization.XDbName
Description: The name of the customization database alias that needs to be set if you want to call the create-database task. This parameter is required for Non-Windows platforms when using DB2. This parameter is also required for local DB2 database using a Type 2 JDBC driver.
Value: none available
Example: none available
Default: wps6TCP

customization.DbNode
Description: This parameter is required for Non-Windows platforms when using DB2. This value is the node for the WebSphere Portal Customization domain database and needs to be set if you want to call the create-database task.
Value: none available
Example: none available
Default: wpsNode

customization.DbStorageGroup
Description: This parameter is required for DB2 for z/OS only. This value is the storage group for the WebSphere Portal customization database.
Value: none available
Example: none available
Default: WPSSG

customization.DbVolumes
Description: This parameter is required for DB2 for z/OS only. This value is the volumes for the WebSphere Portal customization database.
Value: none available
Example: none available
Default: *

customization.DbVcat
Description: This parameter is required for DB2 for z/OS only. This value is the VCAT for the WebSphere Portal customization database.
Value: none available
Example: none available
Default: DSN810

customization.DbIndex4KBufferPoolName
Description: This parameter is 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: none available
Example: none available
Default: BP3

customization.Db4KBufferPoolName
Description: This parameter is required for DB2 for z/OS only. This value is the 4K bufferpool name for the WebSphere Portal customization database.
Value: none available
Example: none available
Default: BP2

customization.Db32KBufferPoolName
Description: This parameter is required for DB2 for z/OS only. This value is the 32K bufferpool name for the WebSphere Portal customization database.
Value: none available
Example: none available
Default: BP32K

customization.TablespaceTrackMod
Description: This parameter is required for DB2 for z/OS only. This value 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
Example: none available
Default: YES

source.customization.DbType
Description: The type of database to be used for the WebSphere Portal Customization domain.
Value: The database server you are using.
Examples: Valid example values are provided above in the "Examples for DbType and DbUrl" section.
Default: derby

source.customization.DbName
Description: The name of the customization database. This value should also appear as the database element in customization.DbUrl
Value:
When WebSphere Portal is configured to use DB2 for i5/OS, this value must be unique for this domain.
When WebSphere Portal is installed on Linux and UNIX-based platforms and configured to use a DB2 database, this value is the TCPIP Alias for the database.
When WebSphere Portal is configured to use a remote DB2 database for iSeries, the value must be: /wpscstdb
Example: none available
Default: wpsdb

source.customization.DbSchema
Description: The 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:
For DB2 database for iSeries, this value must be less than 10 characters.
Example: none available
Default: customization

source.customization.DbNameOnZos
Description: This parameter is required for DB2 for z/OS only. If WebSphere Portal is configured to use a remote DB2 for z/OS database, the value should be the name of the remote Customization 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 customization.DbName parameter.
Value: none available
Example: none available
Default: WPSTST02

source.customization.DataSourceName
Description: The name of datasource to use for the WebSphere Portal Customization domain database.
Value: none available
Example: none available
Default: wpdbDS

source.customization.DbUrl
Description: The WebSphere Portal Customization domain database URL.
Value: URL
Example: Valid example values are provided above in the "Examples for DbType and DbUrl" section.
Default: jdbc:derby:wpsdb;create=true

source.customization.DbUser
Description: The database user ID.
Value: none available
Example: none available
Default: db2admin

source.customization.DbPassword
Description: The database password.
Value: none available
Example: none available
Default: ReplaceWithYourDbAdminPwd

source.customization.XDbName
Description: The name of the customization database alias that needs to be set if you want to call the create-database task. This parameter is required for Non-Windows platforms when using DB2. This parameter is also required for local DB2 database using a Type 2 JDBC driver.
Value: none available
Example: none available
Default: wps6TCP

source.customization.DbNode
Description: This parameter is required for Non-Windows platforms when using DB2. This value is the node for the WebSphere Portal Customization domain database and needs to be set if you want to call the create-database task.
Value: none available
Example: none available
Default: wpsNode

source.customization.DbStorageGroup
Description: This parameter is required for DB2 for z/OS only. This value is the storage group for the WebSphere Portal customization database.
Value: none available
Example: none available
Default: WPSSG

source.customization.DbVolumes
Description: This parameter is required for DB2 for z/OS only. This value is the volumes for the WebSphere Portal customization database.
Value: none available
Example: none available
Default: *

source.customization.DbVcat
Description: This parameter is required for DB2 for z/OS only. This value is the VCAT for the WebSphere Portal customization database.
Value: none available
Example: none available
Default: DSN810

source.customization.DbIndex4KBufferPoolName
Description: This parameter is 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: none available
Example: none available
Default: BP3

source.customization.Db4KBufferPoolName
Description: This parameter is required for DB2 for z/OS only. This value is the 4K bufferpool name for the WebSphere Portal customization database.
Value: none available
Example: none available
Default: BP2

source.customization.Db32KBufferPoolName
Description: This parameter is required for DB2 for z/OS only. This value is the 32K bufferpool name for the WebSphere Portal customization database.
Value: none available
Example: none available
Default: BP32K

1. 
   

END: Customization Database Properties

1. 
   

1. 
   

JCR Database Properties

1. 
   

jcr.DbType
Description: The type of database to be used for the WebSphere Portal JCR domain.
Value: The database server you are using.
Examples: Valid example values are provided above in the "Examples for DbType and DbUrl" section.
Default: derby

jcr.DbName
Description: The name of the JCR domain database. This value should also appear as the database element in jcr.DbUrl
Value:
When WebSphere Portal is configured to use DB2 for i5/OS, this value must be unique for this domain.
When WebSphere Portal is installed on Linux and UNIX-based platforms and configured to use a DB2 database, this value is the TCPIP Alias for the database.
When WebSphere Portal is configured to use a remote DB2 database for iSeries, the value must be: /wpsjcrdb
Example: none available
Default: wpsdb

jcr.DbSchema
Description: The 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:
For DB2 database for iSeries, this value must be less than 10 characters.
Example: none available
Default: jcr

jcr.DbNameOnZos
Description: This parameter is required for DB2 for z/OS only. If WebSphere Portal is configured to use a remote DB2 for z/OS database, the value should be the name of the remote JCR 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 jcr.DbName parameter.
Value: none available
Example: none available
Default: WPSTST02

jcr.DataSourceName
Description: The name of datasource to use for the WebSphere Portal JCR domain database.
Value: none available
Example: none available
Default: wpdbDS

jcr.DbUrl
Description: The WebSphere Portal JCR domain database URL.
Value: URL
Example: Valid example values are provided above in the "Examples for DbType and DbUrl" section.
Default: jdbc:derby:wpsdb;create=true

jcr.DbUser
Description: The database user ID.
Value: none available
Example: none available
Default: db2admin

jcr.DbPassword
Description: The database password.
Value: none available
Example: none available
Default: ReplaceWithYourDbAdminPwd

jcr.DBA.DbUser
Description: The database administrator user for privileged access operations during creation of this database type.
Value: none available
Example: none available
Default: db2admin

jcr.DBA.DbPassword
Description: The database administrator user password for privileged access operations during creation of this database type.
Value: none available
Example: none available
Default: ReplaceWithYourDBAPwd

jcr.DbHome
Description: This is the root location for the database. This value is used to specify the location (remote or locally) to create the tablespaces for Oracle.
Value: Use the following value that is appropriate for your 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: in the path below may or may not be there in your installation.
Oracle: { /product/10.1.0/db_1 }
SQLServer: { C:\\Microsoft SQL Server\\\\MSSQL }
Example: none available
Default: ReplaceWithYourDbHomeDir

jcr.AdminUrl
Description: This parameter is required for SQL Server only. This is used to connect to SQL Server for DBA operations.
Value: The value is the SQL Server URL without a database attached.
Example: Valid example values are provided above in the "AdminUrl" section.
Default: ReplaceWithYourAdminUrl

jcr.XDbName
Description: The name of the JCR database alias that needs to be set if you want to call the create-database task. This parameter is required for Non-Windows platforms when using DB2. This parameter is also required for local DB2 database using a Type 2 JDBC driver.
Value: none available
Example: none available
Default: wps6TCP

jcr.DbNode
Description: This parameter is required for Non-Windows platforms when using DB2. This value is the node for the WebSphere Portal JCR domain database and needs to be set if you want to call the create-database task.
Value: none available
Example: none available
Default: wpsNode

jcr.DbSaPassword
Description: This parameter is optional for MS SQL Server 2005. This value is the SQL Server System Administrator password.
Value: none available
Example: none available
Default: ReplaceWithYourDbAdminPwd

jcr.DbHost
Description: This parameter is required for DB2 for z/OS. This value is the host name (only) of remote system hosting the DB2 Content Manager Runtime Edition database.
Value: none available
Example: none available
Default: ReplaceWithYourDbHost

jcr.DbDomain
Description: This parameter is required for DB2 for z/OS. This value is the domain (not including hostname) of the remote system hosting the DB2 Content Manager Runtime Edition database.
Value: none available
Example: none available
Default: yourco.com

jcr.DbPort
Description: This parameter is required for DB2 for z/OS. This value is the port number of DB2 Content Manager Runtime Edition database on the remote system.
Value: none available
Example: none available
Default: 446

jcr.ZosDbPrefix
Description: This parameter is required for DB2 for z/OS. This value is the common prefix of Node Type database names for DB2 Content Manager Runtime Edition.
Value: none available
Example: none available
Default: ICM

jcr.ZosDbMaxTables
Description: This parameter is required for DB2 for z/OS. This value is the maximum number of User Defined Tables to be stored in a particular Node Type DB in the DB2 Content Manager Runtime Edition database.
Value: none available
Example: none available
Default:400

jcr.DbStorageGroup
Description: This parameter is required for DB2 for z/OS only. This value is the storage group for the WebSphere Portal JCR database.
Value: none available
Example: none available
Default: WPSSG

jcr.DbVolumes
Description: This parameter is required for DB2 for z/OS only. This value is the volumes for the WebSphere Portal JCR database.
Value: none available
Example: none available
Default: *

jcr.DbVcat
Description: This parameter is required for DB2 for z/OS only. This value is the VCAT for the WebSphere Portal JCR database.
Value: none available
Example: none available
Default: DSN810

jcr.DbIndex4KBufferPoolName
Description: This parameter is 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: none available
Example: none available
Default: BP3

jcr.Db4KBufferPoolName
Description: This parameter is required for DB2 for z/OS only. This value is the 4K bufferpool name for the WebSphere Portal JCR database.
Value: none available
Example: none available
Default: BP2

jcr.Db32KBufferPoolName
Description: This parameter is required for DB2 for z/OS only. This value is the 32K bufferpool name for the WebSphere Portal JCR database.
Value: none available
Example: none available
Default: BP32K

jcr.TablespaceTrackMod
Description: This parameter is required for DB2 for z/OS only. This value 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
Example: none available
Default: YES

source.jcr.DbType
Description: The type of database to be used for the WebSphere Portal JCR domain.
Value: The database server you are using.
Examples: Valid example values are provided above in the "Examples for DbType and DbUrl" section.
Default: derby

source.jcr.DbName
Description: The name of the JCR domain database. This value should also appear as the database element in jcr.DbUrl
Value:
When WebSphere Portal is configured to use DB2 for i5/OS, this value must be unique for this domain.
When WebSphere Portal is installed on Linux and UNIX-based platforms and configured to use a DB2 database, this value is the TCPIP Alias for the database.
When WebSphere Portal is configured to use a remote DB2 database for iSeries, the value must be: /wpsjcrdb
Example: none available
Default: wpsdb

source.jcr.DbSchema
Description: The 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:
For DB2 database for iSeries, this value must be less than 10 characters.
Example: none available
Default: jcr

source.jcr.DbNameOnZos
Description: This parameter is required for DB2 for z/OS only. If WebSphere Portal is configured to use a remote DB2 for z/OS database, the value should be the name of the remote JCR 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 jcr.DbName parameter.
Value: none available
Example: none available
Default: WPSTST02

source.jcr.DataSourceName
Description: The name of datasource to use for the WebSphere Portal JCR domain database.
Value: none available
Example: none available
Default: wpdbDS

source.jcr.DbUrl
Description: The WebSphere Portal JCR domain database URL.
Value: URL
Example: Valid example values are provided above in the "Examples for DbType and DbUrl" section.
Default: jdbc:derby:wpsdb;create=true

source.jcr.DbUser
Description: The database user ID.
Value: none available
Example: none available
Default: db2admin

source.jcr.DbPassword
Description: The database password.
Value: none available
Example: none available
Default: ReplaceWithYourDbAdminPwd

source.jcr.XDbName
Description: The name of the JCR database alias that needs to be set if you want to call the create-database task. This parameter is required for Non-Windows platforms when using DB2. This parameter is also required for local DB2 database using a Type 2 JDBC driver.
Value: none available
Example: none available
Default: wps6TCP

source.jcr.DbNode
Description: This parameter is required for Non-Windows platforms when using DB2. This value is the node for the WebSphere Portal JCR domain database and needs to be set if you want to call the create-database task.
Value: none available
Example: none available
Default: wpsNode

source.jcr.DbSaPassword
Description: This parameter is optional for MS SQL Server 2005. This value is the SQL Server System Administrator password.
Value: none available
Example: none available
Default: ReplaceWithYourDbAdminPwd

source.jcr.DbHost
Description: This parameter is required for DB2 for z/OS. This value is the host name (only) of remote system hosting the DB2 Content Manager Runtime Edition database.
Value: none available
Example: none available
Default: hostname

source.jcr.DbDomain
Description: This parameter is required for DB2 for z/OS. This value is the domain (not including hostname) of the remote system hosting the DB2 Content Manager Runtime Edition database.
Value: none available
Example: none available
Default: yourco.com

source.jcr.DbPort
Description: This parameter is required for DB2 for z/OS. This value is the port number of DB2 Content Manager Runtime Edition database on the remote system (required for Driver Type 4 only).
Value: none available
Example: none available
Default: 446

source.jcr.ZosDbPrefix
Description: This parameter is required for DB2 for z/OS. This value is the common prefix of Node Type database names for DB2 Content Manager Runtime Edition.
Value: none available
Example: none available
Default: ICM

source.jcr.ZosDbMaxTables
Description: This parameter is required for DB2 for z/OS. This value is the maximum number of User Defined Tables to be stored in a particular Node Type DB in the DB2 Content Manager Runtime Edition database.
Value: none available
Example: none available
Default: 400

source.jcr.DbStorageGroup
Description: This parameter is required for DB2 for z/OS only. This value is the storage group for the WebSphere Portal JCR database.
Value: none available
Example: none available
Default: WPSSG

source.jcr.DbVolumes
Description: This parameter is required for DB2 for z/OS only. This value is the volumes for the WebSphere Portal JCR database.
Value: none available
Example: none available
Default: *

source.jcr.DbVcat
Description: This parameter is required for DB2 for z/OS only. This value is the VCAT for the WebSphere Portal JCR database.
Value: none available
Example: none available
Default: DSN810

source.jcr.DbIndex4KBufferPoolName
Description: This parameter is 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: none available
Example: none available
Default: BP3

source.jcr.Db4KBufferPoolName
Description: This parameter is required for DB2 for z/OS only. This value is the 4K bufferpool name for the WebSphere Portal JCR database.
Value: none available
Example: none available
Default: BP2

source.jcr.Db32KBufferPoolName
Description: This parameter is required for DB2 for z/OS only. This value is the 32K bufferpool name for the WebSphere Portal JCR database.
Value: none available
Example: none available
Default: BP32K

1. 
   

END: JCR Database Properties

1. 
   
2. END WP.DB.IMPL PROPERTIES #
   

1. BEGIN WP.WSRP.COMMON PROPERTIES #
   

WP.WSRP.COMMON loaded from:
AIX: /usr/IBM/WebSphere/PortalServer/base/wp.wsrp.common/wp.wsrp.common.properties
i5/OS: /QIBM/UserData/WebSphere/PortalServer/base/wp.wsrp.common/wp.wsrp.common.properties
Linux, HP-UX, Solaris: /opt/IBM/WebSphere/PortalServer/base/wp.wsrp.common/wp.wsrp.common.properties
Windows: C:/IBM/wp615/WebSphere/PortalServer/base/wp.wsrp.common/wp.wsrp.common.properties

WsrpContextRoot
Description: The context root for Web Services for Remote Portlets.
Value: none available
Example: none available
Default: wsrp

1. END WP.WSRP.COMMON PROPERTIES #
   

1. BEGIN PREREQ.JCR PROPERTIES #
   

PREREQ.JCR loaded from:
AIX: /usr/IBM/WebSphere/PortalServer/jcr/prereq.jcr/prereq.jcr.properties
i5/OS: /QIBM/UserData/WebSphere/PortalServer/jcr/prereq.jcr/prereq.jcr.properties
Linux, HP-UX, Solaris: /opt/IBM/WebSphere/PortalServer/jcr/prereq.jcr/prereq.jcr.properties
Windows: C:/IBM/wp615/WebSphere/PortalServer/jcr/prereq.jcr/prereq.jcr.properties

1. #
   

DB2 Content Manager Runtime Edition Database Properties - BEGIN

1. #
   

JcrBinaryValueFileDir
Description: Directory for DB2 Content Manager Runtime Edition's binary value files.
Value: none available
Example: none available
Default: ${WasUserHome}/${wps.userdir}/jcr/binaryValues

JcrSearchFileDir
Description: Directory for DB2 Content Manager Runtime Edition's search index files.
Value: none available
Example: none available
Default: ${WasUserHome}/${wps.userdir}/jcr/search

JcrDebugLevel
Description: Debug level for DB2 Content Manager Runtime Edition database utilities.
Value: none available
Example: none available
Default: 2

JcrDbUnicode
Description: Indicates whether or not the DB2 Content Manager Runtime Edition database is unicode.
Value: Use one of the following values:
Y: is unicode
N: is NOT unicode
Example: none available
Default: Y

JcrBPCServerName
Description: The name of application server with a configured Business Process Container.
Value: none available
Example: none available
Default: server1

JcrJMSJAASUser
Description: The user for the Promote J2C alias.
Value: none available
Example: none available
Default: ReplaceWithYourJMSUserId

JcrJMSJAASPassword
Description: The password for the Promote J2C alias.
Value: none available
Example: none available
Default: ReplaceWithYourJMSPwd

JcrJMSType
Description: The type of JMS Provider.
Value: Use one of the following values:
mq: {WebSphere MQ JMS Provider}
embedded: {WebSphere JMS Provider}
Example: none available
Default: embedded

JcrMQQueueManager
Description: The name of the WebSphere MQ Queue Manager. This value is not needed for the WebSphere Embedded Messaging.
Value: none available
Example: none available
Default: no default

1. #
   

DB2 Content Manager Runtime Edition Database Properties - END

1. #
   
2. END PREREQ.JCR PROPERTIES #
   

1. BEGIN WP.PROCESSINTEGRATION.CONFIG PROPERTIES #
   

WP.PROCESSINTEGRATION.CONFIG loaded from:
AIX: /usr/IBM/WebSphere/PortalServer/installer/wp.processintegration.config/wp.processintegration.config.properties
i5/OS: /QIBM/UserData/WebSphere/PortalServer/installer/wp.processintegration.config/wp.processintegration.config.properties
Linux, HP-UX, Solaris: /opt/IBM/WebSphere/PortalServer/installer/wp.processintegration.config/wp.processintegration.config.properties
Windows: C:/IBM/wp615/WebSphere/PortalServer/installer/wp.processintegration.config/wp.processintegration.config.properties

pi.IsCrossCell
Description: Set this value to true if the WebSphere Process Server installation to which WebSphere Portal should be connected to is located in another cell. If it is not in another cell, set the value to false.
Value: true false
Example: none available
Default: true

pi.ProcessServerHostAddress
Description: This value is the address of the WebSphere Process Server. Set this value only if pi.IsCrossCell is set to true.
Value: none available
Example: none available
Default: no default

pi.ProcessServerBootstrapPort
Description: This value is the Bootstrap port of the WebSphere Process Server. Set this value only if pi.IsCrossCell is set to true.
Value: none available
Example: none available
Default: no default

pi.ProcessArtifactsLocation
Description: This value is the directory in which the process artifacts are located. Set this value only if pi.IsCrossCell is set to true.
Value: none available
Example: none available
Default: ${USER_INSTALL_ROOT}/processArtifacts

pi.IsWPSCluster
Description: Set this value to true if WebSphere Portal should be connected to a WebSphere Process Server cluster in the same cell. If WebSphere Portal should not be connected to a WebSphere Process Server cluster, set the value to false. Set this value only if pi.IsCrossCell is set to false.
Value: true false
Example: none available
Default: no default

pi.ClusterName
Description: This value is the name of the WebSphere Process Server cluster. Set this value only if pi.IsCrossCell is set to false and pi.IsWPSCluster is set to true.
Value: none available
Example: none available
Default: no default

pi.NodeName
Description: This value is the name of the node of the WebSphere Process Server server. Set this value only if pi.IsCrossCell is set to false and pi.IsWPSCluster is set to false.
Value: none available
Example: none available
Default: no default

pi.ServerName
Description: This value is the name of the WebSphere Process Server server. Set this value only if pi.IsCrossCell is set to false and pi.IsWPSCluster is set to false.
Value: none available
Example: none available
Default: no default

1. END WP.PROCESSINTEGRATION.CONFIG PROPERTIES #
   

1. BEGIN WP.AC.IMPL PROPERTIES #
   

WP.AC.IMPL loaded from:
AIX: /usr/IBM/WebSphere/PortalServer/base/wp.ac.impl/wp.ac.impl.properties
i5/OS: /QIBM/UserData/WebSphere/PortalServer/base/wp.ac.impl/wp.ac.impl.properties
Linux, HP-UX, Solaris: /opt/IBM/WebSphere/PortalServer/base/wp.ac.impl/wp.ac.impl.properties
Windows: C:/IBM/wp615/WebSphere/PortalServer/base/wp.ac.impl/wp.ac.impl.properties

1. #
   

Advanced Security Configuration using External Security Managers

1. #
   

1. #
   

Namespace management parameters common to TAM and SiteMinder

1. #
   

wp.ac.impl.EACserverName
wp.ac.impl.EACcellName
wp.ac.impl.EACappName
Description: (Optional) You can set different "contexts" to further distinguish externalized Portal role names from other role names in the Tivoli Access Manager namespace. This context information will be added to the namespace entry created upon role externalization. If any of the 3 context values are null, none will be used.
Value: none available
Example: none available
Default:
wp.ac.impl.EACserverName=WebSphere_Portal
wp.ac.impl.EACcellName=no default
wp.ac.impl.EACappName=wps

wp.ac.impl.reorderRoles
Description: This field allows you to either have your externalized Portal rolenames displayed with the resource type first, or the role types first. For example, if you make this variable "true", your TAM namespace or SiteMinder protected resource would look similar to:
/WPv61/wps.CONTENT_NODE/Welcome_Page/10_2E@Aministrator/app/server/cell
/WPv61/wps.CONTENT_NODE/Welcome_Page/10_2E@Editor/app/server/cell
/WPv61/wps.CONTENT_NODE/Administration/15_AF@Aministrator/app/server/cell
/WPv61/wps.PORTLET_APPLICATION/Welcome_Portlet/09_2Q@Aministrator/app/server/cell
/WPv61/wps.PORTLET_APPLICATION/Welcome_Portlet/09_2Q@User/app/server/cell

If you set the variable to false, your TAM namespace or SiteMinder protected resource would look similar to:
/WPv61/Aministrator@wps.CONTENT_NODE/Welcome_Page/10_2E/app/server/cell
/WPv61/Administrator@wps.CONTENT_NODE/Administration/15_AF/app/server/cell
/WPv61/Administrator@wps.PORTLET_APPLICATION/Welcome_Portlet/09_2Q/app/server/cell
/WPv61/Editor@wps.CONTENT_NODE/Welcome_Page/10_2E/app/server/cell
/WPv61/User@wps.PORTLET_APPLICATION/Welcome_Portlet/09_2Q/app/server/cell
Value: true false
Example: none available
Default: false

1. 
   

Tivoli Access Manager

1. 
   

1. 
   

AMJRTE connection parameteres

1. 
   

wp.ac.impl.PDAdminId
Description: An administrative user ID for TAM. This user should have the access to create new TAM servers, new Tivoli protected objectspaces, and new Tivoli protected objects.
Value: none available
Example: none available
Default: sec_master

wp.ac.impl.PDAdminPwd
Description: The password for the administrative TAM user.
Value: none available
Example: none available
Default: ReplaceWithYourTAMAdminPwd

wp.ac.impl.PDPermPath
Description: The location of the TAM AMJRTE properties file. This properties file is created by the TAM SvrSslCfg command and contains information such as: Policy Server host name, ports version of AMJRTE path to encryption keys.
Value: none available
Example: none available
Default: ${WasHome}/java/jre/PdPerm.properties

1. #
   

PDJrteCfg command and filesystem parameters:

The following parameter locations depend on your WAS installation

structure. For more information or detail on the

individual parameters, refer to: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.nd.doc/info/ae/ae/rsec_tampdjrtecfg.html

1. 
   

wp.ac.impl.PDClasspath
Description: The location of the TAM PD.jar. This jar file contains the classes required to establish a connection to the policy server and is passed into the classpath of the command.
Value: none available
Example: none available
Default: ${WasHome}/java/jre/lib/ext/PD.jar

wp.ac.impl.PDHome
Description: The installed location of the TAM AMJRTE. This is the same as the pd.home system property in a manual execution.
Value: none available
Example: none available
Default: ${WasHome}/java/jre/PolicyDirector

wp.ac.impl.JavaHome
Description: The location of the java runtime in which to configure. This is the same as the -java_home command line argument in a manual execution.
Value: none available
Example: none available
Default: ${WasHome}/java/jre/

wp.ac.impl.CfgFilesPath
Description: The desired filesystem directory location of the generated TAM AMJRTE properties. The properties files are created by the TAM PdjrteCfg command. This is the same as the -cfgfiles_path command line argument in a manual execution.
Value: none available
Example: none available
Default: ${WasHome}/java/jre

wp.ac.impl.TamHost
Description: Defines the TAM Policy Server used when running PDJrteCfg.
Value: none available
Example: none available
Default: your.TAM.Policy.Server.hostname

1. #
   

SvrSslCfg command parameters

1. #
   

wp.ac.impl.PDServerName

1. Unique application name. This name will be used to create a new Tivoli server in the
   
2. Access Manager Policy Server. This server will appears in the pdadmin server list
   
3. after running the SvrSslCfg command. If a server with the same name appears in the
   
4. server list command, the SvrSslCfg command will fail.
   

Value: none available
Example: none available
Default: amwp61

wp.ac.impl.SvrSslCfgPort
Description: Configuration port for the application name. This parameter is currently ignored by the SvrSslCfg command.
Value: numeric
Example: none available
Default: 7223

wp.ac.impl.SvrSslCfgMode
Description: Configuration mode of the SvrSslCfg command. Currently, the only valid value is remote.
Value: remote
Example: none available
Default: remote

wp.ac.impl.PDPolicyServerList
Description: Defines host name, port, and priority combinations for your TAM Policy servers used when running SvrSslCfg.
Value: host:port:priority
Example: hosta.ibm.com:7135:1 or host1.ibm.com:7135:1, hostb.7135:2
Default: your.TAM.Policy.Server.hostname:7135:1

wp.ac.impl.PDAuthzServerList
Description: Defines host name, port, and priority combination for your TAM authorization servers.
Value: host:port:priority
Example: hosta.ibm.com:7136:1
Default: your.TAM.Authorization.Server.hostname:7136:1

wp.ac.impl.PDKeyPath
Description: Stores encryption keys used for the SSL communication between AMJRTE and Tivoli Access manager. This file is generated as a result of the SvrSslCfg command.
Value: none available
Example: none available
Default: ${WasHome}/java/jre/lib/pdperm.ks

1. 
   

WebSEAL junction parameters

1. 
   

wp.ac.impl.JunctionType
Description: The type of junction to be created in TAM.
Value: tcp ssl
Example: none available
Default: tcp

wp.ac.impl.JunctionPoint
Description: The WebSEAL junction point to the WebSphere Portal instance. In order to create a valid TAM junction, this property must begin with a / character.
Value: none available
Example: none available
Default: /wpsv61

wp.ac.impl.WebSealInstance
Description: Which WebSEAL instance to create the junction. You can view the different WebSEAL instances by issuing a server list from the pdadmin> command line.
Value: none available
Example: none available
Default: instance-webseald-yourhost.com

wp.ac.impl.TAICreds
Description: The headers inserted by WebSEAL that the TAI uses to identify the request as originating from WebSEAL. Inclusion of these headers is associated with the headers used by the WebSphere Application Server TAI to identify the request as one from WebSEAL. If you are configuring Portal to use TAM as an external authorization engine, you must include at least the iv-user and iv-creds headers.
Value: none available
Example: none available
Default: iv-user,iv-creds

wp.ac.impl.JunctionHost
Description: The backend server host name to supply to the junction create command
Value: none available
Example: none available
Default: ${WpsHostName}

wp.ac.impl.JunctionPort
Description: The backend server port to supply to the junction create command
Value: none available
Example: none available
Default: ${WpsHostPort}

1. #
   

WAS WebSEAL TAI parameters

1. #
   

wp.ac.impl.hostnames
Description: Optional parameter that sets the WebSEAL TAI's hostnames parameter. You should include the host name you provided when configuring the WebSEAL instance. The default behavior when configuring a WebSEAL instance is to use the network short name. For example, hosta.yourcompany.com may be represented as hosta. When the WebSEAL instance is configured and if any additional proxies are included, their host names must be added as well. Presence of a this parameters will cause the TAI to evaluate the VIA header and only handle those requests that contain one of the provided host name, and port combinations.
Value: This value is case-sensitive and may be a comma delimited list if more than one host name is provided.
Example: hosta.yourcompany.com or hosta
Default: no default

wp.ac.impl.ports
Description: Optional parameter that sets the WebSEAL TAI's ports parameter. You should include the WebSEAL ports in this comma delimited list. The default WebSEAL port is 443. Presence of a this parameters will cause the TAI to evaluate the VIA header and only handle those requests that contain one of the provided host name and port combinations.
Value: none available
Example: none available
Default: no default

wp.ac.impl.loginId
Description: When you create a TCP junction, this is WebSEAL identity representing the reverse proxy on every request. WebSphere Application Server will use this identity to establish the "trust" that is required to validate the WebSEAL iv-* headers. The password for this user should be set in the WebSEAL instance's webseald.conf on the basicauth-dummy-passwd property.
Value: none available
Example: none available
Default: wpsadmin

wp.ac.impl.BaUserName
Description: When you create an SSL junction, this is the WebSEAL identity representing the reverse proxy on every request. WebSphere Application Server will use this identity to establish the "trust" that is required to validate the WebSEAL iv-* headers.
Value: none available
Example: none available
Default: wpsadmin

wp.ac.impl.BaPassword
Description: When you create an SSL junction, you can provide a password to the identity representing the reverse proxy on every request. WebSphere Application Server will use this identity to establish the "trust" that is required to validate the WebSEAL iv-* headers.
Value: none available
Example: none available
Default: wpsadmin

wp.ac.impl.checkViaHeader
Description: You can configure TAI so that the via header can be ignored when validating trust for a request. Set this property to false if none of the hosts in the via header need to be trusted. When set to false you do not need to set the trusted host names and host ports properties. The only mandatory property to check when via header is false is com.ibm.websphere.security.webseal.loginId.
Value: true false
Example: none available
Default: false

wp.ac.impl.viaDepth
Description: A positive integer that specifies the number of source hosts in the via header to check for trust. By default, every host in the via header is checked, and if any host is not trusted, trust cannot be established. The via depth property is used when only some of the hosts in the via header have to be trusted. The setting indicates the number of hosts that are required to be trusted.
Value: positive integer
Example: none available
Default: 0

wp.ac.impl.ssoPwdExpiry
Description: After trust is established for a request, the single sign-on user password is cached, eliminating the need to have the TAI re-authenticate the single sign-on user with Tivoli Access Manager for every request. You can modify the cache timeout period by setting the single sign-on password expiry property to the required time in seconds. If the password expiry property is set to 0, the cached password never expires.
Value: time in seconds
Example: none available
Default: 600

wp.ac.impl.ignoreProxy
Description: This property can be used to tell the TAI to ignore proxies as trusted hosts. If set to true the comments field of the hosts entry in the via header is checked to determine if a host is a proxy. Remember that not all proxies insert comments in the via header indicating that they are proxies. If the checkViaHeader property is set to false, then the ignoreProxy property has no influence in establishing trust.
Value: true false
Example: none available
Default: false

1. #
   

Portal authorization parameters

1. #
   

wp.ac.impl.PDRoot
Description: Root objectspace entry in the TAM namespace. All Portal roles will be installed under this objectspace entry.
Value: none available
Example: none available
Default: /WPv61

wp.ac.impl.PDAction
Description: When the Tivoli Access Manager external authorization plugin is started, it will detect and, if necessary, create a custom action in Tivoli Access Manager. The combination of the action group and the action determines the TAM permission string required to assign membership to externalized Portal roles.
Value: none available
Example: none available
Default: m

wp.ac.impl.PDActionGroup
Description: When the Tivoli Access Manager external authorization plugin is started, it will detect and, if necessary, create a custom action group in Tivoli Access Manager. The combination of the action group and the action determines the TAM permission string required to assign membership to externalized Portal roles.
Value: none available
Example: none available
Default: [WP61]

wp.ac.impl.PDCreateAcl
Description: When Portal externalizes a role, it can automatically create and attach a TAM ACL granting membership to the user doing the role. If you select No,the TAM administrator will be responsible for creating TAM ACLs to allow access to Portal roles.
Value: true false
Example: none available
Default: true

1. #
   

Portal vault paramters

1. 
   

wp.ac.impl.vaultType
Description: New vault type identifier representing the Tivoli GSO lockbox vault.
Value: string
Example: none available
Default: AccessManager

wp.ac.impl.vaultProperties
Description: Defines a properties file to be used to configure the vault with TAM specific user and SSL connection information. This file will automatically be created in the wp_profile/shared/app/config subdirectory and populated by the ant task based on previous task execution.
Value: none available
Example: none available
Default: accessmanagervault.properties

wp.ac.impl.manageResources
Description: Determines if the portal credential vault or any custom portlet is allowed to create new resource objects in TAM. If you select false, your Tivoli administrator must define the accessible \ resources to associate users with using the Tivoli command line or GUI.
Value: true false
Example: none available
Default: true

wp.ac.impl.readOnly
Description: Determines if the portal credential vault or any custom portlet is allowed to modify the secrets stored in TAM. If you select "Read Only", the Tivoli administrator must change the credentials associated with resources using the Tivoli command line or GUI.
Value: true false
Example: none available
Default: false

1. #
   

Tivoli Access Manager - End

1. #
   

1. 
   

Netegrity SiteMinder

1. 
   

1. #
   

Portal/SiteMinder authorization parameters

1. 
   

wp.ac.impl.SMDomain
Description: SiteMinder Domain containing all externalized portal resources.
Value: none available
Example: none available
Default: WebSphere Portal v61

wp.ac.impl.SMScheme
Description: SiteMinder Authentication scheme object name to use when creating realms
Value: none available
Example: none available
Default: Basic

wp.ac.impl.SMAgent
Description: The SiteMinder custom or 4.x web agent created to allow communication between WebSphere Portal and SiteMinder.
Value: none available
Example: none available
Default: ReplaceWithYourSiteMinderAgentName

wp.ac.impl.SMAgentPwd
Description: Password for SiteMinder agent.
Value: none available
Example: none available
Default: ReplaceWithYourSiteMinderAgentPwd

wp.ac.impl.SMAgentGroup
Description: An externalized portal resource is assigned to a SiteMinder custom agent for SiteMinder isProtected and isAuthorized calls. In a non-cluster, the agent specified in the wp.ac.impl.SMAgent parameter is used. However, in a cluster, a common SiteMinder Agent Group must be specified to be assigned to the resource.
Value: none available
Example: none available
Default: no default

wp.ac.impl.SMAdminId
Description: SiteMinder administrator. This administrator must have a scope of System, as new SiteMinder domains and realms will be created. In addition, creation of the realms representing Portal roles, reference to the webagent, which also requires System scope.
Value: none available
Example: none available
Default: siteminder

wp.ac.impl.SMAdminPwd
Description: Password for the SiteMinder administrative user.
Value: none available
Example: none available
Default: ReplaceWithYourSiteMinderAdminPwd

wp.ac.impl.SMUserDir
Description: SiteMinder User Directory object referencing the LDAP server used for Portal users and groups.
Value: none available
Example: none available
Default: ReplaceWithYourSiteMinderUserDirectoryObject

wp.ac.impl.SMFailover
Description: Failover mode of Siteminder Policy Server. SMFailover must be set to true if more than 1 policy server is listed in the SMServers property below.
Value: true false
Example: none available
Default: false

wp.ac.impl.SMServers
Description: Comma delimited list of server for SiteMinder agent. Important: If your Policy Servers are listening on non-default ports (for example: not 44441,44442,44443), you must add the port property for each policy server manually in the ExternalAccessControlService.properties.
Value: none available
Example: none available
Default: your.Policy.Server.ipaddress

1. #
   

Netegrity SiteMinder - End

1. #
   
2. END WP.AC.IMPL PROPERTIES #
   

1. BEGIN PREREQ.WCM PROPERTIES #
   

PREREQ.WCM loaded from:
AIX: /usr/IBM/WebSphere/PortalServer/wcm/prereq.wcm/prereq.wcm.properties
i5/OS: /QIBM/UserData/WebSphere/PortalServer/wcm/prereq.wcm/prereq.wcm.properties
Linux, HP-UX, Solaris: /opt/IBM/WebSphere/PortalServer/wcm/prereq.wcm/prereq.wcm.properties
Windows: C:/IBM/wp615/WebSphere/PortalServer/wcm/prereq.wcm/prereq.wcm.properties

1. #
   

Web Content Management (WCM) Properties

1. ###
   

WcmAdminGroupId
Description: The group ID for the WCM Administrator group.
Value:
DEV (No security): WcmAdminGroupId=,o=default organization
IBM Directory Server: { cn=,cn=groups,dc=yourco,dc=com }
Domino: { cn=}
Active Directory: { cn=,cn=groups,dc=yourco,dc=com }
Active Directory AM: { cn=,cn=groups,dc=yourco,dc=com }
SunOne: { cn=,ou=groups,o=yourco.com }
Novell eDirectory { cn=,ou=groups,o=yourco.com }
Example: none available
Default: cn=wcmadmins,o=default organization

WcmAdminGroupCN
Description: The WCM administrative group ID.
Default: wcmadmins

WcmContentAuthorsGroupId
Description: The group ID for the WCM Administrator group.
Value:
DEV (No security): WcmContentAuthorsGroupId=,o=default organization
IBM Directory Server: { cn=,cn=groups,dc=yourco,dc=com }
Domino: { cn=}
Active Directory: { cn=,cn=groups,dc=yourco,dc=com }
Active Directory AM: { cn=,cn=groups,dc=yourco,dc=com }
SunOne: { cn=,ou=groups,o=yourco.com }
Novell eDirectory { cn=,ou=groups,o=yourco.com }
Example: none available
Default: CN=wcmContentAuthors

WcmContentAuthorsGroupCN
Description: The WCM administrative group ID.
Value: none available
Example: none available
Default: contentAuthors

1. 
   

Properties required for importing and exporting of migration data

1. 
   

WpsContentAdministrators=cn=wpsContentAdministrators,o=default organization
WpsDocReviewer=cn=wpsDocReviewer,o=default organization

1. END PREREQ.WCM PROPERTIES #
   

1. BEGIN WP.SITEM.CMD PROPERTIES #
   

WP.SITEM.CMD loaded from:
AIX: /usr/IBM/WebSphere/PortalServer/base/wp.sitem.cmd/wp.sitem.cmd.properties
i5/OS: /QIBM/UserData/WebSphere/PortalServer/base/wp.sitem.cmd/wp.sitem.cmd.properties
Linux, HP-UX, Solaris: /opt/IBM/WebSphere/PortalServer/base/wp.sitem.cmd/wp.sitem.cmd.properties
Windows: C:/IBM/wp615/WebSphere/PortalServer/base/wp.sitem.cmd/wp.sitem.cmd.properties

1. #
   

Basic Auth TAI settings

1. #
   

wp.sitem.cmd.BasicAuthEnabled
Description: This value defines whether the Basic Auth TAI is enabled or not.
Value: true false
Example: none available
Default: true

wp.sitem.cmd.BasicAuthRealm
Description: The HTTP basic authentication realm for TAI.
Value: none available
Example: none available
Default: WPS

wp.sitem.cmd.BasicAuthUseRegExp
Description: This value defines whether lists use regular expressions or not.
Value: true false
Example: none available
Default: false

wp.sitem.cmd.BasicAuthLoginTarget
Description: Target to execute to populate the Subject with portal specific Principals when logging on via the TAI.
Value: none available
Example: none available
Default: Portal_LTPA

wp.sitem.cmd.BasicAuthUserAgentBlackList
Description: List of user agents to not allow.
Value: none available
Example: none available
Default: AllAgentsAllowed

wp.sitem.cmd.BasicAuthUserAgentWhiteList
Description: List of user agents to allow to use the basic auth TAI.
Value: none available
Example: none available
Default: NoAgentSpecified

wp.sitem.cmd.BasicAuthUrlBlackList
Description: List of URIs this TAI will never handle.
Value: none available
Example: none available
Default: /${WpsContextRoot}/myportal*

wp.sitem.cmd.BasicAuthUrlWhiteList
Description: List of URIs that this TAI will handle.
Value: none available
Example: none available
Default: /${WpsContextRoot}/mycontenthandler*

1. END WP.SITEM.CMD PROPERTIES #
   

1. BEGIN WP.XML.CLIENT PROPERTIES #
   

WP.XML.CLIENT loaded from: /opt/IBM/WebSphere/PortalServer/base/wp.xml.client/wp.xml.client.properties
AIX: /usr/IBM/WebSphere/PortalServer/base/wp.xml.client/wp.xml.client.properties
i5/OS: /QIBM/UserData/WebSphere/PortalServer/base/wp.xml.client/wp.xml.client.properties
Linux, HP-UX, Solaris: /opt/IBM/WebSphere/PortalServer/base/wp.xml.client/wp.xml.client.properties
Windows: C:/IBM/wp615/WebSphere/PortalServer/base/wp.xml.client/wp.xml.client.properties

1. #
   

XMLAccess properties

1. #
   

XmlAccessHost
Description: The name of the local WebSphere Portal host. This parameter should not be necessary to modify.
Value: none available
Example: none available
Default: localhost

XmlAccessPort
Description: The port used by the XMLAccess configuration task to connect the XMLAccess server. Do not use this parameter to reconfigure the XmlAccessPort port. The value is set by the basic WebSphere Portal configuration task.
Value: none available
Example: none available
Default: 10040

XmlAccessProtocol
Description: The protocol used to connect to the XMLAccess server.
Value: http https
Example: none available
Default: http

1. END WP.XML.CLIENT PROPERTIES ###