Installing WebSphere Everyplace Access 4.31 on Solaris 8 Using Oracle 9.2.0.1

Full Install

(Created with version 07010845 of the build)

Introduction
Installation Preparation
Installing IBM Directory Server and DB2
Installing the WebSphere Everyplace Access Product
   WebSphere Application Server
   WebSphere Application Server Security Configuration
   Portal Server
   WebSphere Everyplace Access Core Services
   Location Aware Services
   Intelligent Notification Services Server
   Everyplace Synchronization
   Device Manager
   Summary
   Installation Details
Installing DB2 Everyplace Server
Resources Installed by WEA
   WEA/WPO WebSphere Application Servers Installed
   WEA WebSphere JDBC Resources Installed
   WEA WebSphere Enterprise Applications Installed
   WEA Databases Installed During Full Installation

Post Installation Required Steps
Testing The Installation
Starting and Stopping WebSphere Everyplace Access
Uninstalling Everything
Example Mount Script
 

Introduction

This page assumes you have already successfully installed Oracle 9.2.0.1.0 Bit version (see Installation of Oracle 9.2.0.1 on Solaris 8). You will actually run Setup Manager 3 times. First to install IDS and DB2, then to install WEA and all components but DB2e, and then to install DB2e.

This method presumes you are connected to a network drive which has a WebSphere Everyplace Access (WEA) build available, or alternately CDs. This process describes the use of Setup Manager (SUM), which installs WEA and other optional components. It includes the installation of components "IBM HTTP Server", "DB2 Universal Database Server" (and Fixpack 7), "IBM Directory Server", "WebSphere Application Server", "WebSphere Portal Server", "WebSphere Everyplace Access Core Services", and optionally  "Everyplace Synchronization Server", "Intelligent Notification Server", "Device Management Server", "Location Aware Services", "DB2 Everyplace", and all of the associated component's portlets and databases. Note that this was a snapshot for a particular build. There might be changes in defaults in subsequent builds/installs.

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.

Once installation is complete the file "/opt/IBMWPO/conf/WEA.properties" contains information reflecting what components are installed and what versions. The WEA Information Center (which is installed with the build), is normally located at "/opt/HTTPServer/htdocs/en_US/WEAInfo/en/InfoCenter/index.html". Product build information on Solaris is in /opt/WebSphere/AppServer/lib/app/WEAproduct.xml. Product build information on NT is in (x):\WebSphere\AppServer\lib\app

The PVC web based version of the InfoCenter is located at "http://pvcid.raleigh.ibm.com/wea/ic/v431/en/InfoCenter/index.html", and the Release Notes are located at "http://pvcid.raleigh.ibm.com/wea/ic/v431/release_notes.html".
 

Installation Preparation

Useful utilites can be found on the WEA Test Dept mount disk. To mount, create the disk access point (i.e. "mkdir   /WEA"), and then mount the directory (i.e. "mount  weasun16:/WEA  /WEA"). In the directory "/WEA/tools/shayden", there is a profile ".profile" that you can execute which has several aliases that are useful (to execute it, change to the directory and type ".  ./.profile.sol" (thats  dot, space, dot, slash, dot, "profile.sol").

Installing WEA with Oracle requires the "/etc/profile" to be modified to include the variable "ORACLE_HOME", with a value reflecting your Oracle base and SID (i.e. "ORACLE_HOME=/export/home/oracle/ORA9201"). You must logoff and back on to instantiate this value (to assure the value is set, type "echo $ORACLE_HOME").

Additionally, you should avoid the use of the "bash" shell on Solaris when installing WEA ("K" shell has similar functionality to "bash" (i.e. "ksh")).

There are several options on where you can install from. These include CD's, "NAS" server, and "cinta03".
 

Installing From CD's

1) Insert CD1 in your CD drive, and as user "root", from the root directory ("/"), at the Solaris command prompt, create a directory for mounting (i.e.
"mkdir mnt")

2) Also from the Solaris command prompt, execute the mount command to mount the CD (i.e. "mount  -o  ro  -v  cdrfs  /dev/cd0  /mnt").

3) Proceed to Running the Setup Manager
 
 

Installing From NAS

