Browse Prior Art Database

Method, System and Program Product for Integrated Platform Component/Application Distribution Framework, Automated Installation/Configuration Management, and Notification Proxy Services. Disclosure Number: IPCOM000033513D
Original Publication Date: 2004-Dec-13
Included in the Prior Art Database: 2004-Dec-13
Document File: 4 page(s) / 68K

Publishing Venue



Distributing components and platform applications amongst thick client peers can be an unnecessarily cumbersome and unorganized process. If peer A has a component or application he/she would like to give to peers B, C, and D to run locally, he/she might have to do the following : 1) export or otherwise extract the component or application, 2) package the component or application in a zip file or some other format if not previously done so by the export operation, 3) choose from several possible means of making the component or application accessible to the peers (FTP site, Web Server, Email, etc.) , 4) notify the peers regarding the availability of this component and how/where to get it, and 5) each peer must then manually retrieve, install, and configure this component. Since there's no integrated channel or framework for routing these components peer-to-peer(s), you end up having to do a lot of manual and time-consuming processes which can leave you with pockets of components and/or applications in different places depending on which medium peers choose to make their components/applications available and by having to make these components available, you risk unwarranted access unless each peer takes measures to secure access, which requires additional steps and procedures.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 51% of the total text.

Page 1 of 4

Method, System and Program Product for Integrated Platform Component /Application Distribution Framework, Automated Installation /Configuration Management, and Notification Proxy Services.

Core Idea

The core idea of this invention is to provide thick client peers an integrated framework or channel for routing components/applications cross network with automated installation and configuration at the recipient peer and notification. This framework is integrated with both mission critical business platforms and collaboration services such as email and instant messaging to provide integrated notification capabilities through which peers can route components similar to how they send email, which makes for a great ease-of-use and integration story. This streamlines the process of distributing applications/components in a thick client environment and greatly reduces the manual steps otherwise involved in this process. Peers can select one or more components and/or applications, select peers from a buddy list or address book (ideally integrated with their email, instant messaging service, and/or corporate directory services), and then click a button to route the components to n number of peers.


Integrated channel or framework for distributing components and/or applications. Streamlined and integrated process for component distribution.

Aggregate system automation greatly reduces manual steps involved in component distribution.

Automated component/application installation/configuration mechanism at recipient node.

Integrated automatic recipient notification of routed components/applications. Email-like interface makes initiating component distribution processes analogous to sending an email.

The framework described in this invention is comprised of components capable of being mixed and matched as necessitated by the environment in which they operate.


The framework of this invention is comprised of the following main components: Component Client, Component Server, Component Management Container, Server Queue Management Service, and the Notification System (typically an SMTP Client). The client and server components perform the utility operations of routing and receiving components and/or applications, whereas the Container is responsible for coordinating component/application services in conjunction with the platform and notification. The notification component would typically serve as a proxy between the Container and the integrated collaboration service, such as email or instant messaging.

Component Server

The server is responsible for handling and processing incoming, routed components. The components are passed on to the Component Management Container or Server Queue Management Service.


Page 2 of 4

Component Client

The client handles the component routing operations as directed by the configuration of the Component Management Container or Server Queue Management Service.

Component Management Container

The Managemen...