Browse Prior Art Database

Runtime display of application instances within a distributed system of servers

IP.com Disclosure Number: IPCOM000201081D
Publication Date: 2010-Nov-08
Document File: 3 page(s) / 65K

Publishing Venue

The IP.com Prior Art Database

Abstract

Runtime display of application instances within a distributed system of servers

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 50% of the total text.

Page 01 of 3

Runtime display of application instances within a distributed system of servers

Task dataVarious methodologies exist for defining the artefacts that make up a business application and applying that information to display the runtime artefacts corresponding to that application. However, runtime identification and display of individual instances of an application have not been possible. This disclosure describes a mechanism for identifying such instances of a business application. It does so by applying application metadata such as deployment descriptor metadata to data collection from the run time distributed systems, and displaying that information within a single display. The same technique can also be applied to historical data previously collected (e.g through SMF recorded data on IBM's z/OS operating system). The extraction of application metadata is known in the art. The present disclosure relates to exploitation of a subset of such metadata to the real time observation and analysis of business applications in distributed servers.

    The current state of the art allows for manual definition of the application components and the associated resources, with subsequent install into the distributed environment and observation of the installed resources. A particular embodiment of this can be found in CICSPlex SM, a component of IBM's CICS Transaction Server. This corresponds to function found in its Business Application Services (BAS) and Operational component (OPS) when using logical scopes. One drawback of this technique is that it does not take into account the ability to exploit autoinstall for resources such as programs. This drawback can be accommodated for as described below. Furthermore, this "logical scoping" couples application metadata with resource definition, limiting its general use.

    Whilst current art enhances the ability to manage run time resources associated to a given application in isolation to other resources thereby simplifying management, its capability does not provide for looking at individual business application threads which are either local or distributed in nature. Several subclasses of problem can be provided for with different degrees of importance. Applications that:
· Are running normally, and are fleetingly observed within the system. These could be around for milliseconds, and in a run time environment would show up, but not be of great importance (off line of course, this would aid in off line analysis of applications).

· Are running as long running tasks. These exist for longer within the system, and more readily observed using this method. Again, off line would also benefit from this approach as observed above.

· Are running abnormally, so are living for longer within the system. These indicate potential problems with the applications availability and therefore are of interest to the management staff. This approach is therefore of significant benefit to this class of person.

Identification of...