WebSphere Portal, Express Beta Version 6.1
Operating systems: i5/OS, Linux,Windows


 

Publishing your page

After you have created and tested your page, which can be a page, label, or URL, you can publish it to a target server. The publish task can be performed using the Site Management page, or using a JACL script. This topic describes publishing through the Site Management page.

Parent and sibling pages or portlets that you publish using site management must exist with the same unique name on both the source and target servers. Make sure that when you create your page that you assign it a unique name; otherwise, you cannot publish the page to another server. When you create a new page, the system assigns the page a Unique Identifier; this is not the unique name. Use the Manage Custom Unique Names portlet to assign a unique name to your page or label.

Also, if the pages or portlets that you publish have existing personalization visibility rules associated with them, site management will publish the rule associations, but not the rules themselves. You must make sure that the same rules exist on both the source and target servers, and preserve the correct page-to-rule association, by creating a Publish Server using the Personalization tools. Publish the required rule by selecting the Publish Selected menu option under Extra Options.

Perform the following steps to publish a page to a target server:

  1. Create and test a page on your source server. The following information, or referenced items, are published if they are included in a page:

    Some items that may be referenced by a page do not get published:

  2. Perform the following steps to select a server: Note: You can select only your source server or you can also open your target server so you can compare them.

    1. Navigate to the Site Management page by clicking Launch > Administration > Site Management.
    2. Right click on Select a server.
    3. Click Select Server > servername.

      A message displays saying that the server was retrieved successfully.

    4. Click on the plus sign next to the server name to expand the server site tree.
  3. Perform the following steps to publish a single page or label or the entire page or label hierarchy from a test server to your production server:

    1. Right click on the page or label and select Publish to > servername.
    2. Select the Page radio button to publish a single page or label. If this is a hierarchy that you want to publish, select the Entire sub tree radio button.
    3. Enter the Parent page unique name, which is the unique name of the parent page on the target server.

      To find the unique name of the parent page, open the tree for the target server, right click on the page you want as the parent and select Copy page unique name, then go back to the source server and select Publish to > servername. On the Publish Page screen, click the Use saved unique name link to paste the unique name.

    4. Optional: Enter the Sibling page unique name, which is the unique name of the page that will come after the published page in the target server hierarchy.
    5. Click OK to publish the page to the target server or click Cancel to exit without publishing.
    6. Optional: If the target server is also open and showing the list of pages, you can refresh the server site tree to verify that the page was published. Right click on the page that is above the published page in the tree (the parent page), then click Refresh. The newly published page displays a round publish icon next to the page name. Only users who are authorized to view published pages, based on the specialized Personalization publish rule, can see this page on the target server.
  4. Log on to the target server as a user who has the authority to view published pages. Verify that the page(s) you published is available on the server and is working as designed.
Go to the Manage Pages portlet and select Content Root > parent_page. You will see a published version of the page with the following unique name: com.ibm.portal.published_page_name.Note: If two administrative users attempt to publish different versions of the same page at the same time, there is no support for merging these multiple publish actions. The last version of the page to be published is the version that will be displayed, overwriting other versions. Parent topic: Managing your site Related tasks
Enabling remote access to your servers Managing your servers Providing reviewer access to a published page Promoting your page Demoting your page Republishing and promoting a page Creating a portal page from an HTML file Disabling site management Site management extension of the Portal Scripting Interface
Library | Support | Terms of use |