Publish personalization rules overview

Portal Personalization sends published rules across HTTP to a servlet which resides on each personalization server. This servlet can receive publishing data or initiate new publishing jobs. When a user begins a publishing job from the personalization authoring environment, the local servlet is provided with the set of information necessary to complete the job. The local servlet contacts the destination endpoint servlet (which could be the same servlet) and sends its data to it. The destination servlet reports success or failure.

1. Publish considerations
   If we are publishing personalization rules in a clustered server configuration, to an IPv6 host, or using Web Content resource collection classes, there are unique considerations that you should be familiar with.

2. Publish personalization rules
   After developing personalization rules, you publish the rules.

3. Publish and deleting personalization rules using a script
   We can use a Portal Personalization provided script, pznload, to export, publish, and delete Personalization rules on local or remote servers. We can script the delivery of rules and campaigns from staging to production, or the offline publishing between disconnected systems (such as when production servers are secured behind a firewall). We can use this function to quickly revert production servers to an earlier state.

4. Publish personalization rules over SSL
   Portal Personalization uses the built-in SSL capabilities of WebSphere Application Server to provide secure publishing across unprotected networks. Your personalized portal can benefit from the full range of authentication repositories supported by WebSphere Application Server security.

5. Monitoring the status of publishing
   After you start a job to publish a personalization rule, we can monitor the status to make sure the publish completes successfully.

Parent: Personalization

Previous topic: The Personalization interface

Next topic: The Web Content resource collection