Full Install

(Using Build  430 GM)

Introduction
Installation Preparation
Installing the WebSphere Everyplace Access Product
   Java Installation
   WebSphere EveryPlace Access Installation Selection
   IBM HTTP Server
   DB2 Universal Database 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
Testing The Installation
Restarting WebSphere Everyplace Access
 
 
 

Introduction

This method presumes you are connected to a network drive which has a WebSphere Everyplace Access (WEA) build available (or are alternatively installing from CDs. If using the CD method, you will be prompted to change the media when required). This process describes the use of Setup Manager, which installs WEA. It includes the installation of Java, DB2, WebSphere Application Server (WAS), the WAS fixpack 4, the Portal Server, portlets, WEA Core Services, the Device Manager Server, Everyplace Synchronization Server, and the Intelligent Notification Services, Location Aware Services, etc.

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.

Setup Manager Logging

When installing, logs are created in the folder "*:/Program Files/IBMWEA". This includes 2 files "setup<randomstringofnumbers>", where "randomstringofnumbers" is a string of digits (i.e. "setup_05.11.17.27.log"). The first setup log file is created by Setup Manager and will reflect the initial logging done by Setup Manager. After the installation of DB2, you must reboot/restart the machine, which will result in the creation of a second log for logging the remainder of the installation. Within each of the "setup<datestamp>.log>" file, there will be references to "command" files, which are the result of the execution of Setup Manager operations (i.e. located in "*:\Program Files\IBMWEA\RunCommand_05.11.17.27"). These files are more details of the operation and/or failure of a particular components installation. Sections of the "setup<randomstringofnumbers>" file are followed by a "0", reflecting the success of an operation, or a "1", reflecting the failure. When troubleshooting, occasionally the root cause of an error can be traced back to previous failures, so you cannot always assume the last problem found was the main culprit.

Once Setup Manager is completed and you click the "Finish" button, these log files are zipped into a file that contains all associated files for this installation.
 
A word of advice from the author. Avoid going backward from a panel to previous panels. Doing so can be unhealthy. If you go back, you might as well stop Setup Manager and invoke it again.

Installation Preparation

Before installation of WEA with ESS, you must have the Notes Client and Microsoft Outlook installed on your machine (see ESS Prerequisite Software Installation )

If installing from CDs, simply put in the first CD and the Setup Manager will automatically start.

In all examples and steps that follow, the double quote (") is used to reflect a panel name, input field, or value that should be input, and is not to be entered as part of the value.

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

 
 
 

Installing the WebSphere Everyplace Access Product
 

Java Installation

1)  In the Java installation "Choose Setup Language" dialog box, select "English", then click "OK"

2)  Once the "IBM(R) Developer Kit for Windows 2.0 Setup" GUI appears, in the "Welcome" dialog box, click "Next".

3)  In the "Software License Agreement" dialog box, click "Yes".

4)  In the "Choose Destination Location" dialog box, click "Next" to accept the defaults.

5)  In the "Select Components" dialog box, click "Next" to accept the defaults.

6)  If a "Question" popup appears querying "Install the Java Runtime Environment as the System JVM?", click "Yes".

7)  In the "Start Copying Files" dialog box, click "Next" to accept the defaults. Wait a minth.

8)  In the "Setup Complete" dialog box, click "Finish" to proceed.

Readme files and other documentation can be found in the C:\Program Files\IBM\Java131\docs directory.
 
 

WebSphere EveryPlace Access Installation Selection

1)  In the "View Information" "View Prerequisites" panel for WebSphere Everyplace Access, click "Next".

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

3)  In the "Select Installation Type" panel, select "Standard Install" and click "Next".

4)  You then have the option of entering a response file of a previously recorded install if desired, do not enter a value, click "Next".

5)  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 setup" 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: At this point any warnings would appear stating you already have software installed that Setup Manager will install, or that you lack prerequisite software, or have later versions of software, etc. If so, either fix your problem, confirm your environment is OK, then click "Next".
 

IBM HTTP Server

