test

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

Setting Up Portal Server on ps2

This task consists of the following procedures:

ProcedureTo Install Portal Server on ps2

To properly set up Portal Server on ps2, Access Manager SDK must be configured manually. As a result, Access Manager SDK is installed with Portal Server on ps2 using the Configure Later option of the installer rather than being installed with Application Server using the Configure Now option (as it was on ps1).

  1. Repeat the procedure that appears in To Install Portal Server on ps1, except for the following:

    In the Choose Software Components panel (Step 5), select the following components:

    • Portal Server 7.1

      • Netlet Proxy

      • Rewriter Proxy

    • Portal Server Secure Remote Access 7.1

    • Access Manager 7.1

      • Access Manager SDK

    • Service Registry 3.1

      • Service Registry Client Support

    Unselect Directory Server, which is automatically selected by the installer.

ProcedureTo Configure Access Manager SDK on ps2

Because Access Manager SDK was installed using the Configure Later option, you need to configure Access Manager SDK by modifying Access Manager configuration files. The standard approach for making these modifications is to run the amconfig command with an input file.

  1. Change to the directory that contains the amconfig input file template, amsamplesilent.

    # cd /opt/SUNWam/bin

  2. Copy the template to a new file.

    # cp amsamplesilent amconfigps2

  3. In a text editor, edit the amconfigps2 file to set the Access Manager SDK configuration parameters.

    Locate the configuration parameters that are listed in the following table, and change their values to the values shown in the table.

    Parameter 

    Value 

    DEPLOY_LEVEL 

    4

    SERVER_Name 

    am

    SERVER_HOST 

    am.pstest.com

    SERVER_PORT 

    80

    ADMIN_PORT 

    4849

    DS_HOST 

    ds.pstest.com

    DS_DIRMGRPASSWD 

    directory-manager-password

    ROOT_SUFFIX 

    "dc=pstest,dc=com"

    ADMINPASSWD 

    access-manager-admin-password

    AMLDAPUSERPASSWD 

    access-manager-LDAP-password

    COOKIE_DOMAIN 

    pstest.com

    AM_ENC_PWD 

    password-enc-key

    NEW_OWNER 

    root

    NEW_GROUP 

    other

    PAM_SERVICE_NAME 

    other

    AS81_INSTANCE 

    pscluster

    AS81_INSTANCE_DIR 

    /var/opt/SUNWappserver/nodeagents/na-ps2/as-cluster-inst-ps2

    AS81DOCS_DIR 

    /var/opt/SUNWappserver/nodeagents/na-ps2/as-cluster-inst-ps2/docroot

  4. Run the amconfig command with the input file you modified in Step 3.

    # /opt/SUNWam/bin/amconfig -s amconfigps2

    The output should show failures after checking if Application Server is already configured with Access Manager. These errors are expected because the Access Manager configuration was already added to the Application Server cluster configuration when Access Manager SDK was installed and configured on ps1.

  5. Verify that the Access Manager SDK is properly configured.

    # /opt/SUNWam/bin/amadmin —u amadmin —m http://am.pstest.com:80

    When prompted, type the access-manager-admin-password.

    The output should show current session information.

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

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

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

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

    1. Copy the configuration template to a new file.

      # cd /opt/SUNWportal/template

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

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

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

    4. Save your changes and close the file.

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

ProcedureTo 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

ProcedureTo Start and Verify Portal Server on ps2

You start the Portal Server instance by restarting the Application Server instance (as-cluster-inst-ps2) in which it is deployed. You then verify that the instance is running by accessing the portal Welcome page in a browser.

  1. Stop the Application Server instance.

    # /opt/SUNWappserver/sbin/asadmin stop-instance --user admin as-cluster-inst-ps2

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

    The response should indicate that you successfully stopped the instance:

    Command stop-instance executed successfully.

  2. Restart the Application Server instance.

    # /opt/SUNWappserver/sbin/asadmin start-instance --user admin as-cluster-inst-ps2

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

    The response should indicate that you successfully started the instance:

    Command start-instance executed successfully.

  3. Verify that the Portal Server instance is running.

    1. Start a browser.

    2. Go to the following URL:

      http://ps2.pstest.com:80/portal/Welcome

      The portal Welcome page opens, confirming that your Portal Server instance is running.