WebSphere Everyplace Access Testing

Creating Test Scenarios

Verifying Successful Installation of WEA
Logging For WEA Components
Modifying Execution Records
Configuring WEA Notes Connection
Configuring WEA Microsoft Exchange 2000 Connection
Configuring and Starting Sametime
Miscellaneous Commands
 
 

Creating Test Scenarios

1)  In Lotus, connect to database "WEA R2.x Scenario/ER" on server "ATE04DB/D/ATE" filename is "e-dir/WEA_R2scenarios.nsf".
 
 
 
 

Verifying Successful Installation of WEA

This section assumes you have successfully installed and started WebSphere Application Server, and the WebSphere Everyplace Access applications is installed on your machine also, and have also started all of the appropriate applications.

1)  Using the browser of your choice, connect to the URL "http://localhost/wps/portal".

2)  Click on the key in the upper right corner of the web page. For the User ID and Password, enter the value "wpsadmin", and click the "Log In".

3)  In the upper left corner of the IBM WebSphere Everyplace Access web page, select "WEA Home" from the pulldown.

4)  In the navigation tab, click on "Offline" (frankly, there aint much there, only an "Image Viewer").

5)  In the navigation tab, click on "Configure" (frankly, there aint much there, only a "Offline Browsing Configuration").

5)  In the navigation tab, click on "Administration" (frankly, there aint much there, only a "Offline Browsing Administration").
 
 

Logging For WEA Components

ESS Logging
 

ESS Logging

1)  Shutdown Websphere Application server.

2)  Shutdown Everyplace Synchronization server ("esscmd init")

3)  rename c:\websphere\ibmsyncserver\app\ess.ear\ESSBase.war\WEB-INF\lib\tss-server.jar to tss-server.jar.original

4)  copy c:\websphere\ibmsyncserver\app\ess.ear\ESSBase.war\WEB-INF\lib\tss-server_debug.jar to tss-server.jar

5)  Edit the file c:\websphere\ibmsyncserver\app\ess.ear\ESSBase.war\WEB-INF\classes\resource\config\config_tss.txt.  Add the following line to this file:
 INTERNAL_DEBUG_LEVEL=4

6)  Uncomment  the following lines from the config_tss.txt file to capture xml files for each request/response.

 SYNCML_REQUEST_LOG_COUNT=100
 SYNCML_REQUEST_LOG_FILENAME_BASE=/usr/WebSphere/IBMSyncServer/logs/sml

7)  Erase the log files c:\websphere\ibmsyncserver\logs\appserver*

8) restart Websphere Application server

9)  restart ESS

Now you will get debug logging data in the files appserver-stderr.log and appserver-stdout.log which are located in c:\websphere\ibmsyncserver\logs.
You also get files like sml1in.xml and sml1out.xml, sml2in.xml, etc.  These files show the SyncML flows for each individual message in a format that can be loaded with an xml browser (Internet explorer works fine) and is nicely formatted.

Remember to undo these changes when you want to go back to non-debug versions.
 
 
 
 
 
 

Modifying Execution Records
 

Passed Tests

1)   From your Lotus Notes desktop, doubleclick the "WEA R2.x Scenerio/ER on ATE04DB" database.

2)   Scope down into the "f.Execution" item in the left panel.

3)   Choose your view (i.e. "by Tester, Phase").

4)   Choose your Execution Record from the right panel.

5)   Select the execution record(s) you which to modify.

6)   In the menu bar select "Actions", "Execution Records" and "Change Status".

7)   In the "Change Status of Execution Record" window, for the "Change Status to" field, enter the value or use the pulldown to select your choice (i.e. "COMPLETE").

8)   In the "Last Build Executed" field, enter the build number (i.e. "20021003").
 

(OR, if you have several you wish to modify, perform steps 1-3 above, then)

1)  Select all records you wish to modify.

2)  Perform steps 6-8 above
 

Failed Tests

(Assumes you claim all points for a failed test!)

1)  Select all records you wish to modify.

2)  In the Lotus Notes  menu bar select "Actions", "Execution Records" and "Change Status".

3)  In the "Change Status of Execution Record" window, for the "Change Status to" field, enter the value or use the pulldown to select your choice (i.e. "FAILED").

4)   In the "Last Build Executed" field, enter the build number (i.e. "20021003").7), and click "OK".

