Installing Portal Server 7.1 on an IBM WebSphere Server 5.1.1.6

This section includes procedures to install Portal Server on WebSphere 5.1.1.6 in the following scenarios:

• Installing Portal Server on IBM WebSphere 5.1.1.6 Using in the Configure Now Mode

• Installing Portal Server on IBM WebSphere 5.1.1.6 Using the Configure Later Mode

• Installing psconsole on Web Server 7.0

Portal Server administration console (psconsole) is supported only on Sun Java System Web Server 7.0 and Sun Java System Application Server 8.2.

To Install Portal Server on IBM WebSphere 5.1.1.6 in the Configure Now Mode

1. Install IBM WebSphere 5.1.1.6.

2. Start the IBM WebSphere server.

3. Start the Java ES installer. Select Directory Server and Web Server 7.0, and install the components in the Configure Now mode.

4. Start the Directory Server instance.

   DirectoryServer_base/SUNWdsee/ds6/bin/dsadm start DirectoryServer_base/SUNWdsee/dsins1

5. Start the Java ES installer. Install Access Manager in the Configure Later mode.

6. Configure Access Manager on the IBM WebSphere container by modifying the following values in the amsamplesilent file.

   The amsamplesilent file is located at in the following directories:

   • Solaris platform: /AccessManager_base/SUNWam

   • Linux platform: /AccessManager_base/sun/identity

   • Default: AccessManagerSample_Location/bin

   Set values in the amasamplesilent file as follows:

   • DEPLOY_LEVEL=1

   • SERVER_NAME=AM_HOSTNAME without FQDN

   • SERVER_HOST=$SERVER_NAME.domain-name

   • SERVER_PORT=9080

   • ADMIN_PORT=9090

   • DS_HOST=DS_HOSTNAME with FQDN

   • DS_DIRMGRPASSWD=Directory Manager Password

   • ROOT_SUFFIX=root suffix of Access Manager

   • ADMINPASSWD=AM_PASSWORD

   • AMLDAPUSERPASSWD=LDAP_PASSWORD

   • COOKIE_DOMAIN=.doamin-name

   • AM_ENC_PWD=string

   • NEW_OWNER=root

   • NEW_GROUP=other (root for the Solaris 10 release and Linux and other for the Solaris 9 release)

   • PAM_SERVICE_NAME=other

   • WEB_CONTAINER=WAS5

   • BASEDIR= Directory where Access Manager is installed., for example, /AccessManager_base/SUNWam

   • AM_REALM=disabled

   • WAS51_HOME=/WebSphere_base/WebSphere/AppServer

   • WAS51_JDK_HOME=/AccessManager_base/WebSphere/AppServer/java

   • WAS51_CELL=Usually hostname without FQDN. Please check it in your install.

   • WAS51_NODE=Usually hostname without FQDN. Please check it in your install.

   • WAS51_INSTANCE=server1

   • WAS51_PROTOCOL=$SERVER_PROTOCOL

   • WAS51_HOST=$SERVER_NAME

   • WAS51_PORT=9080

   • WAS51_SSLPORT=9081

   • WAS51_ADMIN=admin

   • WAS51_ADMINPORT=9090

7. Run the amsamplesilent script.

   The amsamplesilent file is located in the following directories

   • Solaris platform: /AccessManager_base/SUNWam

   • Linux platform: /AccessManager_base/sun/identity

8. Verify if Access Manager is functioning properly.

   http://host.domain-name:9080/amconsole

9. Install Portal Server in the Configure Now mode using the Java ES installer.

10. Restart IBM WebSphere after the successful installation of the Portal Server.

11. Access the portal.

    http://host.domain-name:9080/portal

To Install Portal Server on IBM WebSphere 5.1.1.6 Using the Configure Later Mode

1. Install IBM WebSphere 5.1.1.6 server.

2. Start IBM WebSphere.

3. Install Directory Server and Web Server 7.0 in the Configure Later mode using the Java ES installer.

4. Start the Directory Server instance.

   /DirectoryServer_base/SUNWdsee/ds6/bin/dsadm start /var/DirectoryServer_base/SUNWdsee/dsins1

5. Install Access Manager in the Configure Later mode using the Java ES installer.

6. Configure Access Manager on IBM WebSphere container using the following values in the amsamplesilent file.

   The amsamplesilent file is located at:

   • Solaris: /AccessManager_base/SUNWam

   • Linux: /AccessManager_base/sun/identity

   • Default: AccessManagerSample_Location/bin

   The values in the amasamplesilent file is as follows:

   • DEPLOY_LEVEL=1

   • SERVER_NAME=AM_HOSTNAME without FQDN

   • SERVER_HOST=$SERVER_NAME.sun-name

   • SERVER_PORT=9080

   • ADMIN_PORT=9090

   • DS_HOST=DS_HOSTNAME with FQDN

   • DS_DIRMGRPASSWD=Directory Manager Password

   • ROOT_SUFFIX=root suffix of Access Manager

   • ADMINPASSWD=AM_PASSWORD

   • AMLDAPUSERPASSWD=LDAP_PASSWORD

   • COOKIE_DOMAIN=.domain-name

   • AM_ENC_PWD=any string

   • NEW_OWNER=root

   • NEW_GROUP=other (root for the Solaris 10 release and Linux and other for the Solaris 9 relesae)

   • PAM_SERVICE_NAME=other

   • WEB_CONTAINER=WAS5

   • BASEDIR=Directory where Access Manager is installed., for example: /AccessManager_base/SUNWam

   • AM_REALM=disabled

   • WAS51_HOME=/WebSphere_base/WebSphere/AppServer

   • WAS51_JDK_HOME=/WebSphere/AppServer/java

   • WAS51_CELL=Usually hostname without FQDN. Please check it in your install.

   • WAS51_NODE=Usually hostname without FQDN. Please check it in your install.

   • WAS51_INSTANCE=server1

   • WAS51_PROTOCOL=$SERVER_PROTOCOL

   • WAS51_HOST=$SERVER_NAME

   • WAS51_PORT=9080

   • WAS51_SSLPORT=9081

   • WAS51_ADMIN=admin

   • WAS51_ADMINPORT=9090

7. Run the AccessManager_base/SUNam/bin/amconfig -s AccessManager_base/SUNam/bin/amsamplesilent script.

   For Solaris, the amsamplesilent file is available in the /AccessManager_base/SUNWam directory. For Linux, it is available in the AccessManager_base/sun/identify directory.

8. Verify if Access Manager is functioning properly.

   http://host.domain-name:9080/amconsole

9. Install Portal Server in the Configure Later mode using the Java ES installer.

10. Modify the example files based on your requirements.

    For IBM WebSphere, you can use the example16.xml file.

11. Configure the common agent container.

    PortalServer_base/bin/psconfig --config example16.xml