Publishing your page

After you have created and tested your content, which can be a page, label, or URL, you can publish it to a target server. You can perform the publish task by using the Resource Manager portlet on the Site Management page, or by using the Portal Scripting Interface. View information on publishing through the Resource Manager portlet.

  1. Parent and sibling pages or portlets that you publish by using site management must have a unique name assigned to them on both the source and target servers. For a portlet the unique name must be the same on both the source and the target server. 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.
  2. 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.
  3. Publishing a page into the public area of the portal is not supported.
  4. When a page hierarchy that you publish contains a page that is marked private for yourself on the source server, that private page is published as a public page on the target server. In other words, users of the target portal might be able to see your private page there. This also applies to private changes that you made to a page that you publish. When you publish that page, other users can see the page just the same as you with all private changes that you made to the page.
  5. Pages that exist on the target server, but have not been created by a by site management publish step cannot be replaced by using the site management functionality. In such a scenario an error message is displayed.
  6. Pages managed by site management must only be changed on the source server, not on the target server; otherwise the site management function may not work any more.
  7. 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 displayed. It overwrites other versions.
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:
    • Unique names
    • Page properties
    • Page layout
    • Page metadata
    • Friendly URLs
    • References to portlets on the page
      Note: The same portlets with the same unique name as on the source portal must also exist on your target portal. References to JSR portlets and to IBM portlet without binary parameters are supported.
    • Shared or default portlet preferences
    • Portlet wires
    • Advanced options under Edit page properties.
    • You can only publish pages that have a unique name.
    • The following items that a page can reference do not get published:
      • Page permissions or access controls
      • URL mappings
      • Derived pages
      • Composite applications
      • Web Content Management content or libraries
      • Private resources
      • Private wires
      • Personalized portlet preferences
      • Portlets or portlet WAR files. You can publish references to portlets only if the portlets exist on the target server.
      • Personalization rules. These must exist on the target server.
    • Site management does not support the merge of multiple publish events from different users. The last publish process overwrites previous publish versions.
    • You can go back only one version on a publish, promote, and demote scenario. If you want to go back farther than that, you need to create backups of the versions that you might want to go back to. You can do this by using the XML configuration interface.
    • Site management publishing does not support cross page wires.
  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 Administration > Site Management.
    2. Select the server from the pull-down list.
    3. 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 subtree 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 comes 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) that you published is available on the server and is working as designed. To do this, go to the Manage Pages portlet and select Content Root > parent_page. You see a published version of the page with the following unique name: