test

Sun Java System Portal Server 7.1 Configuration Guide

Creating a New Portal

After creating a Portal Server installation on a node, you can create another Portal Server installation on the same node or different nodes using the same Access Manager and Directory Server. This new Portal Server installation is empty. You can use the sample portals provided to customize the portal for your specific needs. For example, you could create portals for different departments of an organization but still use the same Access Manager and Directory Server.

This section explains about creating a new portal installation on the same node or different node depending on your first Portal Server installation.

Creating a New Portal on the Same Node

When you create a new portal on the same node where you have the first Portal Server installation, you need to create a web container instance. Then, you need to duplicate the Webcontainer.properties file that is available in the Portal Server installation directory and modify the Webcontainer.properties file to direct to the new web container instance. Finally, you can run the psadmin create-portal sub command to create the new portal.

This section explains how to create a new portal on different web containers, such as Sun Java System Web Server, Sun Java System Application Server, IBM WebSphere, and BEA Web Logic.

ProcedureTo Create a New Portal on a New Configuration of Web Server 7.0

Before You Begin

Ensure the following:

  1. Create a new configuration of Web Server 7.0 on the same node where first portal is up and running.

  2. Name the configuration secondportal and assign the port 8100.

  3. Copy the PortalServer_base/SUNWportal/template/Webcontainer.properties.SJSWS7 file to a PortalServer_base/SUNWportal/bin/secondportal.properties file.

  4. Edit the following properties in the secondportal.properties file.

    • Host=hostname.domain

    • Port=8100

    • Scheme=http

    • WebContainerType=SJSWS7

    • WebContainerInstallDir=/opt/SUNWwbsvr7

    • WebContainerInstanceName=secondportal

    • WebContainerDomainName=secondportal

    • WebContainerDocRoot=/var/SUNWwbsvr7/docs

    • WebContainerAdminHost=hostname.domain

    • WebContainerAdminPort=8989

    • WebContainerAdminScheme=https

    • WebContainerAdminUid=admin

  5. Create the new portal.

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

    Note –

    The ps_password file contains the Access Manager password.

  6. Restart the web container.

  7. Verify whether the new portal has been created.

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

ProcedureTo Create a New Portal on a New Domain of Application Server 8.2

  1. Create a new domain, seconddomain, on port 8100.

    /ApplicationServer_base/appserver/bin/asadmin create-domain --adminport 4850 --adminuser admin --instanceport 8100 seconddomain

  2. Start the new domain.

    /ApplicationServer_base/appserver/bin/asadmin start-domain --user admin seconddomain

  3. Copy the PortalServer_base/SUNWportal/template/Webcontainer.properties.SJSAS81 file to a PortalServer_base/SUNWportal/bin/secondportal.properties file.

  4. Edit the following properties in the secondportal.properties file.

    • Host=hostname.domain

    • Port=8100

    • Scheme=http

    • WebContainerType=SJSAS81

    • WebContainerInstallDir=/opt/SUNWappserver/appserver

    • WebContainerInstanceName=server

    • WebContainerDomainName=seconddomain

    • WebContainerInstanceDir=/var/opt/SUNWappserver/domains/seconddomain

    • WebContainerDocRoot=/var/opt/SUNWappserver/domains/seconddomain/docroot

    • WebContainerAdminHost=hostname.domain

    • WebContainerAdminPort=4850

    • WebContainerAdminScheme=https

    • WebContainerAdminUid=admin

    • WebContainerAdminPassword=ApplicationServer admin password

    • WebContainerMasterPassword=ApplicationServer master password

  5. Create the new portal.

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

  6. Restart the web container.

  7. Verify that the new portal has been created.

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

ProcedureTo Create a New Portal on a New Domain of BEA WebLogic 8.1 Service Pack 5

  1. Create a WebLogic domain, seconddomain running on port 7002.

  2. Create a managed server, 7022server, running on port 7022.

  3. Go to the WebLogic_base/user_projects/domains/seconddomain directory and start the managed server.

    ./startWeblogic.sh

    ./startManagedWeblogic.sh 7022server

  4. Copy the PortalServer_base/SUNWportal/template/Webcontainer.properties.BEAWL8 file to a PortalServer_base/SUNWportal/bin/secondportal.properties file.

  5. Edit the following properties in the secondportal.properties file.

    • Host=hostname.domain

    • Port=7022

    • Scheme=http

    • WebContainerType=BEAWL8

    • WebContainerInstallDir=/usr/local/bea/weblogic81

    • WebContainerInstanceName=7022server

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

    • WebContainerDocRoot=LEAVE BLANK

    • WebContainerAdminHost=hostname.domain

    • WebContainerAdminPort=7002

    • WebContainerAdminScheme=http

    • WebContainerAdminUid=admin userid

    • WebContainerAdminPassword=admin passwd

    • WebContainerJDKDir=/usr/local/bea/jdk142_08

    • WebContainerManagedServer=true

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

  6. Create the new portal.

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

  7. Restart the web container.

  8. Verify that the new portal has been created.

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

