Prakash

With Portal Server 7.2, the steps to install portal on AS cluster is straight forward. Its just like creating multiple portal instances the only difference being the instances belong to a cluster. The only additional attribute to be set for cluster specific instance is the ClusterID attribute.

All it requires is to create an AS cluster with the required number of instances and create a portal instance for each of the clustered application server instances.

The cluster setup instructions page specifies how to create a simple cluster setup with 2 instances managed by a load balancer.

Adding a new instance to the cluster is also straightforward. Create an application server instance(e.g. newinstance) belonging to the cluster(e.g pscluster). Then create a portal instance pointing to the created appserver instance and the appserver cluster i.e, set WebContainerInstanceName=newinstance and ClusterID=pscluster in the WebContainer.properties.SJSAS91 file and run psadmin create-instance.

In Portal Server 7.2 build 7, the steps to configure glassfish have changed. The following are the new steps:

PS/AM separated Install

Host1:

• Install Directory Server(DS), WebServer7(WS7) or ApplicationServer8.2(AS82) and Access Manager(AM) from JES5
• Start DS and WS7 or AS82 and make sure amconsole is accessible.
  

 Host2:

• Install glassfish and start the default domain(domain1)
• Install AM sdk using the JES5 installer in configure later mode
• Modify the following attributes in AMConfig.properties.template present in AM configuration directory.(Solaris: /etc/opt/SUNWam/config and Linux: /etc/opt/sun/identity/config) as mentioned below:

• com.iplanet.security.SecureRandomFactoryImpl=com.iplanet.am.util.SecureRandomFactoryImpl
• com.iplanet.security.SSLSocketFactoryImpl=netscape.ldap.factory.JSSESocketFactory
• com.iplanet.security.encryptor=com.iplanet.services.util.JCEEncryption

• Modify amsamplesilent appropriately for configuring AM sdk and run ./amconfig -s amsamplesilent
• Restart glassfish after AM sdk configuration is over.
• Install Portal Server 7.2 build7 in configure later mode.
  
• Modify example14.xml with the appropriate values. Make sure the WebContainer details are specified properly and the WebContainerAdminScheme has to be "http" and not "https"
  
• Run ./psconfig --config example14.xml
• After portal configuration is over restart glassfish.

PS and AM on the same box 

• Install glassfish and start the default domain(domain1)
• Install Directory Server from JES5
• Install AM using the JES5 installer in configure later mode
• Modify the following attributes in AMConfig.properties.template present in AM configuration directory.(Solaris: /etc/opt/SUNWam/config and Linux: /etc/opt/sun/identity/config) as mentioned below:

• com.iplanet.security.SecureRandomFactoryImpl=com.iplanet.am.util.SecureRandomFactoryImpl
• com.iplanet.security.SSLSocketFactoryImpl=netscape.ldap.factory.JSSESocketFactory
• com.iplanet.security.encryptor=com.iplanet.services.util.JCEEncryption

• Modify amsamplesilent appropriately for configuring AM and run ./amconfig -s amsamplesilent
• Restart glassfish after AM configuration is over and make sure amconsole is accessible.
  
• Install Portal Server 7.2 build7 in configure later mode.
  
• Modify example14.xml with the appropriate values. Make sure the WebContainer details are specified properly and the WebContainerAdminScheme has to be "http" and not "https"
  
• Run ./psconfig --config example14.xml
• After portal configuration is over restart glassfish.