+

Search Tips   |   Advanced Search


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. Publishing via the command-line is a two step process. First, you export the personalization rules you want to transfer from the authoring environment to a remote system. After exporting and saving the desired objects, you use the pznload script to send this data to the desired server.

    • Click More Actions > Export in the Personalization Navigator. You are prompted for a location to save a nodes file. This file contains an XML representation of all the currently selected personalization objects. You can export entire folders.Figure 1. Exporting a folder to the file system

  1. Use pznload to send this data to the desired server. The pznload script is located in the following directory: PortalServer_root/pzn/prereq.pzn/publish/

    1. pznload.bat --serverUrl url --targetPath path--targetWorkspace workspace --username username --password password

    2. pznload.sh --serverUrl url --targetPath path --targetWorkspace workspace --username username --password password

    This program accepts a number of command line options and a set of nodes files to publish. Invoke pznload with the --help option to see a list of all options. The most important arguments are described below:

    serverUrl

    The URL of the remote publish servlet. If you do not specify a value the program will attempt to connect to a WebSphere Portal server running on the local machine.

    targetWorkspace

    The name of the workspace to publish to. The default workspace name on all IBM Content Manager run-time edition installations is RULESWORKSPACE.

    targetPath

    The location in the target workspace which will be the parent for the published nodes. The target path must exist prior to publishing. Example: If the Export function was used on the folder /Projects/HR Website, then the target path should be specified as /Projects so that the published resources are once again located in /Projects/HR Website.

    username

    A valid user on the target system with sufficient access rights.

    password

    The password for the user

After a publish is started, you see status messages in the command console.


Parent topic:

Publish personalization rules