Sun ONE Portal Server 6.1 Installation for BEA Application Server

Sun™ ONE Portal Server 6.1 software can be deployed on BEA WebLogic Server 6.1 (SP4) using it as its web application container. The Portal Server software uses the web server that is supplied with the WebLogic server.

Familiarity with Sun ONE Portal Server 6.1 Release Notes, Sun ONE Portal Server 6.1 Installation Guide, and Sun ONE Portal Server 6.1 Administrator’s Guide are recommended before using this supplement. The installation information only describes the procedure for installing the Sun ONE Portal Server with default settings and includes the sample desktop.

Overview

The BEA WebLogic server is a Java™ application server that enables deployment of web applications, such as the Sun ONE Portal Server software. WebLogic implements the J2EE™ platform specification and supports servlets, JSPs, Enterprise JavaBeans™ (EJB™), and other platform services. In addition, the WebLogic Server can also act as a fully functional web server to serve up static HTML and image files as well as JSPs and servlets.

When installing the Sun ONE Portal Server software, the script assumes you are using BEA WebLogic. It sets up the appropriate default directories, then creates a number of .war files for the Portal and Identity Server web applications, and deploys them on the WebLogic server. The Portal Server installation script updates the startWebLogic.sh, startManagedWebLogic.sh and config.xml files so that the Portal Server software can work with the WebLogic software.

Since you are using the BEA WebLogic Server, the install script needs to know the application server root (Deploy) directory (/opt/bea/wlserver6.1, the default, WL_HOME in the BEA documentation), the application server Domain (mydomain), the application server instance (myserver), the instance listen port, the WebLogic administration server port, and the password you entered for the administration of the WebLogic Server. The Portal Server installation summary lists the deployment information related to WebLogic.

Hardware and Software Requirements

Before installing the Sun ONE Portal Server software, ensure that your system meets the following requirements:

Hardware Requirements

For a new installation of the software, your system must meet the following minimal hardware requirements:

Software Requirements

The software discussed here is required for a successful installation of the Sun ONE Portal Server software. No other versions of these software products are supported.

Space Requirements

Table B-1 is a three column table. The first column lists the directory, the second column lists the required size, and the third column contains additional comments.

Table B-1 Space Requirements
Directory	Size	Comments
/etc/opt	200 MB
/var/opt	200 MB	Add more for extended logging.
Application server base directory (/opt/bea)	50 MB	If using migration tools.
DS_BASEDIR (/usr/ldap)	300 MB	For Directory Server.
Application server base directory (/opt/bea)	300 MB	For iPlanet Directory Server Access Management Edition.
Application server base directory (/opt/bea)	200 MB	For Portal Server only.
Application server base directory (/opt/bea)	500 MB	For Secure Remote Access on the same machine as the Portal Server software.
S1PSBASEDIR (/opt/bea)	100 MB	For Secure Remote Access support on the machine that has the Portal Server software when the gateway is on a separate machine.

Operating System Requirements

The Sun ONE Portal Server software requires at least a user distribution of the Solaris™ 8 software as the operating system. Solaris 8 requires the following operating system patches as well for a successful installation of the product:

These are the minimum required patches. The last two digits of the patch number are the minor revision number. If updates to the patch have been released, install the most recent patch revision (the one with the higher revision number). Typically, these patches are made obsolete when a new patch is released and only the most recent patch is available at the SunSolve site. Please review the readme for each patch to find out what dependencies or patches may be required.

Pre Portal Installation Tasks

Installing the Portal Server Software

This installation example only gives the procedure for installing the Sun ONE Portal Server with default settings, except for the JDK. It includes the sample desktop. The installation script sets the parameters needed. You supply the WebLogic password and a Portal Server passphrase to complete the install.

The Portal Server installation script changes these WebLogic files to facilitate running the Portal Server software on the WebLogic Server: startWebLogic.sh, startManagedWebLogic.sh, and config.xml.


