Sun ONE logo     Previous      Contents     
Sun ONE Portal Server 6.0 Installation Supplement for BEA Application Server


Sun™ ONE Portal Server 6.0 Installation Supplement for BEA Application Server

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

This supplement contains the following sections:

Familiarity with Sun ONE Portal Server 6.0 Release Notes, Sun ONE Portal Server 6.0 Installation Guide, and Sun ONE Portal Server 6.0 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.

About This Document

This section provides details about this document. It contains the following topics:

Typographic Conventions

This table has three columns. The first column displays the typeface; the second column describes where that typeface is used, in other words its meaning; and the third column gives examples. Following the table, there are more detailed explanations about the different typefaces.

Typeface

Meaning

Examples

AaBbCc123

 

The names of commands, files, and directories; on-screen computer output

 

Edit your .login file.

Use ls -a to list all files.

machine_name% You have mail.

 

AaBbCc123

 

What you type, when contrasted with on-screen computer output

 

machine_name% su

Password:

 

AaBbCc123

 

Book titles, new words or terms, words to be emphasized or glossary terms.

 

Read Chapter 6 in the User's Guide.

These are called class options.

You must be superuser to do this.

 

AaBbCc123

 

Command-line variable; replace with a real name or value

 

To delete a file, type rm filename.

 


Note

The settings on your web browser may differ from these.

Monospaced Font

Monospaced font is used for any text that appears on the computer screen or text that you should type. It is also used for file names, distinguished names, functions, and examples.

Bold Monospaced Font

Bold monospaced font is used to represent text within a code example that you should type. For example, you might see something like this:

$ dpadmin list -n TemplateTableContainer -u "uid=amAdmin,ou=people,o=sesta.com,o=isp" -w joshua -d "o=sesta.com,o=isp"

In this example, dpadmin list is what you would type on the command line to list part of a display profile.

Italicized Font

Italicized font is used to represent text that you enter using information that is unique to your installation (for example, variables). It is used for server paths and names and account IDs.

Square or Straight Brackets

Square (or straight) brackets [] are used to enclose optional parameters. For example, in this document you will see the usage for the par command described as follows:

par import -r uid -p password  -a [-d] [-v] parfile [dn|global]

The presence of [-d], [-v], and [dn|global] indicates that there are optional parameters that may be added to the par command.

Command-Line Prompts

Command-line prompts (for example, % for a C-Shell, or $ for a Korn or Bourne shell) vary according to the operating system environment you are using. However, you should enter the command as it appears in the document unless specifically noted otherwise.

What is New in the Sun ONE Portal Server 6.0 Software to Run on the BEA WebLogic Server

This section summarizes enhancements implemented in Sun ONE Portal Server 6.0 software so that it can be deployed on the BEA WebLogic Server.

The visible changes are in the Portal Server install script. 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.

Overview of Products

A portal is a doorway or entry point to an aggregate of pieces of information. What the end user sees when visiting a portal is a set of HTML pages called a desktop. This desktop is made up of an aggregate of channels. Each channel displays a specific type of information. A channel is an area on the portal desktop; it can be small area showing something like stock quotes, it can be a container that aggregates other channels, or it can be the complete page.

The Sun ONE Portal Server 6.0 software provides a portal that is flexible, versatile, customizable, and extensible. An administrator can manage users and content from a single administration console. The administrator can choose how a user logs in and what a user sees. The organization a user belongs to and what a user's role is determine what content is visible to a user, as well as what services and applications are available. The content may be a mix of XML, HTML, RSS, WSDL, and JavaServer Pages™ (JSP™) or something that the administrator has created by extending the public APIs.

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.

Hardware and Software Requirements

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

  • Hardware Requirements

  • Software Requirements

  • Operating System Requirements, including patches

Hardware Requirements

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

  • 1 450 MHz CPU or better

  • 512 Mbytes of RAM

  • 1 Gbyte of hard drive swap space

  • 1 Gbyte of disk space

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.

  • BEA WebLogic Server 6.1 (SP2)

  • iPlanet™ Directory Server 5.1, included in the Portal Server installation

  • Java™ Development Kit (JDK™) 1.3.1_04, included in the Portal Server installation

  • iPlanet™ Directory Server Access Management Edition 5.1a, included in the Portal Server installation
    Note

    iPlanet Directory Server Access Management Edition 5.1a is also known as Sun ONE Identity Server 5.1. For online documentation, see http://docs.sun.com/db/coll/S1_s1IdServ_51.

Space Requirements

These requirements are the ones that are checked for in the Portal Server installation script.

Table 1    Space Requirements

Directory

Size

Comments

/etc/opt

 

200 MB

 

 

 

/var/opt

 

200 MB

 

Add more for extended logging.

 

/usr

 

50 MB

 

