Sun Java Enterprise System 2005Q4 Installation Guide for UNIX

Portal Server and Portal Server Secure Remote Access Postinstallation Configuration

After a Configure Now or a Configure Later installation, the packages are installed and you are ready to perform the configuration tasks for Portal Server using the following procedures.

Configuring Portal Server and Portal Server Secure Remote Access After a Configure Now Installation

Final configuration steps for Portal Server and Portal Server Secure Remote Access differ depending on whether it is deployed in a Sun web container or a third-party web container. The following sections explain the details:

Configuring Portal After a Configure Now Installation on a Sun Web Container

If you are using Application Server or Web Server as the web container for Portal Server and Portal Server Secure Remote Access, you must apply changes to the instance. Follow the instructions in the Sun Java System Portal Server 6 2005Q4 Administration Guide and the Sun Java System Portal Server 6 2005Q4 Release Notes.

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.

To 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

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

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

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.

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.

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.

Configuring Portal Server and Portal Server Secure Remote Access After a Configure Later Installation

Final configuration steps for Portal Server differ depending on whether it is deployed in a Sun web container or a third-party web container. The following sections explain the details:

Note –

Information on configuring Portal Server Secure Remote Access can be found in the Sun Java System Portal Server 6 2005Q4 Secure Remote Access Administration Guide.

Configuring Portal Server After a Configure Later Installation on a Sun Web Container

Portal Server provides a common configurator that can be used to configure all Portal Server subcomponents as well as Portal Server Secure Remote Access.

To Configure Portal Server After a Configure Later Installation on Application Server or Web Server

Steps

Create a runtime configuration for Portal Server by running the Portal Server configurator, PortalServer-base /lib/psconfig.

Instructions for running the configurator as well as descriptions of the settings used by the configurator are contained in the Sun Java System Portal Server 6 2005Q4 Administration Guide.

Apply changes to the instance.

Use the instructions in the “ Post-Installation Tasks” section in the Postinstallation Configuration chapter of the Sun Java System Portal Server 6 2005Q4 Administration Guide.

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

Portal Server provides a common configurator that can be used to configure all Portal Server subcomponents as well as Portal Server Secure Remote Access.

Note –

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

To Configure Portal Server After a Configure Later Installation on BEA WebLogic Server or IBM WebSphere Application Server

Steps

Create a runtime configuration for Portal Server by running the Portal Server configurator, PortalServer-base /lib/psconfig .

Instructions for running the configurator as well as descriptions of the settings used by the configurator are contained in the Postinstallation Configuration chapter of the Sun Java System Portal Server 6 2005Q4 Administration Guide.

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

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

Deploy Portal Server 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.

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

setenv DEPLOY_ADMIN_PASSWORD web-container-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.

Restart the web container instance into which Portal Server was deployed. See your web container documentation for instructions on starting the web container instance.

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.