This section explains how to create a new instance of Portal Server. When you install Portal Server, it creates an instance of Portal Server on the default instance of the web container. For example, if you install Portal Server on Sun Java System Web Server, a Portal Server instance is created on the default instance of Web Server that listens to the port 80. You can also create several instances of the web container and create instances of the Portal Server that are already installed. A new instance of Portal Server that you create will have all the portals that are deployed on your first Portal Server.
After creating instances of Portal Server, you can use clustering or load balancing to serve the users effectively. Portal Server instances can be created on a node where you installed Portal Server or on a remote node where you installed a web container, AMSDK, and Portal Server packages.
This section explains how to create a Portal Server instance on different web containers on the same node where you installed Portal Server. When you create a Portal Server instance, you can create the instance on a new configuration or a new domain of the web container. You can also create a Portal Server instance on the existing configuration or domain of the web container where you have installed Portal Server.
This section explains the following:
Creating a Portal Instance on a New Configuration of Web Server 7.0
Creating a Portal Instance on a New Domain of Application Server 8.2
Creating a Portal Instance on a New Instance of Application Server 8.2
Creating a Portal Instance on a Managed Server of WebLogic 8.1 Service Pack 5
Creating a Portal Instance on a Managed Server of WebLogic 8.1 Service Pack 5 on which Portal Instance Exists
Ensure the following:
Portal Server is installed. Name of the first portal is portal1.
Access Manager administrator console is running.
Web containers are installed under the default directories.
Create a new configuration of Web Server 7.0 on the same node where Portal Server is installed. Specify the name of the configuration as secondinstance and the port as 8100.
Start the new configuration. Ensure that the Web Server administrator console is running.
Copy the PortalServer_base/SUNWportal/template/Webcontainer.properties.SJSWS7 to a PortalServer_base/SUNWportal/bin/secondportal.properties file.
Edit the following properties in the secondportal.properties file.
Host=hostname.domain
Port=8100
Scheme=http
WebContainerType=SJSWS7
WebContainerInstallDir=/WebServer_base/SUNWwbsvr7
WebContainerInstanceName=secondinstance
WebContainerDomainName=secondinstance
WebContainerDocRoot=/var/SUNWwbsvr7/docs
WebContainerAdminHost=hostname.domain
WebContainerAdminPort=8989
WebContainerAdminScheme=https
WebContainerAdminUid=admin
WebContainerAdminPassword=Webserver_admin_password
Create the new portal instance.
PortalServer_base/SUNWportal/bin/psadmin create-instance -u amadmin -f ps_password -p portal1 -w secondportal.properties
The ps_password file contains the Access Manager password
Restart the web container.
Verify that the new portal instance has been created.
PortalServer_base/SUNWportal/bin/psadmin list-portals -u amadmin -f ps_password
Access the new Portal Server instance.
http://hostname.domain-name:8100/portal1
Ensure the following:
Portal Server is installed on Application Server. Name of the first portal is portal1.
Access Manager is installed on Application Server.
Application Server is installed in the default directory.
Create a domain, seconddomain, and a server instance on the port 8100.
/ApplicationServer_base/appserver/bin/asadmin create-domain --adminport 4850 --adminuser admin --instance-port 8100 seconddomain
Start the new domain, seconddomain.
Copy the PortalServer_base/SUNWportal/template/Webcontainer.properties.SJSAS81 file to a PortalServer_base/SUNWportal/bin/secondinstance.properties file.
Edit the following properties in the secondinstance.properties file.
Host=hostname.domain
Port=8100
Scheme=http
WebContainerType=SJSAS81
WebContainerInstallDir=/ApplicationServer_base/SUNWappserver/appserver
WebContainerInstanceName=server
WebContainerDomainName=seconddomain
WebContainerInstanceDir=/var/SUNWappserver/domains/seconddomain
WebContainerDocRoot=/var/SUNWappserver/domains/seconddomain/docroot
WebContainerAdminHost=hostname.domain
WebContainerAdminPort=4850
WebContainerAdminScheme=https
WebContainerAdminUid=admin
WebContainerAdminPassword=Application Server administrator password
WebContainerMasterPassword=Application Server master password
Create the new Portal Server instance.
PortalServer_base/SUNWportal/bin/psadmin create-instance -u amadmin -f ps_password -p portal1 -w secondinstance.properties
Restart the web container.
Verify that the new portal has been created.
PortalServer_base/SUNWportal/bin/psadmin list-portals -u amadmin -f ps_password
Access the new portal instance.
http://hostname.domain.com:8100/portal
Restart the common agent container.
On the Solaris platform:
/usr/share/bin/cacaoadm stop /usr/share/bin/cacaoadm start |
On the Linux platform:
/opt/sun/cacao/bin/cacaoadm stop /opt/sun/cacao/bin/cacaoadm start |
Ensure the following:
Portal Server is installed on Application Server. Name of the first portal is portal1.
Access Manager is installed on Application Server.
Application Server is installed in the default directory.
Create a node agent, nodeagent1, in the same domain in which the first Portal Server instance exists.
ApplicationServer_base/appserver/bin/asadmin create-node-agent --host hostname.domain --port 4849 --user ApplicationServer_admin_user --password ApplicationServer_admin_password nodeagent1 |
Create an instance in the node agent.
ApplicationServer_base/appserver/bin/asadmin create-instance --host hostname.domain --port 4849 --user ApplicationServer_admin_user --password ApplicationServer_admin_password --nodeagent nodeagent1 --systemproperties HTTP_LISTNER_PORT=3870 server2 |
Start the node agent and the instance.
ApplicationServer_base/appserver/bin/asadmin start-node-agent --user admin --password password nodeagent1 ApplicationServer_base/appserver/bin/asadmin start-instance --port 4849 --user admin --password password server2 |
When you start the instance after starting the node agent, the start-instance CLI may fail stating that the server instance is already started. In this case, ignore the message. This is due to the server instance being started while starting the node agent. This behavior is controlled by the start-servers-in-startup attribute, located in the domain.xml and if it is set to true, all the server instances which are not running are started during node-agent startup.
Copy the PortalServer_base/SUNWportal/template/Webcontainer.properties.SJSAS81 to a PortalServer_base/SUNWportal/bin/secondinstance.properties file.
Edit the following properties in the secondinstance.properties file.
Host=hostname.domain
Port=3870
Scheme=http
WebContainerType=SJSAS81
WebContainerInstallDir=/ApplicationServer_base/SUNWappserver/appserver
WebContainerInstanceName=server2
WebContainerDomainName=domain1
WebContainerInstanceDir=ApplicationServer_base/nodeagents/node1/server2
WebContainerDocRoot=ApplicationServer_base/nodeagents/node1/server2/docroot
WebContainerAdminHost=hostname.domain
WebContainerAdminPort=admin port of domain1
WebContainerAdminScheme=https
WebContainerAdminUid=admin id
WebContainerAdminPassword=ApplicationServer admin password
WebContainerMasterPassword=ApplicationServer master password
Create the new Portal Server instance.
PortalServer_base/SUNWportal/bin/psadmin create-instance -u amadmin -f ps_password -p portal1 -w secondinstance.properties
Restart the web container.
Verify that the new portal instance has been created.
PortalServer_base/SUNWportal/bin/psadmin list-portals -u amadmin -f ps_password.
Access the new Portal Server instance.
http://hostname.domain.com:3870/portal
Ensure the following:
Portal Server is installed on WebLogic. Name of the first portal is portal1.
Access Manager is installed on WebLogic.
WebLogic is installed in the default directory.
Create a WebLogic domain, seconddomain on the port 7002.
Create a managed server, 7022server, on the port 7022.
Go to the WebLogic_base/user_projects/domains/seconddomain directory and run the following scripts.
./startWeblogic.sh
./startManagedWeblogic.sh 7022server
Copy the PortalServer_base/SUNWportal/template/Webcontainer.properties.BEAWL8 file to a PortalServer_base/SUNWportal/bin/secondinstance.properties file.
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 Server is installed on administrator server itself.
Create the new portal instance.
PortalServer_base/SUNWportal/bin/psadmin create-instance -u amadmin -f ps_password -p portal1 -w secondinstance.properties
Restart the web container.
Verify that the new portal instance has been created.
PortalServer_base/SUNWportal/bin/psadmin list-portals -u amadmin -f ps_password.
Access the new Portal Server instance.
http://hostname.domain.com:instance-port/portal
Ensure the following:
Portal Server is installed on WebLogic. Name of the first Portal is portal1.
Access Manager is installed on WebLogic.
WebLogic is installed in the default directory.
Create a new WebLogic Server instance, 7022server, on the port 7022.
Go to the WebLogic_base/user_projects/domains/seconddomain directory and run the following scripts:
./startWeblogic.sh
./startManagedWeblogic.sh 7022server
(Optional) You can also follow these steps to create a new portal instance on WebLogic 8.1 Service Pack 5:
Start the WebLogic Administrator Server.
Start the WebLogic node manager with the IP address of the host as the first argument and the port number on which you want the node manager to run as the second argument.
Add the IP address of the node in the /bea_install/weblogic81/common/nodemanager/nodemanager.hosts file.
Log in to the WebLogic administrator console.
Click Machines.
Click Configure a New Machine.
Specify a machine name and click Create.
Click the Node Manager tab.
Specify the IP Address of the host in the listen address and specify the port on which the Node Manager is running.
Click on Servers in the left pane to create a new managed server.
Click on configure a new server.
Specify the server name and Listen Port of the managed server.
Start the managed server from the console.
Copy the PortalServer_base/SUNWportal/template/Webcontainer.properties.BEAWL8 file to a PortalServer-base/SUNWportal/bin/secondinstance.properties file.
Edit the following properties in the secondinstance.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 administrator server itself.
Create the new Portal instance.
PortalServer_base/SUNWportal/bin/psadmin create-instance -u amadmin -f ps_password -p portal1 -w secondinstance.properties
If Portal Server is on the same port as Access Manager, then the Dcom.iplanet.am.serverMode in startWeblogic.sh or startManagedWeblogic.sh should be true, else it should be false. Before restarting the web container, edit the startWeblogic.sh or startManagedWeblogic.sh appropriately.
Restart the web container.
Verify that the new portal instance.
PortalServer_base/SUNWportal/bin/psadmin list-portals -u amadmin -f ps_password.
Access the new Portal Server instance.
http://hostname.domain.com:instance-port/portal
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.
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:
Creating a portal instance on Web Server 7.0 on a Remote Node
Creating a portal instance on WebLogic 8.1 Service Pack 5 on a Remote Node
Creating a portal instance on WebSphere 5.1.1.6 on a Remote Node
Ensure the following:
Portal Server, Access Manager, and Common Agent Container are up and running on the first node. Execute the following command on Node 1: PortalServer-base/SUNWportal/bin/psadmin list-portals -u user-name -f admin-password
Ensure that the Access Manager is accessible.
Web Server 7.0 is installed in the default directory.
The system date on the second instance node should be same as the system date on the first instance node. System dates should be in sync. To achieve this, run the rdate first_instance_node_fqdn command on the second instance node.
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.
Start the Web Server 7.0 administrator server.
WebServer_base/admin-server/bin/startserv
Start the Web Server 7.0 instance.
WebServer_base/https-hostname.domain/bin/startserv
Stat the installer and install Portal Server in the Configure Later mode.
Configure the common agent container and Java DB.
PortalServer_base/bin/psconfig --config example2.xml
Verify that the common agent container is functioning properly.
PortalServer_base/SUNWportal/bin/psadmin list-portals -u amadmin -f ps_password
Copy the PortalServer_base/SUNWportal/template/Webcontainer.properties.SJSAS81 file to a PortalServer_base/SUNWportal/bin/secondinstance.properties file.
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
Create the new portal instance.
PortalServer_base/SUNWportal/bin/psadmin create-portal -u amadmin -f ps_password -p secondportal -w secondinstance.properties
Restart the web container.
Verify that the new Portal Server instance has been created.
PortalServer_base/SUNWportal/bin/psadmin list-portals -u amadmin -f ps_password
Access the second Portal Server instance.
http://hostname.domain.com:instance-port/portal
Ensure the following:
Portal Server, Access Manager, and Common Agent Container are up and running on the first node. Execute the following command on Node 1: PortalServer-base/SUNWportal/bin/psadmin list-portals -u user-name -f admin-password
Install WebLogic 8.1 Service Pack 5 and create a managed server, 7022server on Port 7022.
Go to the WebLogic_base/user_projects/domains/mydomain directory and run the following scripts:
./startWeblogic.sh
./startManagedWeblogic.sh 7022server
Start the installer, select Access Manager SDK and install it in the Configure Later mode.
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.
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
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.
Run the installer again and install Portal Server in the Configure Later mode.
Configure the common agent container and Java DB.
PortalServer_base/bin/psconfig --config example2.xml
Verify that the common agent container is working properly.
PortalServer_base/SUNWportal/bin/psadmin list-portals -u amadmin -f ps_password
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.
Create the new instance of Portal Server.
PortalServer_base/SUNWportal/bin/psadmin create-instance -u amadmin -f ps_password -p portal1 -w secondinstance.properties
Dcom.iplanet.am.serverMode in startWeblogic.sh or startManagedWeblogic.sh should be set to false.
Restart the web container.
Verify that the new portal instance is created.
PortalServer_base/SUNWportal/bin/psadmin list-portals -u amadmin -f ps_password
Access the second portal instance.
http://hostname.domain.com:instance-port/portal
Ensure the following:
Portal Server, Access Manager, and Common Agent Container are up and running on the first node. Execute the following command on Node 1: PortalServer-base/SUNWportal/bin/psadmin list-portals -u user-name -f admin-password
Install WebSphere.
Start the WebSphere.
Run the Java ES installer, select Access Manager SDK and install in the Configure Later mode.
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.
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
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.
Run the installer again and install Portal Server in the Configure Later mode.
Configure the common agent container and Java DB.
PortalServer_base/bin/psconfig --config example2.xml
Verify that common agent container is working properly.
PortalServer_base/SUNWportal/bin/psadmin list-portals -u amadmin -f ps_password
Copy the PortalServer_base/SUNWportal/template/Webcontainer.properties.IBMWAS5 file to a PortalServer_base/SUNWportal/bin/secondinstance.properties file.
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.
Create the new instance of Portal Server.
PortalServer_base/SUNWportal/bin/psadmin create-instance -u amadmin -f ps_password -p portal1 -w secondinstance.properties
Restart the web container.
Verify that the new Portal Server instance is created.
PortalServer_base/SUNWportal/bin/psadmin list-portals -u amadmin -f ps_password
Access the second Portal Server instance.
http://hostname.domain:instance-port/portal URI