If installing JDK 1.3.1_04.

 

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.

 

BASEDIR (/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:

  • 109326-03

  • 108434-03

  • 108827-15

  • 112438-01

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.

Installing BEA WebLogic Server

The BEA WebLogic Server needs to be installed before you install the Portal Server software.

Note

The WebLogic server must be an administration server not a managed server.


Use the standard WebLogic install instructions.

Note the values you enter during the install.

To start the install, go to the directory where the BEA installer is and as root type:

# ./weblogic610sp2_sol.bin

When installing WebLogic to run with the Portal Server software, enter the following values that are different from the WebLogic defaults.

  1. On the Choose BEA Home Directory screen, enter:

    2. /opt/bea

  2. On the Choose Product Directory Screen, enter:

    3. /opt/bea/wlserver6.1

  3. On the Default Server Configuration screen, change the Listen Port from 7001 to 80.


    4. Note

    If you want to retain 7001 as the listen port, the Access URL for the Portal Server must be 7001. In other words, these port numbers must be the same. See Step 4 in the Installing the Portal Server Software section.

  4. On the Create System Password screen, enter a Password, then confirm the Password. Keep a record of this as you need the password for the Portal Server installation.

  5. Start the WebLogic Server. It needs to be running when you install the Portal Server software. As root, go to the /opt/bea/wlserver6.1/config/mydomain directory and type:

    6. # ./startWebLogic.sh

  6. Enter the password you selected earlier to complete the server start up.


    7. Caution

    Do not close this window or type control-c. Closing the terminal window that you started the WebLogic Server in or typing control-c in that terminal window will kill the WebLogic Server.

  7. Check to see that the BEA WebLogic Server installed correctly and is running. Start the WebLogic console. In a web browser, enter:

    8. http://full-hostname:listen-port/console

    If you are running the browser on the WebLogic server, use:

    http://localhost:listen-port/console


    Note

    Create a backup copy of the startWebLogic.sh, startManagedWebLogic.sh and config.xml files since the Portal Server installation script updates these files so the Portal Server software can work with the WebLogic software.

Pre Portal Installation Tasks

This setup is needed in WebLogic before installing the Portal Server software so the documentation link works.

Installing the Portal Server software on a WebLogic managed server in a domain created by the WebLogic Installer:

  1. In WebLogic admin console left pane, expand Web Application.

  2. Select DefaultWebApp.

  3. In the right pane, select the Targets tab.

  4. Select the Servers tab and move the server to the Chosen box.

  5. Click Apply.

  6. Expand the Servers in the left pane.

  7. Select the appropriate server.

  8. In the right pane, select the General tab

  9. Select the HTTP tab (If you are configuring a virtual host, select the General tab instead.).

  10. Select DefaultWebApp from the drop-down list labeled Default Web Application.

  11. Click Apply.

  12. Stop and restart WebLogic servers.

Installing the Portal Server software on a managed server or admin server in WebLogic domain that was NOT created by the WebLogic:

  1. Copy the BEA-HOME/wlserver6.1/config/domain-created-by-installer/applications/DefaultWebApp

    2. to

    BEA-HOME/wlserver6.1/config/current-weblogic-domain/applications/DefaultWebApp

  2. Deploy the DefaultWebApp into the current domain using the command:

    3. JAVA-HOME/bin/java -classpath BEA-HOME/wlserver6.1/lib/weblogic.jar weblogic.deploy -url adminserver-protocol://adminserver-host:adminserver-port -component DefaultWebApp:server-name deploy admin-password DefaultWebApp BEA-HOME/wlserver6.1/config/current-weblogic-domain/applications/DefaultWebApp

  3. In the WebLogic admin console left pane, expand Servers.

  4. Select the appropriate server.

  5. In the right pane, select the General tab.

  6. Select the HTTP tab (If you are configuring a virtual host, select the General tab instead.)

  7. Select DefaultWebApp from the drop-down list labeled Default Web Application.

  8. Click Apply.

  9. Stop and restart the WebLogic servers.

No setup needed if installing on adminserver of domain created by WebLogic installer.

Installing the Portal Server Software


Note

The DocRoot value of DefautlWebApp 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 (myserver) 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 DefautlWebApp 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.

After you download the software, unzip it and run the tar extract command. For the Sun ONE Portal Server 6.0 for BEA, type:

# gunzip -dc ps-6.0-bea-us.sparc-sun-solaris8.tar.gz | /usr/bin/tar xvf -

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

These instructions are for installing the Portal Server software on a WebLogic administration server. You can install the Portal Server software on a managed server.

If you want to use the search function on the Portal Server software, it must be installed on an administration server. The search function does not work on a managed server or in a cluster without a special configuration. See the Known Problems and Limitations section for this information.

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

    2. # ./pssetup

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

    3. A listing of the defaults is displayed. The Organization, Host, Instance, Access URL and Deploy Instance are based on your machine name and your domain name.

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

    4. A list of questions follows.

    Note

    The Portal Server software must be installed into the BEA home directory.

  4. Accept the default values except for these questions:

    1. What is the Application Server administration port? [7001] 80

      2. This is the Application Server listen port. You set it in Step 3 in the Installing BEA WebLogic Server section. Enter the port number you set earlier. It must match the port to access the Portal server (see Step d).

    2. What is the password for the Application Server administrator? Again?

      3. Enter and confirm the password you selected for BEA WebLogic.

    3. Do you want the Application Server to run with JDK 1.3.1_04? [y]/n

      4. Respond y to this question. This causes the installation script to install JDK 1.3.1_04 in the /usr/java_1.3.1_04 directory.

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

      5. Enter the same port you selected as the listen port when installing BEA WebLogic.


      Note

      If you want to retain 7001 as the listen port, the Access URL for the Portal Server must be 7001. In other words, these port numbers must be the same. Set the Access URL to 7001.

    5. What is the passphrase for this server? Again?

      6. Enter and confirm the passphase you want the Portal Server administrator (amadmin) to use. If you choose to install a directory server with the Portal Server installation, use this passphrase to access it.

  5. After all of the questions have been answered, a list of the values is displayed. If these values are correct, respond y to the question: Use these settings? [y]/n

JDK installation summary
------------------------
Directory: /usr/java_1.3.1_04

Directory Server installation summary
-------------------------------------
Base Directory: /usr/ldap
Organization: sesta.com
Host: myappserver.sesta.com
Port: 389
Instance: myappserver
Root Suffix: o=isp
Directory Manager: cn=Directory Manager
Administrator: admin
Administration Port: 8900

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

Portal Server installation summary
----------------------------------
Deployment Type: WEBLOGIC
Deployment Directory: /opt/bea/wlserver6.1
Deploy Domain: mydomain
Deploy Instance: myserver
Base Directory: /opt/bea
Deployment URI: /portal
Sample Portal: y

Use these settings? [y]/n y

The install script finishes installing the Portal Server.

  1. Check the /var/sadm/install/logs/pssetup.pid/setup.log file for errors.

  2. Return to the WebLogic console. Right click on the server and select Stop this server...

  3. In the terminal window you started WebLogic in, restart WebLogic by typing:

    4. # ./startWebLogic.sh

  4. Test the portal server installation by launching the portal desktop in a browser by using:

    5. http://full-hostname:listen-port/portal/dt

    If the sample desktop displays without any exception showing in the WebLogic command window, then your Portal Server installation is good.


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.0 Administrator's Guide for further information.

Configuring UNIX Authentication for the Organization Level

The UNIX authentication documented in the Sun ONE Portal Server 6.0 Administrator's Guide is for configuring UNIX globally. This procedure is to configure at the organization level.

  1. Log in to the iPlanet Directory Server Access Management Edition (DSAME) administration console as administrator (amadmin) by entering http://fullservername:port/amconsole in your browser's web address field.

  2. At the logon screen, enter userid of amadmin and the passphrase you chose during installation.

  3. By default, when you log in, User Management is selected in the View menu, and Organizations are selected in the Show menu. All created organizations are displayed in the navigation.

  4. Navigate to the organization or suborganization that you want to configure authentication for.

  5. Choose Services from the Show menu.

  6. Select Register.

  7. Check UNIX in the right pane and click Register.

  8. Select the properties arrow next to UNIX.

  9. Select Create in the right pane.

  10. Set the appropriate UNIX Attributes for your server.

  11. Select Save.

  12. Select the properties arrow next to Core.

  13. Highlight UNIX in Authentication Menu and select Save.

Installing Secure Remote Access

After you download the software, unzip it and run the tar extract command. For the Sun ONE Portal Server 6.0 with Secure Remote Access (SRA) for BEA, type:

# gunzip -dc ps-sra-6.0-bea-us.sparc-sun-solaris8.tar.gz | /usr/bin/tar xvf -

Follow the instructions in the Sun ONE Portal Server, Secure Remote Access 6.0 Installation Guide to install Secure Remote Access.

  1. Go to the directory where the portal software is, then type the install command:

    2. # ./pssetup

    1. When installing the Portal Server software portion, make the same selections as described in the Installing the Portal Server Software section.

    2. After installing the Portal Server software, stop and restart the WebLogic server before installing the gateway.

    3. When installing the gateway on the same server as the Portal Server software, the base directory can be anything; using the /opt/bea directory as the base directory is not necessary.

    4. After installing the gateway, you need to restart the Portal Server and the gateway.

Some of the files are placed in different directories when using Secure Remote Access with the BEA WebLogic Server software.

The rewriter samples are accessed from a web browser using portal_server_URL/portal/samples/rewriter. These samples are described in the Sun One Portal Server, Secure Remote Access Administrator's Guide, which lists their location as portal_server_URL/rewriter.

The MIME types configuration file is now in the InstallDir/SUNWps/samples/config/netfile directory. In a Portal Server installation not using the WebLogic software, the MIME type configuration file is in the InstallDir/SUNWam/servers/instance_name/config directory.


Note

The WebLogic console is not accessible through the gateway.

The SRA gateway and SRA NetFile do not work if the Portal Server software is configured for session failover.

Setting Up SSL for the Java Secure Socket Extension Socket Factory

Follow the instructions provided in the BEA WebLogic Server documentation to set up SSL. Follow these steps either before (preferably) or after installing the Portal Server software. You need to do this procedure if you want to connect to a secure directory server.

  1. Go to the directory where you have the Portal Server software. Go to subdirectory idsame/SUNWamws/reloc/$PRODUCT_DIR/ (to get to this subdirectory go to idsame/SUNWamws/reloc and type cd \$PRODUCT*).

  2. Copy the iWS6.0.tar file to some temporary directory and expand the tar file.

  3. Install the iPlanet™ Web Server 6.0 by going to the temporary directory with the expanded tar file and typing:

    4. # ./setup

  4. Respond yes to accept the license agreement.

  5. Accept the default values except for these:

    1. Use one of the already installed Java libraries (for example, /usr/java_1.3.1_04 if Portal Server software is already installed).

    2. The default port for the web server is 8888, you can use that or any free port.

    3. If the Portal Server software is already installed, port 80 will already be in use, so use another free port (81).

    4. The default administrator's name is admin; take note if you change it.

    5. Enter a password; you will use it later.

  6. Create the servers subdirectory by typing:

    7. # mkdir /opt/bea/SUNWam/servers

  7. After the installation is complete, go to the /usr/iplanet/servers/https-admserv directory and type:

    8. # ./start

  8. This starts the console, so you can log in from a web browser pointed to

    9. http://myserver.sesta.com:8888

  9. Select the Security tab.

  10. Initialize the Trust Database. Enter and confirm a password. Click OK.

    11. The web server creates a number of certificates.

  11. Select Install Certificate in the left pane and install the appropriate certificates.

  12. In a terminal window, go to the /usr/iplanet/servers directory and type:

    13. # tar cvf cert.tar alias

    This tar file contains all the certificates for all your instances.

  13. Copy cert.tar to a safe directory and also to the /opt/bea/SUNWam/servers directory.

  14. In the /opt/bea/SUNWam/servers directory, type:

    15. # tar xvf cert.tar

    The certificate directory is ready for the Portal Server software to use.

  15. Go to the /usr/iplanet/servers directory and uninstall the web server by typing:

    16. # ./uninstall

  16. Choose what components you want to uninstall (probably not the Java library).

  17. Complete the uninstall by manually removing the remaining web server files.

  18. Stop and restart all the servers.

When you need a certificate database for an instance, copy and expand the cert.tar file. Update each certificate with the correct server name.

For more detailed information on SSL configurations, see the Configuring Secure Sockets Layer (SSL) section of Chapter 11, Managing the Sun ONE Portal Server System, in the Sun ONE Portal Server 6.0 Administrator's Guide.

Setting Up LDAP Replication for a Portal Server

The main reason for using LDAP replication for your Portal Server software is to provide higher availability.

This procedure requires that you install the iPlanet Directory Server 5.1 software on all the machines you want to use for replication, then set up the replication. Next, you install the WebLogic and Portal Server software. The WebLogic and Portal software can be installed on the machines to be used for replication or on separate machines. Before using the Portal Server software, you need to update a number of configuration files.

The following instructions are for setting up two machines: one machine with Portal Server software (ps-server) including LDAP and one machine with just LDAP (x-ldap-server). Replication is set up between the two machines and LDAP failover is set up on the machine with the Portal Server software.

For more details and other replication set ups, see Chapter 8, Managing Replication in the iPlanet Directory Server 5.1 Administrator's Guide.

These instructions assume that the default values are used except where specifically noted.

On both machines, install the directory server.

  1. In a terminal window on the machine that will have the Portal Server installation, as root, go to the directory where the Portal Server software is and type:

    2. # ./pssetup

  2. Select 2, Install Directory Server only.

  3. Remember the passphase.

Setting Up Replication on the Portal Server Machine

  1. As root, in a terminal window start the directory server console by typing:

    2. # /usr/ldap/startconsole

  2. In the login window that is displayed, enter admin as the user name and the passphrase you choose earlier.

  3. In the left pane of the console, expand the directory.

  4. Select Directory Server (ps-server).

  5. In the right pane, click Open.

    6. A pop-up window is displayed.

  6. Select the Configuration tab.

  7. Expand Replication in the left pane.

  8. Select Replication.

  9. Check Enable Changelog check box in the right pane.

  10. Click Use default button in the right pane.

    11. The default directory value is entered in the Changelog database directory text field.

  11. Click Save.

  12. Select userRoot in the left pane.

  13. Check Enable Replica check box in the right pane.

  14. Select Multiple Master.

  15. Enter a number (1-255) in the Replica ID box. This number needs to be unique for each master.

  16. Click Save.

  17. In the tool bar, click Object and select New Replication Agreement.

  18. Enter a name (you can use the name of the x-ldap-server) for the replication agreement. Add a brief description.

  19. Click Next.

  20. Select Other and insert the fully qualified distinguished name of the machine to be connected to with the port number (default 389).

  21. Click OK.

  22. For Bind as, use cn=Directory Manager and insert the password for the directory server on the x-ldap-server machine being connected to.

  23. Click Next.

  24. Click Next again.

  25. Select Do Not Initialize Consumer and click Next.

    26. The replication agreement is displayed.

  26. Click Done if it is correct.

  27. Click OK.

Setting Up Replication on the Dedicated LDAP Machine

  1. As root, in a terminal window start the directory server console by typing:

    2. # /usr/ldap/startconsole

  2. In the login window that is displayed, enter admin as the user name and the passphrase you chose earlier.

    3. The console is displayed.

  3. In the left pane of the console, expand the directory.

  4. Select Directory Server (x-ldap-server).

  5. In the right pane, click Open.

    6. A pop-up window is displayed.

  6. Select the Configuration tab.

  7. Expand the Replication in the left pane.

  8. Select Replication.

  9. Check Enable Changelog check box in the right pane.

  10. Click Use default button in the right pane.

    11. The default directory value is entered in the Changelog database directory text field.

  11. Click Save.

  12. Select userRoot in the left pane.

  13. Check Enable Replica check box in the right pane.

  14. Select Multiple Master.

  15. Enter a number (1-255) in the Replica ID box. This number needs to be unique for each master.

  16. Click Save.

  17. In the tool bar, click Object and select New Replication Agreement.

  18. Enter a name (you can use the name of the ps-server) for the replication agreement. Add a brief description.

  19. Click Next.

  20. Select Other and insert the fully qualified distinguished name of the machine to be connected to with the port number (default 389).

  21. Click OK.

  22. For Bind as, use cn=Directory Manager and insert the password for the directory server on the ps-server machine being connected to.

  23. Click Next.

  24. Click Next again.

  25. Select Initialize consumer now and click Next.

    26. The replication agreement is displayed.

  26. Click Done if it is correct.

  27. Click OK.
    Note

    To check replication status, select the Status tab. Select Replication Status in the left pane. The right pane displays the name of your replication agreement. You may need to click the Refresh button if you are using multiple replication agreements.

  28. In this set up the Portal Server machine's LDAP is a consumer of this LDAP and this LDAP is a consumer of the Portal Server machine's LDAP. So for each additional consumer Portal Server machine, repeat Steps 20 to 30.

  29. Stop each LDAP that has been initialized (Step 25), then restart. For example, log into the supplier machine (ps-server) as root and type:

    30. # /usr/ldap/slapd-servername/stop-slapd
    # /usr/ldap/slapd-servername/start-slapd


    Note

    To check replication on the consumer, start the directory server console, expand the directory in the left pane and select Directory Server. Click Open and select the Directory tab on the pop-up window. Expand the entry for the root suffix (default isp). Note that there are few nodes. After installing BEA WebLogic and Portal Server software, and starting replication, check isp again. If replication is set up correctly, there should be many nodes.

Adding More Suppliers

When making the replication agreements, each master must have an agreement with every other master. Any supplier you initialize, you need to restart.

Configuring the Portal Server Software

These instructions assume that the default values are used excepted where specifically noted.

  1. Install BEA WebLogic Server. Follow the install instructions in the Installing BEA WebLogic Server section.

  2. Install the Portal Server software as described in the Installing the Portal Server Software section with the following changes:

    1. Do not accept the default values.

      2. A series of questions about installation values are asked.

    2. Respond to the question:

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

    3. Respond to the question:

      4. What is the directory manager password?

      by typing the password for the directory server on this machine and confirming it.

  3. After the Portal Server software is installed, return to the WebLogic console. Right click on the server and select Stop this server...

  4. Stop and restart the amserver.

    5. # /etc/init.d/amserver stop

    # /etc/init.d/amserver start

  5. In the terminal window you started WebLogic in, restart WebLogic by typing:

    6. # ./startWebLogic.sh

  6. Test the portal server installation by launching the portal desktop in a browser by using:

    7. http://full-hostname:listen-port/portal/dt

    If the sample desktop displays without any exception showing in the WebLogic command window, then your Portal Server installation is good.

  7. Go to the BASEDIR/config/ums/serverconfig.xml file (the default is /opt/bea/SUNWam/config/ums/serverconfig.xml). Set the configuration to point to the local LDAP.

    1. Copy the Server1 line right below itself.

    2. Edit the lines so they have these values:

      3. <Server name="Server1" host="full-ps-servername" port="389" type="SIMPLE" />

      <Server name="Server2" host="x-ldap-fullservername" port="389" type="SIMPLE" />

    3. If you have multiple suppliers, add similar lines for each one.

      4. <Server name="Server3" host="x-ldap-fullservername2" port="389" type="SIMPLE" />

  8. Go to the BASEDIR/lib/AmConfig.properties file (the default is /opt/bea/SUNWam/lib/AmConfig.properties).

    1. Check that this line is correct:

      2. com.iplanet.am.directory.host=full-ps-servername

    2. Change com.iplanet.am.replica.enable=false to com.iplanet.am.replica.enable=true.

    3. If appropriate, change com.iplanet.am.session.failover.enabled=false to com.iplanet.am.session.failover.enabled=true

  9. Return to the WebLogic console. Right click on the server and select Stop this server...

  10. Stop and restart the amserver.

    11. # /etc/init.d/amserver stop

    # /etc/init.d/amserver start

  11. Restart WebLogic server. In a terminal window, as root, go to the /opt/bea/wlserver6.1/config/mydomain directory and type:

    12. # ./startWebLogic.sh

  12. Log into the Portal Server administration console with user name amadmin and the passphrase you entered during the installation.

  13. Select User Management in the View menu and click on the organization name link in the navigation pane.

  14. Select Services in the Show menu.

  15. Click on the Properties arrow next to LDAP Authentication in the navigation pane.

  16. Check that the Primary LDAP box only has the full-ps-servername listed. If you have multiple LDAP servers, the Primary LDAP box should list localhost or full-ps-servername|full-ps-servername:389.

  17. To the Secondary LDAP box Add the x-ldap-fullservername to the list.

  18. Click Save to save the configuration.

  19. If you have a number of Portal Server installations, complete Step 20 to Step 24. If not, you are finished.

  20. Return to the root level by clicking root suffix (default isp) in the location pane.

  21. In the View menu, select Service Management.

  22. Click on the Properties arrow next to Platform.

  23. Check that the Server List has all of the Portal Server machines listed using the full-ps-servername for each server.

  24. Click Save.

Using BEA Clusters

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

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.

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

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

    2. A list of questions follows.

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

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

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

  4. Check and see that the installations were successful.

  5. Log into one of the Portal Server administration consoles for a machine that will be part of the cluster.

  6. In the View menu, select Service Management.

  7. Click on the Properties arrow next to Platform.

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

  9. Click Save.

To set up a cluster:

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

    1. Select Servers, configure new Server.

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

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

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

    4. # ./startManagedWebLogic.sh CS1 AS:7001

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

    1. Select Clusters, Configure a new Cluster.

      2. For Name, the example uses NEWCLUSTER.

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

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

For more detail, see the BEA WebLogic instructions to set up a cluster.

As you set up clusters remember the following:

  • Stop and restart all the servers each time you change the cluster configuration.

  • Set up your cluster on the administration server (AS) machine in the NEWDOMAIN ADMINSERVER WebLogic admin console.

  • Use the BEA tool to test for multicasting.

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.

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

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

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

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

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

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

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

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

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

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

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

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

  10. Set the following values on all the machines:

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

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

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

  12. Check to see if all is working well.

Migration Issues

The migration from iPlanet™ Portal Server 3.0 (also known as Sun ONE Portal Server 3.0) SP3a or SP4 to Portal Server 6.0 is documented in the Sun ONE Portal Server 6.0 Migration Guide. Follow the instructions in that guide. After installing the WebLogic Server and the Portal Server software, there are a few additional tasks that you must do so that your migrated Portal Server will run on the Weblogic Server.

The 3.x iPlanet Web Server Certificates are not migrated to the Application Server.

The 3.x iPlanet Gateway Certificates are not migrated. This is to be handled by an SRA Migration Module (not yet delivered).

Since WebLogic is the host for the Portal web applications, all 3.x document root or public html files are migrated as a web application. The 3.x document root files are migrated to a directory named SunONEPublicHtml (this is WebLogic specific). You, the migrator, need to deploy and assign it as the Default Web Application.

  1. Run the importps utility to import the converted data. The utility discovers and uses the correct directories. It puts the 3.x document root or public_html files in:

    2. $DEPLOY_DIR/config/$DEPLOY_DOMAIN/applications/SunONEPublicHtml

    For example, the default values are:
    $DEPLOY_DIR=/opt/bea/wlserver6.1
    $DEPLOY_DOMAIN=mydomain

    So the files are in this directory:

    /opt/bea/wlserver6.1/config/sun/applications/SunONEPublicHtml

    Note

    You must check the contents of the SunONEPublicHtml directory. There needs to be a web.xml file in the WEB-INF subdirectory. If there are any symbolic links, be sure that they all have valid targets; if not, remove them.

  2. Deploy the SunONEPublicHtml files as a Web Application by typing this command:

    3. $JAVA_HOME/java -classpath $BEA_JAR weblogic.deploy -host $HOST -port $PORT -component $WEB_APPLICATION_NAME:$MANAGED_SERVER_NAME deploy $PASSWORD $WEB_APPLICATION_NAME $WEB_APPLICATION_DIRECTORY

    For example, the default values are:
    $JAVA_HOME= /usr/java_1.3.1_04/bin
    $BEA_JAR=/opt/bea/wlserver6.1/lib/weblogic.jar
    $HOST=    fully-qualified-servername of server with WebLogic and Portal software
    (example server is myappserver.sesta.com)
    $PORT=80 the WebLogic listen port
    $WEB_APPLICATION_NAME=name
    $MANAGED_SERVER_NAME=myserver
    $PASSWORD=    password for WebLogic Server
    $WEB_APPLICATION_NAME=name Same name as above.
    $WEB_APPLICATION_DIRECTORY=/opt/bea/wlserver6.1/config/mydomain/applications/SunONEPublicHtml

    Using the default values, the command is

    /usr/java_1.3.1_04/bin/java -classpath /opt/bea/wlserver6.1/lib/weblogic.jar weblogic.deploy -host myappserver.sesta.com -port 80 -component name:myserver deploy password name /opt/bea/wlserver6.1/config/mydomain/applications/SunONEPublicHtml

  3. Start the WebLogic console. In a web browser, enter:

    4. http://full-hostname:listen-port/console

    If you are running the browser on the WebLogic server, use:

    http://localhost:listen-port/console

  4. In the left pane, expand Servers and choose your server (the default is myserver).

  5. In the right pane, select the HTTP tab.

    6. Expand the Default Web Application list and select SunONEPublicHtml.

  6. Click Apply.

  7. In the left pane, right click on the server and select Stop this server...

  8. In the terminal window you started WebLogic in, restart WebLogic by typing:

    9. # ./startWebLogic.sh

Known Problems and Limitations

Here is a list of current bugs with workarounds. This is a three column table. The first column lists the bug IDs; the second column describes the bug; and the third column provides the available workarounds.

Table 2    Current Bugs

Bug ID

Description

Workarounds

4769605

 

SRA - Not able to create multibyte profile in gateway admin console

 

No workaround.

 

4766421

 

SRA - WebLogic console not accessible through the gateway.

 

Do not access the console via the gateway. This will not be fixed.

 

4777450

 

SRA rewriter does not work with BEA clusters.

 

When configuring the Rewriter proxy and SRA with the Portal Server software on a BEA cluster, for the gateway, the Portal Server instances in the cluster should be mentioned in the Portal Server server list and the gateway should not point to the proxy servlet of the cluster (proxy.war in the example).

 

4778433

 

Receive a 404 error when log into Portal Server administration console when using SSL for a cluster.

 

All the instances in the cluster must use the same listen port.

 

4778463

 

BEA proxy does not load balance.

 

All server instances in a BEA cluster must use the same listen port. The new cluster servlet (proxy.war in the example) needs to be used for weblogic.servlet.proxy.HttpClusterServlet.

 

4778466

 

Resonate 3.3 can not load balance a BEA cluster.

 

Use a different load balancer.

 

4778391

 

In a cluster, the administration console URL should not be rewritten.

 

All server instances in a BEA cluster must use the same listen port.

 

4783837

 

Garbage collection grows until response time is impaired.

 

Upgrading to BEA WebLogic 6.1 SP 4 and JVM 1.3.1_06 solves this memory leak problem. However, full testing of the Portal Server software with these upgrades has not been completed.

 

4783882

 

The Install Directory Server Only option does not produce a summary report.

 

Under evaluation

 

4774503

 

SRA perftune script does not add keepAlive parameter to CMD line in the gateway script.

 

Due to a problem in jvm 1.3.1_04 the keepAlive functionality must be turned off on the SRA gateway platform. Add the following flag to the java options on the CMD line:    -Dhttp.keepAlive=false

For example:

CMD="$JAVA_HOME/bin/java -server -verbose:gc -Xms1G -Xmx2G -XX:ThreadStackSize=1 28 -XX:MaxPermSize=128M -XX:PermSize=128M -XX:MaxNewSize=256M -XX:NewSize=256M -Dhttp.keepAlive=false -classpath ${CLASSPATH} $DEF

 

4789695

 

There are two areas (documentation link and migration) that require the Default Web Application to be set and use it differently. Only one can be set at a time.

 

Tar one of the contents either DefaultWebApp or SunONEPublicHtml and untar it into the other, then redeploy and restart.

Putting the contents from SunONEPublicHtml into DefaultWebApp worked successfully.

 

Problem:

Cannot scrape http or https content in the URL scraper channel.

Solution:

Login to the Portal Server admin console, click on your organization's link, select Show: Services. Click the Properties arrow next to Desktop in the navigation pane; choose the Channel and Container Management link. Click the Edit link for the SampleURLScraper channel. Edit the URL text box to include a slash (/) at the end of the URL. Click Save.

Problem:

Received an error: Bad URL or file name when running BEA WebLogic command weblogic.deploy for migrated data.

Solution:

This problem is caused by a non-existent symbolic link target in the web application deploy directory. When the customer's files are migrated, symlinks are respected but not tested for validity nor are the target files migrated (see Chapter 1 in the Sun ONE Portal Server 6.0 Migration Guide for more information). So the weblogic.deploy command fails to deploy the web application. The solution to this problem is to verify all symlinks in the migrated SunONEPublicHtml directory or remove them.

Problem:

Using the Portal Server search function on a managed server.

Solution:

1) If you plan to run the Portal Server software off a separate server, do this procedure:

  1. Install to both machines using the same servername.

  2. Create a server on the administration server using a different servername.

    3. This should set up the directories and war files to match.