5)  In the "Claimed ATTEMPT Points" pop-up, enter the Total Points assigned, and click OK.

6)  In the "Claimed SUCCESS Points" pop-up, enter "0", and click OK.

7)  In the "Claimed FAILED Points" pop-up, enter the number of points you wish to claim, and click OK.

(i.e.10 attempted 0 complete 10 failed)
 
 
 
 

Configuring WEA Notes Connection

To perform this configuration, you must first create a user in WEA using the "wpsadmin" account.

The following steps must be performed in the "WEA Home" page group, by clicking on the "Notes" link. To configure your Lotus Notes connectivity, you will need to perform the following steps on your Lotus Notes Mail, Lotus Notes Contacts, Lotus Notes Notebook, Lotus Notes Notebook, Lotus Notes Calendar, and Lotus Notes To Do List by clicking on the edit button (little pencil icon to the right of each function) and adding your Server Name, ID and Password in the resulting portlet.

1)  In the Lotus Notes "Server Name" field enter the value "rushtest02.raleigh.ibm.com".

2)  In the "User Name" and "Password" fields, enter your id/pw ("shayden"/"shayden"),  then click "Save"
 
 
 

Configuring WEA Microsoft Exchange 2000 Connection

The following steps must be performed in the "WEA Home" page group, by clicking on the "Exchange" link.  To configure your Microsoft Exchange 2000 connectivity, you will need to perform the following steps on your Microsoft Exchange 2000 Mail, Microsoft Exchange 2000 Contacts, Microsoft Exchange 2000 Notes, Microsoft Exchange 2000 Calendar, and Microsoft Exchange 2000 Tasks. This is done by clicking on the edit button (little pencil icon to the right of each function) and performing the following steps in the resulting portlets.

Note there are other values you might wish to customize, this procedure only includes the minimum required.

1)  In the Microsoft Exchange 2000 "Server Name" field enter the value "abe.raleigh.ibm.com".

2)  In the "User Name" and "Password" fields, enter your id/pw ("shayden"/"shayden").

3)  In the "Exchange Email address" field enter your email address (i.e. "shayden@abe.raleigh.ibm.com"), then click "OK"
 
 
 

Configuring and Starting Sametime
 

You must first create a Sametime user to be used by the Sametime "Feeder Server". Logon to Sametime server and add a user "samfeeder".

1) From the supported browser of your choice, logon as "wpsadmin"

2) From the Portal portlet group choice, select the "Portal Administration" group.

3) For the "User ID", "Password", "Confirm Password" fields enter "samfeeder". For the "First Name" field enter "Sam", for the "Last Name" field enter "Feeder", and for the "Email" field enter "samfeeder@us.ibm.com", then click "OK".
 
 

Configuring LDAP for INS

1)  Start the Directory Management Tool (DMT) from the "/usr/ldap/bin" directory by typing "dmt&".

2)  In the "Server" in DMT, click "Rebind".

3)  In the Rebind panel, select "Authenticated", and enter your id/pw  (i.e. "cn=wpsadmin", and "wpsadmin), then click "OK".

4)  Scope down to "dc-ins,dc-ibm,dc=com", "sys=SDP", "sys=sam1_wea2aix5" (where "wea2aix5" should be the host name of your INS server machine"), "cid=common", and select "settingID=ibm-sametimeSametimeServer" and click "Edit" button.

5)  In the Edit an LDAP Entry dialog box, in the "cisProperty" field, enter "disorder.raleigh.ibm.com", then click "OK".

6)  Select the "settingID=ibm-sametimeSametimeUser", and click the "Edit" button.

7)  In the "cisproperty" field enter the value "samfeeder", then click "OK".

8)  Select the "settingID=ibm-sametimeSametimePassword", and click the "Edit" button.

9)  In the "cesProperty" field, enter "samfeeder", then click "OK".

1)  Select "settingID=ibm-sametimeRealm", and click "Edit".

11) Verify the "cesProperty" value is "ins.realm", then click "OK". (you can now close "Exit" the DMT GUI).

12) On the machine you have installed INS on, from the "/usr/WebSphere/INS/bin" directory, execute the SAM script file by typing "./startSAM" with your machine name as the only parameter (i.e ./startSAM wea2aix5").

13) In the WEA portlets, in the "Portal Administration" page group, under the "Users and Groups" tab, you need to create a user "insuser2", and add the "insuser2" to the "INSUsersGroup" group (dont forget to click "OK"!).
 
 
 
 