ProcedureTo Create a New Portal on a New Domain of WebSphere 5.1.1.6

  1. Create a WebSphere domain and start the domain.

  2. Copy the PortalServer_base/SUNWportal/template/Webcontainer.properties.IBMWAS5 to a PortalServer_base/SUNWportal/bin/secondportal.properties file.

  3. Edit the following properties in the secondportal.properties file.

    • Host=hostname.domain

    • Port=9080

    • Scheme=http

    • WebContainerType=

    • WebContainerInstallDir=/optM/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=/opt/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.

  4. Create the new portal.

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

  5. Restart the web container.

  6. Verify that the new portal is created.

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

Creating a New Portal on a Remote Node

This section explains how to create a new portal on a remote node. When you create a new portal on a remote node, you should install Access Manager SDK (AMSDK) and a compatible web container. When you install AMSDK, you need to provide the details of Access Manager and Identity Server that you installed for the Portal Server installation. You need to install Portal Server in the Configure Now or Configure Later mode. All the procedures that are explained in this section use the web container of the first portal installation for the second portal installation on a remote node.

Note –

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

After you install AMSDK and the web container, you can use any one of the following options to create a new portal:

ProcedureTo Create a New Portal on Web Server 7.0 in the Configure Now Mode

Before You Begin

Ensure the following:

  1. Run the Java ES installer.

  2. Select Web Server 7.0, Access Manager SDK, and Portal Server and run it in the Configure Now mode.

    In the Installer panels, provide the details about the Directory Server and Access Manager of the first Portal Server installation.

  3. Change the name of the Portal.

    For example, the first portal will be portal1, so change the name of the second portal to portal2.

  4. Complete the installation.

ProcedureTo Create a New Portal on Web Server 7.0 in the Configure Later Mode

Before You Begin

Ensure the following:

  1. Install Access Manager SDK and Web Server 7.0 in the Configure Now mode using the Java ES installer.

    In the installer pages, provide the details about the Directory Server and Access Manager of the first Portal Server installation.

  2. Start the Web Server 7.0 administrator server.

    WebServer_base/admin-server/bin/startserv

  3. Start the Web Server 7.0 instance configuration.

    WebServer_base/https-hostname.domain/bin/startserv

  4. Use the installer to install Portal Server in the Configure Later mode.

  5. Modify the example files accordingly.

    For Web Server 7.0, you can use one of the following example files depending on the requirements:

    • example1.xml

    • example3.xml

    • example4.xml

    • example5.xml

    • example6.xml

    • example7.xml

    • example8.xml

    • example9.xml

    • example13.xml

    • example17.xml

  6. Complete the Portal Server installation.

    PortalServer_base/bin/psconfig --config examplefile

ProcedureTo Create a New Portal on Web Server 7.0 Using the psadmin Command

Before You Begin

Ensure the following:

  1. Install Access Manager SDK and Web Server 7.0 in the Configure Now mode using the Java ES installer.

  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. Install Portal Server in the Configure Now mode using the Java ES installer.

  5. Configure the common agent container and Java DB.

    PortalServer_base/bin/psconfig --config example2.xml

  6. Verify whether the common agent container is working properly.

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

  7. Copy the PortalServer_base/SUNWportal/template/Webcontainer.properties.SJSWS7 file to a PortalServer_base/SUNWportal/bin/secondportal.properties file.

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

    • Host=hostname.domain

    • Port=80

    • Scheme=http

    • WebContainerType=SJSWS7

    • WebContainerInstallDir=/opt/SUNWwbsvr7

    • WebContainerInstanceName=hostname.domain

    • WebContainerDomainName=hostname.domain

    • WebContainerDocRoot=/var/opt/SUNWwbsvr7/docs

    • WebContainerAdminHost=hostname.domain

    • WebContainerAdminPort=8989

    • WebContainerAdminScheme=https

    • WebContainerAdminUid=admin

    • WebContainerAdminPassword=Webserver7.0 admin password

  9. Create the new portal.

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

    Note –

    The ps_password file contains the Access Manager password.

  10. Restart the web container.

  11. Verify that the new portal has been created.

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

