Publish personalization rules

WebSphere 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.

• Publish

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

• Publish personalization rules

  After developing personalization rules, you publish the rules.

• Publish personalization rules using a script

  You can use a WebSphere Portal Personalization provided script, pznload, to export, publish, and delete Personalization rules on local or remote servers. You 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).

  You can use this function to quickly revert production servers to an earlier state.

• Publish personalization rules over SSL

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

• Monitoring the status of publishing

  After you start a job to publish a personalization rule, you can monitor the status to make sure the publish completes successfully.

Parent topic:

Use rules

---