Configuring INS (with Darren )

1) Logon to the wps/portal as "wpsadmin" with password "wpsadmin".

2) Select the "Portal Administration" portlet group.

3) Select the "Security" tab.

4) To the right of the "Selected users and groups" option, click on "Get groups and users".

5) Select the "Search for users" radio button, type a "*" in the "Name is" field and click "Go".

6) In the "Search results" section, select "wps admin (wpsadmin) -- user" and click "Add to list", then click "OK".

7) In the "Select the object for their permissions" field, select "user groups", then click "Go".

8) In the right portion of the panel, for "InsUsersGroup", select "Manage" and "Delegate" permissions then click "Save".

9) Select the "Intelligent Notification" portlet group.

10) Select "Administration" tab, and select "Configure Gateways".

11) In "Configure Gateway" panel, select "Sametime" and click "Edit".

12) In the "Hostname" field, enter "disorder.raleigh.ibm.com".

13) For the "User ID" and "Password" field, enter "samfeeder", and click "OK". (Max retries = 1 and Retry interval = 60 seconds)
 
 
 
 
 

with sunil

14) Logon to the wps/portal as "insuser2" with password "insuser2".

15 Go to the "Intelligent Notification" page group.

16) In the "Sametime Deliver channels" section select "Add Delivery Channel".

16)  In the "Delivery Channel Name", enter a value (i.e. "SHDCName"), and the Sametime ID enter "insuser2", then click "OK".

14) Select the "My Delivery Channel" tab.

15) Click on "Add Delivery Channel".

9) In the "Delivery Channel Name" field enter "StevieChannel", and in the "Sametime ID" field enter "instest1", then click "OK".

10) Select the "My Subscription" tab, and in the "My Stock Subscriptions" field click "Add subscription".

11)  In the My Stock Subscriptions" "Stock Symbol" field enter "IBM", in the "Condition" select "Less than", and in the "Stock price" enter "150", and in the "Notification", select "Always", in the "Send to these delivery channels", select "SHDCName" then click "OK".

12) From your personal PC machine, execute the Sametime Client.

13) In the Sametime Connect window, select "Options", and click on "Preferences".

14) In the Preferences dialog box, select the "Sametime Connectivity" tab.

15) In the Sametime Connectivity panel, for the "Host" field, enter "disorder" and click "OK" (Port = 1533 and Proxy Type = "No proxy").

16) In the Sametime Connect window, select "People", and click on "Log of of Sametime".

17) In the Sametime Connect window, select "People", and click on "Log on to Sametime".

18) In the Log on to Sametime dialog box, enter your username/password (i.e. "instest1" and "instest1"), then click "Log On".

19) From the machine you have installed INS on, go to the directory "/usr/WebSphere/INS/samples", and execute the command "contentfeed.sh stocks stock", within a few seconds a new Sametime window should appear reflecting IBM's stock price.
 
 
 
 

To Test Sametime Server

Instant Messaging

1) From a Sametime client, make sure you are logged off any sessions, then from the "Sametime Connect" window menu bar select "Options" and click on "Preferences".

2) In the "Preferences" dialog box, select the "Sametime Connectivity" tab.

3) In the "Sametime community server" field, enter the value "disorder.raleigh.ibm.com', then click "OK" (original value was "messaging.ibm.com")

4) From the "Sametime Connect" window menu bar click on "People", and select "Log on to Sametime" (you might need to Log Off first!), and enter the User Name "insuser2" with the same value for Password, and click "Log On".

5) Invoke Sametime again, and log on as another user (i.e. "insuser1").

6) From this second Sametime window, add the user "insuser2" by selecting the "Work" field, right mouse click and select "Add".

7) In the "Add Person or Group" dialog box, enter "insuser2" for the User name and Nickname, then click "Add", then "Close".

8) From the Sametime insuser2 window, click "insuser1", right mouse click and select "Message".

9) Enter a message, click "Send", and the message should appear on the "insuser1" dialog box.

10) If you can talk back and forth between these two Sametime users, the installation/configuration might be healthy
 
 
 
 
 
 
 

Miscellaneous Commands

Command used in DMS install to tickle WAS =   "./XMLConfig.sh -import trash.xml -adminNodeName wea2aix2" (of course change the machine name).