Full Install (with DB2)
(Created with version 06140204 of the build)
Introduction
Installation
Preparation
Installing
the WebSphere Everyplace Access Product
IBM
HTTP Server
IBM
Directory Server
WebSphere
Application Server
WebSphere
Application Server Security Configuration
Portal
Server
WebSphere
Everyplace Access Core Services
Location
Aware Services
Intelligent
Notification Services Server
Everyplace
Synchronization
DB2
Everyplace Synchronization Server
Device
Manager
Summary
Installation
Details
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
Installation
with Microsoft Active Directory
Installation
with iPlanet Directory Server
Uninstalling
Everything
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 Java (1.30 and 1.31), "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", "DB2 Everyplace", "Intelligent Notification Server", "Device Management Server", "Location Aware Services", 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.
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".
Before beginning your installation, you must assure your DISPLAY environment variable has been set properly for your machine. This is required for the DMS portion of the installation. This should be done by including an "export" statement in the ".profile" file used for the session you invoke the WEA Setup Manager installer from. Edit your ".profile", and include the statement "export DISPLAY="(yourmachinename).raleigh.ibm.com:0.0" (i.e. "export DISPLAY=weasun10.raleigh.ibm.com:0.0").
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 wea2aix6:/WEA /WEA"). In the directory
"/WEA/tools/shayden",
there is a profile ".profile.sol" 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/ORA817" and "export ORACLE_HOME"). You must logoff and back on to instantiate this value (to assure the value is set, type "echo $ORACLE_HOME").
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, Solaris will automatically mount the CDROM in a directory "/cdrom".
2) Proceed to Running
the Setup Manager
Installing From NAS
1) Log on to Solaris as "root"
2) From the Solaris command prompt create a directory "altnas" (i.e. "mkdir /altnas")
3) Mount the "altnas" file system (i.e. "mount altnas:/staging /altnas").
4) Change directories to the network drive which has the builds on it by changing directories to "/altnas/WEA_R430/". 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. "/altnas/WEA_R430/06140204/done").
4) Determine the build you are interested in and change to that directory (i.e. "06140204"), and in it change to the "cdlinks/cd1" directory (this full path will be "/altnas/WEA_R430/06140204/cdlinks/cd1")
5) 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" = Solaris, and 1 = the
first
build for that day
Example 2:
mntfria3
equals mnt = mount, "fri" = Friday, "a" = 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"),
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
1) At the Solaris command prompt, if installing from CD's, from the root directory ("/") type "/cdrom/install.sh", otherwise, if installing from NAS or cinta03, assure you are in the appropriate "cd1" directory and type "./install.sh". Java will be installed initially, and then 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 the WebSphere Everyplace Access Product
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 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") , "Device Manager" (which includes "Device Manager database" and "Device Manager"), and "DB2 Everyplace", (which includes "DB2 Everyplace database setup", and "DB2 Everyplace Synchronization Server", "IBM Directory Server", and "DB2 Universal Database Server", then click "Next".
(Note: for installation with Microsoft Active Directory, see
Installation
with Microsoft Active Directory NOT VERIFIED YET ON WEA R431)
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".
(at this point, if you have not previously modified your "/etc/system" file to include the appropriate paramaters/values, you will be queried as to whether you want SUM to update this file. You must select "Yes", and let SUM do the modification. When this is done, a popup will appear stating the operation is done and that you must reboot your system. Reboot your system and start SUM again, using the same values as before).
When installing WEA using a different LDAP server, if you install INS, you still have to perform the following:
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").
(Note: for installation with Microsoft Active Directory, see
Installation
with Microsoft Active Directory)
1) In the "WebSphere Application Server directory" panel, click "Next" to accept the defaults ("WebSphere Application Server Directory" is "/opt/WebSphere/AppServer").
2) In the "WebSphere Application Server database" panel "Is this an existing database" field, select "No", and then click "Next".
3) In the "WebSphere Application Server administration" panel, enter "wasinst" for the "Database administrator ID", "Database password" and "Confirm database password" fields, accept the remaining defaults, then click "Next" (already filled in, "Local database group" was "wasgrp").
4) In the "WebSphere Application Server database settings"
panel,
click "Next" to accept the defaults ("Local
database
name" was "wasdbl", "Local database alias" was "wasdb", "Node name" was
"LOOPBACK", and "Database server port" was "55555").
WebSphere Application Server Security Configuration
1) For the "WebSphere Application
Server
security" panel, select "No", then click "Next".
If you are installing an LDAP directory other than SecureWay Directory Server, steps 3 and 4 will be different. See the appropriate LDAP directory instructions for specifics for your LDAP Directory.
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) (Using IDS) - In the "Portal Server LDAP directory" panel, for the "Administrator password" and "Confirm password" fields, enter "wpsadmin", then click "Next" to accept the remaining default (already selected/filled in, "IBM Directory Server" was selected, the "Administrator Distinguished Name" was "cn=wpsadmin", the "Portal Server Suffix" was "dc=raleigh,dc=ibm,dc=com" (or "dc=rushmore"), the "Portal Server LDAP directory server" is the domain name of your machine (i.e. "(yourhostname).raleigh.ibm.com"), and LDAP Port Number was "389").
(Using Lotus Domino LDAP) In the "Portal Server LDAP directory" panel, select "Lotus Domino Application Server", for the "Portal Server LDAP directory server" field, enter "rushtest08.raleigh.ibm.com" (or your Domino LDAP box), for the "Administrator Distinguished Name" field enter "cn=Domino Admin,o=raleigh", for the "Administrator password" and "Confirm password" fields, enter (generic password), and for the "LDAP port number", enter "386", then click "Next". ("Portal Server suffix" was blank).
5) (Using IDS) 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" (or "cn=users,dc=rushmore"), "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" (or "cn=groups,dc=rushmore"), "Administrator Distinguished Name" was "uid=wpsadmin,cn=users,dc=raleigh,dc=ibm,dc=com" (or "uid=wpsadmin,cn=users,dc=rushmore"), and "Administrative group Distinguished Name" was "cn=wpsadmins,cn=groups,dc=raleigh,dc=ibm,dc=com" (or "cn=wpsadmins,cn=groups,dc=rushmore").
(Using Lotus Domino LDAP) 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 "cn", "User
Distinguished
Name suffix" was "o=raleigh", "Group Object Class" was "groupOfNames",
"Group Member" was "member", "Group Distinguished Name prefix" was
"cn",
"Group Distinguished Name suffix" was blank, "Administrator
Distinguished
Name" was "cn=wpsadmin,o=raleigh", and "Administrative group
Distinguished
Name" was "cn=wpsadmins" (and was grayed out)).
6) In the "Portal Server database" panel, for the "Portal Server database configuration options" select "Create and initialize a new database", then click "Next".
7) In the "Portal Server database configuration" panel , for the "Database administrator ID", "User Password", and "Confirm password" fields enter "wasinst, then click "Next" to accept the remaining defaults (already filled in, the "Database name" was "wpsdb", the "JDBC database driver" was "COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource", and the "JDBC driver library" was "/opt/IBMdb2/V7.1/java12/db2java.zip").
8) In the "Member Services database" panel, for the "Select the Member Services option that best fits your environment" select "Create and initialize a new database", and click "Next".
9) In the "Member Services database configuration"
panel,
for the "Database administrator ID", "Administrator password", and
"Confirm
password", enter "wasinst", then click "Next" to accept the remaining
defaults
(already
filled in, the "Database Name" was "wmsdb", the "JDBC database driver"
was "COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource", and the "JDBC
driver
library" was "/opt/IBMdb2/V7.1/java12/db2java.zip").
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 "Database administrator ID", "Database administrator password",
and "Confirm password" fields enter "wasinst", then click "Next" to
accept
the remaining defaults (already filled in, the
"Database
server port" was "55555", the "JDBC driver" was
"COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource",
and the "JDBC driver path" was "/opt/IBMdb2/V7.1/java12/db2java.zip").
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" (or "uid=wpsadmin,cn=users,dc=rushmore"), the "Administrative group Distinguished Name" was "cn=wpsadmins,cn=groups,dc=raleigh,dc=ibm,dc=com" (or "cn=wpsadmins,cn=groups,dc=rushmore"), the "HTTP proxy server" and "Proxy port" fields were blank, the "Portal Server directory" was "/opt/WebSphere/PortalServer", and the "WebSphere Application Server directory" was "/opt/WebSphere/AppServer").
3) In the "Location Aware Services database information" panel, for
the "Database administrator ID", "Database administrator password", and
"Confirm password" fields enter "wasinst", accept the remaining
defaults,
then click "Next" (already filled in, the
"Database
directory" field was "/opt/IBMdb2/V7.1").
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 "Intelligent Notification Services database setup",
for the "Database administrator ID", "Database
password", and "Confirm password" fields, enter "wasinst" and click
"Next"
to accept the remaining defaults (already filled
in, the "Database name" was "insdb", and the "JDBC library" was
"/opt/IBMdb2/V7.1/java12/db2java.zip")
1) In the "Everyplace Synchronization Server database configuration" panel, for both sets of "Password" and "Confirm password" fields, enter "wasinst" (total of 4 fields), for the "Administrator ID" field, enter "essadmin", and accept the remaining defaults and click "Next". (Already filled in,"Node Name" was "LOOPESS", "Port" was "55555", "Everyplace Synchronization directory" was "/opt/WebSphere/IBMSyncServer", "Instance" was "wasinst", "JDBC Driver" was "COM.ibm.db2.jdbc.app.DB2Driver", "JDBC URL Prefix" was "jdbc:db2:", "JDBC Library" was "/opt/IBMdb2/V7.1/java12/db2java.zip", and the "System user group" was "essgrp")
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.)
DB2 Everyplace Synchronization Server
1) In the "DB2 Everyplace" panel, for the "DB2
administrator ID", "Password", "Confirm password" and "Database
instance
name" fields, enter "wasinst", then click "Next" (already
filled in, "WebSphere Application Directory" was
"/opt/WebSphere/AppServer",
and "DB2 Everyplace directory" was
"/opt/WebSphere/IBMSyncServer/DB2Everyplace81",
)
1) In the "Device Manager configuration" panel, for the "Database
administrator ID", "Database password" and "Confirm password"
fields,
enter "wasinst", 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 driver" was
"/opt/IBMdb2/V7.1/java12/db2java.zip",
"Instance name" was "wasinst", and "Database port" was "55555")
1) In the "Display Summary", click "Next" to accept the
defaults.
(note that Steve renamed the script file "/Steves.06140204.061403.1442.R431.Full.BVT.weasun08.WEA_response.script",
and clicked "Save Configuration".). Go have a latte'.
After several minths a popup "Configuring for Admin Role " will appear.
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.). When the installation completes, the majority of SUM logs will be located in a zip file in the "/opt/IBMWPO/logs" directory. HOWEVER, this does not contain all logs. Individual components have additional logs in their associated directory (i.e. /opt/WebSphere/IBMSyncServer/logs", etc.)
Additional logs can be found in "/opt/WebSphere/INS/install", and
"/opt/WebSphere/INS/install/RecentAlert"
directories
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.
Intelligent Notification Services
1) If INS is installed, logoff 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 "/usr/WebSphere/AppServer/lib/app/config/services/ConfigService.properties" must be modified. Find the paramater "use.requestid" and change it's value to "false". You must then recycle Portal Server application server in the WebSphere Admin Console.
DB2e
1. Login as root user.
2. Stop WAS admin server.
3. Modify WAS startup script to include the DB2 driver in the classpath. Edit startupServer.sh and add "/opt/IBMdb2/V7.1/sqllib/java12/db2java.zip" at the end of the DB_CLASSPATH for Oracle.
4. Source the login ".profile" of the db2 user. Change directory to the db2 user's home directory and execute ". ./.profile".
5. Start WAS admin server.
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 "cd /opt/WebSphere/AppServer/bin", and then 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").
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://(yourmachinename.raleigh.ibm.com/servlet/snoop". The userid and password for accessing servlets is "wpsadmin".
To verify the installation of WEA, use the url "http://(yourmachinename.raleigh.ibm.com/wps/portal" to run the "WebSphere Everyplace Access" portlet. 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.
Installation with Microsoft Active Directory
1) In the "Portal Server " "Selection of LDAP server" panel, select "Microsoft Active Directory", and in the "LDAP Server" field enter "wpspro.raleigh.ibm.com", in the "User DN" field enter "cn=wpsadmin,cn=users,dc=raleigh,dc=raleigh,dc=ibm,dc=com", in the "User password" and Confirm password" field enter "wpsadmin", and in the "Suffix" field enter "dc=raleigh,dc=ibm,dc=com", then click "Next".(LDAP Port Number was "389")
2) In the "LDAP Configuration" panel
"User
Object Class" field enter "user", in the "User DN Prefix" field enter
"cn",
in the "User DN Suffix" field enter
"cn=users,dc=raleigh,dc=ibm,dc=com",
in the "Group Object Class" field enter "group", in the "Group Member"
field enter "member", in the "Group DN Prefix" field enter "cn", in the
"Group DN Suffix" field enter "cn=users,dc=raleigh,dc=ibm,dc=com", in
the
"Administrator DN" field enter
"cn=wpsadmin,cn=users,dc=raleigh,dc=ibm,dc=com",
and in the "Administrative group DN" field enter
"cn=wpsadmins,cn=users,dc=raleigh,dc=ibm,dc=com",
then click "Next".
3) At the 13 step portion of the installation, in the "Select Users/Groups - AdminRole" panel, for the "Users", select "CN=wpsadmin,CN=users" , and for the "Groups", select "CN=wpsadmins,CN=Users, dc=raleigh,dc=ibm,dc=com", and click "OK".
4) In the "Security Center", click "Apply", and in the "Warning" popup, click "OK".
5) In the "Security Center" panel, click "OK". Follow
the
remaining steps in the "Configuring the Admin Role" section.
Installation with iPlanet Directory Server
1) In the "Portal Server " "Selection of LDAP server" panel, select "iPlanet", and in the "LDAP Server" field enter "wpspro.raleigh.ibm.com", in the "User DN" field enter "cn=Directory Manager", in the "User password" and Confirm password" field enter "wpstest1", and in the "Suffix" field enter "dc=raleigh,dc=ibm,dc=com", and "LDAP Port Number" was "388", then click "Next".
2) In the "LDAP Configuration" panel "User Object Class" field enter/accept "inetOrgPerson", in the "User DN Prefix" field enter/accept "uid", in the "User DN Suffix" field enter "ou=People,dc=raleigh,dc=ibm,dc=com", in the "Group Object Class" field enter "groupOfUniqueNames", in the "Group Member" field enter "uniquemember", in the "Group DN Prefix" field enter "cn", in the "Group DN Suffix" field enter "ou=groups,dc=raleigh,dc=ibm,dc=com", in the "Administrator DN" field enter "uid=wpsadmin,ou=People,dc=raleigh,dc=ibm,dc=com", and in the "Administrative group DN" field enter "cn=wpsadmins,ou=People,dc=raleigh,dc=ibm,dc=com", then click "Next".
3) In the "Intelligent Notification Services Server" "Select Portal LDAP Type", select "Other LDAP server".
4) At the 13 step portion of the installation, in the "Select Users/Groups - AdminRole" panel, for the "Users", select "CN=wpsadmin,CN=users" , and for the "Groups", select "CN=wpsadmins,CN=Users, dc=raleigh,dc=ibm,dc=com", and click "OK".
4) In the "Security Center", click "Apply", and in the "Warning" popup, click "OK".
5) In the "Security Center" panel, click "OK". Follow the remaining steps in the "Configuring the Admin Role" section.
6) At the "Intelligent Notification Services Server" "Select
Portal
LDAP Type" panel, select "Other LDAP server" and click "Next".
You
will be prompted with a dialog box informing you "If Portal Server is
using
an LDAP server other than SecureWay Directory, you must import or
create
Intelligent Notification Services user and group definitions in the
directory.
Refer to the LDAP documentation for more information and specific
instructions",
click "OK". Supposedly these have already been added to
"wpspro.raleigh.ibm.com"
iPlanet directory.
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'
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 "/usr/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(blahblahblah"), and the directory you are mounting as (i.e. "/mntmona1/cd1").
(by Gary Deen)
#!/bin/ksh
print Fixing Solaris/Linux Issue....
nfso -o nfs_use_reserved_ports=1
function mymount
{
echo Mounting $1 as $2
mkdir -p $2
/usr/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