Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

A method for self diagnosis and health check to improve consumability of software components in an enterprise solution

IP.com Disclosure Number: IPCOM000243560D
Publication Date: 2015-Oct-01
Document File: 3 page(s) / 62K

Publishing Venue

The IP.com Prior Art Database

Abstract

In Enterprise solutions where there are dependencies between components, an issue seen in one component might not have root cause in itself but in another dependent component which makes identifying the root cause time consuming. This article provides a self diagnosis mechanism which builds component hierarchy and dependency relationship of LIVE enterprise stack thereby enabling users to view integrated enterprise component status and diagnostic information in a single snapshot.

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

Page 01 of 3

A method for self diagnosis and health check to improve consumability of software components in an enterprise solution

In Enterprise solutions where there are dependencies between components, an issue seen in one component might not have root cause in itself but in another dependent component. However, as the end-user sees the issue in impacted component, the investigation/troubleshooting will focus the same component, sometimes even involving the concerned L2/L3 support teams. As in this case, the issue is in another component which is identified very late, there is lot of time & effort wasted in this whole process. When customer or end user runs into an issue with one or more software components
in an enterprise solution, the troubleshooting demands verification of piles of documents to isolate the issue on his environment e.g., product stack versions including fix pack levels on a particular OS.

Lack of a mechanism to know the current health of the components and not having the information to troubleshoot the problem will in turn reduce the customer satisfaction and so there by company's revenue.

This proposed method provides a self diagnosis mechanism for troubleshooting w.r.t the product execution environment by enabling trace level logging for the end users who are not experts of all components of the enterprise stack. End users will be provided the health status of each component and the apt information - product versions, component hierarchy / dependency, running status of components, component log locations, capabilities like support to CMIS, REST etc - for the current execution environment (specific to the product version, OS version etc).

In emerging technologies like cloud computing where the enterprise products will be deployed dynamically - the proposed solution enables the DevOps team / customers to see the details of the nodes, distribution of products, product execution logs, steps to enable additional logging etc. End users will be presented the relevant information based their administrative role/access. End users will be directed to the information on latest known product issues, resolutions etc by pointing them to the official publications (TechDocs, TechNotes etc).

The overview of proposed mechanism is described as follows :

All components in the product stack generate their own respective information in the


1.

form of XML documents which contains running/live product/component execution environment status with required static (hostname /modules/standards/logs etc) and dynamic configuration information (status/exceptions/latest issues etc) .

This generated component health XML data files will have details of hierarchy of


2.

product stack named as

and

xml tags and other respective tags like components information along with number of modules which directly interact with DB, Application Server, other major core modules, log file information, sequence of required configuration steps for enabling trace levels, kn...