1)  Log on as "root" and create the directory "/nas" (i.e. "mkdir   /nas"), mount to it (i.e. "mount   nas300:/staging    /nas"),change directories to the network drive which has the builds on it by changing directories to "/nas/WEA_R431/". In that directory there exists all the builds which have
been transferred to NAS (Note: when a new build has COMPLETELY been copied to NAS, there will be a file "done" in the associated directory (i.e.
"/nas/WEA_R430/04170621/done").

2) Determine the build you are interested in and change to that directory (i.e. "03121504"), and in it change to the "cdlinks/cd1" directory (this full path
will be "/nas/WEA_R430/03121504/cdlinks/cd1")

3) Proceed to Running the Setup Manager
 
 

Installing From altnas

1)  Log on as "root" and create directory "altnas" (i.e. "mkdir  /altnas").

2) Mount the "altnas" disk (i.e. "mount  altnas:/staging   /altnas"), and change directories to "/altnas/WEA_R431".

2) Determine the build you are interested in and change to that directory (i.e. "03121504"), and in it change to the "cdlinks/cd1" directory (this full path will be "/altnas/WEA_R431/03121504/cdlinks/cd1")

3) Proceed to Running the Setup Manager
 
 

Installing From cinta03
 

Every morning (and if necessary more than once a day), WEA Test personnel will be ftp'ing the new builds to "cinta03" (if you try to mount a version that does not exist, please see Ken Hoopes or Jim Brancato for more information.)

There are several "mount" scripts located on "/WEA/tools/mounting", that perform the appropriate mounting for each day of the week, for up to 4 builds a day. As well, in that same directory exists the corresponding "unmount" script for each mount. The naming convention for these scripts is as follows:

Script naming convention:    mnt(3 letter day of the week)a(build during the day)

Example 1:    mntmona1       equals  mnt = mount, "mon" = Monday, "a" = AIX/Solaris, and 1 = the first build for that day
Example 2:    mntfria3             equals  mnt = mount, "fri" = Friday, "a" = AIX/Solaris, and 3 = the third build for that day

Once you have run the mount script (i.e. for Monday, build 1, from the Solaris command prompt, change directories to "/WEA/tools/mounting", and type "./mntmona1"), the directory you will execute the installation from will be named after the mount script. In the examples above, for example 1, change directories to "/mntmona1/cd1" and execute the install script (i.e.  "./install.sh").

There are corresponding "unmount" scripts which include the above convention preceded by "u" (i.e. "umntmona1")

Additional Notes For cinta03 Installations

->  CD1 does not necessarily contain the correct build stamp! To conserve disk space, only those CD's which have changed for a particular build will be ftp'd for builds other than the first one each day, so unless CD1 changes in a later build during the day, it will have the build date stamp from the first build of the day.

->  Assuming there will be no more that 4 builds created on any day.

->  We will be "recycling" this disk space, and only keeping one weeks worth of builds in this scheme.

->  If you are using Steves ".profile" (at "/WEA/tools/shayden.sol"), simply type "m" and it will take you to "/WEA/tools/mounting".
 

1) Change directories to the appropriate build mount point for the day and build (i.e. "/mntmona1/cd1").

2) Proceed to Running the Setup Manager
 
 
 

Running the Setup Manager

1)  At the Solaris command prompt, if installing from CD's, type "/mnt/install.sh", otherwise, if installing from NAS or cinta03, assure you are in the
appropriate "cd1" directory and type "./install.sh". In a few seconds a new window should appear for performing the installation.

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

(common Administrator password for Windows machines is (generic password))
 
 
 

Installing IBM Directory Server and DB2

1)  After invoking the install script, the first screen you will see is the "View Information" section and 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 "Install Selection" panel, select "Standard Install" and click "Next".

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

5) In the "Database selection" panel, choose "Oracle Database", then click "Next".

6)  In the "Select Components" panel, select only the components "IBM Directory Server", and "DB2 Universal Database server", then click "Next".
 
 

IBM HTTP Server

1)  In the "IBM HTTP Server administrator ID" panel, enter "ihsadmin" for the "Administrator ID", "Password", and "Confirm password" fields. For the
"Group" enter "ihsgrp", then click "Next".
 
 

IBM Directory Server

1)  In the "IBM Directory Server Information" panel, for the "Administrative ID" field enter "cn=wpsadmin",  for the "Password" and "Confirm
password" fields enter "wpsadmin", and in the "Suffix" field enter "dc=raleigh,dc=ibm,dc=com" (or "dc=rushmore") then click "Next". (LDAP port is
"389").
 
 

IDS and DB2 Installation Summary

