Secured web based access of failed flows in an integration server

• US 20060161801A1
• Filed: 01/20/2005
• Published: 07/20/2006
• Est. Priority Date: 01/20/2005
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Gunasekaran, Senthil, Chandrasekharan, Sivakumar
• Granted Patent: US 8,191,135 B2
• Time in Patent Office: Days
• US Class Current: 714/4
• CPC Class Codes: G06F 11/2294 by remote test
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources

Abstract

A method for accessing failed events in an integrated server environment is disclosed. The method comprises providing a thin client in an application server within the environment, wherein the thin client provides role-based access to a failed event, and wherein the role-based access is based upon a user'"'"'s ability to access critical data. A thin client referred to as the failed event manager aids the user via a web browser, to manage events that failed during an integration scenario. Apart from being web-based, the failed event manager application also provides role-based access wherein users with certain roles are restricted in their ability to access critical data. The web-based failed event manager uses the security of the underlying application server, thus providing a secure environment. A system and method in accordance with the present invention takes advantage of the distributed computing capabilities of the underlying application server. As a result, remote users can simply log into the server via a web-portal from any location, and the familiar Windows environment is visually replicated on the screen. Moreover, a thin client provides higher security as all data including logs are stored and backed up only on the server. Thin clients lessen the danger to confidential information as no data is stored locally.

Claims

1. A method for accessing a failed event in an integrated server environment comprising:

providing a thin client in an application server within the integrated server environment, wherein the thin client provides access to the failed event;

wherein the access is based upon at least one of a plurality of roles, and wherein the access is based upon a user'"'"'s ability to access critical data.

2. The method of claim 1 wherein the plurality of roles comprise default roles.

3. The method of claim 1 wherein the plurality of roles comprise custom roles.

4. The method of claim 1 wherein access may be restricted based upon any of a point of failure of the event, name of a source adapter, name of a business object and key values of a business object.

5. The method of claim 2 wherein the default roles comprise an administrator, View all, View Events, and Submit Events.

6. The method of claim 3 wherein the custom roles provide compartmental level access to a failed event.

7. The method of claim 3 wherein the custom roles are created by setting a parameter value in the application server.

8. A computer readable medium containing program instructions for accessing failed events in an integrated server environment comprising:

providing a thin client in an application server within the integrated server environment, wherein the thin client provides access to the failed event;

wherein the access is based upon at least one of a plurality of roles, and wherein the access is based upon a user'"'"'s ability to access critical data.

9. The computer readable medium of claim 8 wherein the plurality of roles comprise default roles.

10. The computer readable medium of claim 8 wherein the plurality of roles comprise custom roles.

11. The computer readable medium of claim 8 wherein access may be restricted based upon any of a point of failure of the event, name of a source adapter, name of a business object and key values of a business object.

12. The computer readable medium of claim 9 wherein the default roles comprise an administrator, View all, View Events, and Submit Events.

13. The computer readable medium of claim 10 wherein the custom roles provide compartmental level access to a failed event.

14. The computer readable medium of claim 10 wherein custom roles are created by setting a parameter value in the application server.

15. An application server comprising:

a data manager for communicating with an integration server; and

a thin client for communicating with the data manager;

wherein the thin client provides access to a failed event;

wherein the access is based upon at least one of a plurality of roles, and wherein the access is based upon a user'"'"'s ability to access critical data.

16. The application server of claim 15 wherein the plurality of roles comprise default roles.

17. The application server of claim 15 wherein the plurality of roles comprise custom roles.

18. The application server of claim 15 wherein access may be restricted based upon any of a point of failure of the event, name of a source adapter, name of a business object and key values of a business object.

19. The application server of claim 17 wherein the default roles comprise an administrator, View all, View Events and Submit Events.

20. The application server of claim 18 wherein the custom roles provide compartmental level access to a failed event.

21. The application server of claim 18 wherein custom roles are created by setting a parameter value in the application server.