Installing WebSphere Portal Enabled Offering 4.2 On Solaris

Full Install

This method presumes you are connected to a network drive which has a WebSphere Everyplace Access (WEA) build available. This process describes the use of Setup Manager, which installs WPO. It includes the installation of components "WebSphere Portal", "Portal Server", "WebSphere Application Server, Advanced Edition", "WebSphere Application Server Fixpack 4", "WebSphere Application Server", "IBM HTTP Server","IBM Directory Server", "IBM Directory Server", "IBM Directory Client", "DB2 Universal Database, "DB2 Universal Database Server", and the "DB2 Universal Database Fixpack 7". Note that this was a snapshot of the WPO 4.2 GM build.

When using Setup Manager without the use of the keyboard (for accessibility), choosing a radio button involves using the "Tab" key to go to the appropriate field, and pressing the space bar to select that field.  For selecting check boxes, use the tab and arrow keys to move to the appropriate  position, then press the space bar to "check" the box. Also, in the following sections, when instructed to "select" or "click", use the tab key to go to the appropriate field, then press the "Enter" key.

Before you begin installation of the full complement of services, you must increase your file sizes. This can be done automatically using a utility provided in the "tools" directory.

1)  Logon to your Solaris machine (i.e. "(yourmachinename)") as "root".

2)  Mount a network drive to your machine that has the appropriate build on it (i.e. execute the command "/WEA/tools/shayden/mountscripts/mwpo42", shell scripts which mount the network disk with builds on it). See Example Mount Script for details of this script.

3)  Change directories to the newly mounted drive (i.e. "cd  /wpo42/WPO42/Setup"), and at the AIX command prompt type "./". In a few minutes the "WebSphere Portal - (yourmachinename)" GUI window should appear for performing the installation.

During installation, progress will be displayed on the window you started the install on.

WebSphere Portal Offering Install

1)  After invoking the install script, the first screen you will see is the "View Information" window in the "View Prerequisites" panel. If you wish, view the prerequisites (this will be done via a web browser), then click "Next"

2)  In the "Reading Software License" panel, select "Accept" in the "Program License Agreement" section and click "Next".

3)  In the "Validate the Installation Key" panel, enter the key values for the "Enable" version of WPO, then click "Next".

4)  In the "Install Selection" panel, select "Standard Install" and click "Next".

5)  You then have the option to enter a response file of a previously recorded install if desired, do not enter a value (and if one is there by default, delete it from this input field), and click "Next".

6)  In the "Select Components" panel, select ONLY the components "WebSphere Portal", "Portal Server", "WebSphere Application Server, Advanced Edition", "WebSphere Application Server Fixpack 4", and "WebSphere Application Server", then click "Next".

7)  In the "Checking Previous Installation" panel, accept the information and click "Next".

WebSphere Application Server

1)  In the "Installation Directories"  panel, accept the default and click "Next" (already filled in "WebSphere Application Server installation directory" was "/opt/WebSphere/AppServer").

2) In the "Choose Database Location" panel, "Is this a remote database", select "No", then click "Next".

3) In the "Choose Database Type" panel, select "Oracle", then click "Next".

4) In the "Collect Database User Info" panel, for the "Database Password" and "Confirm Database Password" fields, enter  "ejsadmin", then click "Next".

5) In the "Collect Database Settings" panel, for the "Database SID" field enter "ORA817", for the "Database Home" field enter "/export/home/oracle/ORA817", for the "Database URL" field enter "jdbc:oracle:thin:@(yourhostname)" (where "(yourhostname)" = your machine, i.e. "weasun08"), and "Database Hostname" field enter  "(yourhostname)" (i.e. ", then click "Next" (already filled in "Database Server Port" was "1521").

6) In the "Choose Web Server Location" panel, "Is your Web server on a remote machine", select "No", then click "Next".

7)  In the "Checking Previous Installation" panel, accept the information and click "Next".

WebSphere Application Server Web Server Plugin

1) In the "Select Web server" panel, select "IBM HTTP Server", then click "Next".

2) in the "Configure Plugin" panel, accept the defaults and click "Next" (already filled in,  "IBM HTTP Server installation directory was "/opt/IBMHTTPD", and "Location of httpd.conf" was "/opt/IBMHTTPD/conf/httpd.conf").

Portal Server

1) In the " Authentication Mode" panel, select "Database and LDAP Directory mode", then click "Next".

2) In the "Security Configuration" panel, select "Now", then click "Next".

3) In the "LTPA Password" panel, for the "LTPA Password" and "Confirm password" fields enter "wpsbind", then click "Next".

4)  In the "Server Configuration" panel, click "Next" to accept the defaults. (the "Install Directory" is
"/opt/WebSphere/PortalServer", the "Hostname" is
"(yourmachinename)", the "Base URI" i.e. "/wps", and the "Home page" is. "/portal", and the
"Customized page" is "/myportal". "Proxy Host" and "Proxy port" were blank. The Base URI and the Home page will be
the URL to access the Portal portlet, i.e.. "http://(yourmachinename)".).

5)  In the "Administrative Settings" panel, accept the defaults, then click "Next" (Portal Admininstrator User ID was
"wpsadmin", and the Administrator Password and Confirm Password fields were 8 "*").

6)   In the "Selection of LDAP Server" panel, for the "LDAP Server" field, change the value to your machine name (i.e.
", and accept the remaining defaults, then click "Next". (IBM Directory Server was selected,
User DN was "cn=wpsadmin", "User Password" and "Confirm Password" fields were 8 "*", Suffix was "dc=raleigh,dc=ibm,dc=com", LDAP Port Number was "389", and "Make sure LDAP server is properly configured" was checked).

