To Modify the Configuration of the Portal Server Instance on ps2

The previous procedure deployed Portal Server by using pscluster as the target Application Server instance. The instance.id entry, however, needs to be targeted to as-cluster-inst-ps2, rather than to the cluster. The following procedure removes this entry from the pscluster configuration and adds it to the as-cluster-inst-ps2 configuration.

The following commands are run on ps2, but can also be run on ps1 without using the --host option.

1. Remove the instance.id entry from the cluster configuration.

   # /opt/SUNWappserver/sbin/asadmin delete-jvm-options --user admin --target pscluster "-Dcom.sun.portal.instance.id=ps-inst-ps2" --host ps1.pstest.com

   When prompted, type the app-server-admin-password.

   The response should indicate that you successfully removed the instance from the cluster configuration:

   Command delete-jvm-options executed successfully.

2. Add the instance.id entry to the as-cluster-inst-ps2 configuration.

   # /opt/SUNWappserver/sbin/asadmin create-system-properties --user admin --target as-cluster-inst-ps2 com.sun.portal.instance.id=ps-inst-ps2 --host ps1.pstest.com

   When prompted, type the app-server-admin-password.

   The response should indicate that you successfully added Portal Server instance information to the Application Server instance on ps2:

   Command create-system-properties executed successfully.

3. Restart the pscluster cluster.

   The cluster needs to be restarted for changes in configuration to take effect.

   # /opt/SUNWappserver/sbin/asadmin stop-cluster --user admin pscluster --host ps1.pstest.com

   # /opt/SUNWappserver/sbin/asadmin start-cluster --user admin pscluster --host ps1.pstest.com