1)  In the "Display Summary", click "Next" to accept the defaults. (note that Steve renamed the script file "/Steves.07010845.070103.1722.DB2.IDS.weasun16.WEA_response.script", and clicked "Save Configuration".). Go have a latte'.
 
 
 

Installing the WebSphere Everyplace Access Product

1)  Again, invoke the install script, the first screen you will see is the "View Information" section and 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 "Install Selection" panel, select "Standard Install" and click "Next".

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

5) In the "Database selection" panel, choose "Oracle Database", then click "Next".

6)  In the "Select Components" panel, select all the components "WebSphere Everyplace Access", "WebSphere Everyplace Access Core Services", (which includes "Everyplace Access database setup", "Everyplace Access Portal extensions", "Everyplace Access Client services"), "Location Aware Services", (which includes "Location Aware Services database setup" and "Location Aware Services Portal extensions"), "Intelligent Notification Services" (which includes "Intelligent Notification Services database setup", "Intelligent Notification Services Subscription Services", "Intelligent Notification Services Portal extensions", and "Intelligent Notification Services Messaging Server"), "Everyplace Synchronization Server" (which includes "Everyplace Synchronization database setup", "Everyplace Synchronization Server", and "Everyplace Synchronization Portal extensions") , and "Device Manager" (which includes "Device Manager database" and "Device Manager"), then click "Next".

You should get an information panel stating other components have already been installed, click "Next".
 
 

WebSphere Application Server

1)  In the "WebSphere Application Server directory" panel, click "Next" to accept the defaults ("WebSphere Application Server Directory" is "/opt/WebSphere/AppServer", "IBM HTTP Server directory" is "/opt/IBMHTTPD", and "Location of IBM HTTP Server htpd.conf configuration file" is "/opt/IBMHTTPD/conf/httpd.conf").

2)  In the "WebSphere Application Server administrator" panel, enter "ejsadmin" for the "Database password" and "Confirm database password", then click "Next" (presuming this is the password you used during the creation of this account in Oracle)..

3)  In the "WebSphere Application Server database settings" panel, for the "Database SID" field, enter "ORA9201", then click "Next" to accept the defaults ("Database host name" was "(yourhostname).raleigh.ibm.com", "JDBC Port" was "1521", "Oracle home" was "/export/home/oracle/ORA9201", and "JDBC driver library" was "/export/home/oracle/ORA9201/jdbc/lib/classes12.zip").
 
 
 

WebSphere Application Server Security Configuration

1) For the "WebSphere Application Server security" panel, select "No", then click "Next".
 
 

Portal Server

1)  In the "WebSphere Application Server security" panel, enter "wpsbind" for the "LTPA password" and "Confirm password" fields, then click "Next".

2)  In the "Portal Server configuration" panel, click "Next" to accept the defaults. (the "Portal Server directory" is "/opt/WebSphere/PortalServer", the "Host name" is "(yourmachinename).raleigh.ibm.com", the "Base URI" is "/wps", 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).raleigh.ibm.com/wps/portal".).

3) In the "Portal Server administrator ID" panel, for the "Portal administrator ID", "Administrator password", and "Confirm password" fields, enter "wpsadmin", then click "Next".

4) In the "Portal Server LDAP directory" panel, select "IBM Directory Server", and for the "Administrator Distinguished Name" enter "cn=wpsadmin",  for the "Administrator password" and "Confirm password" fields, enter "wpsadmin", for the "Portal Server suffix" enter "dc=raleigh,dc=ibm,dc=com", and for the "Portal Server LDAP directory server" enter "(yourmachinename).raleigh.ibm.com" (where "yourmachinename" is your machine name, i.e. "weasun16"), then click "Next" to accept the remaining default (already filled in "LDAP Port Number" was "389").

5) In the "Portal Server LDAP directory  configuration" panel, accept the defaults and click "Next". (already filled in, "User Object Class" was "inetOrgPerson", "User Distinguished Name prefix" was "uid", "User Distinguished Name suffix" was "cn=users,dc=raleigh,dc=ibm,dc=com", "Group Object Class" was "groupOfUniqueNames", "Group Member" was "uniqueMember", "Group Distinguished Name prefix" was "cn", "Group Distinguished Name suffix" was "cn=groups,dc=raleigh,dc=ibm,dc=com", "Administrator Distinguished Name" was "uid=wpsadmin,cn=users,dc=raleigh,dc=ibm,dc=com", "Administrator group Distinguished Name" was "cn=wpsadmins,cn=groups,dc=raleigh,dc=ibm,dc=com").