ProcedureTo Create a New Portal on Application Server 8.2 in the Configure Now Mode

Before You Begin

Ensure the following:

  1. Start the Java ES installer and select Application Server 8.2, Access Manager SDK, and Portal Server and install them in the Configure Now mode.

  2. Provide the Access Manager host and the Directory Server host information.

  3. Change the name of the portal.

    For example, first portal will be portal1. Change the second portal name to portal2.

ProcedureTo Create a New Portal on Application Server 8.2 in the Configure Later Mode

Before You Begin

Ensure the following:

  1. Install Access Manager SDK and Application Server 8.2 in the Configure Now mode using the Java ES installer.

  2. Start the Application Server 8.2 administrator server.

    ApplicationServer_base/appserver/bin/asadmin start-domain --user admin_user --password admin_password domain-name

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

  4. Complete the Portal Server installation.

    PortalServer_base/bin/psconfig --config example7.xml

ProcedureTo Create a New Portal on Application Server 8.2 Using the psadmin Command

Before You Begin

Ensure the following:

  1. Install Access Manager SDK and Application Server 8.2 in the Configure Now mode using the Java ES installer.

  2. Start the Application Server 8.2.

    ApplicationServer_base/appserver/bin/asadmin start-domain --user admin_user --password admin_password domain-name

  3. Run the installer and install Portal Server software in the Configure Later mode.

  4. Configure common agent container and Java DB.

    PortalServer_base/bin/psconfig --config example2.xml

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

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

  6. Copy the PortalServer_base/SUNWportal/template/Webcontainer.properties.SJSWS7 file to a PortalServer_base/SUNWportal/bin/secondportal.properties file.

  7. Edit the following properties in the secondportal.properties file.

    • Host=hostname.domain

    • Port=8080

    • Scheme=http

    • WebContainerType=SJSAS81

    • WebContainerInstallDir=/opt/SUNWappserver/appserver

    • WebContainerInstanceName=server

    • WebContainerDomainName=domain1

    • WebContainerInstanceDir=/var/opt/SUNWappserver/domains/domain1

    • WebContainerDocRoot=/var/opt/SUNWappserver/domains/domain1/docroot

    • WebContainerAdminHost=hostname.domain

    • WebContainerAdminPort=4849

    • WebContainerAdminScheme=https

    • WebContainerAdminUid=admin id

    • WebContainerAdminPassword=ApplicationServer admin password

    • WebContainerMasterPassword=ApplicationServer master password

  8. Create the new portal.

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

  9. Restart the web container.

  10. Verify that the new portal has been created.

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

ProcedureTo Create a New Portal on WebLogic 8.1 Service Pack 5 in the Configure Now Mode

Before You Begin

Ensure the following:

  1. Install WebLogic 8.1 Service Pack 5 and create a managed server in a domain.

  2. Start the administrator server and managed server.

  3. Run the installer and 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 host name without FQDN

    • SERVER_HOST=$SERVER_NAME.domain-name

    • SERVER_PORT=AccessManager Server 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=.doamin-name

    • AM_ENC_PWD=any string

    • NEW_OWNER=root

    • NEW_GROUP=other

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

    • 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 second 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 second 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 in the Configure Now mode.

  8. Change the name of the portal.

    For example, if the first portal is portal1, change name of the second portal to portal2.

ProcedureTo Create a New Portal on WebLogic 8.1 Service Pack 5 in the Configure Later Mode

Before You Begin

Ensure the following:

  1. Install WebLogic 8.1 Service Pack 5 and create a managed server in a domain.

  2. Start the WebLogic administrator server and managed server.

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

  4. Edit 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-name

    • SERVER_PORT=AccessManager_server_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 Access Manager

    • ADMINPASSWD=AccessManager Password

    • AMLDAPUSERPASSWD=LDAP Password

    • COOKIE_DOMAIN=.domain-name

    • AM_ENC_PWD=any string

    • NEW_OWNER=root

    • NEW_GROUP=other

      (This value is root for the Solaris 10 release and Linux, and other for the Solaris 9 release)

    • PAM_SERVICE_NAME=other

    • WEB_CONTAINER=WL8

    • BASEDIR=Directory where Access Manager SDK is installed.

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

    • CONSOLE_PORT=Port where second 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=myservername 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 second 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 and install portal in the Configure Later mode.

  8. Complete the portal Server installation.

    PortalServer_base/bin/psconfig --config example15.xml

