Deploy

Note:

Deploying a portal is primarily a system administrator task; however, you can assign the Portal Server: Deploy permission to another custom role. It is recommended that you create a custom role and assign this permission to the custom role in order to restrict the user roles that can deploy portals.

Only the Portal Manager (or Delegated Manager) of the portal can deploy the portal, and in addition, must be in a role that has the Portal Server: Deploy permission.

To deploy a portal using WebCenter Portal:

1. From the Server Name list under Target Portal Server, select the portal server connection you want to use to deploy your portal.
2. In the Comments box, specify comments, if any, about portal deployment.
3. In the Options section, select the deployment options:

   • Include Portal Content: Select to specify that the portal content stored on Content Server must be included in portal deployment on the target server. This option is available only if the content repository is WebCenter Content Server.

   • Include Shared Assets: Deploys the shared assets used by the portal. Clear the check box if you do not want to deploy shared assets.

   • Include Shared Libraries: Deploys the shared libraries used by the portal. Clear the check box if you do not want to deploy shared libraries. If you include shared libraries in portal deployment, you must restart the target server after deploying the portal for the shared library changes to be picked up.

   If this is the first time the portal is being deployed, the Redeploy instead of propagating changes check box appears disabled. Expanding the Change Details section displays a message that the portal is being deployed (for the first time) and hence all the data will be carried over to the target server. When you propagate a portal, this section displays the changes made to the portal since the last deployment.

4. Click Deploy.

   The Deploy Portals dialog displays the progress and status of portal deployment. While the portal is being deployed, you can choose to close the dialog and continue to work on the portal if required.

5. Click Close.

   Once a portal is deployed, you can view its deployment history and status.

6. Restart the target server where the portal is deployed if you included shared libraries in portal deployment.