Sun ONE logo      Previous      Contents      Index      Next     

Sun ONE Portal Server 6.1 Installation Guide

Appendix C
Sun ONE Portal Server 6.1 Installation for IBM Application Server

Sun™ ONE Portal Server 6.1 can be deployed on an IBM WebSphere Application Server 4.0.5 Advanced Edition using it as its web application container.

This supplement contains the following sections:

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 IBM WebSphere Server is a Java™ application server that enables deployment of web applications, such as the Sun ONE Portal Server, and web services. The IBM WebSphere Server implements the J2EE™ platform specification and supports servlets, JSPs, JavaBeans™, and other platform services. In addition, the IBM WebSphere Server allows you to use the Sun ONE 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 asks you which deployment type you are using. Once you select IBM WebSphere Server, the install script sets up the appropriate default directories and adds a number of .war files that facilitate running the Portal Server on a IBM WebSphere Server.

Since you are using the IBM WebSphere Server, the install script needs to know the application server directory is (/opt/WebSphere/AppServer, the default) and the name of the application server instance on which the Portal Server will be deployed. The Portal Server installation summary lists the deployment information related to the application server.

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. Other versions of these software products are not supported.

Space Requirements

These requirements are the ones that are checked for in the Portal Server installation script. Table C-1 is a three column table. The first column lists the directory, the second the size in megabytes, and the third adds relevant comments.

Table C-1  Space Requirements

Directory

Size

Comments

/etc/opt

200 MB

 

/var/opt

200 MB

Add more for extended logging.

Portal installation base directory (/opt)

50 MB

If using migration tools.

DS_BASEDIR (/usr/ldap)

300 MB

For Directory Server.

Portal installation base directory (/opt)

300 MB

For iPlanet Directory Server Access Management Edition.

Portal installation base directory (/opt)

200 MB

For Portal Server only.

Portal installation base directory (/opt)

500 MB

For Secure Remote Access on the same machine as the Portal Server software.

S1PSBASEDIR (/opt)

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.

Additional Software Requirements for WebSphere

There are FixPaks from IBM for DB2 and WebSphere that are required. The WebSphere FixPak upgrades the 4.01version base to version 4.0.5. The listed eFix from IBM is also required.

Installing the Portal Server Software

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

Note

Portal Server cannot be installed into an application server instance or domain whose name contains a dash or a space, for example, Default-Server or Default Server. If you try to install into an application server instance or domain with a dash or space in the name, the installation script returns the error message Invalid response! and prompts for the application server domain or application server instance name again.

Note

Be sure that /usr/bin/jar exists. If not, add appropriate link.

  1. 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. Select option 1, IBM WebSphere, as the deployment type.
  4. At the install script query for the application server directory, accept the default /opt/WebSphere/AppServer.

Note

To install the Portal Server, the application server instance to which you install must already exist. You can create a new application server instance or use an existing instance; however, the instance name must not contain a space.

The install program defines the default application server instance as Default_Server. If you want to perform an install of the Portal Server software to an application server instance named Default_Server you would need to create the instance before starting the Portal Server install. See "Installing the Portal Server Software" for information.

A list of default settings is displayed with the following values.

 

Application Server summary

------------------------

Directory: /opt/WebSphere/AppServer

Virtual Host: default_host

Node:myappserver

Instance: Default_Server

Document Root: /opt/IBMHTTPD/htdocs

 

Directory Server installation summary

-------------------------------------

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

Access URL: http://myappserver.sesta.com:80

 

Portal Server installation summary

----------------------------------

Base Directory: /opt

Deployment URI: /portal

Sample Portal: y

Upgrade Mode: n

 

Use these settings? [y]/n y

 

  1. Accept the settings if they are correct, otherwise change as necessary.
  2. Enter a passphrase for the portal server and confirm it

    3. The install script finishes installing the Portal Server.

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

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.

  1. Check the /var/sadm/install/logs/pssetup.pid/setup.log file for errors.
  2. Stop and restart the application server instance and the application server node.
  3. Test the portal server installation by launching the portal desktop and administration console in a browser by using:

    4. http://full-hostname:listen-port/portal/dt and http://full-hostname:listen-port/amconsole

    If the sample desktop and administration console display without any exception, then your Portal Server installation is good.

Creating an Application Server Instance

To install the Portal Server, the application server instance to which you install must already exist. You can create a new application server instance or use an existing instance; however, the instance name must not contain a space.

For example, the Portal Server installation program defines the default application server instance for an IBM WebSphere Application Server as Default_Server. If you want to perform an install of the Portal Server to the application server instance Default_Server you would need to create an application server instance named Default_Server using the Create Application Server wizard in the administration console before starting the Portal Server install.

  1. Open the admin console. For example, to start the console installed in the default base directory of /opt, type:

    2. /opt/WebSphere/AppServer/bin/adminclient.sh

  2. Click Console, Wizards, and Create Application Server.
  3. On the Specifying Application Server Properties page, enter the following:

    4. Application Server: Default_Server

    Node to install server on: node_name

    where node_name is the machine name on which the application server is installed.

  4. Click Next and Finish.



Previous      Contents      Index      Next     

Copyright 2003 Sun Microsystems, Inc. All rights reserved.