Steves WEA Basic Verication Test (BVT) (Unix Systems)

This procedure is what Steve uses for BVT of WEA, but, only does a minimal sanity check, and should not be considered exhaustive. Although it is written from the Unix (AIX/Solaris) perspective, similar or exact operations can be performed on Windows.

The procedure assumes a Full WEA installation has been performed, and everything is (semi)operational. It begins by adding groups/users required, then using  DMS portlets to download all client applications to a Pocket PC (PPC), configuring DB2e for enrolling the device, synchronizing the device (ESS and DB2e), verifying LAS by viewing a map, and verifying INS by using the Message Center to send a note.

After installation of WEA and all components, log off your session and then log back on as root to set appropriate environment variables. First start the WAS Admin Console and assure all application servers are running and healthy. If your system has been rebooted, see WEA Starting and Stopping  for instructions on assuring/performing startup of all component functionality.

Commands below are written from the AIX perspective, and default locations for WEA and all components are "/usr/WebSphere". For Solaris, this will be "/opt/WebSphere", so modify your input accordingly.

To provide (hopefully) the most expeditious BVT, a minimal amount of users (3) and groups (1) will be added to perform testing of all components.
 
 

Create DB2e User Group DB2eTesting

For the DB2e, any DB2e users must be members of a group who's name begins with "DB2e" in order to sychnonize their associated database. Create the group, "DB2eTesting" with the following steps.

1) Log on to WebSphere Portal as an administrative user (i.e "wpsadmin").

2) Select "Portal Administration" tab.

3) In the left frame, under "Users and Groups", click "Manage Groups" .

4) In the "Manage User Groups" portlet, type "DB2eTesting" into the "Group Name" field, then click "Create group".
 
5) Perform the previous step to add "SyncGroup".

Create Users For Testing All Components

Create and add users to DB2eTesting, SyncGroup, INSUserGroup, dmadmins, etc., using the following steps.

1) You should be logged on to WebSphere Portal as an administrative user (i.e "wpsadmin").

2) Select "Portal Administration" tab.

3) In the left frame, under "Users and Groups", click on "Manage Users".

4) In the "Manage Users" portlet, on the right side, click "Create new user".

5) In the following fields, enter the following values, then click "OK":

  Field                         Value

User ID:                    weaabuser
Password:                 weaabuser
Confirm Password:    weaabuser
First Name:               Wea
Last Name:               Abuser
Email:                        weaabuser@us.ibm.com

6) Perform steps 4-5 to create users "insabuser", and "essadmin", substituting the appropriate values in step 5.

7) In the left side of the portlet, click "Manage Groups".

8) Type an asterisk in the "Search for groups" field, then click "Get groups".

9) In the list of User Groups displayed, select "DB2eTesting" from the list and click "Membership".

10) On the "Manage User Groups" portlet, in the "Add users to group:" field, enter an "*", then click "Go".

11) In the "Search Results" list, select the "weaabuser" and click "Add to group" then click "OK"

Note: Once a user is a member of dmadmins, they can also utilize the Device Manager Console.

12) Perform above steps 9-11 to add user "weaabuser" to groups "INSUserGroup", "SyncGroup", "dmadmins", and "essusers".

13) Perform above steps 9-11 to add user "essadmin" to group "essadmins".

14) Perform above steps 9-11 to add user "insabuser" to group "INSUserGroup."

15) At this point you should be able to confirm that DB2e is installed by accessing the URL "http://yourbox.raleigh.ibm.com/db2e/db2erdb", where
"yourbox" should be replaced by your WAS/WEA machine name. Logon using the userid you just created ("weaabuser") (or "wpsadmin").
Information similar to the following should be displayed:

MDSSServlet Information

 MDSSServlet loaded at 04/01/03 16:30:36:134 EST
 DB2 Everyplace SyncServer 8.1.2 WEA20030326
 The current time is 04/02/03 09:46:20:798 EST  

  

Device Management Services
DB2 Everyplace
Everyplace Synchronization Services
Offline Browsing and Forms
Location Aware Services
Intelligent Notification Services

 
 

Device Management Service

Jobs are submitted to DMS and the associated information is stored in the DMS database. Active jobs show up in "DMS" database in the "ACTIVE_JOB" table. After an install there should be 3 records in this table. One for Inventory for "WinCE", "Palm", and "SYNCML". As more jobs are submitted, this will of course change.
 
 

