In the Package Explorer view of the Integration Studio, double-click the custom extractor module that you want to activate. The module is selected.
In the ETL Module view, complete the following steps:
If the ETL Module view is not displayed in the Integration Studio, add the view. For detailed steps, see To add the ETL Module view to the Integration Studio.
After you activate a module, the following updates occur:
The Status value is Ready for production, which means the module is activated and is available for usage in the production environment.
The module is uploaded to the repository and the code is distributed to all ETL Engine Server computers (copied into the
/customsrc folder on each ETL Engine Server), to be available for running in an ETL.
The custom module is displayed in the list of ETL modules when adding an ETL in the TrueSight Capacity Optimization console.
If you make changes to the ETL code later and want to bring the updated module in production mode on the ETL Engine Server, then you must activate the module again by clicking the Activate button, even if it is already active. At this point, you will be asked whether or not you want to overwrite the existing module.
As a best practice, if a new or a modified module is different in behavior than an existing one, provide it an explicitly different name (Use a version number such as TSCOextractor02E.pm). By doing so, the old ETLs continue to use the old module and the new ETLs can use the new module.