Browse Prior Art Database

Method of enterprise application integration in a content management system Disclosure Number: IPCOM000124407D
Original Publication Date: 2005-Apr-19
Included in the Prior Art Database: 2005-Apr-19
Document File: 3 page(s) / 56K

Publishing Venue



Enterprise application integration is an important aspect for a content management system. In an enterprise computing environment, a content management system may interact with various external applications in a business process. Disclosed is a method that supports fast and easier application integration with a content management by: (1) hiding the detail of C programming from the application programmer - The application programmer only needs to focus on writing his/her Java program. The detail of C programming part will be handled by the proposed method. (2) eliminating the compilation of the DLL routine by the application programmer – A pre-compiled DLL will be provided for the target platform. The application programmer is no longer responsible for compile the DLL routine any more. (3) allowing the manipulation of container data and return route at the Java program level by the application programmer – The data container and the return route will be transparent to the Java program. The application programmer can easily manipulate the container data and return route in the Java program.

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 52% of the total text.

Page 1 of 3

Method of enterprise application integration in a content management system

The disclosed method can be briefly summarized as follows.

Common structure of DLL invocation in a user exit - a common structure of invoking a DLL routine is proposed. The application programmer does not need to compile any DLL routine. Two control parameters will be passed into the DLL routine through the container: the location (i.e., path) of the data file for container data, and the location of the batch file to be launched at the DLL routine. Invocation of an application launch program - An application launch program will be invoked by the DLL routine. The location (i.e., path) of the program is specified in one of the control parameters. The sole purpose of this program is to launch a Java application.

Indirect invocation of Java program - A Java program will be indirectly invoked by the DLL routine through the application launch program. The program will contain business logic and interact with the container data carried in the data file which is specified in one of the control parameters.

In essence, the method fundamentally changes the way how the user exit is developed by the application programmer in IBM DB2 Content Manager. The application programmer will develop the user exit at the Java level, instead of the C level. The programming and compilation of the DLL routine by the application programmer is eliminated. Furthermore, the container data is much more accessible at the Java level.

Figure 1 shows an overall flow sequence of the operations among various entities, including workflow execution, DLL routine, application launch program, and Java application. The number associated with each box representation the order of execution. The arrow shows the direction of the flow. The operations are aligned vertically with each entity for readability.

Figure 1. Sequence of operations among various entities


[This page contains 1 picture or other non-text object]

Page 2 of 3

Workflow execution

Before invoking the user exit, two control parameters need to be defined as part of the container data:

@DATA_PATH@ - it represents the location (i.e., path) of the data file containing container data. @LAUNCH_PATH@ - it represents the location (i.e., path) of the application launch program that will launch a Java application.

A sample data file is listed below. It is a text file with a list of name/value pairs of data. The name with a pair of @'s indicates a reserved name. Again, DATA_PATH@ and @LAUNCH_PATH@ are two control parameters as mentioned above. @WP_COMP_ID@, @WP_ITEM_ID@, and @NUM_CONTAINER_DATA@ are used for internal purpose. @ROUTE_SEL@ and @UPDATE_FLAG@ will be set, if required, when the data file is passed back to the DLL routine.

@DATA_PATH@ = c:\drtesting\ @LAUNCH_PATH@ = c:\drtesting\userexit\EAILaunch.bat @WP_COMP_ID@ = A04I16A92004I82847 @WP_ITEM_ID@ = A1001001A04I15B80006G89298 @NUM_CONTA...