6)  In the "Portal Server database" panel, for the "Portal Server database configuration options" select "Initialize an existing database", then click "Next".

7)  In the "Portal Server database configuration" panel , for the "Database administrator ID", "User Password", and "Confirm password" fields enter "wps", for the "Database SID" field, enter "ORA9201", then click "Next" to accept the remaining defaults (already filled in, the "Database server host name" was "(yourmachinename).raleigh.ibm.com (where "yourmachinename" is your machine name, i.e. "weasun16")", the "JDBC Port" was "1521", the "JDBC database driver" was "oracle.jdbc.pool.OracleConnectionPoolDataSource", the "Oracle home" was "/export/home/oracle/ORA9201", and the "JDBC driver library" was "/export/home/oracle/ORA9201/jdbc/lib/classes12.zip").

8)  In the "Member Services database" panel,  for the "Select the Member Services option that best fits your environment" select "Initialize an existing  database", and click "Next".

9)  In the "Member Services database configuration" panel, for the "Database administrator ID", "User Password", and "Confirm password" fields enter "wms", for the "Database SID" field, enter "ORA9201", then click "Next" to accept the remaining defaults (already filled in, the "Database server host name" was "(yourmachinename).raleigh.ibm.com (where "yourmachinename" is your machine name, i.e. "weasun16")", the "JDBC Port" was "1521", the "JDBC database driver" was "oracle.jdbc.pool.OracleConnectionPoolDataSource", the "Oracle home" was "/export/home/oracle/ORA9201", and the "JDBC driver library" was "/export/home/oracle/ORA9201/jdbc/lib/classes12.zip").

(a panel will be displayed informing you that some software is already installed, click "Next".
 

WebSphere Everyplace Access Core Services

1)  In the "WebSphere EveryPlace Access Portal extensions" panel, accept the default and click "Next" (already filled in was the "WebSphere Everyplace Access directory" field which had a value of "/opt/WebSphere/WEACoreServices").

2)  In the next "WebSphere EveryPlace Access Portal extensions" panel, select all portlets, which includes "Portlets for Lotus Notes IIOP", "Portlets for Microsoft Exchange", and "Portlets for productivity enhancement", then click "Next".

3)  In the "WebSphere Everyplace Access administrator ID" panel, click "Next" to accept the defaults ( the "Portal administrator ID" was "wpsadmin", the, "Portal administrator password" and "Confirm password" fields, were "wpsadmin" (actually 8 "*"), the "Administrator group" was "wpsadmins", the "Portal Server host name" was "(yourhostname).raleigh.ibm.com", the "Portal base URI" was "/wps", the "Home page" was "/portal", and the "Portal customized page" was "/myportal")

4)  In the "WebSphere Everyplace Access database setup" panel, for the "Administrator ID", "Database Password", and "Confirm database password" fields enter "wea", for the "Database SID" field, enter "ORA9201", then click "Next" to accept the remaining defaults (already filled in, the "Local Oracle user ID" was "oracle", the "Database server host name" was "(yourmachinename).raleigh.ibm.com (where "yourmachinename" is your machine name, i.e. "weasun16")", the "JDBC Port" was "1521", the "JDBC database driver" was "oracle.jdbc.pool.OracleConnectionPoolDataSource", the "Oracle home" was "/export/home/oracle/ORA9201", and the "JDBC driver library" was "/export/home/oracle/ORA9201/jdbc/lib/classes12.zip").
 
 
 

Location Aware Services

1) In the "Location Aware Services directory" panel, accept the default and click "Next" (already filled in was the value "/opt/WebSphere/LAS").

2) In the "Portal Server configuration" panel, accept the defaults, then click "Next" (already filled in, the "Portal Server administrator Distinguished Name" was "uid=wpsadmin,cn=users,dc=raleigh,dc=ibm,dc=com", the "Administrative group Distinguished Name" was "cn=wpsadmins,cn=groups,dc=raleigh,dc=ibm,dc=com", the "HTTP proxy server" and "Proxy port" fields were blank, the "Portal Server directory" was "/usr/WebSphere/PortalServer", and the "WebSphere Application Server directory" was "/usr/WebSphere/AppServer").