1)  In the "IBM HTTP Server Directory" panel, click "Next" to accept the defaults (the defaults were "C:\Program Files\IBM HTTP Server").

2)  In the "Collecting Admin Username for IBM HTTP Server" panel, enter "ihsadmin" for the "Administrator ID", and "ihsadm1n" for the "Password", and "Confirm password" fields, then click "Next".
 
 

DB2 Universal Database Server

1)  In the "DB2 Server Directory" panel, click "Next" to accept the defaults (default is "C:\Program Files\SQLLIB").

2)  In the "DB2 Administrator ID" panel, enter "db2admin" for the username, and "ibmdb2" for the password and confirm password fields, then click "Next".
 
 

IBM Directory Server

1)  In the "IBM Directory Server directory"panel, for the "IBM Directory Server directory" field, click "Next" to accept the defaults (i.e. "C:\Program Files\IBM\LDAP").

2)  In the "IBM Directory Server information" panel, in the "Adminstrator ID" field enter "cn=wpsadmin", for the "Password" and "Confirm password" fields, enter "wpsadm1n",  in the "Suffix" field, enter "dc=raleigh,dc=ibm,dc=com" (DO NOT INCLUDE ANY SPACES IN THE SUFFIX!) , then click "Next" (LDAP port to use was "389").
 
 

WebSphere Application Server

1)  In the "WebSphere Application Server directory" panel, click "Next" to accept the defaults (i.e. "c:\WebSphere\AppServer").

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

3)  In the "WebSphere Application Server database" panel, for the "Is this an existing database" question, select "No", and then click "Next".

4)  In the "WebSphere Application Server administrator" panel, for the "Database administrator ID" enter "db2admin" , and enter "ibmdb2" for the "Database password, and "Confirm database password" fields, then click "Next".

5)  In the "WebSphere Application Server database settings" panel, click "Next" to accept the defaults  (already filled in, "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, for the "Is WebSphere Application Server Security enabled" 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, and click "Next".

2)  In the "Portal Server Configuration" panel, click "Next" to accept the defaults. (already filled in, the "Portal Server Directory" was "C:\WebSphere\PortalServer", the "Host name" was "(yourmachinename).raleigh.ibm.com", the "Base URI" was "/wps", the "Home page" was "/portal", and the "Customized page" was "/myportal". The "Proxy host" and "Proxy port" were blank. FYI, the Base URI and the Home page will be the URL to access the Portal portlet, i.ee "http://(yourmachinename).raleigh.ibm.com/wps/portal".).

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

4)  In the "Portal Server LDAP directory" panel, select "IBM Directory Server", for the "Portal Server LDAP directory server", enter the domain name of  your machine (i.e. "stup1d.raleigh.ibm.com"). For the "Administrator Distinguished Name", enter "cn=wpsadmin" (with no quotes). For the "Administrator
password" and "Confirm password" fields, enter "wpsadm1n", then click "Next" to accept the remaining default (the "Portal Server Suffix" was
"dc=raleigh,dc=ibm,dc=com", and LDAP Port Number was "389").

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

5)  In the "Portal Server database" panel, select "Create and initialize a new database", and click "Next".

6)  In the "Portal Server database configuration" panel, for the "Database administrator ID" field, enter "db2admin", enter "ibmdb2", and for the "User Password", and "Confirm password" fields,and click "Next". (already filled in, the "Database Name" was "wpsdb", the "JDBC database driver" was "COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource", the "JDBC URL prefix" was "jdbc:db2", and "JDBC driver library" was "C:\Program Files\SQLLIB\java\db2java.zip").

7)  In the "Member Services database" panel, select "Create and initialize a new database", and click "Next".

