Steves Know WEA 4.21 Full Install on Win 2k

Installing WebSphere Everyplace Access 4.21 On Windows 2000

Full Install

This method presumes you are connected to a network drive which has a WebSphere Everyplace Access (WEA) build available. This process describes the use of Setup Manager, which installs WEA. It includes the installation of Java, DB2, WebSphere Application Server (WAS), the WAS fixpack 4, the Device Manager Database, the Portal Server, portlets, Everyplace Synchronization Server, and the Intelligent Notification 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.

There are two methods for installing WEA. The first method is to install using physical CDs, and the second method presumes you are connected to a network drive which has a WebSphere Everyplace Access (WEA) build available.

This process installs WEA, which includes the installation of Java, DB2, WebSphere Application Server (WAS), the WAS fixpack 4, the Device Manager Database, the Portal Server, portlets, Everyplace Synchronization Server, and the Intelligent Notification Services, etc.

When installing, logs are created in the folder "C:/Program Files/IBMWEA". This includes 2 files "setup<randomstringofnumbers>", where "randomstringofnumbers" is a string of digits (i.e. "setup0193479641986941"). 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 the "setup<randomstringofnumbers>" file, there will be references to "command" files, which are the result of the execution of Setup Manager operations. 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.

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.

If installing from the network, perform the following 2 steps:

1) First map a network drive to your machine (network drive = "\\cinta03\42newbuild)
(i.e.. from DOS, type "net use j: \\cinta03.raleigh.ibm.com\42newbuild").

2) Change directories to the newly networked drive (i.e. "cd /D J:"), change to the "cd1" directory, and type "install".

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

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

WebSphere EveryPlace Access Version 4.2 Setup Manager

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.

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

9) In the "Question" popup regarding installing the JRE as the System JVM, click "Yes".

(you might not see the following 2 steps)

10) In the "Start Copying Files" dialog box, accept the defaults and click "Next". Wait a few minutes.

11) In the "Setup Complete" dialog box, click "Finish".

WebSphere EveryPlace Access

1) In the "View Information" "View Prerequisites" panelfor 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 components and 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 "wpsadmin" for the username, password, and confirm password fields, then click "Next".

DB2 Universal Database Server

1) In the "Selecting Install Location" panel, click "Next" to accept the defaults (default is "C:\Program Files\SQLLIB").

2) In the "Collecting Admin Username for Control Center" panel, enter "db2admin" for he username, password, and confirm password fields, then click "Next".

SecureWay Directory Server

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

2) In the "Collecting LDAP Suffix Information" panel, in the "Suffix" field, enter "dc=raleigh,dc=ibm,dc=com" (DO NOT INCLUDE ANY SPACES IN THE SUFFIX!). In the "Adminstrative User" field enter "cn=wpsadmin", and for the "Password" and "Confirm password" fields, enter "wpsadmin", 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 "Collect Username" panel, enter "wpsadmin" for the User Name, Password, and Confirm password (Username was "wasadmin").

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

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

5) In the "Collect Database Settings" panel, click "Next" to accept the defaults (Local Database Name = "wasdbl", Local Database Alias Name = "wasdb", Node Name = "LOOPBACK", and Database Server Port = "55555").

Portal Server

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

2) In the "Server Configuration" panel, click "Next" to accept the defaults. (the Install Directory is "C:\WebSphere\PortalServer", the
Hostname is "(yourmachinename).raleigh.ibm.com", the Base URI i.e. "/wps", and the Home page is. "/portal", and the Customized page is
"/myportal". Proxy Host and Proxy port were blank. FYI, 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 "Selection of LDAP Server Type" panel, in the "User Password" and "Confirm Password" fields enter "wpsadmin", then click "Next" to accept the defaults ("SecureWay Directory" was selected, LDAP Server was "(yourmachinename).raleigh.ibm.com", User DN was "cn=wpsadmin", Suffix was "dc=raleigh,dc=ibm,dc=com", and LDAP Port Number was "389").

4) In the "LDAP Configuration" "Distinguished Name" panel, accept the defaults and click "Next" (User Object Class was "inetOrgPerson", User DN Prefix was "uid", User DN Suffix was "cn=users,dc=raleigh,dc=ibm,dc=com", Group Object Class was "groupOfUniqueNames", Group Member was "uniqueMember", Group DN Prefix was "cn", Group DN Suffix was ""cn=groups,dc=raleigh,dc=ibm,dc=com", Administrator DN was "uid=wpsadmin,cn=users,dc=rushmore", and Administrative group DN was "cn=wpsadmins,cn=groups,dc=raleigh,dc=ibm,dc=com").

5) In the "Portal Server Database Selection" panel, select "Create and initialize a new database (DB2 Only)", and click "Next".

6) In the "Additional DB Configuration" panel, enter "db2admin", and for the Database User, User Password, and Confirm password fields,and click "Next". (Database Name was "wpsdb", JDBC Database Driver was "COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource", JDBC URL Prefix was "jdbc:db2", and JDBC Driver Library was "/home/db2inst1/sqllib/java12/db2java.zip").

7) In the "Database option for Member Services" "Database option for Member Services" panel, select "Create and initialize a new database (DB2 Only)", and click "Next".

8) In the "Database Configuration for Members" "Database option for Member Services" panel, already filled in is the "Database Name" "wmsdb", and for the "Database User", "User Password" and "Confirm password" fields enter "db2admin", then click "Next". (JDBC Database Driver was "COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource", JDBC URL Prefix was "jdbc:db2", and JDBC Driver Library was "/home/db2inst1/sqllib/java12/db2java.zip").

