test

Sun Java System Portal Server 7.1 Configuration Guide

Creating a Portal Server Instance a Remote Node

This section explains how to create a Portal Server instance on a remote node. In this scenario, you have Portal Server installed on a node. You are creating an instance of Portal Server on another node. You need to install AMSDK, web container, and Portal Server packages on the node where you wish to install Portal Server instance. Then, you need to run the psadmin create-instance command to create a new Portal Server instance.

Note –

When you install AMSDK, provide the same encryption key, am password, and LDAP password that are used for Access Manager on Node 1.

This section explains the following:

ProcedureTo Create a New Portal Instance on Web Server 7.0 on a Remote Node

Before You Begin

Ensure the following:

  1. Start the installer and install Access Manager SDK and Web Server 7.0 in the Configure Now mode.

    In the installer panel, provide the details of the Identity Server and Access Manager that you installed in the first node.

  2. Start the Web Server 7.0 administrator server.

    WebServer_base/admin-server/bin/startserv

  3. Start the Web Server 7.0 instance.

    WebServer_base/https-hostname.domain/bin/startserv

  4. Stat the installer and install Portal Server in the Configure Later mode.

  5. Configure the common agent container and Java DB.

    PortalServer_base/bin/psconfig --config example2.xml

  6. Verify that the common agent container is functioning properly.

    PortalServer_base/SUNWportal/bin/psadmin list-portals -u amadmin -f ps_password

  7. Copy the PortalServer_base/SUNWportal/template/Webcontainer.properties.SJSAS81 file to a PortalServer_base/SUNWportal/bin/secondinstance.properties file.

  8. Edit the following properties in secondinstance.properties file.

    • Host=hostname.domain

    • Port=80

    • Scheme=http

    • WebContainerType=SJSWS7

    • WebContainerInstallDir=/WebServer_base/SUNWwbsvr7

    • WebContainerInstanceName=hostname.domain

    • WebContainerDomainName=hostname.domain

    • WebContainerDocRoot=/var/SUNWwbsvr/docs

    • WebContainerAdminHost=hostname.domain

    • WebContainerAdminPort=8989

    • WebContainerAdminScheme=https

    • WebContainerAdminUid=administrator id

    • WebContainerAdminPassword=WebServer administrator password

  9. Create the new portal instance.

    PortalServer_base/SUNWportal/bin/psadmin create-portal -u amadmin -f ps_password -p secondportal -w secondinstance.properties

  10. Restart the web container.

  11. Verify that the new Portal Server instance has been created.

    PortalServer_base/SUNWportal/bin/psadmin list-portals -u amadmin -f ps_password

  12. Access the second Portal Server instance.

    http://hostname.domain.com:instance-port/portal

ProcedureTo Create a Portal Instance on WebLogic 8.1 Service Pack 5 on a Remote Node

Before You Begin