8)  In the "Member Services database configuration" panel, for the "Database administrator ID" field, enter "db2admin", for the "Administrator password" and "Confirm password" fields, enter "ibmdb2", then click "Next" (already filled in is the "Database Name" "wmsdb", the "JDBC database driver" was "COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource", the "JDBC URL Prefix" was "jdbc:db2", and "JDBC driver library" was "C:\Program Files\SQLLIB\java\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, the "WebSphere Everyplace Access directory" was "C:\WebSphere\WEACoreServices").

2)  In the "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,  then click "Next" to accept the defaults. (already filled in, "Portal Server host name" was (yourmachinename).raleigh.ibm.com", the "Portal base URI" was "/wps", the "Home page" was "/portal", the "Portal customized page" was "/myportal", the "Portal administrator ID" was  "wpsadmin", the "Portal administrator ID" was "wpsadmin", the "Portal administrator password" and "Confirm password" were "wpsadmin" (actually 8 "*"s), the "Administrator group" was "wpsadmins").

4) In the "WebSphere Everyplace Access database setup" panel, for the "Database Administrator ID" field enter "db2admin", for the "Database administrator password" and "Confirm password" fields, enter "ibmdb2", 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 "C:\Program Files\SQLLIB\java\db2java.zip").
 
 

Location Aware Services

1) In the "Location Aware Services directory" panel, accept the default and click "Next" (already filled in was the value "/usr/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
"C:\WebSphere\PortalServer", and the "WebSphere Application Server directory" was "C:\WebSphere\AppServer").

3) In the "Location Aware Services database information" panel, for the "Database administrator ID" field enter "db2admin", for the "Database administrator password", and "Confirm password" fields enter "ibmdb2",  accept the remaining defaults, then click "Next" (already filled in, and the "Database directory" field was "C:\Program Files\SQLLIB").
 
 

Intelligent Notification Service

1)  In the "Intelligent Notification Services directory" panel, click "Next" to accept the defaults. (already filled in, the "Host name" was "(yourmachinename".raleigh.ibm.com", and the "Install directory" was "c:\WebSphere\INS")

2)  In the "Intelligent Notification Services configuration" panel, click "Next" to accept the default path (i.e. "C:\WINNT\TEMP\").

3)  In the "Intelligent Notification Services database setup" panel, in the "Database administrator ID" field enter "db2admin", and in the "Database password" and "Confirm password" fields enter "ibmdb2", accept the remaining defaults and click "Next". (already filled in, the "Database name" was "insdb", and the " JDBC library" was "C:\Program Files\SQLLIB\java\db2java.zip").
 
 

Everyplace Synchronization Server

1)  In the "Everyplace Synchronization Server database configuration" panel, for the "Administrator ID" field enter "db2admin", for the "Password" and "Confirm password" fields, enter "ibmdb2", accept the remaining defaults and click "Next". (Already filled in,"Node Name" was  "LOOPESS", "Port" was "55555", "Everyplace Synchronization directory" was "C:\WebSphere\IBMSyncServer", "JDBC Driver" was "COM.ibm.db2.jdbc.app.DB2Driver", "JDBC URL Prefix" was "jdbc:db2:", "JDBC Library" was "C:\Program Files\SQLLIB\java\db2java.zip")

2)  In the "Everyplace Synchronization Adapters" panel, select "Adapter for Lotus Domino", "Adapter for Microsoft Exchange 2000", and "Adapter for Microsoft Exchange 5.5", then click "Next".

3)  In the "Microsoft Exchange 5.5 Adapter configuration" panel, for the "Host name" field, enter your host (i.e. "pvcex55.raleigh.ibm.com"), for the "User ID" enter the appropriate value (i.e. "Administrator"), and for the "Password" and "Confirm password" fields enter the appropriate values (i.e. "pv1cex55"), then click "Next". ("Domain name" can be left blank).

4)  In the "Microsoft Exchange 2000 Adapter configuration" panel, for the Hostname field enter "pvcexch.raleigh.ibm.com", then click "Next".

5) In the "Lotus Domino Adapter configuration" panel, for the "Hostname" field enter "imabox.raleigh.ibm.com" (FULLY QUALIFIED DOMAIN NAME!), and the "Username" field enter the appropriate name (i.e. "admin"), and "Notes Password" and "Confirm password" fields enter your password (i.e. "adminwea"), then click "Next".
 
 
 
 