Copy CAB Files To WEA Database

(the following instructions are for PPC2002 devices. With WEA FP5 and IF1 you can also load the PPC2003 software)

1) Get the client software from the WEA CD7, which will be in the directory/folder "/client/PPC2002/cabs/en/2577".

2) With the Web browser of your choice, logon as "wpsadmin".

3) Click on the "WEA Home" tab, and then click on the "Administration". First assure DM Jobs portlet is OK ("no text is RED").

4) In the "Device Management -Configure" portlet, in the "New file" field, enter a filename (i.e. "StevieDMS"), then click "New".

5) Again, in the "Device Management -Configure" portlet, to the right of the "Device connection profiles" click the "New" link.

6) Again, in the "Device Management - Configure" portlet, in the section "Create a device connection profile.", for the "Profile name:", enter a value (i.e. "StevesProf"), accept the remaining default values, then click "OK".

7) In the "Device Management - Configure" portlet, accept the defaults ("Default profile" is "SteveProf", "Allow users to modify network profiles" and "Require users to log in" are both checked), again click "OK".

8) In the "Device Management - Jobs" portlet, click the wrench.

9) In the " Enter the host name of your Websphere Everyplace Access application server." field, assure your machine name you will be downloading from is filled in (i.e. "yourbox.raleigh.ibm.com"), and click the "Upload Pocket PC 2002 client installation files" link (or alternatively "Upload Pocket PC 2003..").

10) In the "Upload files for" choice, select the language you wish to use (i.e "English"), and under the "IBM Everyplace Client for PPC2002" section, for each of the "CAB" files, browse to the associated file in the directory/folder from step 1 above, then click "Upload" (after several seconds the portlet should reflect "All files have been uploaded"). (you can optionally perform this same operation for the "Sametime Mobile Client for PPC2002" and "DB2 Everyplace Sync Client for PPC2002"). Once they are done, then click on "Done", and when you are back in the "Device Management - Jobs" panel, click "OK".

11) Back in the "Device Management - Jobs" portlet, under the "Jobs" listed, click "Create Job".

12) In the "Create a Job" section, under the "Job Name:" field, select "WEA Client install - PPC2002" from the choices (or "WEA Client install - PPC2003").

13) In the "Create a Job" section of the portlet, the "Job Name:" field should already reflect the appropriate name (i.e. WEA Client install - PPC2002"), and the "Create job for:" field should be "English". Select all components you desire and have previously prepared (i.e. "IBM Everyplace Client for PPC2002" should already be selected/grayed), "Sametime Mobile Client for PPC2002", and/or "DB2 Everyplace Sync Client for PPC2002". For the "Group:", accept the default "All",  then click "OK". (after several minths, two new jobs should be displayed in the "Jobs" list.)

14) Back in the "Device Management - Jobs" portlet, under the "Jobs" listed, click "Create Job" (things to get sent to device).

15) In the "Create a Job" section, under the "Job Name:" field, select "WEA Client Configure" from the choices.

16) Accept the defaults, and click "OK" ("Job Name" field is "Wea Client Configure", "Configuration File:" is "StevieDMS", and "Group" is "All"). Wait a few minths and there now should be 4 jobs listed.

17) In the "WEA Home" page group, click the "Configure" tab.

18) In the "Everyplace client installer" portlet, click the wrench icon.

19) In the "Everyplace Client Installer" portlet, "Device Manager server hostname", assure your fully qualified server hostname is in this field (i.e "yourbox.raleigh.ibm.com"), and click "OK"
 
 
 

Download The Client To The Device (PPC)

(Do a "hard reset" on the PPC, go through the normal startup and bluetooth/network, see Pocket PC Operation)

1) From the PPC, tap the "Start", and in the selection, tap "Internet Explorer".

2) In the Internet Explorer GUI, in the lower left, tap "View", and select "Address Bar", then connect to your portal (i.e. "yourbox.raleigh.ibm.com/wps/portal").

3) Logon to the WEA Home page by tapping the key icon in the upper right corner of the portal page, and when prompted enter your ID and password (i.e. "weaabuser" and "weaabuser").

4) Under the portlet group selection "WEA Home" in the "Welcome" pull down selection, select "Configure"

5) In the "Configure" portlet, tap the "Everyplace Client Installer" icon.

