Before you can publish a rule, create a rule and a rule mapping
(and a campaign if applicable).
Note: To publish, a user requires the following authorities:
- On the local system:
- View access to everything that must be published (items that are not visible
to the publishing user will not be published)
- View access to the publish server.
- On the remote system:
- The user specified in the Publish All and Publish Selected screens is
the user that must have the authority on the remote system
- Edit access for the root node
- In general, edit and delete access to everything that will be published
(some items may have to be deleted or moved)
To activate a rule, publish it to a publish server. The Personalization Navigator and Editor portlets
contain help files that describe basic publishing procedures. When using SSL
to connect to a secured WebSphere Portal system,
the following steps must be performed to allow Personalization users
to publish resources:
- Select Manage Portlets under Portal Administration section
- Locate the Personalization Navigator
portlet and click the edit icon.
- Add a portlet parameter named pzn.publishServlet.url with a properly
formed URL of the following pattern
https://<hostname>:<sslport>/<wpscontextroot>/pznpublish/pznpublishtarget
where <hostname> is the fully qualified domain name of the portal system (such as 'portal00.raleigh.ibm.com'), <sslport> is the configured SSL HTTP port for the server (if the default SSL port has not been changed this value may be omitted) and <wpscontextroot> is the context root of the WebSphere Portal system (the default is 'wps').
- Save your changes.
An example url for a default WebSphere Portal installation
with SSL enabled through
IBM HTTP Server might look like:
https://portal00.raleigh.ibm.com/wps/pznpublish/pznpublishtarget
Home |
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.