DB2 Everyplace Synchronization Server

1) In the "DB2 Everyplace" panel, for the "DB2 administrator ID" enter "db2admin", for the "Password" and "Confirm password" fields enter "ibmdb2", then
click "Next". (already filled in, "WebSphere Application Server Directory" was "c:\WebSphere\AppServer", and "DB2 Everyplace Directory" was "c:\WebSphere\IBMSyncServer\db2e").

 

 

Device Manager

1)  In the "Device Manager Configuration" panel, for the "Database Password" and "Confirm Password" enter ("ibmdb2"), click "Next" to accept the defaults (already filled in, "Device Manager directory" was "C:\WebSphere\DMS", "IBM HTTP Server directory" was "c:\Program Files\IBM HTTP Server", JDBC Driver was "C:\Program Files\SQLLIB\java\db2java.zip", and the "Database Username" was "db2admin").
 
 
 
 

Summary

1)  In the "Display Summary" panel, save your response file and click "Next". (note that Steve renamed the script file "C:\imaboxWEA430GM.05-10-04.WEA_response.script", and clicked "Save Configuration".). Go have a latte'.
 
 

Installation Details

At the point DB2 is installed a popup will be displayed telling you to reboot your machine. Do it. After you reboot, the installation will continue.

After several minths a popup "Configuring for Admin Role" will appear.  Before performing these instructions it is necessary to apply an APAR fix for WAS on the machine. Follow the instructions in the section "Installation for Expiring WAS Certificates". Then 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. You will be queried as to whether you want to perform the steps, as you already have, click "No". The installation will then continue.
 

Wait a month, and eventually an "Installation Complete" popup should be displayed stating you should restart your machine, click "OK". In the Display Summary window, click "Finish", and then restart your machine.  Once you restart your machine you will need to perform the operations in the section Starting WEA and if you choose, you can test your installation by performing the operations in the Testing The Installation section.
 

WEA And Component Logs

Most of the WEA components have associated WAS application servers, directory structure, and associated log(s) directories. A plethora of logs exist by default and additional logging can be turned on via configuration/parameter adjustments. Each application server has an

WAS logs are in *:\WebSphere\AppServer\logs", "tracefile" being the most informative for normal operation

WEA logs are in *

Installation for Expiring WAS Certificates

1)  The install will proceed and at some point during the "Portal Server" installation a pop-up will appear that asks you to configure the Admin Role.  Normally we would execute these instructions right away, but since the WAS security ceriticates expired on Jan. 15, 2004, we now have to install PQ77261 during every WEA installation at this point because the WAS Admin Server will not start without them.

2)   When the "Configuring the Admin Role" pop-up appears, using Windows Explorer (or DOS commands if you wish), in the folder "C:\WebSphere\AppServer" create a new folder "CertFix".

3)   We will now download the PQ77261 fix to our new folder.  The fix has been placed on pvcsvr.  From a DOS prompt, change to the new folder, and type “ftp pvcsvr.raleigh.ibm.com” and press enter.  Login as username “ftpuser” and password “pvc1pvc”.

4)   Type “cd Software/WAS_Cert_Fix” and press enter.  Type “ls” and press enter to display the files in this directory.  We want to retrieve “PQ77261_Fix.jar”.

5)   Type “bin” and press enter to change to binary mode.

6)   Type “get PQ77261_Fix.jar” and press enter.  The transfer should complete successfully.

7)   Exit the FTP utility. You should be in “C:\WebSphere\AppServer\CertFix” and have "PQ77261_Fix.jar" in this folder.

8)   Type "(correct java)\java -jar PQ77261_Fix.jar -backupJar PQ77261_backup.jar" and press enter.

9)   The fix install program will prompt you for a target directory.  Type "c:\WebSphere\AppServer" and press enter.  You should see the message "*** End of PQ77261 Install Process *** with no errors."

10)   We must now and start WAS (Windows "Start", "Programs", "IBM WebSphere", "Application Server V4.0", and click on "Start Admin Server").