6) In the "Everyplace Client Installer" portlet, tap "Download Installer".

7) In the "Download" popup requesting "Download the 3(**) KB file 'ceagent.arm.cab' to the "My Documents' folder in Main Memory?" tap "Yes".

At this point the download to the PPC occurs. It installs, connects to server, and all the cab files will be downloaded. Once they are there, the panel clears and are presented with Everyplace Client Installer which initializes. Dependant upon how many CAB files you selected, the download operation may take several minutes. When it is done, you will be presented with a Welcome page.

8) In the "Welcome" page, tap the keyboard icon in the lower right corner, and for the "User name" and "Password" fields, enter your id/pw (i.e.
"weaabuser"), and tap the "Log in" button. Your WOX (WEA Access Client) has been installed, and the "My Settings", "Network profiles" portlet on the client should already be configured with your Portal server URL for all servers.
 
 
 
 

DB2 Everyplace

Mobile Devices Administration Center Operations

DB2 Subscription and Subscription Set Configuration

On Windows

From the MS "Start", "Programs", "IBM Everyplace Synchronization Server", click on "Launch MDAC". The MDAC GUI will appear. Go to step 4 below.
 

On AIX

1) From the machine you have installed DB2e on (i.e. "yourbox"), from the command line execute the command "xhost  +".

2) Switch users to you DB2 instance administrator user (i.e. if your instance administratore is "wasinst", "su - wasinst" password = "wasinst", OR, "su - db2inst1", password = "ibmdb2" if appropriate),  and execute the command "unset JAVA_HOME" (might not have to do this on Sun). You must then export your display to the machine you wish to display the Mobile Device Administration Console (MDAC) GUI on. To export your display to allow the (MDAC) to run on this machine type the command "export  DISPLAY=yourbox.raleigh.ibm.com:0.0" (where your display machine is "yourbox").

3) Change directories to "/home/wasinst/db2everyplace81/Server/bin" (or "/home/db2inst1" if appropriate), and execute the command "./dsyadmin.sh".

For Both Platforms


Note in the following step, occasionally there is a problem with the Java/GUI, exhibited by missing dialog box content in MDAC. This can be cured by "maximizing" the GUI once, then the problem goes away and GUI will operate normally for max/minimize.

4) The DB2 GUI will appear as well as the DB2e MDAC GUI. A pop-up for the DB2 GUI ("Attach - LOOPBACK") might appear, if so logon using the ID/Password "wasinst" (or "db2inst1"/"ibmdb2"  if appropriate) and press "OK". Afterwards, a "WPS LDAP Logon" dialog box will appear, and in the "User ID" and "Password" fields enter "wpsadmin" (might already be filled in), and in the "Sync group" field enter "SyncGroup" (might already be filled in), then press "OK" (at this point you should be able to click on "Groups" and "Users", and see the group and user you added to the Portal server in the Create DB2e Group and Users section above.)

5) In the MDAC, select "Subscriptions", right mouse click and select "Create", "Table subscription", and select "JDBC subscription". A "Create JDBC Subscription" dialog box will appear.

6) In the "Identification" tab, in the "Name" field, enter "Nursing", in the "Description" field enter "Nursing the VNURSE DB", and in the "Adapter" field, accept the default "DSYJDBC - Default DB2 Everyplace JDBC adapter".

7) In the "Source" tab, for the "Database URL", click on the "..." icon.

8) In the "Select Local DB2 Source Database", select "VNURSE", then click "OK".

9) In the Source "User ID" field, enter your DB2 instance id/PW (i. e. "wasinst" or "db2admin" as appropriate. In the "Password" and "Verify password" fields enter "was1nst" or "ibmdb2"  as appropriate),  (the "Driver" should be "IBM DB2 UDB local").

10) Click the "Test connection" button to confirm connectivity to the database, and click "Close" in the resulting pop-up stating your connection was successful (assuming it was!).

11) In the "Mirror" tab, for the "Database URL", click on the "..." icon.

12) In the "Select Local DB2 Mirror Database", select "M_VNURSE", then click "OK".

13) In the Mirror "User ID" field, enter your DB2 instance id/PW (i. e. "wasinst" or "db2admin" as appropriate. In the "Password" and "Verify password" fields enter "was1nst" or "ibmdb2"  as appropriate),  (the "Driver" should be "IBM DB2 UDB local").