3) In the "Oracle Server information" panel, for the "Database Password", and "Confirm password" fields enter "atlas", for the "Database SID" field, enter "ORA9201", then click "Next" to accept the remaining defaults (already filled in, the "Administrator ID" was "atlas", the "JDBC Port" was "1521", the "JDBC database driver" was "oracle.jdbc.pool.OracleConnectionPoolDataSource", the "Oracle home" was "/export/home/oracle/ORA9201", and the "JDBC driver library" was "/export/home/oracle/ORA9201/jdbc/lib/classes12.zip").
 
 

Intelligent Notification Services Server

1)  In the "Intelligent Notification Services directory" panel, click "Next" to accept the defaults. (Already filled in, "Host name" was "(yourservername).raleigh.ibm.com", and "Install directory" was "/opt/WebSphere/INS")

2)  In the "Intelligent Notification Services Configuration" panel, click "Next" to accept the default path (Already filled in, "Path" was "/opt/IBMWPO/").

3) In the "Portal Server LDAP directory" panel, select "IBM Directory Server", then click "Next".

4) In the "Intelligent Notification Services LDAP directory" panel,  for the "Administrator Distinguished Name" enter "cn=wpsadmin",  for the "Administrator password" and "Confirm password" fields, enter "wpsadmin", for the "Portal Server suffix" ener "dc=raleigh,dc=ibm,dc=com", and for the "Portal Server LDAP directory server" enter "(yourmachinename).raleigh.ibm.com" (where "yourmachinename" is your machine name, i.e. "weasun16"), then click "Next" to accept the remaining default (already filled in "LDAP Port Number" was "389").

5)  In the "Intelligent Notification Services database setup", for the "Local Oracle user ID" field enter "oracle" (as this is the user Oracle was installed with), for the "Administrator ID", "Database password", and "Confirm password" fields, enter "insuser", for the "Database SID" field, enter "ORA9201", and click "Next" to accept the remaining defaults (already filled in, the "JDBC Port" was "1521", and the "JDBC driver library" was "/export/home/oracle/ORA9201/jdbc/lib/classes12.zip").
 
 
 

Everyplace Synchronization

1)  In the "Everyplace Synchronization Server database configuration" panel, for the "Administrator ID", "Database password" and "Confirm database password" fields, enter "essadmin", for the "Database SID" field, enter "ORA9201", for the "Connection string" field, enter "ORA9201" (if you want ESS on it's own database, you would enter the other DB's SID here), accept the remaining defaults and click "Next". (Already filled in, the "Everyplace Synchronization Directory" was  "/opt/WebSphere/IBMSyncServer", the "Database server host name" was "(yourmachinename).raleigh.ibm.com", "JDBC Port" was "1521", the "Oracle home" was "/export/home/oracle/ORA9201", and the "JDBC driver library" was "/export/home/oracle/ORA9201/jdbc/lib/classes12.zip").

2)  In the "WebSphere Synchronization adapters" panel select "Adapter for Microsoft Exchange 2000", then click "Next".

3)  In the "Microsoft Exchange 2000 Adapter configuration" panel, for the "Host name" field enter "abe2.raleigh.ibm.com",  then click "Next". (See WEA Test Department Backend Servers for information on these accounts.)
 
 
 

Device Manager

1) In the "Device Manager configuration" panel, for the "Administrator ID", "Database password" and "Confirm database password" fields, enter "dms", for the "Oracle DBA group" field enter "dba", for the "Local Oracle user ID" field enter "oracle", accept the remaining defaults, and click "Next" (already filled in, "Device Manager directory" was "/opt/WebSphere/DMS", "IBM HTTP Server directory" was "/opt/HTTPServer", "JDBC port" was "1521", the "Oracle home" was "/export/home/oracle/ORA9201", and the "JDBC driver library" was "/export/home/oracle/ORA9201/jdbc/lib/classes12.zip").)
 
 

Summary

1)  In the "Display Summary", click "Next" to accept the defaults. (note that Steve renamed the script file "/Steves.07010845.070103.1722.DB2.IDS.R431.WEA.INS.ESS.DMS.LAS.weasun16.WEA_response.script", and clicked "Save Configuration".). Go have a latte'.
 
 
 

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 "/opt/IBMWPO/RunCommand". (note that in the "setup*", and the "RunCommand*", the "*" refers to a "randomly generated" numeric value created during the install process.)

Additional logs can be found in "/opt/WebSphere/INS/install", and "/opt/WebSphere/INS/install/RecentAlert" directories
 
 
 

