Portal, Express Beta Version 6.1 Operating systems: i5/OS, Linux,Windows

Preparing for creation of databases

This section steps through mandatory preparation tasks prior to creating databases that are required by WebSphere Portal.

1. Preparing the Coded Character Set Identifier (CCSID) value prior to creating database names and schemas. Whether local or remote, a necessary preparation task is to change the Coded Character Set Identifier (CCSID) value to one that is supported by DB2 Universal Database for System i5. The default Coded Character Set Identifier (CCSID) #65535 is not supported by DB2 Universal Database for System i5, so it is essential to complete this task to change the 65535 CCSID value to a valid CCSID on the system where you run the database transfer tasks, regardless of whether the database is local or remote. You must also run this task on any remote database server machine. Complete all of the following steps to set a valid CCSID for every existing database administrator user profile.

   1. Query the current system value of CCSID by typing DSPSYSVAL SYSVAL(QCCSID). If the CCSID value shown is 65535 then continue with these steps. Otherwise these steps are not required.
   2. Type the following command, including the parentheses, once for every existing database administrator user profile, including the user ID currently logged on and running the installation:

      DSPUSRPRF USRPRF(usrprf)

      where usrprf is the database administrator user ID, for example, DB2ADMIN. This command displays the user's profile settings, including the Coded Character Set Identifier (CCSID) value that may need to change. If the value is *SYSVAL, *HEX, or 65535, you are finished with this step and can continue to the next step, which is to display job settings. Otherwise, you are finished with this CCSID section.
   3. Prior to running a job in any given session, type DSPJOB OPTION(*DFNA) and scroll to find the default coded character set identifier value used by the database administrator profile running jobs. Write down that value if it is not 65535.
   4. For the database administrator user profile to be used to run jobs, type in the following change user profile command and specify the value you wrote down in the previous step, or a CCSID value based on the language to be used, for example 037 for English. The value cannot be 65535:

      CHGUSRPRF USRPRF(usrprf) CCSID(ccsid-value)

   5. Log off the system for the profile changes to take effect.
   6. Log back on before attempting to run any database configuration tasks.
   7. Repeat these commands for every existing database administrator user profile on every portal system and every remote database server machine.
2. Preparing database domain property values prior to creating database names and schemas. Before you manually configure your database schemas, first edit your database domain properties files.

   1. Locate the following files and create a backup copy of each using the backup-main-cfg-file task before changing any values:

      • portal_server_root_user/config/wkplc.properties
      • portal_server_root_user/config/wkplc_comp.properties
      • portal_server_root_user/config/wkplc_dbtype.properties
   2. The WebSphere Portal Express database can be used to hold information for applications such as Document Manager, 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. For example:

      • release.DbName=*LOCAL/wpsdb
      • community.DbName=*LOCAL/wpsdb
      • customization.DbName=*LOCAL/wpsdb
      • jcr.DbName=*LOCAL/wpsdb
      • feedback.DbName=*LOCAL/wpsdb
      • likeminds.DbName=*LOCAL/wpsdb
      When you create a schema, use the following schema naming conventions on the i5/OS 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")
      • Invalid characters include:

        spaces	null
        *	"
        :	>
        <	|
        +	;
        '	?

        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 DB2 Universal Database for System i5 topic in the System i5 information center.

      • Do not change any settings other than those that are specified in these substeps.
      • If you are using a remote database, be sure to enter the values for the remote server.
      • Use / instead of \ for i5/OS.
      • 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_comp.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.
      • There might be additional database properties other than those listed here. Only change the properties within this table; skip all other properties.
      • Depending on which database domain has to be configured, the variable dbdomain may need to be replaced by:

        • release
        • customization
        • community
        • jcr
        • feedback
        • likeminds
   3. Use a text editor to open the properties files and enter the values that are appropriate for your environment. You can also modify each properties file locally on your System i5 system by typing the following on an OS/400 command line in a 5250 session:

      EDTF 'portal_server_root_user/config/property filename.properties'

      where property filename is either wkplc_comp, wkplc or wkplc_dbtype.

      Note: You must have a user profile on the System i5 server and must have at least *USE special authority to edit the properties file. Tips:

      • The steps for transferring data to another supported database section provides instructions for manually transferring data. 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.
      • A configuration template might exist to support these instructions. Refer to the wp_profile_root/ConfigEngine/helpers directory for available configuration templates. Use the configuration template to update the wkplc.properties, wkplc_comp.properties, and wkplc_dbtype.properties files, as described in the topic Configuration program, according to the property descriptions and recommended values provided. If you do not want to use a configuration template, follow the steps in this task.
      • If you are transferring from Oracle, the open_cursors setting should be set to 1500 by default. If you are using Java Content Repository, this value might need to be increased based on the table count in the Java Content Repository schema.
      • Be sure that DB2 is started by checking the service. If attempts to restart result in a logon failure message, then go to the DB2 properties and reenter the password.

      The following properties must be changed before creating a database name and schema on a local or remote System i5 server.

3. Use a text editor to open the properties file wkplc_comp.properties and modify the values to correspond to your environment.

   1. For dbdomain.DbType, type db2_iseries.
   2. For dbdomain.DbName, type the name of the WebSphere Portal Express domain database and schema. Note: This value is also the database element in the dbdomain.DbUrl property.
   3. For dbdomain.DbSchema, type the schema name of the database domain. Note: 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.
   4. For dbdomain.DataSourceName, type the name of the data source that WebSphere Portal Express uses to communicate with its databases.
   5. For dbdomain.DbUrl, type the database URL used to access the WebSphere Portal Express database with JDBC. The value must conform to the JDBC URL syntax specified by the database. Note: The database element of this value should match the value of DbName. Recommended value:

      • Type 2 driver: 2 (local only, non-clustered only): { jdbc:db2:*LOCAL/QWPS61 }
      • Type 4 driver: 4 (local or remote or clustered): { jdbc:as400:hostname/QWPS61 }
   6. For dbdomain.DbUser, type the user ID for the database administrator.
   7. For dbdomain.DbPassword, type the password for the database administrator.
   8. For dbdomain.DBA.DbUser, type the database administrator user ID for privileged access operations during creation of the database.
   9. For dbdomain.DBA.DbPassword, type the database administrator password for privileged access operations during creation of the database.
4. Save and close the file.
5. Update the following properties in the file wkplc_dbtype.properties.

   1. For db2_iseries.DbDriver, type the name of the class that SqlProcessor uses to import SQL files. Recommended value:

      • Type 2 driver: com.ibm.db2.jdbc.app.DB2Driver
      • Type 4 driver: com.ibm.as400.access.AS400JDBCDriver
   2. For db2_iseries.DbLibrary, type the directory and name of the .zip or .jar file that contains the JDBC driver class. Recommended value:

      • Type 2 driver: /QIBM/ProdData/Java400/ext/db2_classes.jar
      • Type 4 driver: /QIBM/ProdData/HTTP/Public/jt400/lib/jt400.jar
   3. For db2_iseries.JdbcProviderName, type the name of the JDBC provider that WebSphere Portal Express uses to communicate with its databases.

      Recommended value: wpdbJDBC_db2_iseries

   4. For db2_iseries.DbDriverType, type the of the driver type for the database. Recommended value:

      • Type 2 driver: 2 (local only, non-clustered only)
      • Type 4 driver: 4 (local or remote or clustered)
      wpdbJDBC_db2_iseries
6. Save and close the file.
7. Update the following property in the file wkplc.properties.

   1. For WasPassword, type the password for the WebSphere Application Server security authentication used in your environment.
8. Save and close the file.