11) Return to normal installation (perform Admin Config steps).

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)
 
 

Testing The Installation

At this point WEA and associated software should be installed, but WAS and your applications will need to be started.

1)  Start the "IBM SecureWay Directory V3.2.2" service.

2)  Start the "IBM WS AdminServer 4.0" service.

3)  Start the WebSphere Administration Console (Windows "Start", "Programs", "IBM WebSphere", "Application Server V4.0", and click on "Administrator's Console"), and when queried for authentication, use the value "wpsadmin" for the ID and "wpsadm1n" for the 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/wpsadm1n").

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

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

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

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

If the snoop servlet and portal portlet both work your installation was (probably) successful.
 
 

Restarting WebSphere Everyplace Access

There are often more than one way to stop and start WEA and it's associated components, i.e. the Windows "Services" utility, from Windows menu bar "Start", "Programs", etc, or from the DOS command prompt. The following simply uses the Windows "Services" utility.

Stopping WEA

From the Windows "Services" utility, if desired/necessary, stop the "IBM Everyplace Synchronization Server", the "IBM WS Admin Server", and then the "IBM SecureWay Directory V3.2.2".

Starting WEA

First start the "IBM Directory Server", then "IBM WS Admin Server". Once these servers have been started you can optionally start the "IBM Everyplace Synchronization Server". You can also start the INS services (i.e "Windows "Start", "Programs", "IBM Intelligent Notification Services", and click on "Start Administration Component", wait for it to start, and then start "StartHA" ("Windows "Start", "Programs", "IBM Intelligent Notification Services", and click on "StartHA"). To start the remaining INS servers, you must logon to the WEA portal as administrator, select the "Intelligent Notification" tab, and in that portlet click "Run all servers".

(alternatively)

For ESS, you can, from a DOS command prompt, go to folder "*:\WebSphere\IBMSyncServer\caf\bin" and execute the command "esscmd init", and that DOS window will remain a "logging" window for ESS server operations.

For INS, you can, from a DOS prompt, go to folder "*:\WebSphere\INS\bin" and execute the command "startADM" giving the machine name as a parameter (i.e. "startADM stup1d"), and from another DOS window prompt, in the same folder (*:\WebSphere\INS\bin"), execute the command "startHA". Test will also become logging windows for these server's operation. To start the remaining INS servers, you must logon to the WEA portal as administrator, select the "Intelligent Notification" tab, and in that portlet click "Run all servers".

At this point you should be able to configure and operate all WEA components.
 
 

ESS Prerequisite Software Installation

Backend servers used in the following:  Exchange 5.5, Exchange 2000, and Domino 6.5.1, and require the appropriate client to be on the WEA machine for access to the backend servers.

Obtain Outlook 2000 Software

(From sdsmsrv)

1) Create a temporary folder on your computer to copy the software to.

2) Connect to a network drive that has the software on it (i.e. "net use *  \\sdsmsrv\software").

3) Change directories to "yourdrive:\IBM\office2k". Copy the file "office2k_ISDS_EA" to your temporary folder.

4) Double click the "office2k_ISDS_EA" file, which will extract the Office 2k files.

5) Proceed to Installation of Microsoft Outlook.

(From pvcsvr)

1) Map network drive on pvcsvr (from DOS prompt type "net use *   \\pvcsvr\software"), and change directories to "\\Pvcsvr\software\Microsoft Office 2000\Office 2000 Premium SR-1 Disk 1", then proceed to Installation Of Microsoft Outlook.

Installation Of Microsoft Outlook

1) Double click the "SETUP" application.

Notus Notes Client Installation

1) Change directories to "yourdrive:\IBM\Lotus_Notes\R6\6.5\AllClients", and execute "c5163na.exe", which will install the Client. After all files are extracted, the "Lotus Notes 6.5 - Installation Wizard" GUI will appear, click "Next".

2) In the "License Agreement" panel, click "I accept the terms in this license agreeement", then click "Next".

