Browse Prior Art Database

Solution level problem determination

IP.com Disclosure Number: IPCOM000124664D
Original Publication Date: 2005-May-03
Included in the Prior Art Database: 2005-May-03
Document File: 5 page(s) / 121K

Publishing Venue

IBM

Abstract

Mid-market business partners and customers traditionally view application software stacks as a single solution and not as collection of individual middleware components. They expect these 'solutions' to be able to be managed and debugged as a single entity. Often IBM middleware based solutions consist of a number of distinct products with dozens of logs located throughout the organization's network topology. What is needed is a way to provide mid-market customers a view of their solutions that allows the user to quickly determine the overall health of their deployed solution and perform problem determination on the solution if necessary. The view should obfuscate the fact that there are many independent product logs and instead allow the user to act on a single set of solution logs without understanding the details of where the logs are located or which logs should be analyzed. Additionally, these users must be able to easily share the log information contained in the correlated log with local or remote support personnel.

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

Page 1 of 5

Solution level problem determination

Disclosed is a mechanism for performing problem determination on a deployed middleware solution. The deployed solution typically consists of multiple middleware product log files deployed across multiple remote machines. A view is provided that allows the user to quickly determine the overall health of a solution and perform problem determination on a set of logs which have been correlated into a solution log. The solution log can be exported and shared with support personnel.

Mid-market business partners and customers traditionally view application software stacks as a single solution and not as collection of individual middleware components. They expect these 'solutions' to be able to be managed and debugged as a single entity. Often IBM middleware based solutions consist of a number of distinct products with dozens of logs located throughout the organization's network topology. What is needed is a way to provide mid-market customers a view of their solutions that allows the user to quickly determine the overall health of their deployed solution and perform problem determination on the solution if necessary. The view should obfuscate the fact that there are many independent product logs and instead allow the user to act on a single set of solution logs without understanding the details of where the logs are located or which logs should be analyzed. Additionally, these users must be able to easily share the log information contained in the correlated log with local or remote support personnel.

This technique assumes the user has access to an administrative console that is capable of performing basic administration tasks of the middleware components included in a defined 'solution'. The administration console also contains tasks that allow the user, or a solution provider, to define a Solution that includes information about the managed middleware components. A solution oriented view is described that shows the basic health of the Solution. In addition, the user may launch an integrated log and trace correlator that will automatically gather and correlate the logs that are crucial for that Solution. The advantages of this approach are:

Logs are detected and gathered from the remote middleware components on

behalf of the user. The user does not have to go to each system and find the logs on their own.

The gathered logs are converted to a standardized format which allows for a

single correlated solution level log to be displayed. This Solution log can be analyzed immediately by the user or sent to remote support personnel for analysis.

The logs that are important for the specific Solution are predetermined for the

user, but can be customized at runtime.

A solution provider, such as an ISV, RSI, or consultant can customize the

Solution on behalf of an inexperienced user.

One embodiment of this technique uses an administrative console, such as the IBM Express Runtime console, that allows the soluti...