Browse Prior Art Database

System and method for integration of Instant Messaging application (s) and J2EE web application(s)

IP.com Disclosure Number: IPCOM000180186D
Original Publication Date: 2009-Mar-05
Included in the Prior Art Database: 2009-Mar-05
Document File: 5 page(s) / 44K

Publishing Venue

IBM

Abstract

There is a common need to integrate Instant Messaging application (s) and J2EE (Java 2 Platform Enterprise Edition) web application(s) within an enterprise so that they can facilitate enhanced collaboration between parties that have frequent needs for interaction. One example scenario that portrays the need for such integration involves IBM Tivoli Service Desk (J2EE web application) and IBM Lotus Sametime (Instant Messaging application). The IBM Tivoli Service Desk provides incident/problem management capabilities, unifies key service support and asset management processes. Even though IBM Tivoli Service Desk provides complete incident/problem management for handling end user problems, there is a need to enable better communication between the teams to ensure timely, accurate and appropriate information is collected and previous experiences are brought to bear. Integrating IBM Lotus Sametime and IBM Tivoli Service Desk provides an ideal mechanism for meeting these needs. This integration allows IBM Tivoli Service Desk users to communicate and collaborate more efficiently so that the incidents/problems are resolved quickly. All the known design solutions have significant disadvantages. There is a need for a new methodology that offers a complete integration solution that is easy to consume and doesn't introduce multiple points of failure.

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

Page 1 of 5

System and method for integration of Instant Messaging application (s) and J2EE web application(s)

There is a common need to integrate Instant Messaging application(s) and J2EE (Java
2 Platform Enterprise Edition) web application(s) within an enterprise so that they can facilitate enhanced collaboration between parties that have frequent needs for interaction.

One example scenario that portrays the need for such integration involves IBM Tivoli Service Desk (J2EE web application) and IBM Lotus Sametime (Instant Messaging application). The IBM Tivoli Service Desk provides incident/problem management capabilities, unifies key service support and asset management processes. Even though IBM Tivoli Service Desk provides complete incident/problem management for handling end user problems, there is a need to enable better communication between the teams to ensure timely, accurate and appropriate information is collected and previous experiences are brought to bear. Integrating IBM Lotus Sametime and IBM Tivoli Service Desk provides an ideal mechanism for meeting these needs. This integration allows IBM Tivoli Service Desk users to communicate and collaborate more efficiently so that the incidents/problems are resolved quickly.

The following are the known design solutions to integrate the two applications.

Solution #1 Use proxy web application Ajax (asynchronous JavaScript and XML ( Extensible Markup Language)) or XMLHttpRequest to modify the HTTP (Hypertext Transfer Protocol) response.

Disadvantages: This methodology requires additional systems for fronting the application. There is a performance overhead associated with this approach and work associated with maintaining the additional infrastructure. Also, the proxy web application adds unnecessary problem determination complexity.

Solution #2 Use a Java Proxy server and filters to modify the HTTP response. Disadvantages: This methodology requires additional systems for fronting the application. There is a performance overhead associated with this approach and work associated with maintaining the additional infrastructure. Also, this methodology requires customers to switch from web servers to Java proxy server.

Solution #3 Use a customized HTTP transport channel for handling the web application. This will allow HTTP response to be modified to include the changes needed for integration
Disadvantages: This methodology is very low level solution and this solution can't be integrated easily with existing J2EE web application(s).

Solution #4 Enhance the existing J2EE web application directly to include changes needed for the integration.

Disadvantages: This methodology requires redeployment of the J2EE web application

1

Page 2 of 5

and can't be used on existing versions of the J2EE web application.

All of the design solutions listed above have significant disadvantages. The...