Install a Personalization Server cluster

 

+

Search Tips   |   Advanced Search

 

  1. Preliminary information and procedures
  2. Install Personalization Server
  3. Set up the cluster
  4. Uninstal Personalization Server

 

Overview

The Personalization Server enables you to...

  • Deploy applications that have been developed with WebSphere Portal
  • Serve personalized content to users
  • Record site metrics

...without requiring that WebSphere Portal also be present on the machine

While rules may be executed from any WebSphere Application Server (WAS) installation, a full WebSphere Portal installation is still required as a workspace for authoring rules and campaigns.

This section explains how to install Personalization Server in a clustered environment using WAS and IBM WAS Network Deployment (ND).

Cells, which are sets of nodes, clusters, applications and additional configuration, are maintained by a central deployment manager that is responsible for maintaining the status of each node in the cell.

Refer to the appropriate information center for information:

The cluster environment setup in the following sections is described according to the following topology:

DM01 WAS ND node
WP01 on NODE01 First Personalization Server in the cell
WP02 on NODE02 Second Personalization Server in the cell (horizontal scaling only)

You will install each Personalization Server instance on a dedicated WAS profile, bring it under deployment manager control if it is not already federated into a cell, and finally add it to the cluster after it is completely configured.

 

Install Personalization Server

When install Personalization Server into a cluster environment, we can approach the installation process in two ways:

It is not necessary to use the same approach for every node when install Personalization Server on multiple nodes in a cell. Select an appropriate approach for each node, according to whether the node is federated into a cell.

 

Use the addNode command

Before running the addNode command, update the addNode script to increase the maximum heap size for Java commands.

To add a node to the deployment manager cell, from the server system to be added, execute...

    was_profile_root/bin/addNode.sh dmgr_host dmgr_port -username admin_user_id -password admin_password [-includeapps] [-trace] [-ulimit]

i5/OS:

    app_server_root/bin/addNode dmgr_host dmgr_port -profileName profile_root -username admin_user_id -password admin_password -startingport startingport [-includeapps] [-trace] [-ulimit]

profile_root is the name of the WAS profile where WebSphere Portal is installed; for example, wp_profile

startingport is the port number used as the base port number for all node agent and JMS server ports created during the running of the addNode command.

where:

was_profile_root profile directory on WAS.
dmgr_host deployment manager host name.
dmgr_port deployment manager SOAP connector-address. The default value is 8879.
admin_user_id WAS administrative user name. This parameter is optional but is required if security is enabled.
admin_password administrative user password. This parameter is optional but is required if security is enabled.

Parameters:

-includeapps

The -includeapps parameter is optional. This parameter should only be used if there are enterprise applications already installed on this node that need to be added to the deployment manager's master configuration. If you do not specify this flag, any application servers that are defined on this node will be included in the deployment manager's configuration, but they might not be functional without their corresponding enterprise applications. If the application already exists in the cell, a warning is generated and the application is not installed into the cell.

-trace

The -trace parameter is optional. This parameter generates trace information that is stored in the addNode.log file for debugging purposes.

-ulimit

The -ulimit parameter is optional and is used to specify the number of supported open files. The default setting is typically sufficient for most applications. If the value is set too low, one of the following error message might occur:

  • File open error
  • Memory allocation error
  • Connection establishment error

After the addNode command completes successfully, the cell name of the configuration on the node that you added is changed from the base cell name to the deployment manager cell name.

Refer to the appropriate WAS ND information center for details on the addNode command:

 

Approach 1. Install Personalization Server on a federated WAS node

This section describes how to federate two separate WAS nodes into a cell that is managed by the deployment manager on the WAS ND system (DM01) and then install an instance of Personalization Server (WP01 and WP02) on each of those nodes. Below are detailed steps for implementing this scenario.

When you remove a node from a managed cell, the application server on that node reverts to the state it had at the time it was originally federated.

Consequently, if you install Personalization Server on a node that has already been federated into a cell and then later remove that node from the cell, Personalization Server will not be usable on the resulting stand-alone server.

i5/OS limitation: WebSphere Portal installation is not supported on a federated node in an i5/OS environment. If you are building a WebSphere Portal cluster on i5/OS, use the instructions in the following section to install WebSphere Portal and then federate the node:

Approach 2. Install Personalization Server on a separate WAS node that is not managed by a deployment manager

 