Installing DB2 Everyplace Server

1)  After invoking the install script, the first screen you will see is the "View Information" section and 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 "Install Selection" panel, select "Standard Install" and click "Next".

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

5) In the "Database selection" panel, choose "IBM DB2 Universal Database", then click "Next".

6)  In the "Select Components" panel, select only the components "DB2 Everyplace" (which includes "DB2 Everyplace database setup" and "DB2 Everyplace Synchronization Server"), then click "Next".

(a panel will be displayed informing you that some software is already installed, click "Next".
 
 

WebSphere Application Server Security Configuration

1) For the "WebSphere Application Server security" panel, select "Yes", then click "Next".

2) In the "WebSphere Application Server administrator ID" panel, for the "Administrator ID", "Password", and "Confirm password" fields, enter "wpsadmin", then click "Next".

 3) In the "WebSphere Everyplace Access Portal extensions" panel, for the "Portal administrator ID", "Administrator password", and "Confirm password" fields, enter "wpsadmin", then click "Next".(already filled in, the "System user group" was "wpsadmins", the "Portal Server host name" was "(yourmachinename".raleigh.ibm.com", the "Portal base URI" was "/wps", the "Home page" was "/portal", and the "Portal customized page" was "/myportal")
 
 

DB2 Everyplace Synchronization

1) In the "DB2 Everyplace" panel, for the "DB2 administrator ID" and "Database Instance name" fields, enter "db2inst1". For the "Password", "Confirm password"  fields, enter "ibmdb2", accept the remaining defaults, and click "Next". (already filled in, the "WebSphere Application Server directory" was "/opt/WebSphere/AppServer/" and the "DB2 Everyplace directory" was "/opt/WebSphere/DB2Everyplace81").
 

Db2e Installation Summary

1)  In the "Display Summary", click "Next" to accept the defaults. (note that Steve renamed the script file "/Steves.06261121.062603.1722.DB2e.weasun16.WEA_response.script", and clicked "Save Configuration".). Go have a latte'.
 
 
 

Resources Installed by WEA

   WEA/WPO WebSphere Application Servers Installed
   WEA WebSphere JDBC Resources Installed
   WEA WebSphere Enterprise Applications Installed
   WEA Databases Installed During Full Installation
 

WEA/WPO WebSphere Application Servers Installed

WebSphere Portal
DMS_AppServer
WEA Server
Everyplace Recent Alert Server
Everyplace Synchronization Server
IBM DB2 Everyplace Server
DMconsole_AppServer
(the "Default Server" is also installed)
 

WEA WebSphere JDBC Resources Installed

wps40JDBC
WEA Services DB Driver
LasDBDriver
INS DB Driver
ESS DB Driver
(the "Sample DB Driver" is also installed)
 
 

WEA WebSphere Enterprise Applications Installed

(Note that when listed in the WAS Admin Console, some apps have a numeric value included at the end which are not included in the list below)

(yourmachinename)_sampleApp
WebSphere Member Subsystem
WPS Enterprise Application
WS Proxy
PortletInstaller_WPS_PA_
CustomizerPortlets_WPS_PA_
ThemesAndSkinsManager_WPS_PA_
CredentialAdministration_WPS_PA_
WebServicesAdministration_WPS_PA_
Settings_WPS_PA_
MarkupsManager_WPS_PA_
UsersManager_WPS_PA_
PortletManagementPortlets_WPS_PA_
Tracing_WPS_PA_
GroupsManager_WPS_PA_
SearchPortlets_WPS_PA_
ClientsManager_WPS_PA_
AccessControl_WPS_PA_
WebServicesManager_WPS_PA_
PortalContentPortlets_WPS_PA_
ContentOrganizer_WPS_PA_
QCustomizer_WPS_PA_
obconfig_WPS_PA_
QuickLinks_ea_WPS_PA_
reminder_ea_WPS_PA_
worldclock_ea_WPS_PA_
wpsmail_ea_WPS_PA_
imageviewer_ea_WPS_PA_
ClippingPortlets_ea_WPS_PA_
ClientInstaller_ea_WPS_PA_
dms_WPS_PA_
UserGroupInfoWebService
BannerAd_ea_WPS_PA_
ldapSearch_WPS_PA_
XSLT_ea_WPS_PA_
Exchange3_WPS_PA
notesiiopcalendar_WPS_PA_
notesiiopcontacts_WPS_PA_
notesiiopjournal_WPS_PA_
notesiiopmail_WPS_PA_
notesiioptodo_WPS_PA_
WebCache
DMSFileUtility_war
lasuserportlet_WPS_PA_
adminportlet_WPS_PA_
RecentAlertWebService
INSPortlet_WPS_PA_
ESS Enterprise Application
ESSAdmin_WPS_PA_
IBM DB2 Everyplace
(yourmachinename)_DMS_WebApp
(yourmachinename)_DMconsole_WebApp
 
 
 

