Install IBM WebSphere 5.1.1.6 server.
Start IBM WebSphere.
Install Directory Server and Web Server 7.0 in the Configure Later mode using the Java ES installer.
Start the Directory Server instance.
/DirectoryServer_base/SUNWdsee/ds6/bin/dsadm start /var/DirectoryServer_base/SUNWdsee/dsins1
Install Access Manager in the Configure Later mode using the Java ES installer.
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
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.
Verify if Access Manager is functioning properly.
http://host.domain-name:9080/amconsole
Install Portal Server in the Configure Later mode using the Java ES installer.
Modify the example files based on your requirements.
For IBM WebSphere, you can use the example16.xml file.
Configure the common agent container.
PortalServer_base/bin/psconfig --config example16.xml