Browse Prior Art Database

Automatic Services status Monitoring System of Information Server

IP.com Disclosure Number: IPCOM000239032D
Publication Date: 2014-Oct-02
Document File: 3 page(s) / 60K

Publishing Venue

The IP.com Prior Art Database

Abstract

Abstract: When ever an ETL (Extraction , Transformation & Loading) / DataWarehouse engineer is trying to connect to the Information Server though DataStage clients engineer may get some failure showing the reason after few min. Later then engineer will check all the tiers like Repository , WAS and DataStage Engine to understand the reason for failure. This may take lot of time for an engineer to trace actual problem. It will also cause delay to an ETL developer to bring back the server in active state with out knowing reason and failure. There is a need to avoid the delay in understanding the reason and diagnosis. It would be good if there exists a complete monitoring system which will get the status of engine, services and repository ties status only when it is stopped / not functioning. The moment engineer gives IP address of server to which he wants to connect to one of component of IS, there should be a way to give a message / prompting on 'Unavaiability' of server. Meaningful message along with reasons failure at any tier will help engineer to alert other team members.

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

Page 01 of 3

Automatic Services status Monitoring System of Information Server


• When ever an ETL engineer is trying to connect to the Information Server (aka DataStage) in Development / QA / production environment though clients engineer may get some failure showing the reason after few min.

• Engineer will have to check all the services one after other to understand the reason for failure. Which is time taking process.

• Developers will not have access to know the services status. Hence they will have to wait for System administrator to come.

• At the same time other applications might be executing other end which will cause lot of data loss.

• This will force developer to reset all the data records ( if processed) and reset all other dependent components execution cycle.

• Difficult to understand Log messages which will be bigger in size.

• Developers will not have access to Log files in some critical environments like

production servers.

• This will cause lot of waste in man efforts / resources of same technology and other dependent technology.

For example : If automation scripts are being executed on Information Server which is down, all the scripts will be failed, and all dependent scripts will be failing consecutively.

If there is a mechanism to get alert, then the scripts can be stopped from running .

Some time developers in DataStage in Development / QA / Production environment may get intermittent warnings / error messages for unknown reasons.

This...