WEA Databases Installed During Full Installation

WebSphere Application Server:   wasdbl  (alias: wasdb)
WebSphere Everyplace Access and Offline Browsing:  weasdb
WebSphere Portal:     xwpsdb  (alias: wpsdb)
WebSphere Member Services:   xwmsdb (alias: wmsdb)
Intelligent Notification Services"   insdb
Everyplace Synchronization Server:  cafprsst  (alias: cafalias)  tss1  (alias: tssalias)
DB2 Everyplace:     dsyctldb  vnurse  m_vnurse  m_vn2
Device Manager:     dms
Location Aware Services:   lasdb
 
 
 

WPO and WAS DB's

WebSphere Application Server   wasdbl  (alias: wasdb)
WebSphere Portal     xwpsdb  (alias: wpsdb)
WebSphere Member Services   xwmsdb (alias: wmsdb)
 
 
 
 

Post Installation Required Steps

After the installation has completed, manual steps are required which includes environment initialization as well as corrections for various problems in the WEA environment.

If using Oracle 9.2.0.1.0, you must modify the "startupServer.sh" file to use a 32 bit library. Edit the file
"/opt/WebSphere/AppServer/bin/startupServer.sh", and in the library definition section located a few lines after the following line (as of 07190942 build, line 103):

if [ "${DB_TYPE}" != "DB2" ]

for the "LD_LIBRARY_PATH" definition, for the "$DB_INSTANCE_HOME" variable, rename "lib" to "lib32". Instantiation of this new parameter will require the stop and start of WAS (wait until you perform additional steps below before recyclying WAS)
 

Intelligent Notification Services

1) If INS is installed, log off and then log back on the AIX session (this sets up appropriate environment variable(s).

2) Might need to apply IDS fixpack. Let's wait and see (Darren Childress doing experiments).

Offline Browsing

1) The file "/opt/WebSphere/AppServer/lib/app/config/services/ConfigService.properties" must be modified. Find the parameter "use.requestid" and change it's value to "false". You must then recycle Portal Server application server in the WebSphere Admin Console.

DB2e

1). As root user, modify WAS startup script ("/opt/WebSphere/AppServer/bin/startupServer.sh") to include the DB2 driver in the classpath. Edit "/usr/WebSphere/AppServer/bin/startupServer.sh" and at the end of the DB_CLASSPATH for Oracle, add ":/opt/IBMdb2/V7.1/java12/db2java.zip"

2) Modify the DB2 instance's ".profile" to include exporting the DISPLAY to your machine (i.e. "export DISPLAY=(yourmachinename).raleigh.ibm.com:0.0), then source the login ".profile" of the db2 user (change directory to the db2 user's home directory and execute ".  ./.profile").

After making all of the above changes, stop WAS admin server (from WAS Admin Console, select the node (i.e. "wea2aix2") right mouse click, and select "Stop"). Then, after sourcing the DB2 intances ".profile", start WAS, then the Admin Console, and start all
application servers.

Start the INS and ESS backend servers (in separate windows, execute "./startADM <yourmachinename>", "startHA", and "./esscmd init"). Logon to Portal server as administrator, select INS tab, "Manager Servers" and click on "Run All Servers)
 
 
 

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 (from a command prompt type "./adminclient.sh  &"), 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").

If you provide the "Security Center password" with anything other than "wpsbind", it will be changed. Apparently during the installation process the Security Center password was changed from the value input (i.e. "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.. "http://rushtest55.raleigh.ibm.com/wps/portal") to run the "WebSphere Everyplace Access" 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 your installation was (probably) successful.
 
 

DMS Create Jobs Problem

The following is the workaround for DMS if Setup Manager creates userid.

Switch users to "dms", modify the ".profile" to include ".    /home/oracle/.profile"

Then, as root, run the following commands:

cd <DMS_HOME>/tmp
touch DMSplugin.PalmOS
touch DMSplugin.Wince
touch DMSplugin.BaseSyncMLDM
cd <DMS_HOME>/bin
./osplugin.sh

You must then stop and restart the "DMS_AppServer" application server in the WAS console,
 

DB2e Sync Problem

1) From WAS admin console, stop the WAS admin server.

