To Create a Portal Instance on a Managed Server Instance of WebLogic 8.1 Service Pack 5 on Which Portal Instance Exists

Before You Begin

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.

1. Create a new WebLogic Server instance, 7022server, on the port 7022.

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

   ./startWeblogic.sh

   ./startManagedWeblogic.sh 7022server

3. (Optional) You can also follow these steps to create a new portal instance on WebLogic 8.1 Service Pack 5:

   1. Start the WebLogic Administrator Server.

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

   3. Add the IP address of the node in the /bea_install/weblogic81/common/nodemanager/nodemanager.hosts file.

   4. Log in to the WebLogic administrator console.

   5. Click Machines.

   6. Click Configure a New Machine.

   7. Specify a machine name and click Create.

   8. Click the Node Manager tab.

   9. Specify the IP Address of the host in the listen address and specify the port on which the Node Manager is running.

   10. Click on Servers in the left pane to create a new managed server.

   11. Click on configure a new server.

   12. Specify the server name and Listen Port of the managed server.

   13. Start the managed server from the console.

4. Copy the PortalServer_base/SUNWportal/template/Webcontainer.properties.BEAWL8 file to a PortalServer-base/SUNWportal/bin/secondinstance.properties file.

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

6. Create the new Portal instance.

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

   ---

   Note –

   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.

   ---

7. Restart the web container.

8. Verify that the new portal instance.

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

9. Access the new Portal Server instance.

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