2) If you have already set up the servers with different names, do this procedure:

  1. Rename the search directory in /var/opt/SUNWps on the managed server.

  2. In the following files, change https-installed-to-servername to https-installed-to-servername-on-the-manager-machine. For example, if the manager server was installed to servername PORTALSERVER1 and the machine that is the managed server was installed to servername PORTALSERVER2, then https-PORTALSERVER2 needs to be renamed to https-PORTALSERVER1 on the managed machine. And all the references inside https-PORTALSERVER1 on the managed machine need to refer to https-PORTALSERVER1.

    3. /var/opt/SUNWps/tmp/context-param.tmp

    /var/opt/SUNWps/https-PORTALSERVER1/portal/config/search.conf

    /var/opt/SUNWps//https-PORTALSERVER1/portal/config/robot.conf

    /var/opt/SUNWps//https-PORTALSRVER1/portal/config/filter.conf

    /var/opt/SUNWps//https-PORTALSERVER1/portal/config/filter.conf.run

    /var/opt/SUNWps//https-PORTALSERVER1/portal/run-cs-cli

    /var/opt/SUNWps//https-PORTALSERVER1/portal/StartRobot

    /var/opt/SUNWps//https-PORTALSERVER1/portal/StopRobot

Troubleshooting

The debug logs are in the /var/opt/SUNWam/debug directory.

