test

Sun Java System Portal Server 7.2 Installation and Configuration Guide

Installing Portal Server and Access Manager in a High Availability Scenario with Berkeley Database

This section explains how to install Portal Server and Access Manager in a high availability scenario using Berkeley database. Berkeley database is installed when you install Access Manager. In a high availability scenario, Berkeley database is used to store session variables of the user.

In the procedures in this section, you do the following:

Figure 7–1 Portal Server With Berkely Database

Portal Server and Access Manager in a High Availability Scenario with Berkeley Database

ProcedureTo Install Portal Server and Access Manager in a High Availability Scenario with Berkeley Database

These instructions require the following:

  1. On Node 1, install Directory Server, Access Manager, and Application Server 9.1.

  2. Verify whether Access Manager is installed properly by accessing Access Manager Console.

    http://node1.domain-name:8080/amconsole

  3. Login to amconsole on Node 1. In the Organization Aliases List, add the Fully Qualified Domain Name (FQDN) of Node 2.

  4. Click Service Configuration and click Platform in the right panel.

  5. In the Platform Server List, add the following.

    http://node2.domain-name:8080|02

  6. On Node 2, run the Java ES installer to install Access Manager.

    On the page that asks whether Directory Server is already provisioned with data, select Yes and proceed with installing Access Manager.

    Note –

    Ensure that the password encryption key on Node 2 is the same as the password encryption key on Node 1. The password encryption key should be the same for the LDAP internal password on both of the nodes.

  7. On Node 2, start Application Server 9.1 and verify whether Access Manager is installed properly by accessing Access Manager Console.

    http://node2.domain-name:8080/amconsole

  8. In a text editor, open the AMConfig.properties file on Node 1 and Node 2.

    The file is located in the AccessManager_base/SUNWam/config directory.

    1. Edit the com.iplanet.am.cookie.encode property to be false.

    2. Edit com.sun.identity.server.fqdnMapNode3.domain-name=isserver.mydomain.com with the Fully Qualified Domain Name of the Load Balancer.

ProcedureTo Install the Load Balancer on Node 3

  1. Install the Load Balancer plugin on Node 3 that is provided with Application Server 9.1. Select Web Server as a component to install with the Load Balancer plugin.

  2. In a text editor, open the loadbalancer.xml file on Node 3.

    This file is located in the WebServer_base/SUNWwbsvr7/https-Node3/config directory.

  3. Edit the file so that the Load Balancer balances the load between the two Access Manager instances.

    Edit the listeners with the appropriate values.

    A sample loadbalancer.xml which balances the load on Portal Server and Access Manager instances on Node 1 and Node 2 is as follows:


    <!DOCTYPE loadbalancer PUBLIC 
"-//Sun Microsystems Inc.//DTD Sun ONE Application Server 9.1//
EN" "sun-loadbalancer_1_1.dtd">
<loadbalancer>
<cluster name="cluster1">
<!--
Configure the listeners as space seperated URLs like
listeners="http://host:port https://host:port" For example:
<instance name="instance1" enabled="true"
disable-timeout-in-minutes="60"
listeners="http://localhost:80 
https://localhost:443"/>
-->
<instance name="instance1" enabled="true"
disable-timeout-in-minutes="60"
listeners="http://node1.domain-name:8080"/>
<instance name="instance2" enabled="true"
disable-timeout-in-minutes="60"
listeners="http://node2.domain-name:8080"/>
<web-module context-root="/portal" enabled="true"
disable-timeout-in-minutes="60" error-url="sun-http-lberror.html" />
<web-module context-root="/psconsole" enabled="true"
disable-timeout-in-minutes="60" error-url="sun-http-lberror.html" />
<web-module context-root="/amserver" enabled="true"
disable-timeout-in-minutes="60" error-url="sun-http-lberror.html" />
<web-module context-root="/amconsole" enabled="true"
disable-timeout-in-minutes="60" error-url="sun-http-lberror.html" />
<web-module context-root="/ampassword" enabled="true"
disable-timeout-in-minutes="60" error-url="sun-http-lberror.html" />
<web-module context-root="/amcommon" enabled="true"
disable-timeout-in-minutes="60" error-url="sun-http-lberror.html" />
<web-module context-root="/" enabled="true"
disable-timeout-in-minutes="60" error-url="sun-http-lberror.html" />
<health-checker url="/" interval-in-seconds="10" timeout-in-seconds="30" />
</cluster>
<property name="reload-poll-interval-in-seconds" value="60"/>
<property name="response-timeout-in-seconds" value="30"/>
<property name="https-routing" value="true"/>
<property name="require-monitor-data" value="false"/>
<property name="active-healthcheck-enabled" value="false"/>
<property name="number-healthcheck-retries" value="3"/>
<property name="rewrite-location" value="true"/>
</loadbalancer>

  4. Start the Web Server.

  5. On Node 1 and Node 2, start Access Manager, Directory Server, and Application Server 9.1.

