Developing custom ETLs
The TrueSight Capacity Optimization ETL set can be extended using the ETL Development API provided by Integration Studio.
The ETL Development API allows you to develop a new ETL from scratch, drawing heavily from the existing ETL framework. This ensures that the new ETL run is efficient, safe, controlled, and maintained. The ETL Development API is the only Integrated Development Environment required to write, test, and run both standard, and open ETLs.
Standard ETLs and Open ETLs (also known as Custom ETLs) are ETL modules responsible for data integration in the ETL Development API. These modules let you integrate custom data into the TrueSight Capacity Optimization space. Before developing a new ETL, it is advisable to check if an existing custom ETL is already available for use.
The ETL Development API
The ETL Development API supports two programming languages – Perl, and Java.
Developing custom Perl ETLs is deprecated in TrueSight Capacity Optimization version 11.3.01. BMC recommends that you use the Java language and Java ETL development API to develop new custom ETLs. For more information, see Deprecated and dropped features and components.
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.
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 developing ETLs, see: