IBM i clustered server: Modify DB2 for IBM i database properties
Modify wkplc.properties, wkplc_dbdomain.properties, and wkplc_dbtype.properties before running tasks to create databases, create users, or transfer data.
- The WebSphere Portal database can be used to hold information for applications such as Personalization (Feedback) and LikeMinds. Use similar naming conventions for property values such as release.DbName. Here are some examples:
- release.DbName=hostname/WP70REL
- community.DbName=hostname/WP70COM
- customization.DbName=hostname/WP70CUS
- jcr.DbName=hostname/WP70JCR
- feedback.DbName=hostname/WP70FBK
- likeminds.DbName=hostname/WP70LKM
- If you are using a remote database, enter the values for the remote server.
- Regardless of the OS, use a forward slash (/) instead of a backslash (/) in the property files for file system paths.
- Property files provide default values that may not be correct for the database that you are using. Enter values in accordance with the database management system that you are using.
- There might be additional database properties other than those listed here. Only change the properties within this task and skip all other properties.
- Some values, shown here in italics, might need to be modified to specific environment.
- Password considerations: For security reasons, you should not store passwords in wkplc.properties, wkplc_dbdomain.properties, and wkplc_dbtype.properties. It is recommended that you edit each of the properties files prior to running a configuration task, inserting the passwords needed for that task. Then, after the task has run, you should delete all passwords from each file.
- The recommended value listed for each property represents the specific information that is required to configure WebSphere Portal to target database.
- Depending on which database domain has to be configured, replace dbdomain with:
- release
- customization
- community
- jcr
- feedback
- likeminds
- The values for at least one of the following properties must be unique for the release, customization, community, and JCR domains:
- dbdomain.DbName
- dbdomain.DbUrl
- dbdomain.DbSchema
- If you use the same values for all three properties across the release, customization, community, and JCR domains, the database-transfer task fails due to ambiguous database object names.
- If DbUser, DbUrl, and DbPassword are not the same across domains, the value for DataSourceName must differ from the DataSourceName of the other domains. In other words, this value must be unique for the database domain.
- When you create a schema, use the following schema naming conventions on the IBMi system:
The default schema names may be used with the product.
- Length cannot exceed 10 characters
- All alphanumerical characters are allowed ( "A" through "Z" and "1" through "0")
- The following characters are invalid:
- spaces
- null values
- asterisk (*)
- quotation marks (")
- colon (:)
- greater than symbol (>)
- less than symbol (<)
- vertical bar (|)
- plus sign (+)
- semicolon (;)
- single quotation mark (')
- question mark (?)
Do not use a schema name which already exists on the local or remote system. Follow the documentation of the target database management system in order to define a valid schema name as restrictions apply. Note that the Create WebSphere Portal wizard will automatically check schema names for you.
Refer to the DB2Universal Database for System i5content in the System i5 information center.
- Create backups:
- WP_PROFILE/ConfigEngine/properties/wkplc.properties
- WP_PROFILE/ConfigEngine/properties/wkplc_dbdomain.properties
- WP_PROFILE/ConfigEngine/properties/wkplc_dbtype.properties
- If you are transferring from a database other than Derby: WP_PROFILE/ConfigEngine/properties/wkplc_sourceDb.properties
Default values are listed in these files. Unless otherwise noted, all values are of type alphanumeric text string. Print out the steps below for reference before modifying the properties files. Make sure to enter the appropriate values for each instance of each property. In wkplc_dbdomain.properties, most properties are repeated for each domain.
- Edit properties files and enter the values that are appropriate for environment. You can also modify each properties file locally on System i5 system by typing the following on an OS/400 command line in a 5250 session:
This step only applies when WebSphere Portal is installed on IBM i, and you are transferring to IBM DB2 for i.
EDTF 'WP_PROFILE/ConfigEngine/properties/property filename.properties'where property filename is wkplc_dbdomain, wkplc, or wkplc_dbtype. You must have a user profile on the IBM i server and must have at least *USE special authority to edit the properties file.
Instead of performing the following steps, you can use the configuration wizard, which is a graphical user interface, to transfer data to another supported database.
Properties must be changed before creating a database name and schema on a local or remote IBM i server.
- Edit wkplc_dbdomain.properties
- dbdomain.DbType=db2_iseries
- dbdomain.DbName=domain_db_name
This value is also the database element in the dbdomain.DbUrl property.
- dbdomain.DbSchema=domain_schema_name
- dbdomain.DataSourceName=data_source_name
Do not use the following reserved words:
releaseDS
communityDS
customizationDS
jcrDS
lmdbDSfeedback
- dbdomain.DbUrl=jdbc_db_url
The connection property metadata source=1 must be specified for databases running on systems older than IBM i V7R1.
- WebSphere Portal is installed on IBM i and you transferring data remotely or locally to IBM DB2 for i:
dbdomain.DbUrl="jdbc:as400:daisy.mycorp.com/WPDBREL;metadata source=1"
- WebSphere Portal is installed on Windows and you transferring data remotely to IBM DB2 for i:
dbdomain.DbUrl="jdbc:as400:daisy.mycorp.com/WPDBREL;metadata source=1"
- WebSphere Portal is installed on a UNIX platform, and you are transferring data to IBM DB2 for i:
dbdomain.DbUrl="jdbc:as400:daisy.mycorp.com/WPDBREL;metadata source=1;prompt=false"
If the X11 DISPLAY is set and active, do not add the ;prompt=false to the URL.
The database element of this value should match the value of DbName.
- dbdomain.DbUser = database configuration user.
- dbdomain.DbPassword = password for database configuration user.
- dbdomain.DbConfigRoleName = group for database configuration users
Database rights are granted to this group instead of individuals. The user specified for dbdomain.DbUser must be assigned to this group.
- Optional. For dbdomain.DbRuntimeUser, type the user ID of the database user that should be used by WebSphere Portal to connect to the database at runtime. If no value is specified for this setting, the database configuration user will be used to connect to the databases at runtime.
- If dbdomain.DbRuntimeUser is specified, set dbdomain.DbRuntimePassword to be the password of the runtime database user.
- For dbdomain.DbRuntimeRoleName, type the name of the group for database runtime users
Database rights are granted to this group instead of individuals. The user specified for dbdomain.DbRuntimeUser must be assigned to this group.
- Optional. For dbdomain.DBA.DbUser, type the database administrator user ID for privileged access operations during database creation. If not required, you can accept the default value or leave blank.
- Optional. For dbdomain.DBA.DbPassword, database administrator password for privileged access operations during database creation. If not required, you can accept the default value or leave blank.
- Save and close the file.
- Update the following properties in wkplc_dbtype.properties.
You must download the jt400.jar file prior to database transfer.
- db2_iseries.DbDriver = name of the JDBC driver class
- db2_iseries.DbLibrary = path to JDBC .zip or .jar file
- db2_iseries.JdbcProviderName = JDBC provider
- db2_iseries.DbDriverType = driver type for the database
- Save and close the file.
- Update the WasPassword value in wkplc.properties. Password for the WAS security authentication used in environment.
- Save and close the file.
Parent
IBM i clustered server: Prepare DB2 for IBM i
Next topic
IBM i clustered server: Create DB2 for IBM i user profiles