Developing custom ETLs
You can create custom ETLs to extend data collection capabilities of TrueSight Capacity Optimization. These custom ETLs can be used to collect data from a variety of data sources according to your requirement.
Both standard and custom ETLs rely on the ETL Development API provided by the platform to allow data integration.
The ETL Development API
The ETL Development API supports Java and Perl programming languages.
Before developing a new custom ETL, BMC recommends checking if an existing custom ETL is already available for use.
You can use one of the following methods for creating custom ETLs:
- ETL Development kit – Java and Perl
- Integration Studio – Java only
ETL Development kit
ETL Development kit is a command line based utility that you can use for creating and packaging custom ETLs. This utility supports ETL development in Perl and Java, allowing you to edit the ETL code in your development environment. For more information, see Using the ETL Development kit for creating custom ETLs.
Integration Studio is an Integrated Development Environment (IDE) based on Eclipse Rich Client Platform.
ETL development in Integration Studio enables you to:
- Write, test, and debug a custom ETL module.
- Quickly access code templates, and other useful information to build a custom ETL.
- Activate a custom ETL in your TrueSight Capacity Optimization environment, and use it as a standard ETL.
- Use a shared code repository local to your installation.
You can use Integration Studio for creating custom ETLs only in Java. If you want to use Perl for creating custom ETLs, use the ETL Development kit.
BMC recommends using the Integration Studio only in a test environment. Verify the ETL run in the simulation and production modes in the test environment. When the ETL is ready, move it to the production environment using the export/import ETL feature of the TrueSight Capacity Optimization console.
To modify the configuration of the ETL that is running in the production environment, update the ETL configuration in the test environment, and then export the updated ETL again to the production environment.
For more information on using Integration Studio for developing ETLs, see the following topics:
- ETL life cycle
- Preparing to develop custom ETLs
- Developing a custom parser module
- Developing a custom extractor module
- Debugging a custom parser or extractor module
- Saving a copy of an Integration Studio project
- Importing an Integration Studio project
- Upgrading an ETL package
- Using the ETL Development kit for creating custom ETLs