Install the Personalization Server

Install the Personalization Server

+

Search Tips | Advanced Search

This section describes the steps required to install and configure the Portal Personalization Server on a machine without IBM WebSphere Portal. The Personalization Server is installed by default with WebSphere Portal, so if you have done a customary Portal install, you already have the Personalization Server installed.
The Personalization Server is not supported on iSeries as a standalone server; Personalization is only supported on iSeries when installed with Portal.
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.

Install the Personalization Server
Automate Installation
Configure the Personalization Server after installation
Verify the Personalization Server after installation
Uninstall the Personalization Server

Password considerations: For security reasons, you should not store passwords in the wpconfig.properties file. IBM recommends that you edit the wpconfig.properties 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 the wpconfig.properties file.
Alternatively, we can specify the password on the command line using the following syntax:

WPSconfig.{sh|bat} task_name -Dpassword_property_key=password_value

As with other properties, each password property must have the -D prefix and be set equal to (=) a value. If you have multiple properties in a single command, use a space character between each -Dproperty=value setting.

Install the Personalization Server

To install the Personalization Server, complete the following steps:

Ensure that the machine where you are installing the Personalization Server meets the appropriate prerequisites.

Perform this step only if you are installing on UNIX and intend to store Personalization data in a DB2 database. Use the following steps to export the db2instance environment in the profile:

In our.bashrc,.dshrc, or.profile file, add:

if [ -f /home/db2inst1/sqllib/db2profile ]; then ./home/db2inst1/sqllib/db2profile; fi

...where db2inst1 represents the database instance and db2profile represents the user profile.

Reopen all the shells

Run the env command to verify that the environment has set the IBM DB2 Universal Database Enterprise Server Edition profile environment variables, such as DB2INSTANCE=db2inst1, where db2inst1 represents the database instance.

Insert the disc containing the Personalization component into the CD-ROM drive, and launch the installation program. Open a command prompt to the PZN directory and enter one of the following commands, depending on the operating system:

Windows pzninstallwin.exe
AIX pzninstallaix.bin
Linux pzninstalllin.bin
Linux on zSeries pzninstalllin390.bin
Linux on POWER pzninstalllinppc.bin
Linux on POWER is a term used to refer to IBM system product lines including IBM iSeries, pSeries, BladeCenter JS20 and OpenPower hardware that are based on IBM Power Architecture technology and run the same Linux distributions from Red Hat and Novell SUSE.
Solaris pzninstallsol.bin
HP-UX pzninstallhpux.bin

The welcome panel is displayed.

Enter the path where you want the Personalization Server installed. Click Next.

Select Yes, configure features. Although we can choose to manually configure the features you select after they are installed, it is recommended that you allow the component installer to configure the features during installation.

Click Next to display the list of features we can install.

Select from Personalization, LikeMinds, and Feedback and click Next.

Enter the path where IBM WAS is installed and click Next.

Select the profile you are installing to.

Enter the following information for WAS :

Cell to install to The cell to which the Personalization Server will be installed.
Node to install to The WAS node to which the Personalization Server will be installed. Typically this value is the same as host.name of the machine where you are installing the Personalization Server.
Application server to install to The name of the application server to which you are installing. For example, server1.
Virtual host The name of the host for which Personalization will be configured.
Is WAS security enabled Specify whether security is enabled on WAS.

Click Next.

If you indicated that security was enabled, enter the WAS administrator ID and password, and click Next. Otherwise continue to the next step.

Enter the following information for the DB2 Content Manager database required by Personalization.

Database type The database type used for DB2 Content Manager database.
Database host Hostname (only) of remote system hosting the DB2 Content Manager database.
Database port The listening port of the database.
Microsoft SQL Server Enterprise Edition and Oracle Enterprise Edition only.
Database name The name of the DB2 Content Manager database.
If you are installing on a non-Windows platform to a DB2 database, fill in the TCPIP alias with which the database is cataloged, rather than the name of the physical database.
This value should also appear as the database element in Database URL field.
Database user ID The user ID of the administrator for the database.
Not required if Cloudscape was chosen as the database type.
Database user password The password for the administrator.
Not required if Cloudscape was chosen as the database type.
Database URL The database URL used to access the jcrdb database through JDBC.
Conforms to standard JDBC URL syntax. For example, for DB2 you might use jdbc:db2:jcrdb.
Database Driver The JDBC Driver which is used for JDBC to connect to the database.
Location of Database driver The directory and name of the zip file containing the JDBC driver classes.