Portlets

1) In the "WebSphere EveryPlace Access Portlets" to be installed panel, for the "Portal Administrator Password" enter "wpsadmin", and for the "Database Administrator Password" enter "db2admin", then click "Next" to accept the defaults (all portlets selected) (Already filled in were Portal Administrator Username "wpsadmin", Group was "wpsadmins", Portal Server Hostname was "(yourhostname).raleigh.ibm.com". In the "Offline Browsing Database Configuration" section, "Create and initialize a new database (DB2 Only)" was selected, and Database Administrator Username was "db2admin" and Database Administrator Password was 8 "*"s ("db2admin".) .

Everyplace Synchronization Server

1) In the "Choose Everyplace Synchronization Adapters" panel, select "Adapter for Microsoft Exchange", and "Adapter for relational databases using DB2 Everyplace (JDBC compliant)", and click "Next".

2) In the "Configure Adapter for Lotus Domino" panel, for the "Hostname" field enter "rushtest02.raleigh.ibm.com", and the "Username" and "Notes Password", enter your id/password (i.e. "shayden") and click "Next".

3) In the "Configure Adapter for Microsoft Exchange" panel, for the Hostname field enter "abe.raleigh.ibm.com", and the Username and Password, enter your id/password (i.e. "shayden") and click "Next".

4) In the "DB2 Everyplace" "DB2 Everyplace server access information" panel, in the Username, Password, and Password Confirm fields, enter "db2admin", and click "Next".( WebSphere Application Path was "c:\WebSphere\AppServer", DB2 Everyplace Path was "c:\WebSpehere\IBMSyncServer\de2e")

5) In the "Configure Database Server" "Enter the install directory for Everyplace Synchronization Server.." panel, for the "Database Username", "Database Password", and "Password Confirm", enter "wpsadmin", and click "Next". (Node Name was "LOOPESS", Port was "55555", Install Directory was "c:\WebSphere\IBMSyncServer", JDBC Driver was "COM.ibm.db2.jdbc.app.DB2Driver", JDBC Library was c:\Program Files\SQLLIB\java\db2java.zip", and Server Administrator was "essadmin").

6) In the "Configure Portal Server" "Enter WebSphere App Server and WebSphere Portal Server info" panel, accept the defaults and click "Next". (Portal Base URI was "/wps", and Portal Server Hostname was "(yourservername).raleigh.ibm.com").

Intelligent Notification Services

1) In the "General Install Information" panel, click "Next" to accept the defaults. (Install Path was "c:\WebSphere\INS", and Hostname was "(yourmachinename".raleigh.ibm.com")

2) In the "Selected SubComponents configuration" panel, select "Messaging Services" and "Subscription Services", and click "Next".

3) In the "Subcomponent Configuration" panel, click "Next" to accept the default path (i.e. "c:\temp\undDelayQueue").

4) In the "Select Portal LDAP Type" panel, select "SecureWay Directory", and click "Next".

5) In the "Configure LDAP Server" panel, click "Next" to accept the defaults (LDAP Install Directory was "C:\Program Files\IBM\LDAP", LDAP server hostname was "(yourmachinename).raleigh.ibm.com", LDAP Server Port was "389", Root Username was "cn=wpsadmin", Root Password was 8 "*"s ("wpsadmin"), and LDAP Suffix was "dc=raleigh,dc=ibm,dc=com").

6) In the "Configure Database" panel, use the default database name ("insdb), and enter "db2admin" for the Database User, Database Password, and Confirm Password fields, and click "Next".

7) In the "Administration portlets install" panel , click "Next" to accept the defaults. (WebSphere Portal Hostname was "(yourmachinename).raleigh.ibm.com" and Portal Base URI was "/wps".)

Device Manager Database

1) In the "Choose or use an existing databaser" panel, click "Next" to accept the defaults ("Create and initialize a local database (recommended)" was selected).

2) In the "Database creation mode" panel, enter "db2admin" for the Database Username, Database Password, and Confirm fields, then click "Next"..

Device Manager

1) In the "Configure Device Manager" panel, click "Next" to accept the defaults (Device Manager Directory was "C:\WebSphere\DMS", Web Service Directory was "c:\Program Files\IBM HTTP Server", JDBC Driver was "C:\Program Files\SQLLIB\java\db2java.zip", Database Username was "db2admin", and Database Password and Confirm Password were 8 "*"s ("db2admin").

Summary

1) In the "Display Summary" panel, click "Next" to accept the defaults. (note that Steve renamed the script file "C:\Steve1015021035WEA_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. 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 you should restart your machine, click "OK". In the Display Summary window, click "Finish", and then restart your machine.

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, and when queried for authentication, use the value "wpsadmin" for the ID and password. (Note: if you had left the Admin Console running after performing the steps in "Configuring for Admin Role", you still have a snapshot of the configuration of WES/WAS at that point. Refreshing the Admin Console will not show you the remaining applications that were installed after the configuration was performed. To see these applications you must exit the Admin Console and restart it. Logon using ID/Password of "wpsadmin").

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

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

5) 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 "World Clock" portlet. If you are queried for an ID/Password, use "wpsadmin" for both.

6) 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.

Restarting WebSphere Everyplace Access

1) From the Windows "Services" utility, if necessary, stop the "IBM SecureWay Directory V3.2.2" and the "IBM WS Admin Server".

2) First start the SecureWay Directory server and then IBM WS Admin Server.