ProcedureTo Configure Session Failover with Message Queue and Berkeley Database

  1. Edit the Application Server 9.1 domain.xml file on Node 1 and Node 2 to add locations of the jms.jar file and imq.jarfile.


    <JAVA javahome="/usr/jdk/entsys-j2se"
server-classpath="/usr/share/lib/imq.jar:/usr/share/lib/jms.jar: ....?
    Note –

    When you create a Message Queue instance, do not use the default Message Queue instance that starts with Application Server 9.1 or the guest user for Message Queue.

  2. Start Message Queue on Node 1 and Node 2.

    /bin/imqbrokerd -tty -name mqins -port 7777 &

    where mqins is the Message Queue instance name.

  3. Add a user to this message queue.

    imqusermgr add -u amsvrusr -p secret12 -i mqins -g admin

    where amsvrusr is the name of the new user that is used instead of guest.

  4. Inactivate the guest user.

    imqusermgr update -u guest -i mqins -a false

  5. Create an encrypted file for the message queue on Node 1 and Node 2.

    ./amsfopasswd -f /AccessManager_base/SUNWam/.password -e password-file

  6. Edit the amsfo.conf file on both the nodes.

    A list of sample entries in amsfo.conf file is displayed as follows:


    AM_HOME_DIR=/opt/SUNWam
AM_SFO_RESTART=true
LUSTER_LIST=node1.domain-name:7777,node2.domain-name:7777
DATABASE_DIR="/tmp/amsession/sessiondb"
DELETE_DATABASE=true
LOG_DIR="/tmp/amsession/logs"
START_BROKER=true
BROKER_INSTANCE_NAME=amsfo
BROKER_PORT=7777
BROKER_VM_ARGS="-Xms256m -Xmx512m"
USER_NAME=amsvrusr
PASSWORDFILE=$AM_HOME_DIR/.password
AMSESSIONDB_ARGS=""
lbServerPort=8080
lbServerProtocol=http
lbServerHost=node3.domain-name
SiteID=10

  7. Configure amsfo.confon Node 1.

    AccessManager_base/SUNWam/bin/amsfoconfig

    After running the script, the following output is displayed:


    Session Failover Configuration Setup script.
=========================================================
=========================================================
Checking if the required files are present...
=========================================================

Running with the following Settings.
-------------------------------------------------
Environment file: /etc/opt/SUNWam/config/amProfile.conf
Resource file: /opt/SUNWam/lib/amsfo.conf
         -------------------------------------------------
Using /opt/SUNWam/bin/amadmin

Validating configuration information.
Done...

Please enter the LDAP Admin password: 
(nothing will be echoed): password1
Verify: password1
Please enter the JMQ Broker User password: 
(nothing will be echoed): password2
Verify: password2

Retrieving Platform Server list...
Validating server entries.
Done...

Retrieving Site list...
Validating site entries.
Done...

Validating host: http://amhost1.example.com:7001|02
Validating host: http://amhost2.example.com:7001|01
Done...

Creating Platform Server XML File...
Platform Server XML File created successfully.

Creating Session Configuration XML File...
Session Configuration XML File created successfully.

Creating Organization Alias XML File...
Organization Alias XML File created successfully.

Loading Session Configuration schema File...
Session Configuration schema loaded successfully.

Loading Platform Server List File...
Platform Server List server entries loaded successfully.

Loading Organization Alias List File...
Organization Alias List loaded successfully.

Please refer to the log file /var/tmp/amsfoconfig.log for additional
information.
###############################################################
Session Failover Setup Script. Execution end time 10/05/05 13:34:44
###############################################################

  8. Edit the amsessiondb script with the default path and directory of the following:


    JAVA_HOME=/usr/jdk/entsys-j2se/
IMQ_JAR_PATH=/usr/share/lib
JMS_JAR_PATH=/usr/share/lib
BDB_JAR_PATH=/usr/share/db.jar
BDB_SO_PATH=/usr/lib
AM_HOME=/opt/SUNWam

  9. Start and stop the Message Queue instance running on port 7777.

    AccessManager_base/SUNWam/bin/amsfo start

    AccessManager_base/SUNWam/bin/amsfo stop

  10. Restart Access Manager, Directory Server, Application Server 9.1, and Web Server on all the nodes.

  11. Login to the amconsole through Load Balancer.

    http://node3.domain-name:80/amconsole

  12. Stop the Application Server 9.1 on Node 1.

    The session is handled by Access Manager on Node 2.

ProcedureTo Install Portal Server on Node 1

  1. Invoke the Portal Server 7.2 GUI installer and install Portal Server on Node 1 in the Configure Now mode.

  2. Access Portal Server to verify the installation.

    http://node1.domain-name:8080/portal

  3. Create a Portal Server instance on Node 2.

ProcedureTo Create a Portal Server Instance on Node 2

  1. Invoke the Portal Server 7.2 GUI installer on Node 2 and provide the same portal-id as node 1.

  2. The Access Manager SDK will be automatically configured and the installer will detect the portal-id that exists and create an instance of portal.