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