Developing a custom extractor module
Use the Integration Studio to develop and work with custom extractor modules. In order to produce data and perform extraction activities, you need to implement the abstract
In addition, you also need to implement the following methods:
connect: To connect the extractor module to external sources.module to external sources.
disconnect: To close the open connections.
For more information, see the following sections:
About the abstract methods
The call sequence to the methods is always connect-extract-disconnect. Although, note that it is perfectly correct to perform the connection and disconnection inside the extract method. There is no difference in execution, and the separation between the three phases is only for code readability.
The following example shows an implementation of the
Getting information from a JDBC database
If you are connecting to a JDBC database, ensure that the JDBC driver file (.jar file) is stored in the <Installation_directory_of_Capacity_Optimization>/etl/libext directory on the ETL server that runs the ETL task.
If you are using a database other than Oracle or Microsoft SQL Server, you must explicitly specify the JDBC driver information when you are configuring the extractor. For more information, see Generic - Database extractor (Java).
To develop a custom extractor module
- Creating a custom extractor module
- Editing the extractor code
- Activating a custom extractor module
- (Optional) To store your ETL code in a secure location and share the code, see Saving a copy of an Integration Studio project.
- (Optional) To debug the custom extractor module, see Debugging a custom parser or extractor module.