14) Click the "Test connection" button to confirm connectivity to the database, and click "Close" in the resulting pop-up stating your connection was successful (assuming it was!).

15) Select the "Identification" tab, and then select the "Define subscription" button on that panel.

16) In the "Define Replication Subscription" dialog box, click "Add" (then wait several seconds).

17) In the "Add Table" dialog box, select "DSYSAMPLE.VNCONTACT", and click "Add".

18) Perform the above step for the "DSYSAMPLE.VNMEDICALRECORD", the "DSYSAMPLE.VNPERSON", "DSYSAMPLE.VNSCHEDULE", and "DSYSAMPLE.VNSIGNATURE" tables, then click "Close".

19) Back in the "Define Replication Subscription", click the "Timing" button.

20) In the "Subscription Timing" dialog box, in the "Batch window" field, enter "60" seconds, then click "OK".

21) Click "OK" to close the "Define Replication Subscription" dialog box.

22) Click "OK" in the "Create JDBC Subscription" dialog box (then wait several seconds).

23) Back in the MDAC console, select "Subscription sets", right click and select "Create".

24) In the "Create Subscription Set" dialog box, select the "Identification" tab.

25) In the "Name" field enter "NurseSet", and in the "Description" field, enter "The Nurses Subscription Set".

26) Select the "Subscriptions" tab, and in the "Available subscriptions" area, select "Nursing" and click the ">" button to add it to the "Selected Subscriptions" area, then click "OK".

27) In the MDAC, select "Groups", and in the right panel, select the DB2e group you had previously created in the Portal server ("DB2eTesting"), right click and select "Edit".

28) In the "Change Group - DB2eTesting" dialog box, select the "Subscription sets" tab, and in the "Available subscription sets" section, select "NurseSet" and click the ">" button to move to the "Selected subscription sets" section, then click "OK" in the "Change Group - DB2eTesting" dialog box.
 
 
 
 

Everyplace Synchronization Service

1) Start the ESS Service:

On Windows, "Start", "Programs", "IBM Everyplace Synchronization Server", and click on "Start Local Server". (or do similar command as below in a DOS window, OR from the "Services" panel, start it there).

On AIX, from the Unix command prompt, go to the "/usr/WebSphere/IBMSyncServer/caf/bin" directory and run the command "./esscmd init".

2)  Log on to WEA Portal Sever using "wpsadmin" and click the "Everyplace Synchronization" place tab.

3)  Select the "Everyplace Synchronization Servers" tab, "Manage Servers" tab, and the "Status" of the backend server should be "Running". 

4)  Log off as "wpsadmin", and then login as "essadmin", and you should have "Everyplace Synchronization" place tab and all "Synchronization" portlets

5)  Log off as "essadmin", and log into the Portal Server as "weaabuser". Go to the WEA Home "Configure" page and the "Synchronization settings" portlet should appear

6) From the "Synchronization setting" portlet, click "Create a new device profile".

7)  Again, in the "Synchronization settings" portlet, in the "Provide a name for your new profile" field, type "weaabprof", then click "Next".

8) Again, in the "Synchronization settings" portlet, for the sync user, select the mail backend server to sync from (i.e."pvcexchg.rtp.raleigh.ibm.com"), enter the appropriate "User name", "Password", (i.e. "steve").  For the remaining values, "Exchange 2000", and "Mailbox name" you should obtain/assure the correct values from your Exchange administrator. If your backend is "Exchange 2000", your "Mailbox name", "Domain" fields can (probably) be left blank. If your backend is "Exchange 5.5", the "Mailbox name" will probably be your username (i.e. "shayden"), and your "Domain" should be the appropriate value (i.e. "sync2"). Once you have finished filling in these fields,  click "Next".

9) Again, in the "Synchronization settings" portlet, select "Create custom settings for "weaabprof'", then click "Next".

10) For each of the E-mail, Calendar, Contacts, Tasks, and Notes preferences, assure your "Synchronization" data filter encompasses activity if you have not done any operations lately, then click "Next" (i.e. if you have not received mail lately, click under "E-mail", click "Syncronization data". In the resulting panel select "All available data", or selectively choose with the "Only created within the past..." to enter a narrower selection, click "OK", and back in the "Synchronization settngs" panel click "Next".)

11) Back, in the "Synchronization settings" portlet, in the "When there is a conflict between the data on the server and the data on the device, use the information from the:" field select "Server" or "Device" to determine which has control, then click "Next".

