Computer directory system having an application integration driver infrastructure

• US 7,743,388 B2
• Filed: 10/18/2006
• Issued: 06/22/2010
• Est. Priority Date: 12/22/1999
• Status: Expired due to Fees

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: Novell Incorporated (Open Text Corporation)
• Inventors: Nikols, Nick N., Rapp, Daniel Wallace
• Primary Examiner(s): Cao; Diem K
• Application Number:
  US11/550,765
• Publication Number:
  US 20070226753A1
• Time in Patent Office: 1,343 Days
• Field of Search: 719/318, 719/320, 709/223
• US Class Current: 719/319
• CPC Class Codes: G06F 2209/544 Remote
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

An application integration driver infrastructure for facilitating the use of a distributed directory running in a computer network is provided. The infrastructure can transform specific directory events into a vendor-neutral data identification system and then use vendor-neutral transformation technologies to transform the neutral data identification into a specific application'"'"'s data format, and vice-versa. The infrastructure receives an event from the distributed directory into a markup language generation system, such as an extensible markup language (“XML”) generator. The XML generator converts the event into XML data and provides the XML data to a transformation processing system, such as an extensible transformation language (“XSLT”) processor. The XSLT processor transforms the XML data to a predetermined format. The format can be dictated by a stylesheet provided to the XSLT processor, the stylesheet being responsive to requirements of a computer application. The transformed data is then provided to the application for the application to use in a conventional manner. The application may use an application shim to convert the transformed data into a native application program interface (“API”) for the application.

Claims

1. A software program for transforming events in a computer network, the program comprising being stored on a recordable medium and including instructions for:

detecting an event through notification from an event handler of a component;

receiving the event into an XML generator from the component;

converting the event into XML data representing the event;

transforming the XML data representing the event to a first predetermined format by a transformation processor using a first stylesheet, the first predetermined format being responsive to a first application running in the computer network;

transmitting the transformed XML data representing the event in the first predetermined format to the first application through a first application shim to provide the transformed XML data representing the event to the first application by using a first native application program interface for the first application, where the first application is unable to receive an input data stream except through the first application shim;

transforming the XML data representing the event to a second predetermined format by the transformation processor using a second stylesheet, the second predetermined format being responsive to a second application running in the computer network;

transmitting the transformed XML data representing the event in the second predetermined format to the second application through a second application shim to provide the transformed XML data representing the event to the second application by using a second native application program interface for the second application, where the second application is unable to receive an input data stream except through the second application shim; and

receiving updates to the first stylesheet responsive to any changes in either the component or the first application.

2. The software program of claim 1, wherein the first predetermined format and the second predetermined format are the same predetermined format.

3. A distributed computer system, comprising:

a first processor connected to a network for executing computer code;

a second processor connected to the network for executing computer code;

a first memory connected to the first processor;

a second memory connected to the second processor;

a first application, a portion of which being stored in one of the first memory and the second memory;

a second application, a portion of which being stored in one of the first memory and the second memory;

a first transformation profile defining a first predetermined format for use by the first application;

a second transformation profile defining a second predetermined format for use by the second application;

software for detecting an event through notification from an event handler of a Component;

software for receiving the event from the component;

software for converting the event to a generic data description before transforming the event, wherein the generic data description is in a markup language;

software for transforming the event to the first predetermined format by using a generic transformation tool and the first transformation profile;

software for transforming the event to the second predetermined format by using the generic transformation tool and the second transformation profile;

software for providing to the first application the event transformed to the first predetermined format, including a first application shim for the first application to receive the transformed event and provide the event to the first application by using a first native application program interface for the first application, where the first application is unable to receive an input data stream except through the first application shim;

software for providing to the second application the event transformed to the second predetermined format, including a second application shim for the second application to receive the transformed event and provide the event to the second application by using a second native application program interface for the second application, where the second application is unable to receive an input data stream except through the second application shim; and

software to receive updates to the first transformation profile responsive to any changes in either the component or the first application.

4. The system of claim 3, wherein the generic transformation tool includes a markup language and the software for transforming the event includes a transformation processor.

5. The system of claim 3, further comprising:

a component transformation profile defining a predetermined format for use by the component;

software for detecting an application event in the first application;

software for transforming the application event to the component predetermined format by using the generic transformation tool and the component transformation profile; and

software for providing the transformed application event to the component.

6. The system of claim 5, further comprising:

software for detecting a second application event in the second application;

software for transforming the second application event to the component predetermined format by using the generic transformation tool and the component transformation profile; and

software for providing the transformed second application event to the component.

7. A method for interfacing with a component in a computing system, comprising:

identifying a first transformation profile defining a first predetermined format for use by a first application wherein the first transformation profile includes a stylesheet;

identifying a second transformation profile defining a second predetermined format for use by a second application;

receiving notification of an event from an event handler of the component;

receiving the event from the component;

converting the event to a generic data description before transforming the event, wherein the generic data description is in a markup language;

transforming the event to the first predetermined format by using a transformation tool and the first transformation profile;

transforming the event to the second predetermined format by using the transformation tool and the second transformation profile;

providing to the first application the event transformed to the first predetermined format, including providing an application shim for the first application to receive the event transformed to the first predetermined format and to provide the event to the first application by using a native application program interface for the first application, where the first application is unable to receive an input data stream except through the application shim; and

providing to the second application the event transformed to the second predetermined format, providing a second application shim for the second application to receive the event transformed to the second predetermined format and to provide the event to the second application by using a second native application program interface for the second application, where the second application is unable to receive an input data stream except through the second application shim; and

receiving updates to the first transformation profile responsive to any changes in either the component or the first application.

8. The method of claim 7, further comprising updating the application shim and the first transformation profile responsive to changes in the first application.

9. The method of claim 7, further comprising updating the second application shim and the second transformation profile responsive to changes in the second application.

10. The method of claim 7, further comprising storing the first transformation profile with the component.

11. A computer-readable medium storing a driver infrastructure for interfacing a component and applications, comprising:

a generator to receive an event from the component and to generate a generic data for the event, wherein the generic data is in a markup language;

a first transformation profile defining a first predetermined format for use by a first application, wherein the first transformation profile includes a stylesheet;

a second transformation profile defining a second predetermined format for use by a second application;

a transformation processor to transform the generic data for the event into a first application data for the first application using the first transformation profile and to transform the generic data for the event into a second application data for the second application using the second transformation profile;

a transmitter to transmit the first application data to the first application and to transmit the second application data to the second application, including;

a first application shim for the first application to receive the first application data and provide the first application data to the first application by using a first native application program interface for the first application, where the first application is unable to receive an input data stream except through the first application shim; and

a second application shim for the second application to receive the second application data and provide the second application data to the second application by using a second native application program interface for the second application, where the second application is unable to receive an input data stream except through the second application shim; and

software to receive updates to the first transformation profile responsive to any changes in either the component or the first application.

12. A driver infrastructure according to claim 11, wherein:

the driver infrastructure further comprises a second generator to receive an application event from the first application and to generate a second generic data for the application event;

the transformation processor is operative to transform the second generic data for the application event into a data; and

the transmitter is operative to transmit the data to the component.

13. A driver infrastructure according to claim 11, wherein the generator is operative to receive the event from a third application via an application shim, where the third application is unable to communicate with the program except through the application shim.