The terminal window that you are running WebLogic in sometimes provides relevant output about exceptions or errors.

If you are reinstalling the Portal Server software, after uninstalling the Portal software, in addition to doing what you normally do to clean up files and directories, go to the WebLogic console, expand Deployments, then Web Applications. Delete portal. Now you can successfully reinstall the Portal Server software.

How to Report Problems

If you have problems with Sun ONE Portal Server 6.0, contact Sun ONE customer support using one of the following mechanisms:

  • Sun ONE online support Web site at

    • http://www.sun.com/service/support

    After selecting Sun ONE software support, Online Support Center and Product Tracker are available for logging problems.

  • The telephone dispatch number associated with your maintenance contract

So that we can best assist you in resolving problems, please have the following information available when contacting customer support:

  • Description of the problem, including the situation where the problem occurs and its impact on the operation

  • Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem

  • Detailed steps on the methods used to reproduce the problem

  • Any error logs or core dumps

Where to Find More Information

In addition to this guide, Sun ONE Portal Server comes with supplementary information for administrators as well as documentation for developers. Use the following URL to see all the Sun ONE Portal Server documentation:

http://docs.sun.com/prod/s1portalsrv

Listed below are the additional documents that are available:

  • Sun ONE Portal Server 6.0 Administrator's Guide

  • Sun ONE Portal Server 6.0 Desktop Customization Guide

  • Sun ONE Portal Server 6.0 Developer's Guide

  • Sun ONE Portal Server 6.0 Installation Guide

  • Sun ONE Portal Server 6.0 Migration Guide


Previous      Contents     
Copyright 2002 Sun Microsystems, Inc. All rights reserved.