12) Again, in the "Synchronization settings" portlet, in the "Creating profile: weaabprof" fields, select the time zone and locale, then click "Next".

13) Again, in the "Synchronization settings" portlet, verify the "Profile summary", then click "OK".

14) Once device profile is created for user, you are now ready to sync data to/from a Device
 
 
 
 
 

Offline Browsing and Forms

Please note that not all portlets are suitable for Offline browsing/forms, check the WEA InfoCenter for the latest info. At this moment, the following portlets could be used for Offline test:

Bannar Ad
Image Viewer
INS Message Center
LDAP Search
Quicklinks
Reminder
Web Clipping
World Clock

1) Log into WEA/Portal with browser as the administrator (i.e. "wpsadmin"), click on the "WEA Home" tab, then the "Administration" tab, and change the hostname for the "Offline Browsing Administration" portlet to your server (i.e "yourbox.raleigh.ibm.com/wps/myportal"), then click "Save"

2) In Portal server, select tab "Work with Pages", select "Edit Layout", and in the left side of the portlet, scope down to "WEA Home", select a portlet (i.e "Offline", then in the "Page:Offline" click the "+" button above the document/folder icon to add this portlet. Then, in the right panel, select "All available", then click "Go". Select several portlets, then click "OK". Back in the "Page:Offline" porlet, select all of the portlets you selected then click "Activate". (also you can click the "+" button, select "Name contains" option, and enter "LDAP" in the field beside it, then click "Go". The "LDAP Search" portlet will then be a selectable option, so select it, then click "OK". Then click "Activate" to activate these selections.)

At this point the Offline browsing could be tested with the browser running on your desktop, i.e., open the URL
http://<your_WEA_server>/WebCache/WebCache?userid=<your_userid>&password=<your_password>

You will be prompted for your credentials. Close the browser and try this again, this time, the Offline page will be loaded in your browser. So far, you'll know that at least the Offline browsing should work on the server side. You will next sync your device (see next section), and then perform additional actions to confirm Offline Browsing is functional.
 
 
 
 

Synchronize Your PPC (DB2e and ESS)

The following assumes you have either used the DMS to enroll your device and downloaded the WOX client to your device, or have downloaded it using the steps defined in Pocket PC Operation (which includes "Microsoft Activesync Software Installation", "Pocket PC Client Software Installation", and "Connecting To Al Gores Internet"), and started the Everyplace Client (tap "Start", and select "Everyplace Client", logged on with "weaabuser").

1) In the upper left section of the WEA Client page, in the selection box, select "My settings" (on PPC2003, click the wrench to get this panel). (If you have not performed the preceding steps, you must assure you have downloaded the PPC WEA Client (WOX), and have configured the PPC for approrpiate connectivity (i.e. wireless, cradle, Bluetooth, etc.) and successfully connected to the Internet. Then execute and logon to the WEA Client as "weaabuser".)

2) In the resulting page, tap "Organize categories".

3) In the resulting list, select the "Calender", "Contacts', "Database sync", "Inbox", and "Notes" options, then tap the check mark in the upper right corner of your web page.

4) Back in the "My Settings" page, scroll down and tap the "Network profiles" option.

5) For the "Everyplace Synchronization server, "Offline Portal Content server", "DB2 Everyplace server", "Device Manager server", and "Sametime Connect server", assure these fields have the correct machine name for your server (i.e. "yourbox.raleigh.ibm.com") then tap the check mark in the upper right corner of your web page, and again,  tap the check mark in the upper right corner of your web page. ("Community port" should be "1533").

6) In the upper left section of the web page, in the selection box, select "My tools"

7) At this point you can choose to synchronize everything by tapping the large circular arrow yin/yang icon, or tap the individual options you wish to sync, and then view the results of this sychronization. If it seems nothing is happening, you can look at the HTTP Server "access_log" (i.e. "tail -f  /usr/HTTPServer/logs/access_log") to confirm synchronization is continuing to occur.

The following sections ("Inbox", "DB2e", and "Offline Browsing), reflect possible ways to invoke and view the results of your synchoronization
 

Inbox

1) Tap the "Inbox" link.

2) In the upper left corner, the text beside the down arrow reflects what your current view is. Tap the down arrow and scope to "SyncML", and then to "Inbox" . You can now view any mail you had received.
 

