This page refers to an older version of the product.
View the current version of the User Help.
Personalization Servers Policy
Enabling User Personalization is a policy decision and the setting is configured within the Policy Configuration side of the console. It is the deployed configuration which determines whether managed endpoints are subject to User Personalization and to which server endpoints connect.
It is recommended that multiple servers and/or virtual hosts are added to the Select Personalization Server dialog so alternative servers can be easily selected for failover purposes.
Deploy the policy configuration that contains a list of Personalization Servers to the endpoints sending the configuration.aemp to managed computers. The first time a user logs on to a managed endpoint, the Environment Manager agent contacts the first personalization server to request the actual list of servers the endpoint should use (based on the sites configured in the database). The client then contacts the correct server to pull down the User Personalization configuration, containing the list of the applications which should be personalized for the user.
If all attempts to connect to a Personalization Server fail, then the User Personalization configuration is not downloaded and User Personalization does not take place.
For details about configuring Personalization Servers, see the User Workspace Manager help.
To cater for such a scenario it is recommended that the 9661 - Timeout Communicating with Personalization Server auditing event is enabled.
Configure a Personalization Servers List
- Select the Policy Configuration navigation button.
From the Manage tab select Personalization Servers.
The Configure Personalization Servers dialog displays.
Click the add server button .
The Add Server dialog displays.
Enter the server name or click the ellipsis to search for the required server by specifying locations and searching for server names.
Do not select or enter Localhost as the server name. If Localhost is entered as the server name it is added to the configuration.aemp file as the location of the Personalization Server. The client tries connecting to http://localhost/Personalization which is incorrect and User Personalization is disabled.
- Enter a Friendly Name for the server. This can be any text but should be something which will enable you to identify the server. If no text is entered, the server name is used.
- Select the required protocol - http or https.
- Enter the server name or browse for the required server by specifying locations and searching for server names.
Enter a port number. The port range for Personalization servers is 7771 to 7790 and the default port is 7771.
Once the server details have been added, the URL for the server is displayed.
The server is listed in the Select Personalization Server dialog.
Repeat steps 3 to 9 to add more servers.
Servers in the list can have their details edited or be deleted from the list using the buttons at the top of the dialog.
If you have added more than one server, use the arrow buttons to reorder the list. When the configuration is deployed, endpoints attempt to connect to each server in turn. If a connection cannot be made with any server in the list, Personalization does not occur.
- Click OK to save the server list.
When the configuration is deployed to endpoints, this list is used to determine which servers managed users connect to.