If you selected IBM DB2 Universal Database for z/OS as the database type, enter the following information, and click Next. Otherwise, skip this step.

JcrDbNameOnZos The name of the remote DB2 Content Manager database for IBM DB2 Universal Database for z/OS only.
JcrDbTablespace The name of the DB2 Content Manager database table space.

If you selected DB2 as the database type and are installing on a UNIX system, enter the following information, and click Next. Otherwise, skip this step.

JcrXDbName The name of the WebSphere Portal database for the DB2 Content Manager database.
JcrDbNode The node for the database.

Enter the following information for the Feedback database. Note that the DB2 Content Manager database and the Feedback database are expected to have the same database type. Consequently, some field values cannot be edited.

Database name The name of the Feedback database.
Database user ID The user ID of the administrator for the database.
Database user password The password for the administrator.
Schema name The schema to be used for the creation of resources in this database.
Database URL The database URL used to access the Feedback database through JDBC. Conforms to standard JDBC URL syntax. For example, for DB2 you might use jdbc:db2:fbkdb.

Click Next.

If you selected IBM DB2 Universal Database for z/OS as the database type, enter the following information, and click Next. Otherwise, skip this step.

FeedbackDbNameOnZos The name of the remote Feedback database for IBM DB2 Universal Database for z/OS only.
FeedbackDbTablespace The name of the Feedback database table space.

If you selected DB2 as the database type and are installing on a UNIX system, enter the following information, and click Next. Otherwise, skip this step.

FeedbackXDbName The name of the Feedback database.
FeedbackDbNode The node for the Feedback database.

Enter the following information for the Likeminds database. Note that the DB2 Content Manager database required by Personalization and the Likeminds database are expected to have the same database type. Consequently, some field values cannot be edited.

Database name The name of the Likeminds database.
Database user ID The user ID of the administrator for the database.
Database user password The password for the administrator.
Schema name The schema to be used for the creation of resources in this database.
Database URL The database URL used to access the Likeminds database through JDBC. This value conforms to standard JDBC URL syntax. For example, for DB2 you might use jdbc:db2:lmdb.

Click Next.

If you selected IBM DB2 Universal Database for z/OS as our database type, enter the following information, and click Next. Otherwise, skip this step.

LikemindsDbNameOnZos The name of the remote Likeminds database for IBM DB2 Universal Database for z/OS only.
LikemindsDbTablespace The name of the Likeminds database table space.

If you selected DB2 as our database type and are installing on a UNIX system, enter the following information, and click Next. Otherwise, skip this step

LikemindsXDbName The name of the Likeminds database.
LikemindsDbNode The node for the Likeminds database.

If you are using a local DB2 database, Select Yes to create the database during the installation, and click Next.

Verify the components to be installed and click Next. The installation program begins installing the selected components. Unless you selected otherwise previously, the components will be automatically configured. Throughout the installation and configuration process, the installation program displays progress indicators for each component.

When the installation is finished, the installation program displays a confirmation panel.

Click Finish to close the component installer.

Automating Installation

When running the Personalization Runtime installer, a response file is not created by default like it is for WebSphere Portal. To create a response file that can be used for a silent install, use the install option...
-options-record filename

To use it for the install use -options filename like the WebSphere Portal install.
The Personalization without WebSphere Portal is not supported for i5/OS.

Configure the Personalization Server after installation

If you configured the Personalization server during install and the configuration was successful, you do NOT need to perform the following steps.
If you chose not to configure the Personalization Server during installation, manually configure it before we can use it.
To configure the Personalization Server, do the following:

Edit...

portal_server_root/config/wpconfig.properties
pzn_root/config/wpconfig_dbdomain.properties
pzn_root/config/wpconfig_dbtype.properties files

...and uncomment the properties for the environment.

Save the file.

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 -Dfeedback.DbPassword=password

Windows:
WPSconfig.bat setup-pzn -DWasPassword=password -Dfeedback.DbPassword=password

If you wish also to configure Likeminds Recommendation Engine, follow the instructions at Configure LikeMinds support for Personalization

Verify the Personalization Server

To verify that the Personalization Server is properly installed and running on the machine, from a command prompt, run the following command:

UNIX:

./WPSconfig.sh validate-pzn -DWasPassword=password -Dfeedback.DbPassword=password

Windows:
WPSconfig.bat validate-pzn -DWasPassword=password -Dfeedback.DbPassword=password

