Browse Prior Art Database

Identifying Unused Connectors Using An Extract-Transform-Load (ETL) Cleanup Tool

IP.com Disclosure Number: IPCOM000234052D
Publication Date: 2014-Jan-09
Document File: 5 page(s) / 178K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method and system is disclosed for using an Extract-Transform-Load (ETL) cleanup tool to identify one or more objects/components/activities such as, but not limited to, unused connectivity stages, user written routines and buildups that are not referenced in a DataStage* project. The method and system uses the xmeta repository to run a usage analysis for selectively removing the unused components.

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

Page 01 of 5

Identifying Unused Connectors Using An Extract - -Transform

Transform- -Load Load (((ETL ETL)

Cleanup Tool

Cleanup Tool

Connectors are used for supporting various data sources during the packaging of an information server. During auto-install, the connectors get installed into the system regardless of whether they are used or are even desired by the user. Once the product is installed and additional DataStage projects are created, the time to install fix packs or patches is increased substantially due to the installation of connectivity components into each project. Moreover, there are no known solutions where the user can selectively install connectors or selectively remove them post-install.

The method and system disclosed herein uses an Extract-Transform-Load (ETL) cleanup tool to identify one or more objects/components/activities such as, but not limited to, unused connectivity stages, user written routines and buildups that are not referenced in a DataStage project. The method and system uses the xmeta repository to run a usage analysis for selectively removing the unused components.

In an exemplary embodiment, after a DataStage project has been created, the ETL cleanup tool uses the xmeta repository to run a usage analysis for identifying one or more objects/components/activities such as, but not limited to, unused connectivity stages, user written routines and buildups that are not referenced in the DataStage project. Subsequently, the output of the results where no usage is detected is presented to allow the user to selectively remove the components that were identified as part of the automated analysis either categorically or individually.

In another embodiment of the present invention, the ETL cleanup tool can be automatically initiated without prompting the user for additional input as in the case of bundling of a product within a solution. Also, the ETL cleanup tool can be automatically initiated without prompting the user for additional input as in the case of bundling of the product with another product. Moreover, the ETL cleanup tool can be automatically initiated without prompting the user for additional input as in the case of bundling of the product with a Virtual Machine (VM) image. In addition, the ETL cleanup tool can automatically initiate when invoked on a newly installed production or a quality check instance.

Fig. 1 discloses an existing Infosphere** information server functionality which allows a user to select a single component or a set of components and run "find where used (deep)" query to the xmeta repository using the DataStage designer.

1

)


Page 02 of 5

Figure 1***

Subsequently, the results of the query are saved to a report which includes the details of the query. The report also includes the location details specifying where any of the components are being used.

In an exemplary implementation, a sample query for identifying unused connectors from the connectivity stages selected from the "\Stage...