The InnovationQ application will be updated on Sunday, May 31st from 10am-noon ET. You may experience brief service interruptions during that time.
Browse Prior Art Database

%INC6%Method of packaging multi-database Lotus Notes applications for server installation

IP.com Disclosure Number: IPCOM000013334D
Original Publication Date: 2002-Oct-12
Included in the Prior Art Database: 2003-Jun-18

Publishing Venue



Many Lotus Notes applications are made up of multiple, separate database files. For multiple users to share data in Lotus Notes applications, the databases for these applications must be placed on a server at some point in the process. Some applications require that initial users of the application first use it on their own PCs for a period of time before it is put on a server to be shared and used by the rest of the users. A problem arises when it comes time to move the application from the initial user's PC to a server. The application must be transferred to the server and be configured properly, so that the rest of the users can install the application. These users must also have Lotus Notes replication configured correctly to enable user collaboration for the application. This work could be performed manually, but it requires many manual and error-prone steps. It also requires that the users and/or server administrators have some knowledge of and/or training in the internals of the application to properly make the manual changes. To solve this problem, we created a utility for the Engagement Support Environment (ESE) application called "Send ESE". This utility enables an ESE user to package the ESE application that exists on his PC, and send it to a server administrator using a Notes memo. The server administrator, who has authority to create files on a server, then uses the attachment in this memo to install ESE on a server. The application database files are placed on a server by this process, and are automatically configured so that other users can install ESE on their own PCs, and can replicate changes to and from the server. This is accomplished automatically without the many complex manual steps that would normally be needed to transfer the files to the server and perform other setup tasks. Send ESE is invoked using a Notes agent. When an ESE user is satisfied that the ESE application on his PC is ready to be shared with other members of his team, he invokes the Send ESE agent. At this point, a document is composed using the Send ESE form and the user is prompted to enter the name of the server administrator that ESE is to be packaged and sent to: The user is then asked if they would like to continue sending ESE to the specified administrator. If the user chooses to continue, he is presented with the following form. The items under the Status header are status messages that tell the user what the Send ESE process is doing. These messages keep changing to inform the user of the current activities and status of the send: