Portal Server Post-Installation Tasks

Post-installation tasks need to be performed for each of the following components:

• Portal Server

• Secure Remote Access

• Gateway

• Netlet and Rewriter Proxy

To Access Portal Server

Before You Begin

To access the Portal Server or the Identity Server administration console the directory server and the web container must first be started.

Step

Use the following command to start a local installation of the directory server:

/var/opt/mps/serverroot/slapd-hostname/start-slapd

The following post-installation tasks depend on the type of web container on which you deployed the Portal Server.

• Sun Java System Web Server

• Sun Java System Application Server

• BEA WebLogic Server

• IBM WebSphere Application Server

To Start the Sun Java System Web Server

Steps

1. Start the admin instance. In a terminal window type:

   cd WebServer-base/SUNWwbsrv/https-webserver-instance-name ./start

   or

2. Access the Sun Java System Web Server administration console.

3. Click Apply Changes to restart the web container.

To Start Sun Java System Application Server 7.0

Step

In a terminal window, change directories to the application server’s instances utilities directory and run the startserv script. The following example assumes that the default application server domain and instance have been used.

cd /var/opt/SUNWappserver7/domains/domain1/server1/bin
./startserv

To stop and start the Sun Java System Application Server using the asadmin utility or from the Sun Java System Application Server administration console, consult the Sun Java System Application Server documentation.

To Configure the Sun Java System Application Server 8.1 Instance

Steps

1. Stop the domain instance. In a terminal window, type:

   /opt/SUNWappserver/appserver/bin/asadmin stop-domain domainname

   For example

   /opt/SUNWappserver/appserver/bin/asadmin stop-domain domain1

2. Start the domain instance. In a terminal window, type:

   /opt/SUNWappserver/appserver/bin/asadmin start-domain --user administrator-user-name --password administartor-user-password domainname

   For example,

   /opt/SUNWappserver/appserver/bin/asadmin start-domain --user admin --password password domain1

To Deploy Portal Server on BEA WebLogic Server

Before You Begin

Portal Server must be installed before performing the following steps.

Steps

1. Check the /var/sadm/install/logs/Java_Enterprise_System_install.BMMddhhmm file for errors.

   MM = month

   dd = day

   hh = hour

   mm = minute

2. Stop all BEA WebLogic Server instances (the admin and managed servers).

3. Start the BEA WebLogic admin server instance. If you have installed on a managed instance, start the managed instance too.

4. From the command line, execute the following:

   PortalServer-base/bin/deploy

   Choose the default for the deploy URI and server instance name, and enter the BEA WebLogic Server admin password when prompted.

5. Restart the BEA WebLogic Server 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 a managed server installation, the .war files do not get deployed. The .war files should be deployed using the BEA WebLogic Server administration console.

   ---

   If you will be supporting multiple authentication methods, for example, LDAP, UNIX, Anonymous, you must add each authentication type to the Core authentication service to create an authentication menu. See the Sun Java System Portal Server 6 2005Q1 Administration Guide for further information.

To Deploy Portal Server on IBM WebSphere Application Server

Steps

1. Check the /var/sadm/install/logs/Java_Enterprise_System_install.B/MMddhhmm file for errors.

2. Stop and restart the application server instance and the application server node. See your web container documentation for instructions on starting the web container instance.

3. From the command line, execute the following:

   PortalServer-base/bin/deploy

   Choose the default for the deploy URI and server instance name, and enter IBM WebSphere Server admin password when prompted.