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

Configuring Personalization after installation

If you chose not to configure Personalization during installation, manually configure it before you can use it.

1. Locate in the following files and create a backup copy of each before changing any values:

   • wp_profile_root/ConfigEngine/properties/wkplc.properties
   • wp_profile_root/ConfigEngine/properties/wkplc_comp.properties
   • wp_profile_root/ConfigEngine/properties/wkplc_dbtype.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_comp.properties, most properties are repeated for each domain

   Working with properties files:

   • The WebSphere Portal Express 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, jcr.DbName, feedback.DbName, and likeminds.DbName. For example:

     • release.DbName=wpsdb
     • jcr.DbName=jcrdb
     • feedback.DbName=fdbkdb
     • likeminds.DbName=lkmddb
   • If you are using a remote database, enter the values for the remote server.
   • Use forward slash (/) instead of backslash (\).
   • There might be additional database properties other than those listed here. Only change the properties within this task and skip all other properties.
   • 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.DbType
     • dbdomain.DbName
     • dbdomain.DbUrl
     • dbdomain.DbSchema
     If you use the same values for all four properties across the release, customization, community, and JCR domains, the database-transfer task fails because of 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.
2. 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 the name of the database used.
   2. 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.
   3. For dbdomain.DbUser, type the user ID for the database administrator.
   4. For dbdomain.DbPassword, type the password for the database administrator.
   5. For dbdomain.DbNameOnZos, type the name of the WebSphere Portal Express database on DB2 for z/OS. Note:

      • If running DB2 for z/OS as a remote database, set the value to the name of the remote database for the domain.
      • If WebSphere Portal Express is running on z/OS with DB2 for z/OS, set the value equal to the value of DbName.
   6. For dbdomain.DbTablespace, type the name of the DB2 for z/OS tablespace.
3. Save and close the file.
4. Update the following properties in the file wkplc_dbtype.properties.

   1. For dbtype.DbDriver, type the name of the JDBC driver class.
   2. For dbtype.DbLibrary, type the directory and name of the .zip or .jar file that contains the JDBC driver class.
5. Save and close the file.
6. 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.
7. Save and close the file.
8. Enter the following command to run the configuration task:

   • Linux: ./ConfigEngine.sh setup-pzn -DWasPassword=password -DFeedbackDbPassword=password
   • Windows: ConfigEngine.bat setup-pzn -DWasPassword=password -DFeedbackDbPassword=password
   • i5/OS: ConfigEngine.sh -profileName profile_root setup-pzn-iseries -DWasPassword=password -DFeedbackDbPassword=password

   where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal Express is installed; for example, pzn_profile.