InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

System, Device, User Independent Test Solution for Creating, Deleting, Modifying and Synchronizing Personal Information Management Data

IP.com Disclosure Number: IPCOM000038303D
Original Publication Date: 2005-Jan-31
Included in the Prior Art Database: 2005-Jan-31
Document File: 4 page(s) / 38K

Publishing Venue



Many eBusiness mail systems such has Lotus Domino or Microsoft Exchange support Personal Information Management (PIM) data such as email, address book, calendars, invitations, memos, etc. Additionally there are an ever-increasing number of pervasive devices that also handle some PIM data. Moreover, many companies including IBM have come up with solutions that allow synchronization between these devices and to associated accounts on backend mail systems. Synchronization solutions can be very problematic due to complex data flow between the back-end mail servers and pervasive devices. It is critical to develop a system, device and user independent test solution to create, delete, modify and synchronize the PIM to test these synchronization solutions.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 46% of the total text.

Page 1 of 4

System, Device, User Independent Test Solution for Creating, Deleting, Modifying and Synchronizing Personal Information Management Data

ECAT is a system-independent , device-independent, and user independent test solution to create, delete, modify, and synchronize personal informtion management data in an automated, repeatable way.

A test scenario is embodied by an XML file known as Scenario XML. The Scenario XML would refer to one or more abstract users. A typical user would be 'user1'. Each user could and usually did have both a 'client side' and 'server side'. The user information is embodied by an XML file known as User XML. The same scenario may be run against a very rich set of parameters. Here are three sample invocations shown below each running the sample scenario 'ContactSampleScenario'

ECAT scenario=ContactSampleScenario userinfo=LotusINotesUser ECAT scenario=ContactSampleScenario userinfo=LotusStdTemplateUser ECAT scenario=ContactSampleScenario userinfo=Exchange2000User

LotusStdTemplateUser Exchange2000User <label>user1</label>

<backendtype>Domino</backendtype> <backendinfo> <server> esswin40.rtp.raleigh.ibm.com </server> <userid>sam</userid> <password>essadmin</password> <maildb>mail/sam.nsf</maildb> <contactdb>addr/sam.nsf</contactdb> <eventdb>mail/sam.nsf</eventdb> <taskdb>mail/sam.nsf</taskdb> <memodb>journal/sam.nsf</memodb> </backendinfo>


<backendtype>Exchange</backendtype> <backendinfo> <server>

pvcapar116.rtp.raleigh.ibm.com </server> <userid>joesph</userid> <password>as12qw</password> </backendinfo>

The above table shows only a portion of the User XML files. The user XML has all the information needed so the ECAT controller program can create, modify, delete, or examine data regardless of whether the scenario is being run against a Domino Server, an Exchange server. Server hostname, passwords, address information and other information is included in the User XML. The design is quite flexible, but some advanced planning is necessary. For instance if a set of scenarios refers to 'user1', 'user2', and 'user3' any User XML file used against the scenarios should properly resolve these users.

A scenario may have a lot of specific data associated with it. In addition to the Scenario XML and User XML ECAT also defines Data XML. For instance when creating a contact,


Page 2 of 4

a user in an address book, typically used to send email or record data such as phone numbers, email addresses, mailing addresses and so on. Scenario XML is mainly used to describe the add/delete/update/export actions the user wants the controller to perform, while Data XML is used to record detailed PIM data information. Separating Scenario XML and data XML makes the reuse of scenario and data XMLs extremely easy. The XML below shows an example of a simple Scenario XML, based on the scenario.dtd we defined. In this scenario XML, we specified to add a contact called contact1.xml on the server, export the contact content and...