Federate the WAS nodes

  1. Prerequisites for federating the WAS nodes (NODE01 and NODE02):

    • WAS must be installed and operational on each node.

    • WAS ND must be installed on DM01 to the same release level as the profiles of WAS.

    • If security is enabled, the same security settings must be specified for the WAS ND system and for each WAS node, or each Application Server node must not have global security enabled. When the node is federated, the deployment manager's security settings will propagate to the node.

  2. Add NODE01 to the deployment manager (DM01) cell by entering the addNode command. Specify the -includeapps parameter only if there are enterprise applications already installed on this node that need to be added to the deployment manager's master configuration.

  3. Repeat the previous step for NODE02, if you are setting up a horizontal cluster. This step is not required if you are using vertical scaling.

  4. If any application servers and enterprise applications were already installed before you added the node to the cell, verify that they still function properly.

    The Personalization install accesses the node to which it is install via localhost. Verify that your virtual hosts are configured in such a way that we can access the node applications through localhost before continuing.

  5. Refer to 3: Setting up the cluster if you are ready to set up the cluster.

 

Install WP01

  1. Prerequisites for installation of first Personalization Server instance (WP01):

    • The WAS nodes must be installed with any fix packs or interim fixes required by Personalization Server. The nodes must also be operational and federated into the deployment manager cell.

    • WAS ND must be installed on DM01 to the same release level as the profiles of WAS.

    • The remote database server must be installed and operational.

  2. Install Personalization Server. Refer to the appropriate instructions for install on an existing WAS, according to the platform:

  3. Verify that Personalization Server is operational after installation.

  4. Configure the node to use an external Web server. By default, Personalization Server uses its own HTTP service for client requests. However, an external Web server is required to take advantage of features such as workload management.

  5. Verify that Personalization Server is operational with the new external Web server configuration.

  6. Once complete, the federated servers will be visible in the ND Admin Console

    Servers | Application Server

    Start and verify the operability of the Personalization Server instance.

 

Install WP02 (horizontal scaling only)

Vertical cluster note: If you intend to use Personalization Server in a vertical scaling topology, we can disregard the steps in this section and skip to Setting up the cluster.

  1. Install the second Personalization Server instance, but do not configure it. Rather choose the option that allows you to copy files.

  2. In pzn_root/config, edit the following files so that they are correct for the environment:

  3. Configure WP02 to function in the managed environment by running the following command from the pzn_root/config directory:

    • Windows:

      WPSconfig.bat cfg-pzn-secondary-node

    • UNIX:

      ./WPSconfig.sh cfg-pzn-secondary-node

  4. Verify that the secondary instance is now operational.

 

Configuring secondary cluster members on WP01 (vertical scaling only)

  1. For each secondary cluster member you create on WP01, configure Personalization work managers by running the following commands from the pzn_root/config directory:

    • Windows:

      1. WPSconfig.bat - DServerName=secondary_cluster_member init

      2. WPSconfig.bat action-create-workmanager-cmapi

      3. WPSconfig.bat action-create-workmanager-cleanup-daemon

      4. WPSconfig.bat action-create-workmanager-jcr

      5. WPSconfig.bat action-create-workmanager-ci

      6. WPSconfig.bat action-create-all-workmanagers-pzn

    • UNIX:

      1. ./WPSconfig.sh - DServerName=secondary_cluster_member init

      2. ./WPSconfig.sh action-create-workmanager-cmapi

      3. ./WPSconfig.sh action-create-workmanager-cleanup-daemon

      4. ./WPSconfig.sh action-create-workmanager-jcr

      5. ./WPSconfig.sh action-create-workmanager-ci

      6. ./WPSconfig.sh action-create-all-workmanagers-pzn

  2. Restart the cluster member.

 

Approach 2. Install Personalization Server on a separate WAS node not managed by the deployment manager

This section describes how to set up two separate Personalization Server instances (WP01 and WP02) on two dedicated systems and add them to the Deployment Manager (DM01). Below are detailed steps for implementing this scenario.

 

Install WP01

  1. Prerequisites for installation of first Personalization Server instance (WP01):

    • Deployment Manager must be installed on DM01 to the same release level as the profiles of WAS.

    • The remote database server must be installed and operational.

  2. Install Personalization Server. Refer to the appropriate instructions, according to the platform:

  3. Verify that Personalization Server is operational after installation.

  4. If you installed Personalization Server on a WAS node with security already enabled, ensure that the WAS ND machine is configured with the same security settings as Personalization Server before adding the secured Personalization Server node to the deployment manager cell. Custom user registry note: If you are using a custom user registry for security, ensure that the required WMM JAR files are present on the WAS ND machine. For details on using a custom user registry for security in a cluster, refer to Enabling WAS security for WebSphere Portal .

  5. Add WP01 to the deployment manager cell by entering the addNode command. Ensure that you include the -includeapps parameter. Refer to Using the addNode command for command syntax and other information.

  6. Once complete, the federated servers will be visible in the deployment manager administrative console in the Servers > Application Server view. Start and verify the operability of the Personalization Server instance.

 