7)  In the "LDAP Configuration" panel, accept the defaults and click "Next". (User Object Class was "inetOrgPerson",
User DN Prefix was "uid", User DN Suffix was "cn=users,dc=raleigh,dc=ibm,dc=com", Group Object Class was
"groupOfUniqueNames", Group Member was "uniqueMember", Group DN Prefix was "cn", Group DN Suffix was
""cn=groups,dc=raleigh,dc=ibm,dc=com", Administrator DN was "uid=wpsadmin,cn=users,dc=raleigh,dc=ibm,dc=com", Administrative group DN was "cn=wpsadmins,cn=groups,dc=raleigh,dc=ibm,dc=com", BIND DN was "uid=wpsbind,cn=users,dc=raleigh,dc=ibm,dc=com", and "Bind
Password" and "Confirm Bind Password" were 7 "*". Leave the two remaining fields "objectAttribute name" and
"pluginAttribute name" blank).

8)   In the "Portal Server Database Selection" panel, for the "Database Backend" select "Oracle", for the "Is this a remote database" field select "No", for the Portal Server database configuration options "Initialize an exiting database", and for the "Do you want to share the database with Member Services", select "Share this database" and click "Next".

9) In the "Portal Server Database Configuration" panel , for the "Database User ID", "Database Password" and "Confirm
Database Password" fields enter "wps", for the "Database SID" field enter "ORA817", and for the "JDBC database driver" field enter "oracle.jdbc.pool.OracleConnectionPoolDataSource", for the "JDBC URL prefix" field, enter "jdbc:oracle:thin:@(yourmachinename)", and for the "JDBC driver libary" field, enter "/export/home/oracle/ORA817/jdbc/lib/, then click "Next".

10)  In the "License Use Managment" panel, select "Local License Server" and accept the default "LUM Server Hostname" "(yourmachinename)", and click "Next".

11)  In the "Checking Previous Installation" panel, accept the information and click "Next".


1)  In the "Save Response File" panel, you can optionally save your response file (be sure to click "Save Response File"), then click "Next".

2)  In the "Display Summary" panel, click "Next" to proceed with installation. The following is the Summary Results for the above installation. Go have a latte'.

Display Summary Results

The following components are selected for install. Components that appear that you have not selected are listed because a component that you have selected requires them in order to be installed. All components listed will be installed when you hit the next button

Global Security Toolkit

WebSphere Application Server
    WebSphere Application Server installation directory: /opt/WebSphere/AppServer
    Local Database User ID:  EJSADMIN
WebSphere Application Server Fixpack4
    Included eFixes: PQ61935, PQ66355, PQ67566, Cumulative CM, Cumulative Security, PQ69078
Portal Server
    Authentication Mode: Database and LDAP Directory mode
    Install Directory:  /opt/WebSphere/PortalServer
    Hostname for the Web Server:
    LDAP Server type: WPS Ldap SWD
    LDAP Server:
    Database backend: Oracle
    Is this a remote database?  No
    Portal Server database configuration options: Initalize an existing databse
    Do you want to share the database with Member Services?  Share the database
Transcoding Technology
License Use Management Runtime
Productivity Portlets

Installation Details

After several minths a popup "Configuring for Admin Role " will appear.  While you are in the process of performing these steps you should also change the WebSphere Portal Ping Initial Timeout value to 1800.  From the WebSphere Administrative Console, scope down to "WebSphere Administrative Domain", "Nodes", (yournodename), "Application Servers", and select "WebSphere Portal".  In the "Advanced" tab for the Portal Server, change "Ping initial timeout" to "1800", click "Apply".

Follow the Configuring for Admin Role instructions before you continue with the installation of the software. When you are through with the configuring for admin role, be sure to click OK in the Configuring for Admin Role popup. The installation will then continue.

Wait a month, and eventually an "Installation Complete" popup should be displayed stating the response file has been saved, click "OK".  In the Display Summary window, click "Finish".

Logs resulting from the installation include the "setup*" file, which is the overall install log. Within that file will be references to additional logs "RunCommand* that will be in the directory "/usr/IBMWPO/RunCommand". (note that in the "setup*", and the "RunCommand*", the "*" refers to a "randomly generated" numeric value created during the install process.)

Testing The Installation

At this point WEA and associated software should be installed, and WAS and your applications should have been started. Start the Admin Console, and when queried for authentication, use the value "wpsadmin" for the ID and password. (Note: if you had left the Admin Console running after performing the steps in "Configuring for Admin Role", you still have a snapshot of the configuration of WES/WAS at that point. Refreshing the Admin Console will not show you the remaining applications that were installed after the configuration was performed. To see these applications you must exit the Admin Console and restart it. Logon using ID/Password of "wpsadmin").

Steve:  Apparently during the installation process the Security Center password was changed from the value input ("wpsadmin") to "wpsbind". Dont know why!

To verify the installation and operation of WebSphere Application Server, scope down to "WebSphere Administrative Domain", "Nodes", (yournodename), "Application Servers", select "Default Server", right mouse click and select "Start". Once the Default Server has started you should be able to run the "snoop" servlet by using your favorite browser and browsing the url "http://localhost/servlet/snoop". The userid and password for accessing servlets is "wpsadmin".

To verify the installation of WEA, use the url "http://localhost/wps/portal" (or alternatively your machinename, i.e.. "") to run the "World Clock" portlet. If you are queried for an ID/Password, use "wpsadmin" for both.

To login to the WebSphere Everyplace Access using the "portal" portlet, click on the key icon on the upper right corner of the web page. For the User ID and Password, enter the value "wpsadmin", and click the "Log In".

If the snoop servlet and portal portlet both work you