ProcedureTo Create a New Portal on WebLogic 8.1 Service Pack 5 Using the psadmin Command

Before You Begin

Ensure the following:

  1. Install Weblogic 8.1 Service Pack 5 and create a managed server.

  2. Start the administrator server and the managed server.

  3. Run 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_hostname without FQDN

    • SERVER_HOST=$SERVER_NAME.domain-name

    • SERVER_PORT=AccessManager_server_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 Access Manager

    • ADMINPASSWD=AccessManager_password

    • AMLDAPUSERPASSWD=LDAP_password

    • COOKIE_DOMAIN=.domain-name

    • 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.

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

    • CONSOLE_PORT=Port where second 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=myservername 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 second 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 and install portal in the Configure Later mode.

  8. Configure common agent container and Java DB.

    PortalServer_base/bin/psconfig --config example2.xml

  9. Verify that common agent container is functioning properly.

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

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

    • Host=hostname.domain

    • Port=port on which second Portal needs to be installed

    • Scheme=http

    • WebContainerType=BEAWL8

    • WebContainerInstallDir=/usr/local/bea/weblogic81

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

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

    • WebContainerDocRoot=Leave Blank

    • WebContainerAdminHost=hostname.domain

    • WebContainerAdminPort=port of admin server

    • WebContainerAdminScheme=http

    • WebContainerAdminUid=admin userid

    • WebContainerAdminPassword=admin password

    • WebContainerJDKDir=/usr/local/bea/jdk142_08

    • WebContainerManagedServer=true

      false if new portal is installed on administrator server itself.

  11. Create the new portal.

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

  12. Restart the web container.

  13. Verify that the new portal is created.

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

ProcedureTo a Create a New Portal on WebSphere 5.1.1.6 in the Configure Now Mode

Before You Begin

Ensure the following:

  1. Install WebSphere.

  2. Start WebSphere.

  3. Start the Java ES installer and 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_hostname without FQDN

    • SERVER_HOST=$SERVER_NAME.domain-name

    • SERVER_PORT=AccessManager_server_port

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

    • DS_HOST=DirectoryServer with FQDN

    • DS_DIRMGRPASSWD=Directory Manager Password

    • ROOT_SUFFIX=root suffix of Access Manager

    • ADMINPASSWD=AccessManager Password

    • AMLDAPUSERPASSWD=LDAP_Password

    • COOKIE_DOMAIN=.domain-name

    • 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=WAS5

    • BASEDIR=Directory where Access Manager SDK is installed.

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

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

    • CONSOLE_PROTOCOL=$SERVER_PROTOCOL

    • AM_REALM=disabled

    • WAS51_HOME=/Websphere_base/WebSphere/AppServer

    • WAS51_JDK_HOME=/Websphere_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=$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. Start the Java ES installer again and install portal on the Configure Now mode.

  8. Change the name of the portal.

    For example, if the first portal is portal1, then change the name of the new portal to portal2.

ProcedureTo Create a New Portal on WebSphere 5.1.1.6 in the Configure Later Mode

Before You Begin

Ensure the following:

  1. Install Websphere.

  2. Start the Websphere.

  3. Run the installer and 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 host name without FQDN

    • SERVER_HOST=$SERVER_NAME.domain-name

    • SERVER_PORT=AccessManager server port

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

    • DS_HOST=DirectoryServer with FQDN

    • DS_DIRMGRPASSWD=DirectoryManager Password

    • ROOT_SUFFIX=root suffix of AccessManager

    • ADMINPASSWD=AccessManager_password

    • AMLDAPUSERPASSWD=LDAP_password

    • COOKIE_DOMAIN=.domain-name

    • AM_ENC_PWD=any string

    • NEW_OWNER=root

    • NEW_GROUP=other

      This value is 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 SDK is installed.

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

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

    • CONSOLE_PROTOCOL=$SERVER_PROTOCOL

    • AM_REALM=disabled

    • WAS51_HOME=/Websphere_base/WebSphere/AppServer

    • WAS51_JDK_HOME=/Websphere_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=$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. Start the installer again and install portal on the Configure Later mode.

  8. Complete the Portal Server installation.

    PortalServer_base/bin/psconfig --config example16.xml

ProcedureTo Create a New Portal Using the psadmin Command

Before You Begin