Note	The search module needs special configuration when the Sun ONE Portal Server is being installed in a WebLogic cluster. Please refer the Sun ONE Portal Server 6.1 Release Notes for this information.



Note	The document root value of DefaultWebApp needs to be deployed to the WebLogic instance you are running the Portal Server software on. DefaultWebApp is the default web application, from which is served static content in a WebLogic server. By default it is only deployed to the domain (mydomain) and the server instance defined or created during the BEA WebLogic install. This means that if you create your own WebLogic domain or server, you need to deploy the DefaultWebApp to it, either by copying the directory to the new server’s deployment directory, or by using the WebLogic admin console. See the BEA documentation for more detail on how to configure a default web application.

The WebLogic Server must be running. Go to the directory where the portal software is, then type the install command:

# ./pssetup

After you have accepted the licensing agreement, select option 1, Install Portal Server.

Select option 2, BEA WebLogic, as the deployment type.

A list of the default values is displayed. The organization, host name, instance name, access URL and deploy instance are based on your machine name and your domain name.

When asked: Use the settings?, type n to change the values as necessary. The values entered for the following questions depend on wether you are installing Sun ONE Portal Server on a managed instance or an administration instance.

What is the application server instance name?

If you are installing Sun ONE Portal Server on an administration server instance this will be the name of the adminserver instance. Otherwise it will be the name of the managed server instance.

What is the Application Server document root?

The document root value of DefaultWebApp needs to be deployed to the WebLogic instance you are running the Portal Server software on. DefaultWebApp is the default web application, from which is served static content in a WebLogic server. By default it is only deployed to the domain (mydomain) and the server instance defined or created during the BEA WebLogic install. This means that if you create your own WebLogic domain or server, you need to deploy the DefaultWebApp to it, either by copying the directory to the new server’s deployment directory, or by using the WebLogic admin console. See the BEA documentation for more detail on how to configure a default web application.

What is Application Server administration port?

If you are installing on an administration server instance your response should be same as the response for the question: What is the admin server port?

Enter a passphrase for the portal server and confirm it.

Enter a value for the Identity Server Internal LDAP Authentication User (amldapuser) password and confirm it.


Note	The password used for the passphrase and the password used for the Identity Server Internal LDAP Authentication User (amldapuser) password can not be the same. If you use the same password for the passphrase and amldapuser password you will be prompted to enter a different password for the amldapuser.


Application Server summary
------------------------
Directory: /opt/bea/wlserver6.1
Domain: mydomain
Instance: psserver
Document Root: /opt/bea/wlserver6.1/config/mydomain/applications/DefaultWebApp
Administration URL: http://myappserver.sesta.com:7001

Directory Server installation summary
-------------------------------------
Base Directory: /usr/ldap
Host: myappserver.sesta.com
Port: 389
Instance: myappserver
Root Suffix: dc=iplanet,dc=com
Directory Manager: cn=Directory Manager
Administrator: admin
Administration Port: 58900

Identity Server installation summary
------------------------------------
Base Directory: /opt/bea
Access URL: http://myappserver.sesta.com:80
JDK Directory: /opt/bea/jdk131

Portal Server installation summary
----------------------------------
Base Directory: /opt/bea
Deployment URI: /portal
Sample Portal: y
Upgrade Mode: n

Use these settings? [y]/n y


Note	To provide UNIX login for your users, configure UNIX authentication in the Portal Server administration console, then stop and restart the amserver: # /etc/init.d/amserver stop # /etc/init.d/amserver start

If you will be supporting multiple authentication methods, for example, LDAP, UNIX, Anonymous, you must add each authentication type to the Core authentication service to create an authentication menu. See the Sun ONE Portal Server 6.1 Administrator’s Guide for further information.

Setting Up Sun ONE Portal Server on BEA Clusters

This section gives a brief description and example of how the Portal Server software can be used with BEA WebLogic clusters.