2) From Solaris prompt, login as "db2inst1".

3) Modify the ".profile" to include the following

 EXTSHM=ON
 export EXTSHM

3. Set the DB2 environment of the db2 user to include the environment variable EXTSHM. Command to be executed is:

 db2set DB2ENVLIST=EXTSHM

4) Stop DB2 instance. Command to be executed is

 db2stop  force

5) Source the login profile of the user. Execute . ./.profile from the home directory.

6) Start the DB2 instance. Command to be executed is

db2start

7) Login as root user.

8) Modify WAS startup script to include the DB2 driver in the classpath. Edit the file "/opt/WebSphere/AppServer/bin/startupServer.sh", and search for the line "elif [ "${DB_TYPE}" = "Oracle" ]".  In the "then" clause, append the string ":/opt/lpp/db2_07_01/java12/db2java.zip" to the end of the line "DB_CLASSPATH=$DB_INSTANCE_HOME/jdbc/lib/classes12.zip" (the resulting line will be "DB_CLASSPATH=$DB_INSTANCE_HOME/jdbc/lib/classes12.zip:/opt/lpp/db2_07_01/java12/db2java.zip" (with no quotes).

9) Source the login profile of the db2 user. Change directory to the "/export/home/db2inst1" directory and execute ". ./.profile".

10) Start WAS admin server.
 
 
 
 
 
 

Uninstalling Everything
 

1) Run the script "/opt/IBMWPO/uninstall/uninstall.sh" giving the build the path to your CD1 as the only parameter (i.e. "uninstall.sh   /nasimgs/cd1").

2) In the "Selecting Components", select all that are highlighted, then click "Next".  (Portal Server, WEA Basic Services, WAS, Secureway Server and Client, INS Server, IBMHTTP Server, ESS Server, DMS Server, DB2 UDS, and the DB2 Fixpack)

3) In the "Previous installation(s) of component(S)....", all are selected for uninstall, click "Next".

4) In the "Summary" click "Next". Hava a latte'
 
 
 
 
 
 
 

Example Mount Script

The following are the contents of a schell script which can be used as is or modified for mounting the build you wish. The important things to consider is the line "/opt/sbin/mount  cinta03.raleigh.ibm.com:/$1  $2", which specifies the machine ("cinta03"), as well as the directory path the build is on (i.e. "/drive1/430mona/install/cd(blahblahbla"), and the directory you are mounting as (i.e. "/mntmona1/cd1").

(by Gary Deen)
#!/bin/ksh
print  Fixing AIX/Solaris/Linux Issue....
nfso -o nfs_use_reserved_ports=1

function mymount
{
echo Mounting $1 as $2
mkdir -p $2
/opt/sbin/mount  cinta03.raleigh.ibm.com:/$1  $2
}
echo  Mounting "cinta03 drive1/421"....

mymount   /drive1/430mona/install/cd1    /mntmona1/cd1
mymount   /drive1/430mona/install/cd2-1    /mntmona1/cd2-1
mymount   /drive1/430mona/install/cd2-2    /mntmona1/cd2-2
mymount   /drive1/430mona/install/cd2-3    /mntmona1/cd2-3
mymount   /drive1/430mona/install/cd2-4    /mntmona1/cd2-4
mymount   /drive1/430mona/install/cd2-5    /mntmona1/cd2-5
mymount   /drive1/430mona/install/cd2-6    /mntmona1/cd2-6
mymount   /drive1/430mona/install/cd2-7    /mntmona1/cd2-7
mymount   /drive1/430mona/install/cd3    /mntmona1/cd3
mymount   /drive1/430mona/install/cd4    /mntmona1/cd4
mymount   /drive1/430mona/install/cd5    /mntmona1/cd5
mymount   /drive1/430mona/install/cd6    /mntmona1/cd6
mymount   /drive1/430mona/install/cd7    /mntmona1/cd7
mymount   /drive1/430mona/install/cd8    /mntmona1/cd8
mymount   /drive1/430mona/install/cd9    /mntmona1/cd9