Transferring data to IBM DB2 for i from a non-default database
Learn how to modify the wkplc.properties, wkplc_dbdomain.properties, wkplc_dbtype.properties, and wkplc_sourceDb.properties files to work with your database when transferring data to DB2® from a database other than the default database. Modify these property files before running tasks to create databases, create users, or transfer data.
About this task
This topic replaces the Modifying database properties topic in the sequence of tasks you need to perform when configuring your database. After completing the steps in this topic, refer to the topics following the Modifying database properties topic for your configuration scenario.
Working with properties files:
- The WebSphere® Portal Express® database
can be used to hold information for applications such as Personalization
(Feedback) and LikeMinds. To prepare the database to hold such application
information, you should use similar naming conventions for property
values such as release.DbName. Here are some
examples:
- release.DbName=hostname/WP80REL
- community.DbName=hostname/WP80COM
- customization.DbName=hostname/WP80CUS
- jcr.DbName=hostname/WP80JCR
- feedback.DbName=hostname/WP80FBK
- likeminds.DbName=hostname/WP80LKM
- If you are using a remote database, enter the values for the remote server.
- Regardless of the operating system, 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 your specific environment.
- Password considerations: For security reasons, you should not store passwords in the wkplc.properties, wkplc_dbdomain.properties, and wkplc_dbtype.properties files. 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 Express to your 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 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, you must use the following schema naming
conventions on the IBM® i system: Note: 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 (?)
Notes:- Make sure you know what valid schema names are and 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 Express wizard will automatically check schema names for you.
- For more information on database and schema naming conventions, refer to the DB2 Universal Database for System i5® content in the System i5 information center.