For our example, there are five machines. All the machines must be on the same subnet. One has a directory server only (DSmach). Another is the WebLogic administration server (AS). There are three cluster machines (CS1, CS2, and CS3). If you want to support load balancing, an additional machine or the administration server machine may be configured as a proxy servlet for load balancing. You may also use a hardware-based load balancer. Load balancing is needed for clusters. In this example, the proxy is on the administration server.

Install the directory server on DSmach. Install BEA WebLogic on all four of the other machines using the default installation. Check that all servers are working correctly.

On the four machines with WebLogic, using the BEA instructions, create a new domain (NEWDOMAIN on all machines) consisting of an administration server with listen port of 7001 (ADMINSERVER on all machines) and another server with a listen port of 80 (PORTALSERVER on all machines). Each listen port should be the same; the example uses 80.

Next install the Portal Server software on the four machines to the managed server instance (PORTALSERVER).


Note	For a cluster, all the machines must be on the same subnet. All BEA instances participating in the cluster must listen on the same port. In order to run the Portal Server software with session failover successfully you need three managed servers running the Portal Server software. Do not run perftune if you are planning on using clusters. SRA does not work with clusters. The BEA proxy does not load balance. All server instances in a BEA cluster must use the same listen port. The new cluster servlet needs to be used for weblogic.servlet.proxy.HttpClusterServlet. Resonate 3.3 cannot load balance a BEA cluster.

Respond n to the question: Use these settings? [y]/n

A list of questions follows.

Accept the default values except for these questions. These questions show the values that need to be changed and important default values. This example is for the WebLogic Administration server. The installation values for the cluster machines is similar.

What is the Application Server domain? [mydomain] NEWDOMAIN

What is the Application Server instance? [myserver] PORTALSERVER

What is the Application Server administration port? [7001]

What port should be used to access the Portal Server? [80]

Use an existing Directory Server? y/[n] y

What is the name of the directory server?[...] DSmach

Answer the questions about the directory server appropriately.

Stop and restart all the servers (the Portal Server, the managed server and the administration server) on all the machines.

Check and see that the installations were successful.

By default, Identity Management is selected in the location pane and All created organizations are displayed in the navigation pane.

Choose Service Configuration in the location pane.

Click on the Properties arrow next to Platform in the navigation pane.

Check that the Server List has the full-ps-servername for the machine you plan to put the proxy on. In our example, the machine is http://AS.sesta.com:80.

Click Save.