Uninstall the Personalization Server

To uninstall the Personalization Server, complete the following steps:

Uninstalling the Personalization Server can only be performed when Personalization server is installed without WebSphere Portal. If Personalization is installed with WebSphere Portal, it can only be uninstalled when WebSphere Portal is uninstalled.

Launch the uninstallation program by doing one of the following:

UNIX:
From a command prompt, run the following command:
java -cp pzn_root/uninst/pznuninstall.jar run

Windows:
Select Personalization from the Add/Remove Programs window in the Control Panel.

After you have launched the uninstall program, do the following:

Select the language for the uninstall, and click OK. The welcome panel is displayed.

Click Next to display the components to be uninstalled.

Click Next to begin the uninstall process. When the uninstall program finishes, the program displays a confirmation panel.

Click Finish to close the uninstall program.

Some temporary files and directories may remain after Personalization Server is uninstalled. These files may be removed.

Windows	pzninstallwin.exe
AIX	pzninstallaix.bin
Linux	pzninstalllin.bin
Linux on zSeries	pzninstalllin390.bin
Linux on POWER	pzninstalllinppc.bin Linux on POWER is a term used to refer to IBM system product lines including IBM iSeries, pSeries, BladeCenter JS20 and OpenPower hardware that are based on IBM Power Architecture technology and run the same Linux distributions from Red Hat and Novell SUSE.
Solaris	pzninstallsol.bin
HP-UX	pzninstallhpux.bin

Cell to install to	The cell to which the Personalization Server will be installed.
Node to install to	The WAS node to which the Personalization Server will be installed. Typically this value is the same as host.name of the machine where you are installing the Personalization Server.
Application server to install to	The name of the application server to which you are installing. For example, server1.
Virtual host	The name of the host for which Personalization will be configured.
Is WAS security enabled	Specify whether security is enabled on WAS.

Database type	The database type used for DB2 Content Manager database.
Database host	Hostname (only) of remote system hosting the DB2 Content Manager database.
Database port	The listening port of the database. Microsoft SQL Server Enterprise Edition and Oracle Enterprise Edition only.
Database name	The name of the DB2 Content Manager database. If you are installing on a non-Windows platform to a DB2 database, fill in the TCPIP alias with which the database is cataloged, rather than the name of the physical database. This value should also appear as the database element in Database URL field.
Database user ID	The user ID of the administrator for the database. Not required if Cloudscape was chosen as the database type.
Database user password	The password for the administrator. Not required if Cloudscape was chosen as the database type.
Database URL	The database URL used to access the jcrdb database through JDBC. Conforms to standard JDBC URL syntax. For example, for DB2 you might use jdbc:db2:jcrdb.
Database Driver	The JDBC Driver which is used for JDBC to connect to the database.
Location of Database driver	The directory and name of the zip file containing the JDBC driver classes.

JcrDbNameOnZos	The name of the remote DB2 Content Manager database for IBM DB2 Universal Database for z/OS only.
JcrDbTablespace	The name of the DB2 Content Manager database table space.

JcrXDbName	The name of the WebSphere Portal database for the DB2 Content Manager database.
JcrDbNode	The node for the database.

Database name	The name of the Feedback database.
Database user ID	The user ID of the administrator for the database.
Database user password	The password for the administrator.
Schema name	The schema to be used for the creation of resources in this database.
Database URL	The database URL used to access the Feedback database through JDBC. Conforms to standard JDBC URL syntax. For example, for DB2 you might use jdbc:db2:fbkdb.

FeedbackDbNameOnZos	The name of the remote Feedback database for IBM DB2 Universal Database for z/OS only.
FeedbackDbTablespace	The name of the Feedback database table space.

FeedbackXDbName	The name of the Feedback database.
FeedbackDbNode	The node for the Feedback database.

Database name	The name of the Likeminds database.
Database user ID	The user ID of the administrator for the database.
Database user password	The password for the administrator.
Schema name	The schema to be used for the creation of resources in this database.
Database URL	The database URL used to access the Likeminds database through JDBC. This value conforms to standard JDBC URL syntax. For example, for DB2 you might use jdbc:db2:lmdb.

LikemindsDbNameOnZos	The name of the remote Likeminds database for IBM DB2 Universal Database for z/OS only.
LikemindsDbTablespace	The name of the Likeminds database table space.

LikemindsXDbName	The name of the Likeminds database.
LikemindsDbNode	The node for the Likeminds database.