To Create a Portal Server Instance on ps2 (Sun Java System Reference Configuration Series: Portal Service on Application Server Cluster)

Sun Java System Reference Configuration Series: Portal Service on Application Server Cluster

To Create a Portal Server Instance on `ps2`

When you created a Portal Server instance (ps-inst-ps1) on ps1 (see To Create a Portal Server Instance on ps1), you deployed Portal Server to pscluster and created additional portal and instance configuration information on ps1.

To create a Portal Server instance (ps-inst-ps2) on ps2, you need to set up the portal's administrative infrastructure that is needed to copy the portal and instance configuration information from ps1 to ps2.

In addition, before you can use the portal's administrative interface to create ps-inst-ps2, you must remove ps_util.jar from the pscluster classpath, as described in the following procedure. If you try to run the psadmin -create-instance command without first removing ps_util.jar, psadmin will detect the presence of ps_util.jarand exit without creating a new instance.

The following procedure sets up the portal's administrative infrastructure, removes ps_util.jar from the pscluster classpath, creates a custom configuration file for creating ps-inst-ps2, and then uses the psadmin -create-instance command to create the new instance.

You begin with an appropriate example configuration file as a template and edit the file to specify parameter values that are needed for the reference configuration.

Set up the portal's administrative infrastructure.
1. Create a config-ps2 configuration file.
  
  Use the example2.xml file as a template.
  
  # cd /opt/SUNWportal/samples/psconfig
  
  # cp example2.xml config-ps2.xml
2. Open the config-ps2.xml file in a text editor.
3. Modify the config-ps2.xml file to use parameter values that are appropriate for the reference configuration.
  
  The modified config-ps2.xml file is reproduced in Example Configuration File: Portal Server Instance on ps2.
4. Run the psconfig command:
  
  # /opt/SUNWportal/bin/psconfig --config /opt/SUNWportal/samples/psconfig/config-ps2.xml
  
  The response should resemble the following:
```
Logs redirected to /var/opt/SUNWportal/logs/config/portal.fabric.0.0.log
Creating directory: /etc/opt/SUNWportal
Successfully created PSConfig.properties file
Copying config templates from: /opt/SUNWportal/template/config
Successfully created PortalDomainConfig.properties file
Validating the Input Config XML File
Configuring Cacao Agent for Portal Software
Configuring Derby Server Instance
Closing MBean Server connection ...
Resetting log level ...
Configuration Successful
```

Remove ps_util.jar from the pscluster classpath.
1. Start a browser.
2. Go to the following URL:
  
  https://ps1.pstest.com:4849
  
  The Application Server login page opens.
3. Log in to the Application Server Admin Console by typing the following values and clicking Login.
  
  Input Field
  
  Value
  
  User ID
  
  admin
  
  Password
  
  app-server-admin-password
  
  The Application Server Admin Console opens.
4. Click on the small triangle next to Configurations on the Common Tasks panel.
  
  The configurations are expanded.
5. Click on the small triangle next to pscluster-config.
  
  The pscluster configuration is expanded.
6. Click on JVM Settings.
  
  The frame on the right shows the configuration options.
7. In the right frame, select the Path Settings tab.
  
  The JVM Classpath Settings panel opens.
8. Remove /opt/SUNWportal/lib/ps_util.jar from the Classpath Suffix list.
9. Click Save.
10. Restart the pscluster cluster.
  
  The cluster needs to be restarted for the change in configuration to take effect. The following commands are run on ps2, but can also be run on ps1 without using the --host option.
  
  # /opt/SUNWappserver/sbin/asadmin stop-cluster --user admin --host ps1.pstest.com pscluster
  
  # /opt/SUNWappserver/sbin/asadmin start-cluster --user admin --host ps1.pstest.com pscluster

Input Field	Value
User ID	`admin`
Password	`app-server-admin-password`

Create a custom configuration file to use when creating a new Portal Server instance.

Copy the configuration template to a new file.

# cd /opt/SUNWportal/template

# cp Webcontainer.properties.SJSAS81 Webcontainer.properties.ps-inst-ps2

Open Webcontainer.properties.ps-inst-ps2 in a text editor.

Set the parameters that are listed in the following table.

Parameter	Value
Host	`ps2.pstest.com`
Port	`80`
Scheme	`http`
WebContainerInstallDir	`/opt/SUNWappserver/appserver`
WebContainerInstanceName	`pscluster`
WebContainerDomainName	`domain1`
WebContainerInstanceDir	`/var/opt/SUNWappserver/nodeagents/na-ps2/as-cluster-inst-ps2`
WebContainerDocRoot	`/var/opt/SUNWappserver/nodeagents/na-ps2/as-cluster-inst-ps2/docroot`
WebContainerAdminHost	`ps1.pstest.com`
WebContainerAdminPort	`4849`
WebContainerAdminScheme	`https`
WebContainerAdminPassword	`app-server-admin-password`
WebContainerMasterPassword	`app-server-master-password`

Save your changes and close the file.

Create a new Portal Server instance.

Execute the following command on ps2:

# /opt/SUNWportal/bin/psadmin create-instance -u amadmin -p pstestPortal --instance ps-inst-ps2 --webconfig Webcontainer.properties.ps-inst-ps2