3) In the "Customer Information" panel, for the "User Name" field, enter the appropriate value (i.e. "PVC WEA"), for the "Organization" field enter the appropriate value (i.e. "IBM"), then click "Next".

4) In the "Installation Path Selection" panel, accept the defaults and click "Next".

5) In the "Custom Setup" panel, accept the defaults and click "Next".

6) In the "Ready to Install the Program" panel, accept the default ("Make Notes the default email..." selected), and click "Install". (wait a minth).

7) In the "Install Wizard Completed" panel, click "Finish".

Configure the Lotus Notes Client

For this section you must obtain the Administrator ID file from the associated Domino Server (i.e. "imabox" "admin.id" file is in c:\Domino 6.5.1 Stuff"), and place it on the machine you are installing WEA on (for later configuration steps). Place the file "admin.id" file in your local machine's "C:\Program Files\Lotus\Notes\data" folder.

1) From the Windows menu bar click on "Start", "Programs", "Lotus Applications", and click on "Lotus Notes".

2) In the "Lotus Notes Client Configuration" "Welcome" panel click "Next".

3) In the "User Information" panel, for the "Your Name" field enter "admin", and for the "Domino server" field enter "imabox", then click "Next". ("I want to connect to a Domino server" was checked).

4) In the "How Do You Want To Connect To A Domino Server" panel, select the default ("Set up a connection to a local area network (LAN)"), then click "Next".

5) In the "Domino Server Network Information" panel, accept the default value for the "Domino server name" ("imabox"), and for the  "Please provide specific network information" choice, select "TCP/IP", and for the "Server Address" field, enter the IP address of the server (for imabox enter "9.27.68.19"), then click "Next".

6) In the "Notes ID File" panel, for the "File name" field click "Browse" and select the appropriate ID file (i.e. "C:\Program Files\Lotus\Notes\data\admin.id"), then click "Next". You will be queried for the password, enter the appropriate value ("adminwea") then click "Next".

7) For the "Instant Messaging" setup panel, unselect "Setup Instant Messaging" and click "Next".

8) In the "Additional Services" panel accept the defaults and click "Next".

9) In the "Notes Setup is Complete" popup click "OK".

10) For any additional panels, accept the defaults.

11) At this point you can exit Notes.

(From pvcsvr)

2) In the "License Agreement" panel, click "I accept the terms in this license agreeement", then click "Next".

3) In the "Customer Information" panel, for the "User Name" field, enter the appropriate value (i.e. "PVC WEA"), for the "Organization" field enter the appropriate value (i.e. "IBM"), for the "Install this application for:" question, select "Only for Me (Single User Install)", then click "Next".

4) In the "Installation Path Selection" panel, accept the defaults and click "Next".

5) In the "Custom Setup" panel, accept the defaults and click "Next".

6) In the "Ready to Install the Program" panel, click "Install". (wait a minth).

7) In the "Install Wizard Completed" panel, click "Finish".

Configure the Lotus Notes Client

(This section needs verification Steve)

For this section you must obtain the Administrator ID file from the associated Domino Server (i.e. "imabox" "admin.id" file is in c:\Domino 6.5.1 Stuff"), and place it on the machine you are installing WEA on (for later configuration steps). Place the file"admin.id" file in your local machine's "C:\Program Files\Lotus\Notes\data" folder.

1). From the Windows menu bar click on "Start", "Programs", "Lotus Applications", and click on "Notes".

2) In the "Lotus Notes Client Configuration" "Welcome" panel click "Next".

3) In the "User Information" panel, for the "Your Name" field enter "admin", and for the "Domino server" field enter "imabox", then click "Next". ("I want to connect to a Domino server" was checked).

4) In the "Notes ID File" panel, for the "File name" field click "Browse" and select the appropriate ID file (i.e. "C:\Program Files\Lotus\Notes\data\admin.id"), then click "Next". You will be queried for the password, enter the appropriate value ("adminwea") then click "Next".

5) In the "Additional Services" panel accept the defaults and click "Next".

6) In the "Notes Setup is Complete" popup click "OK".