Ensure the following:

  1. Install WebSphere.

  2. Start the WebSphere.

  3. Start the 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 without FQDN

    • SERVER_HOST=$SERVER_NAME.domain-name

    • SERVER_PORT=AccessManager admin password

    • 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 Access Manager

    • ADMINPASSWD=AccessManager Password

    • AMLDAPUSERPASSWD=LDAP_password

    • COOKIE_DOMAIN=.domain-name

    • 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=WAS5

    • BASEDIR=Directory where Access Manager SDK is installed.

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

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

    • CONSOLE_PROTOCOL=$SERVER_PROTOCOL

    • AM_REALM=disabled

    • WAS51_HOME=/Websphere_base/WebSphere/AppServer

    • WAS51_JDK_HOME=/Websphere_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=$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. Start the installer again and install Portal Server in the Configure Later mode.

  8. Configure Common Agent Container and Java DB.

    PortalServer_base/bin/psconfig --config example2.xml

  9. Verify that common agent container is functioning properly.

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

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

  11. Edit the following properties in the secondportal.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 password

    • 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 portal.

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

  13. Restart the web container.

  14. Verify that the new portal is created.

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

Deploying Sample Content to a New Portal

When you create a new portal, it does not have any sample portal deployed in it. However, you can deploy sample portals such as community sample, enterprise sample, and developer sample to the new portal.

ProcedureTo Deploy a Sample Content to a New Portal

  1. Copy the /PortalServer-base/SUNWportal/samples/portals/shared/input.properties.template file to the /var/opt/SUNWportal/tmp/input.properties file.

    In the Linux platform, copy to the /var/opt/sun/portal/tmp/input.properties file.

  2. Edit the input.properties file that you created in the /var/opt/SUNWportal/tmp directory with the following values.

    • ps.config.location=/etc/opt/SUNWportal

    • ps.portal.id=new portal id

    • ps.access.url=access url of the new portal.

    • ps.webapp.uri=access uri of the new portal.

    • ps.profiler.email=admin@domain.com

      Optional. You can leave this value empty.

    • ps.profiler.smtp.host=host.domain

      Optional. You can leave this value empty.

    • search.access.url=http://host.domain:port/search1/search

    • search.id=search1

    • am.admin.dn=uid=amAdmin,ou=People,dc=domain,dc=com

    • default.org.dn=dc=domain,dc=com

  3. Copy the /PortalServer-base/SUNWportal/samples/portals/shared/password.properties.template file to the /var/opt/SUNWportal/tmp/password.properties file.

    In the Linux platform copy the file to the /var/opt/sun/portal/tmp/password.properties directory.

  4. Edit the /var/opt/SUNWportal/tmp/password.properties file and set proper passwords.

    • amadminPassword=%AMADMIN_PASSWORD%

    • amldapuserPassword=%AMLDAPUSER_PASSWORD%

    • userManagementPassword=%USER_MANAGEMENT_PASSWORD%

      You can ignore this value if you are not setting up Communication channels.

  5. Run the following command.

    export JAVA_HOME=/usr/jdk/entsys-j2se

  6. Run the following command to deploy all the portals.

    /usr/sfw/bin/ant -buildfile /PortalServer-base/SUNWportal/samples/portals/build.xml -Dconfig.location /var/opt/SUNWportal/tmp/ -logfile /var/opt/SUNWportal/tmp/log-file.txt

  7. (Optional) Run the following command if you wish to deploy only the developer portal.

    /usr/sfw/bin/ant -buildfile /PortalServer-base/SUNWportal/samples/portals/developer/build.xml -Dconfig.location /var/opt/SUNWportal/tmp/ -logfile /var/opt/SUNWportal/tmp/log-file.txt

  8. (Optional) Run the following command if you wish to deploy only the enterprise portal.

    /usr/sfw/bin/ant -buildfile /PortalServer-base/SUNWportal/samples/portals/enterprise/build.xml -Dconfig.location /var/opt/SUNWportal/tmp/ -logfile /var/opt/SUNWportal/tmp/log-file.txt

  9. (Optional) Run the following command if you wish to deploy only the community portal.

    /usr/sfw/bin/ant -buildfile /PortalServer-base/SUNWportal/samples/portals/community/build.xml -Dconfig.location /var/opt/SUNWportal/tmp/ -logfile /var/opt/SUNWportal/tmp/log-file.txt

  10. (Optional) Run the following command if you wish to deploy only the welcome portal.

    /usr/sfw/bin/ant -buildfile /PortalServer-base/SUNWportal/samples/portals/welcome/build.xml -Dconfig.location /var/opt/SUNWportal/tmp/ -logfile /var/opt/SUNWportal/tmp/log-file.txt

  11. Restart the web container.