Sun Java Enterprise System 2005Q4 Installation Guide for UNIX

Configuring Portal After a Configure Now Installation on a Third-Party Web Container

If you are using BEA WebLogic Server or IBM WebSphere Application Server as the web container for Portal Server and Portal Server Secure Remote Access, use the following procedure.

ProcedureTo Configure Portal on a Third-Party Web Container


Note –

Deployment of Portal Server and Portal Server Secure Remote Access on third-party web containers is only supported on the Solaris OS.


Steps
  1. Stop all web container instances, including the admin instance and, in the case of BEA WebLogic Server, managed server instances.

  2. Start the web container’s admin server instance. If you have installed on a BEA WebLogic Server managed instance, start the managed instance too.

  3. Deploy Portal Server and Portal Server Secure Remote Access by running the deploy command:

    cd PortalServer-base /bin ./deploy

    When prompted, choose the default for the deploy URI and server instance name, and enter the web container admin password.

  4. Deploy the Portlet samples (that is, the portletsamples.war file):

    setenv DEPLOY_ADMIN_PASSWORD webcontainer-admin-password

    setenv IDSAME_ADMIN_PASSWORD AccessManager-admin-password

    cd PortalServer-base/lib

    ./postinstall_PortletSamples

    When prompted, enter the web container admin password and the Access Manager admin password.

  5. Restart the web container instance into which Portal Server and Portal Server Secure Remote Access was deployed.

    See your web container documentation for instructions on starting the web container instance. Additional information can be found in the Sun Java System Portal Server 6 2005Q4 Administration Guide and the Sun Java System Portal Server 6 2005Q4 Release Notes, respectively.


    Note –

    In the case of installation on a BEA WebLogic Server managed server, the WAR files do not get deployed. Deploy the WAR files using the BEA WebLogic Server administration console.