Ensure the following:

  1. Install WebLogic 8.1 Service Pack 5 and create a managed server, 7022server on Port 7022.

  2. Go to the WebLogic_base/user_projects/domains/mydomain directory and run the following scripts:

    ./startWeblogic.sh

    ./startManagedWeblogic.sh 7022server

  3. Start the installer, select Access Manager SDK and install it in the Configure Later mode.

  4. Edit the values in the amsamplesilent file.

    For Solaris, the amsamplesilent file is present in the /AccessManager_base/SUNWam/bin directory. For Linux, it is in the /AccessManager_base/sun/identity directory.

  5. Change the following values in the amsamplesilent file.

    • DEPLOY_LEVEL=4

    • SERVER_NAME=AccessManager host name without FQDN

    • SERVER_HOST=$SERVER_NAME.domain.com

    • SERVER_PORT=AccessManager server port

    • ADMIN_PORT=Admin port for the web container on which Access Manager resides

    • DS_HOST=Directory Server HOSTNAME with FQDN

    • DS_DIRMGRPASSWD=Directory Manager Password

    • ROOT_SUFFIX=root suffix of Access Manager

    • ADMINPASSWD=AccessManger Password

    • AMLDAPUSERPASSWD=LDAP password

    • COOKIE_DOMAIN=.domain.com

    • AM_ENC_PWD=any string

    • NEW_OWNER=root

    • NEW_GROUP=other

      This value is root for Solaris 10 and Linux, and other for Solaris 9

    • PAM_SERVICE_NAME=other

    • WEB_CONTAINER=WL8

    • BASEDIR=Directory where Access Manager SDK is installed

      For example, /AccessManager_base/SUNWam

    • CONSOLE_HOST=FQDN of host where Portal needs to be installed

    • CONSOLE_PORT=Port where new Portal needs to be installed, which is the port of the managed server

    • CONSOLE_PROTOCOL=$SERVER_PROTOCOL

    • AM_REALM=disabled

    • WL8_HOME=/usr/local/bea

    • WL8_PROJECT_DIR=user_projects

    • WL8_DOMAIN=mydomain

    • WL8_CONFIG_LOCATION=$WL8_HOME/$WL8_PROJECT_DIR/domains

    • WL8_SERVER=myserver

      Name of the managed server on which second Portal needs to be installed.

    • WL8_INSTANCE=$WL8_HOME/weblogic81

    • WL8_PROTOCOL=$SERVER_PROTOCOL

    • WL8_HOST=FQDN of the node on which second Portal needs to be installed

    • WL8_PORT=Port where the new Portal needs to be installed, which is the port of the managed server

    • WL8_SSLPORT=Weblogic ADMIN_PORT

    • WL8_ADMIN=weblogic

    • WL8_PASSWORD=weblogic admin password

    • WL8_JDK_HOME=$WL8_HOME/jdk142_08

  6. Run the following command:

    AccessManager_base/SUNWam/bin/amconfig -s AccessManager_base/SUNWam/bin/amsamplesilent

    For Linux, the amsamplesilent utility is available in the /AccessManager_base/sun/identity directory.

  7. Run the installer again and install Portal Server in the Configure Later mode.

  8. Configure the common agent container and Java DB.

    PortalServer_base/bin/psconfig --config example2.xml

  9. Verify that the common agent container is working properly.

    PortalServer_base/SUNWportal/bin/psadmin list-portals -u amadmin -f ps_password

  10. Edit the following properties in the secondinstance.properties file.

    • Host=hostname.domain

    • Port=Port on which new Portal needs to be installed

    • Scheme=http

    • WebContainerType=BEAWL8

    • WebContainerInstallDir=/usr/local/bea/weblogic81

    • WebContainerInstanceName=Name of the managed server on which second instance of Portal needs to be installed

    • WebContainerInstanceDir=/usr/local/bea/user_projects/domains/mydomain

    • WebContainerDocRoot=Leave Blank

    • WebContainerAdminHost=hostname.domain

    • WebContainerAdminPort=Port of admin server

    • WebContainerAdminScheme=http

    • WebContainerAdminUid=admin id

    • WebContainerAdminPassword=admin password

    • WebContainerJDKDir=/usr/local/bea/jdk142_08

    • WebContainerManagedServer=true

      The value is false, if new Portal is installed on administrator server itself.

  11. Create the new instance of Portal Server.

    PortalServer_base/SUNWportal/bin/psadmin create-instance -u amadmin -f ps_password -p portal1 -w secondinstance.properties

    Note –

    Dcom.iplanet.am.serverMode in startWeblogic.sh or startManagedWeblogic.sh should be set to false.

  12. Restart the web container.

  13. Verify that the new portal instance is created.

    PortalServer_base/SUNWportal/bin/psadmin list-portals -u amadmin -f ps_password

  14. Access the second portal instance.

    http://hostname.domain.com:instance-port/portal

ProcedureTo Create a Portal Instance on WebSphere 5.1.1.6 on a Remote Node

Before You Begin

