Configure Personalization after installation

 

+
Search Tips   |   Advanced Search

 

 

Configure Personalization

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

Note that the WPSconfig scripts 'setup-pzn' and 'remove-pzn' are only supported when installing Personalization Server without WebSphere Portal as documented in the Information Center.

If you have installed WebSphere Portal, personalization is installed and configured by default. Executing 'setup-pzn' and/or 'remove-pzn' after WebSphere Portal has been installed is not supported in any way. This includes but is not limited to the following scenarios:

  • Installing a standalone full Portal instance
  • Installing an empty Portal
  • Running 'action-empty-portal' after installing a full Portal instance
  • Installing Portal in a managed node environment

The 'setup-pzn' and 'remove-pzn' were never intended to be executed in an environment with WebSphere Portal. If this happens, a complete reinstall may be required in order to regain full functionality.

To configure Personalization...

  1. Edit each of the following files...

  2. Uncomment and verify the following properties for the environment:

     

    WAS properties

    Property Value
    WasHome

    WAS install directory.

    Recommended: dir

    Default: /opt/WebSphere/AppServer

    WasUserHome

    Directory where WAS user data is created.

    Recommended: dir

    Default: /opt/WebSphere/AppServer

    WasUserid

    The user ID for WAS security authentication.

    Recommended: userid

    Default User Registry (CUR) value: wpsbind

    WasPassword

    The password for WAS security authentication.

    Recommended: password

    Default: none

    WpsInstallLocation

    The directory where WebSphere Portal is installed

    Recommended: portal_server_root

    Default: opt/WebSphere/PortalServer

    CellName

    The WAS cell to which the application server belongs.

    Recommended: cell

    Default: cell

    NodeName

    The node within the cell to which the WAS belongs (typically this value is the same as the host.name for the computer).

    Recommended: node

    Default: node

    ServerName

    The name of the application server where the Personalization enterprise application is deployed. This value must be unique among other application server names in the same cell.

    Recommended: WebSphere_Portal

    Default: server1

     

    Database domain properties

    For these properties, dbdomain will be replaced with the database domain you are configuring. Depending on which database domain has to be configured, dbdomain will be replaced by:

    • jcr
    • feedback
    • likeminds

    Property Value
    dbdomain.DbType The type of database used with Personalization.

    Recommended: db2

    Default: cloudscape

    dbdomain.DbUrl The JDBC URL to the WebSphere Portal database.

    Default: jdbc:db2j:wpsdb;create=true (Cloudscape )

    dbdomain.DbUser The user ID for the database administrator.

    For SQL Server and Oracle only, this value MUST be set to FEEDBACK, which corresponds to the user FEEDBACK in the SQL Server or Oracle database.

    Default: db2admin

    dbdomain.DbPassword

    The Feedback database user password.

    A value must be set for this property; it cannot be empty.

    Value type: Alphanumeric text string

    Default: ReplaceWithYourDbAdminPwd

    dbdomain.DbNameOnZos

    The name of the WebSphere Portal database on DB2 for z/OS.

    Notes:

    • Required for DB2 for z/OS only.

    • If you are running DB2 for z/OS as a remote database, set this property to the name of the remote WebSphere Portal database.

    Recommended: WPSTST02

    Default: WPSTST02

    dbdomain.DbTablespace The name of the Feedback database tablespace. Required for DB2 and z/OS.I

    This property is for Feedback and LikeMinds only.

    Recommended: wpsdbts

    Default: fdbk5dbs

     

    DB2Content Manager Runtime Edition Database properties

     

    Database type properties

    Property Value
    jcr.DbHost The hostname of the system hosting the DB2 Content Manager Runtime Edition database.

    Required for DB2 for z/OS and OS/390 only.

    Value type: Alphanumeric text string

    jcr.DbDomain The domain of the system hosting the DB2 Content Manager Runtime Edition database.

    Required for DB2 for z/OS and OS/390 only.

    Value type: Alphanumeric text string

    jcr.ZosDbPrefix Common prefix of Node Type database names for the DB2 Content Manager Runtime Edition database.

    Required for DB2 for z/OS and OS/390 only.

    Recommended: Set this value according to your own environment, to match the value used when executing the commands to create the database found in the file Creating the DB2 Content Manager Runtime Edition database.

    Default: ICM

    jcr.ZosDbMaxTables Maximum number of User Defined Tables to be stored in a particular Node Type DB in the DB2 Content Manager Runtime Edition database.

    Required for DB2 for z/OS and OS/390 only.

    Recommended: 400.

    Default: 400

    jcr.DbStorageGroup The storage group for the DB2 Content Manager Runtime Edition database.

    Required for DB2 for z/OS and OS/390 only.

    Recommended: Set this value according to your own environment, to match the value used when executing the commands to create the database found in the file Creating the DB2 Content Manager Runtime Edition database.

    Default: WPSSG

    jcr.DbVolumes The volumes for the DB2 Content Manager Runtime Edition database.

    Required for DB2 for z/OS and OS/390 only.

    Recommended: Set this value according to your own environment, to match the value used when executing the commands to create the database found in the file Creating the DB2 Content Manager Runtime Edition database.

    Default: *

    jcr.DbVcat The VCAT for the DB2 Content Manager Runtime Edition database.

    Required for DB2 for z/OS and OS/390 only.

    Recommended: Set this value according to your own environment, to match the value used when executing the commands to create the database found in the file Creating the DB2 Content Manager Runtime Edition database.

    Default: DSN810

    jcr.Db4KBufferPoolName The 4K bufferpool name for the DB2 Content Manager Runtime Edition database.

    Required for DB2 for z/OS and OS/390 only.

    Recommended: Set this value according to your own environment, to match the value used when executing the commands to create the database found in the file Creating the DB2 Content Manager Runtime Edition database.

    Default: BP0

    jcr.Db32KBufferPoolName The 32K bufferpool name for the DB2 Content Manager Runtime Edition database.

    Required for DB2 for z/OS and OS/390 only.

    Recommended: Set this value according to your own environment, to match the value used when executing the commands to create the database found in the file Creating the DB2 Content Manager Runtime Edition database.

    Default: BP32K

    jcr.DbPort Port number of the DB2 Content Manager Runtime Edition database, if not on the local system (required for Driver Type 4 only).

    Required for DB2 for z/OS and OS/390 only.

    Recommended: Set this value according to your own environment.

    Default: 446

    jcr.DbSaPassword The SQL Server System Administrator password.

    Required for SQL Server only.

    Default: ReplaceWithYourDbAdminPwd

    For these properties, dbtype will be replaced with the database domain you are configuring. Depending on which database domain has to be configured, dbtype will be replaced by:

    • cloudscape
    • db2
    • oracle
    • sqlserver
    • db2_zos

    Property Value
    dbtype.DbDriver

    The Java class name for the JDBC provider that Personalization uses to communicate with its databases.

    Recommended: com.ibm.db2.jdbc.app.DB2Driver

    Default: com.ibm.db2.jdbc.app.DB2Driver (Cloudscape )

    dbtype.DbLibrary

    The fully qualified directory path name where the classes for the JDBC provider are located.

    Recommended: SQLLIB/java/db2java.zip

    Default: portal_server_root /shared/app/cloudscape/db2j.jar, where portal_server_root is the Portal installation directory. (Cloudscape )

  3. Save the file.

  4. Enter the following commands to run the appropriate configuration tasks:

    Check the output for any error messages before proceeding with the next task. If any of the configuration tasks fail, verify the values in the wpconfig.properties, wpconfig_dbdomain.properties, and wpconfig_dbtype.properties files.

    • UNIX:

      ./WPSconfig.sh setup-pzn -DWasPassword=password -DFeedbackDbPassword=password

    • Windows:

      WPSconfig.bat setup-pzn -DWasPassword=password -DFeedbackDbPassword=password

    • i5/OS:

      WPSconfig.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 is installed; for example, pzn_profile.

    If the passwords were set in the above property files, they do not need to be entered into the command line.