DB2e

1) Tap "Database sync", and in the resulting panel tap "Synchronize". (you might need to "Reset" the user in the MDAC). Wait for DB2 sync to happen.

2) When complete, in the "iSync" page, tap "File", and then tap "View Logfile". View this file and assure no errors occurred.

At this point you can use the DB2e client to assure tables were downloaded see Pocket PC Operation) for details of the operation of the DB2e client).
 

Offline Browsing

Under Construction By Steve

3. In the Offline portal page entry, click the green icon (the device must be connected, or in the cradle) to sync
4. after the sync finishes, disconnect, tap the "Offline portal page" entry, browse the content
5. if you have any portlets like LDAP or World clock, you can submit some forms
6. connect the device, tap the green icon next to the "Offline forms" to sync the forms
7. after the sync finishes, disconnect, tap the "Offline forms" entry, and the requests should be in "success" status
8. tap any of the "success" link, the response should be displayed
 
 
 

Location Aware Services

Configure LAS webraska Services

There are 2 alternatives for configuring LAS. One is the manual procedure described next, and the second is an Automated LAS Configuration procedure described later. The Automated LAS Configuration requires the use of database command line options to update the database using SQL scripts.

To manually configure nebraska for North America services, complete the following steps:

1) Logon to Portal as administrator (i.e. "wpsadmin" / "wpsadmin").

2) Select the "Locacation Aware Services", click on "Manage Services", and then click on "webraska-na.DirectoryService".

3) In the "View, add, and modify services." portlet, click on "Modify properties of configuration profiles".

4) In the next "View, add, and modify services." portlet view, select "server - -pvc1.tw.ibm.com" and click "Delete Key-Value pair". Then select and
delete "clientName -- demo", and "clientPassword -- demo" pairs.

5) In the "Properties for service provider configuration profile:", "Key:" field enter "server", and the "Value:" field, enter "na12.webraska.com", then
click "Add Key-Value pair". Additionally perform the Add Key-Value pair operation using "Key" =  "clientName", and the "Value:" = "ibmus4", click
"Add Key-Value pair". Then add "Key" = "clientPassword", and the "Value:" field, = "itb:160", then click "Add Key-Value pair", then click "OK".

6) Now click "OK", and in the "View, add, and modify services."

7) Then perform steps 2-6 for  "webraska-na.GeocodingService", "webraska-na.MappingService", "webraska-na.ReverseGeocodingService",
and "webraska-na.RoutingService".

8) In the LAS Services page, click "Refresh". Within a few seconds it should reflect "Success".

9) Click on the "Locations" tab.

10) Enter a city and state, then click "Get Map". Your map should be displayed.

(as of 07/25/03, webraska North America is busted. You can configure for webraska Europe by performing the above but using the "server" name of "eu12.wbska.com")
 

Automated LAS Configuration

ToSTEVE
 


Intelligent Notification Services

Starting INS Servers on AIX

1) From the Unix command prompt, assure the "db2jd  6789" process is running (i.e. "ps -ef | grep 6789"). If it is not running switch users to the
appropriate database instance (i.e. "su - wasinst")  and execute the DB2 Java start command with the appropriate parameter (i.e. "db2jstrt  6789").

2)  You will need to run some additional servers from a Unix command prompt. In the directory "/usr/WebSphere/INS/bin", run the script "startADM"
including as the only parameter your machine name ("./startADM yourbox", or "./startADM yourbox  2>&1 | tee /Steves.startADM.log" to also log
to a logging file "/Steves.startADM.log"), and in another AIX window, run the script "startHA" or "./startHA 2>&1 | tee /Steves.startHA.log" to also
log to a logging file "/Steves.startHA.log"). Both of these windows will be tied up by the invoking of these scripts (which start the corresponding server).

3) Log on to WebSphere Portal as an INS user (i.e "weaabuser"). You should see the "Intelligent Notification" portlet group available.

4) Select the "Intelligent Notification" tab.

5) Select the "Message Center" tab.

6) Click the "Compose a message" link, and compose a message to user "insabuser" with a test subject and message, then click "OK".

7) Log off as "weaabuser", log back in as "insabuser", click on the "Intelligent Notification" tab, select "Message Center". You should see a message from "weaabuser". Send one back to "weaabuser", logoff as insabuser, back in as "weaabuser", and confirm reception of message.