Ensure the following:

  1. Install WebSphere.

  2. Start the WebSphere.

  3. Run the Java ES installer, select Access Manager SDK and install in the Configure Later mode.

  4. Edit the values in the amsamplesilent file.

    For Solaris, the amsamplesilent file is present in the /AccessManager_base/SUNWam/bin directory. For Linux, it is in the /AccessManager_base/sun/identity directory.

  5. Change the following values in the amsamplesilent file:

    • DEPLOY_LEVEL=4

    • SERVER_NAME=AccessManager_hostname without FQDN

    • SERVER_HOST=$SERVER_NAME.domain.com

    • SERVER_PORT=AccessManager_admin_port

    • ADMIN_PORT=Admin port for the web container on which Access Manager resides

    • DS_HOST=DirectoryServer_hostname with FQDN

    • DS_DIRMGRPASSWD=Directory Manager Password

    • ROOT_SUFFIX=root suffix of AccessManager

    • ADMINPASSWD=AccessManager_password

    • AMLDAPUSERPASSWD=LDAP_password

    • COOKIE_DOMAIN=.domain.com

    • AM_ENC_PWD=any string

    • NEW_OWNER=root

    • NEW_GROUP=other

      This value is root for Solaris 10 and Linux, and other for Solaris 9.

    • PAM_SERVICE_NAME=other

    • WEB_CONTAINER=WL8

    • BASEDIR=Directory where Access Manager SDK is installed.

      For example, /Access_Manager_base/SUNWam.

    • CONSOLE_HOST=FQDN of host where Portal needs to be installed

    • CONSOLE_PORT=Port where new Portal needs to be installed, which is the port of the managed server

    • CONSOLE_PROTOCOL=$SERVER_PROTOCOL

    • AM_REALM=disabled

    • WAS51_HOME=/Websphere_base_dir/Websphere/AppServer

    • WAS51_JDK_HOME=/Websphere_base_dir/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=$SERVER_PORT

    • WAS51_SSLPORT=9081

    • WAS51_ADMIN=admin

    • WAS51_ADMINPORT=$ADMIN_PORT

  6. Run the following command:

    AccessManager_base/SUNWam/bin/amconfig -s AccessManager_base/SUNWam/bin/amsamplesilent

    For Linux, the amsamplesilent utility is available in the /AccessManager_base/sun/identity directory.

  7. Run the installer again and install Portal Server in the Configure Later mode.

  8. Configure the common agent container and Java DB.

    PortalServer_base/bin/psconfig --config example2.xml

  9. Verify that common agent container is working properly.

    PortalServer_base/SUNWportal/bin/psadmin list-portals -u amadmin -f ps_password

  10. Copy the PortalServer_base/SUNWportal/template/Webcontainer.properties.IBMWAS5 file to a PortalServer_base/SUNWportal/bin/secondinstance.properties file.

  11. Edit the following properties in the secondinstance.properties file.

    • Host=hostname.domain

    • Port=9080

    • Scheme=http

    • WebContainerType=IBMWAS5

    • WebContainerInstallDir=/Websphere_base/IBM/WebSphere/Express51/AppServer

    • WebContainerInstanceName=server1

    • WebContainerDomainName=Leave Blank

    • WebContainerInstanceDir=Leave Blank

    • WebContainerDocRoot=Leave Blank

    • WebContainerAdminHost=hostname.domain

    • WebContainerAdminPort=9090

    • WebContainerAdminScheme=http

    • WebContainerAdminUid=admin userid

    • WebContainerAdminPassword=admin passwd

    • WebContainerJDKDir=/Websphere_base/IBM/WebSphere/Express51/AppServer/java

    • WebContainerDeployCell=usually hostname without FQDN. Please check it in your install.

    • WebContainerDeployNode=usually hostname without FQDN. Please check it in your install.

  12. Create the new instance of Portal Server.

    PortalServer_base/SUNWportal/bin/psadmin create-instance -u amadmin -f ps_password -p portal1 -w secondinstance.properties

  13. Restart the web container.

  14. Verify that the new Portal Server instance is created.

    PortalServer_base/SUNWportal/bin/psadmin list-portals -u amadmin -f ps_password

  15. Access the second Portal Server instance.

    http://hostname.domain:instance-port/portal URI