Browse Prior Art Database

Retrieving and restoring the ETL changes which could not be saved due to sudden network connectivity failure between the client machine and the ETL Server

IP.com Disclosure Number: IPCOM000225350D
Publication Date: 2013-Feb-12
Document File: 3 page(s) / 65K

Publishing Venue

The IP.com Prior Art Database

Abstract

This article proposes introducing a feature in ETL Client tool that will help the end user to restore the last made changes which could be saved due to an event of sudden network failure between the ETL Server and the ETL client.

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

Page 01 of 3

Retrieving and restoring the ETL changes which could not be saved due to sudden network connectivity failure between the client machine and the ETL Server

Disclosed is a concept for restoring the last made changes in ETL (Extract Transformation Loading) jobs, which could not be saved in the Server Repository on an event of sudden

Network disconnection of ETL client tool from the remotely located ETL Server.

The most common used ETL setup is the one where the client installed in a local machine (windows based OS) while the server is being installed in a remote machine (windows or AIX or Linux machine). There are situation of sudden disconnects between the server and the client. If the client gets disconnected from the network while the user is still making the changes or could not save the changes made till that point, there is no way to recover the changes. It is very frustrating for the user as the user has to manually redo all the changes and if the job is very big, it will consume significant amount of development time and also can introduce unwanted bugs.

The concept disclosed herein provides an auto-recovery feature in the ETL Client tool. This auto- recovery feature is user friendly and saves a lot of time which would otherwise be wasted in redoing the changes again.

Mechanism for Auto - Recovery

Whenever there is a sudden disconnect between the client and the Server, unsaved ETL jobs are saved internally in the local client machine as XML files with the most recent changes.

This job XML files is saved in the default path where the client is install in local machine (or any directory defined by the user) as < local-ETL-Client_path>\AlertReport\job.xml>

The flowchart ( Fig 1 ) explains the logic for the auto-recovery system...