Install WP02 on a separate WAS node not managed by the deployment manager (horizontal scaling only)

The procedure for install WP02 is nearly identical to that for install WP01, except that WP02 is federated into the cell without including any of its applications. This is because the cell can contain only one set of these applications, and the applications have already been included when WP01 was federated.

  1. Install second Personalization Server instance. Refer to the appropriate instructions, according to the platform:

  2. Add WP02 to the deployment manager (DM01) cell by entering the addNode command. Do not include the -includeapps parameter. Refer to Using the addNode command for command syntax and other information.

    • It is important not to use the -includeapps option. The applications will not be transferred as they are already in the deployment manager's master configuration.

    • Applications stored in the master configuration are still only assigned to WP01. In order to share them with WP02 and any additional nodes, a cluster must be created.

 

Configuring the nodes to operate in a cluster

This section describes the steps to configure Personalization and Deployment manager to use a cluster. Once you have completed these steps, you may skip to Section 3.3: Updating Personalization properties in a cluster.

  1. On WP01, open pzn_root/config/wpconfig.properties and set the ClusterName property to the name of the cluster you wish to create on the deployment manager. Verify that all of the security settings are still accurate for the environment. Execute from pzn_root/config:

  2. Horizontal Scaling Only: On WP02, open pzn_root/config/wpconfig.properties and set the ClusterName property to the name of the cluster you just created on the deployment manager. In addition, verify the property PrimaryNode is set to false. Verify that all security settings are still accurate for the environment. Execute from pzn_root/config:

  3. Windows:

    WPSconfig.bat cluster-setup

  4. UNIX:

    ./WPSconfig.sh cluster-setup

  5. Vertical Scaling Only: Execute from pzn_root/config to configure secondary cluster members:

    • Windows :

      1. WPSconfig.bat -DPrimaryNode=false - DServerName=new_cluster_member cluster-setup

      2. WPSconfig.bat - DServerName=secondary_cluster_member init

      3. WPSconfig.bat action-create-workmanager-cmapi

      4. WPSconfig.bat action-create-workmanager-cleanup-daemon

      5. WPSconfig.bat action-create-workmanager-jcr

      6. WPSconfig.bat action-create-workmanager-ci

      7. WPSconfig.bat action-create-all-workmanagers-pzn

    • UNIX :

      1. ./WPSconfig.sh -DPrimaryNode=false - DServerName=new_cluster_member cluster-setup

      2. ./WPSconfig.sh - DServerName=secondary_cluster_member init

      3. ./WPSconfig.sh action-create-workmanager-cmapi

      4. ./WPSconfig.sh action-create-workmanager-cleanup-daemon

      5. ./WPSconfig.sh action-create-workmanager-jcr

      6. ./WPSconfig.sh action-create-workmanager-ci

      7. ./WPSconfig.sh action-create-all-workmanagers-pzn

 

3: Setting up the cluster

Once the Personalization Server application servers reside on the federated WAS nodes, we can create a cluster and add the Personalization Server instances (WP01 and WP02) as cluster members. This section also describes how to add additional cluster members after the cluster has been created.

 

Creating the cluster

  1. To create the cluster, use the administrative console on the deployment manager. Start the administrative console by opening a browser and entering http://DM01:9060/admin in the address bar, where DM01 is the deployment manager node or host.name.

    i5/OS users: The profile referred to here was created from the app_server_root/bin directory.

  2. Click Servers > Clusters in the navigation tree, and click New.

  3. Enter the basic cluster information:

    1. Define the cluster name.

      Do not use spaces in the cluster name.

    2. Check the box Prefer local enabled.

    3. Check the box Create Replication Domain for this cluster.

    4. Select the option Select an existing server to add to this cluster and then choose server Personalization_Server on node WP01 from the list.

    5. Check the box Create Replication Entry in this Server.

    6. Click Next.

  4. Create the second cluster member.

    1. Define the name of cluster member.

      Do not use spaces in the cluster member name.

    2. Select the appropriate node, depending on the cluster topology you are using:

      • Horizontal: WP02

      • Vertical: WP01

    3. Select the appropriate HTTP port setting, depending on the cluster topology you are using:

      • Horizontal: Uncheck the box Generate Unique HTTP Ports.

      • Vertical: Check the box Generate Unique HTTP Ports.

    4. Check the box Create Replication Entry in this Server.

    5. Click Apply and then click Next to view the summary.

  5. To create the new cluster, click Finish.

  6. To save changes, click Save, and then click Save again to confirm the changes and update the deployment manager configuration.

  7. When you have completed the steps above, the cluster topology can be viewed from the Servers > Cluster Topology view.

  8. The application server view will list the new server cluster members.

  9. Save the changes and resynchronize the nodes:

    1. In the administrative console for the deployment manager, click Save on taskbar, and save the administrative configuration.

    2. Select System Administration > Nodes, select the node from the list, and click Full Resynchronize.

  10. Regenerate the Web server plug-in using the deployment manager administrative console.

    1. WAS V6: In the administrative consoleselect...

      Servers | Web Servers | Web server | Generate Plug-in

    2. Edit...

      nd_root/config/cells/plugin-cfg.xml

      ...and change any directory structure occurrences specific to the WAS ND machine to match the directory structure used on the Web server. For example, references to...

      install_dir/WebSphere/DeploymentManager

      ...would be replaced with...

      install_dir/WebSphere/AppServer

    3. If you are using a remote Web server, copy the updated plug-in configuration file (nd_root/config/cells/plugin-cfg.xml) to the Web server's plug-in configuration directory.

  11. Stop and start the Web server.

  12. Restart all nodes in the cluster.