Using the admin console of the admin machine AS (http://AS:7001/console), create a server for each of the machines to be in the cluster.

Select Servers, configure new Server.

Use the machine name for the new servername: CS1, CS2,and CS3.

Stop all the servers on the machines to be in the cluster.

Restart those servers, but have them connect to the admin server AS. For example,

# ./startManagedWebLogic.sh CS1 AS:7001

Using the admin console of the admin machine AS (http://AS:7001/console), create the cluster.

Select Clusters, Configure a new Cluster.

For Name, the example uses NEWCLUSTER.

For Address, put in the names for the servers representing the machines to be clustered: CS1,CS2,CS3.

Inside this same window, select the Servers tab, then select the servers CS1, CS2, and CS3; move them from the Available box to the Chosen box.

Check to see that cluster is set up correctly by going the WebLogic administration console, selecting Cluster in the left pane, selecting the Monitoring tab in the right pane, then select Monitor server participation in cluster. If one or more of the started server instances does not appear in the display, use the BEA tool to verify the correct multicast addresses and port numbers.


Note	If you want to start and stop the WebLogic managed servers remotely from the administration console, you need to configure and run a BEA Node Manager. See the BEA documentation for detailed information.

If you are going to use a proxy servlet for load balancing, create a web.xml file for your cluster to use to configure the load balancing servlet. Using a temporary directory make a subdirectory WEB-INF. The web.xml file is the only file in a directory (WEB-INF). Use the fully qualified machine names in the file.

Code Example 1 Sample web.xml File


<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.
//DTD Web Application 2.2//EN"
"http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">

<web-app>

<servlet>
<servlet-name>HttpClusterServlet</servlet-name>
<servlet-class>
weblogic.servlet.proxy.HttpClusterServlet
</servlet-class>

<init-param>
<param-name>WebLogicCluster</param-name>
<param-value>
CS1.domain.COM:80:7002\|CS2.domain.COM:80:7002\|CS3.domain.COM:80:7002
</param-value>
</init-param>

</servlet>

<servlet-mapping>
<servlet-name>HttpClusterServlet</servlet-name>
<url-pattern>/</url-pattern>
</servlet-mapping>

<servlet-mapping>
<servlet-name>HttpClusterServlet</servlet-name>
<url-pattern>*.jsp</url-pattern>
</servlet-mapping>

<servlet-mapping>
<servlet-name>HttpClusterServlet</servlet-name>
<url-pattern>*.htm</url-pattern>
</servlet-mapping>

<servlet-mapping>
<servlet-name>HttpClusterServlet</servlet-name>
<url-pattern>*.html</url-pattern>
</servlet-mapping>

</web-app>

Make web.xml with your cluster server values into a .war file (jar cvf proxy.war WEB-INF). Deploy it on the WebLogic administration server using the java weblogic.deploy command supplied by the WebLogic server software. In the WebLogic administration console on the administration server, expand Servers and select PORTALSERVER:80, and click the HTTP tab. Set the Default Web Application to the proxy. Restart the PORTALSERVER server. Or after making the .war file, copy the .war file to the applications directory in the NEWDOMAIN on the administration machine (AS). Select Web Applications, click Configure a new Web Application, enter proxy as the Name and give the complete path to the .war file. Click Create. In the left pane under Web Applications, click proxy; in the right pane, click the Target tab, and move PORTALSERVER from the Available box to the Chosen box.

Next you need to deploy the Portal Server software to the cluster. So for each web application (amconsole, amserver and portal) follow these steps.

Go to the WebLogic administration console for the administration server (AS:7001/console).

Expand Web Applications in the left pane, then select one of the Portal Server software web applications (amconsole, amserver and portal).

Undeploy the admin server (you have installed Portal on the PORTALSERVER server, but it is not part of the cluster, so now you remove it from this server).

Select the Target tab, then the Servers sub-tab.

Move your server name from Chosen to Available box and click Apply.

Click the Edit Web Application Descriptor link; click the Configure a new Web App Ext Descriptor link.

In the left pane under WebApp Ext, Select Session Descriptor.

In the right pane, change Persistent Store Type to replicated. Click Apply.

Select top topic in the left pane, Web Descriptor or iDSAME Services. Select Persist. Close this window.

Select the Target tab, then the Cluster sub-tab.

Move your cluster name (NEWCLUSTER) from Available to Chosen box and click Apply.

For each of the three Portal Server machines, go to the /opt/bea/SUNWam/lib directory and open the AMConfig.properties files with a text editor.

Set the following values on all the machines:

com.iplanet.am.session.failover.enabled=true

com.iplanet.am.replica.enable=true

com.iplanet.am.naming.url=http://AS.sesta.com:80/amserver/namingservice

com.iplanet.am.notification.url=http://AS.sesta.com:80/amserver/notificationservice

com.iplanet.am.session.server.host=AS.sesta.com

com.iplanet.am.server.host=ASNMS.sesta.com

com.iplanet.services.cdsso.CDCURL=http://AS.sesta.com:80/amserver/cdcservlet

com.iplanet.services.cdc.authLoginUrl=http://AS.sesta.com:80/amserver/login

Stop and restart all the servers. For the managed servers, on each machine, type:

# ./startManagedWebLogic.sh managed-servername http://AS.sesta.com:80

Check to see if all is working well.

Appendix B Sun ONE Portal Server 6.1 Installation for BEA Application Server