Web server note: If you are not using an external Web server in the clustered environment, you might need to manually configure appropriate virtual host entries for the ports in the plugin-cfg.xml file to ensure that the HTTP requests can reach all the application servers.

 

Creating additional cluster members

Although it is possible to define all cluster members at the same time you initially create the cluster (as described in Creating the cluster), you might also need to add cluster members at some later time, after the cluster has already been configured. This section provides instructions for adding cluster members in both horizontal and vertical scaling topologies for an existing cluster.

 

Create horizontal cluster members

Cluster members in a horizontal scaling topology reside on different nodes in the cell. To create an additional cluster member in a horizontal cluster, complete the following steps:

  1. Install Personalization Server on the new node in the cell. Follow the instructions in Install Personalization Server , depending on whether the node is already federated into the cell.

  2. Access the administrative console on the deployment manager by opening a browser and entering http://DM01:9060/admin in the address bar, where DM01 is the deployment manager node or host.name. The port number might differ based on the installation.

  3. Click Servers > Clusters in the console navigation tree, select the cluster name, and then click Cluster members from the list of additional properties.

  4. Click New to create the cluster member.

    1. Define the name of cluster member.

      Do not use spaces in the cluster member name.

    2. Select the node where you installed the new instance of Personalization Server.

    3. Uncheck the box Generate Unique HTTP Ports.

    4. Click Apply and then click Next to view the summary.

  5. Click Finish, and save the changes.

    • The new cluster topology can be viewed from the Servers > Cluster Topology view.

    • The Servers > Application Servers view will list the new server cluster members.

  6. Regenerate the Web server plug-in using the deployment manager administrative console..

  7. Stop and start the Web server.

  8. Restart all nodes in the cluster.

 

Create vertical cluster members

Cluster members in a vertical scaling topology reside on the same node in the cell. To create an additional cluster member in a vertical cluster, complete the following steps:

  1. Access the administrative console on the deployment manager by opening a browser and entering...

    http://DM01:9060/admin

    ...in the address bar, where DM01 is the deployment manager node or host.name. The port number might differ based on the installation.

  2. Click...

    Servers | Clusters | cluster_name | Cluster members | New

    1. Define the name of cluster member.

      Do not use spaces in the cluster member name.

    2. Select an existing node where Personalization Server is installed.

    3. Check the box Generate Unique HTTP Ports.

    4. Click Apply and then click Next to view the summary.

  3. Click Finish, and save the changes.

    • The new cluster topology can be viewed from the Servers > Cluster Topology view.

    • The Servers > Application Servers view will list the new server cluster members.

  4. Regenerate the Web server plug-in using the deployment manager administrative console.

  5. Stop and start the Web server.

Web server note: If you are not using an external Web server in the clustered environment, you might need to manually configure appropriate virtual host entries for the ports in the plugin-cfg.xml file to ensure that the HTTP requests can reach all the application servers. Refer to the WAS information center for more information:

 

Updating Personalization properties in the cluster

Personalization Server provides two property files that we can modify to customize the Personalization feature. These files are not managed by the WAS deployment manager. This means that if you make any changes to these files on a node in the cluster, those changes are not transferred to other nodes when you perform a synchronization of the cluster members. Instead manually copy the following properties files to each node in the cluster:

 

4: Uninstall Personalization Server

  1. Ensure that you have removed the Personalization Server node from the cell.

  2. Uninstall the product files from the node

Related information