Preface
Introduction to Informatica Connector Toolkit
- Supported features
- Informatica Connector perspective
  - Connector Navigator
  - Connector Progress
Before you begin
- Download the welcome kit
- Download and install Eclipse IDE
- Download and install the Informatica Connector Toolkit
- Download OpenJDK and configure environment variables
- Log in to Informatica Intelligent Data Management Cloud
Develop a connector for Cloud Data Integration
- Create a new connector project
- Phase 1: Establish a connection
  - Create a connection
  - Test a connection
- Phase 2: Define the metadata
- Phase 3: Configure the runtime behavior
- Phase 4: Generate the connector package
  - Naming Convention
- Phase 5: Generate and run the test scenarios
  - Generate the test scenarios
    - Configure parameters in test suite file
    - Regenerate a test case
  - Run the test scenarios
    - Unit tests and sanity tests
    - Integration tests
Develop a connector for Data Loader
- Create a new connector project
- Phase 1: Establish a connection
  - Create a connection
  - Test a connection
- Phase 2: Define the metadata
- Phase 3: Configure the runtime behavior
- Phase 4: Generate the connector package
  - Naming Convention-DLT
- Phase 5: Generate and run the test scenarios
  - Generate the test scenarios
    - Configure parameters in test suite file
    - Regenerate a test case
  - Run the test scenarios
    - Unit tests and sanity tests
    - Integration tests
Import a connector
Connection attributes
- Connection attribute properties
Type system
- Native types and semantic categories
  - Native Type Properties
- Cloud Data Integration types
Connector metadata
- Metadata components
- Import dialog box settings
Partitioning capability
- Automatic partitioning
- Static partitioning
Pushdown capability
- Pushdown optimization execution flow
- Classes and methods for pushdown capabilities
Mappings in advanced mode
- Project, classes, and methods
Manual changes to Informatica Connector Toolkit source code
- Code changes for connection pooling
  - Connection Pooling through API
- Code changes for custom query
- Code changes for object path override
- Code changes for pushdown capability
- Code changes for SQL transformation
- Code changes for stored procedures
Runtime behavior
- Runtime Java functions
Connector example: MySQL_Cloud
- MySQL_Cloud Connector requirements
- Building the sample connector
- MySQL_Cloud Connector components
Version control integration
- Git version control integration
  - Prerequisites
  - Build a connector in Git repository
- Perforce version control integration
Appendix A: Metadata models
- Metadata model components
- Metadata patterns
- Features of type A metadata template
Appendix B: ASO model
- ASO model components
- ASO projections
Appendix C: Connector project migration
- Migrate connector project from Windows platform to other platforms
Appendix D: Frequently used generic APIs in Informatica Connector Toolkit
Appendix E: Frequently asked questions

Cloud Data Integration Connector Toolkit Developer Guide

Back Next

Configure advanced capabilities

Configure the advanced read and write capabilities for a JDBC driver-based connector. Enable the record extension and field extension to include additional metadata information for objects and fields.

Click

Configure Advanced Capabilities

Enable the advanced read capabilities for the connector.

Enable advanced read capabilities for the connector.

Select whether the connector supports lookup, foreign key, custom query, object path override, and partitioning when the connector reads from the data source.

To implement a partition logic based on the partition information that the user specifies, select

Fixed

. Implement the partition logic in the DataAdapter class. The user can specify the required partition information before the connector reads from the data source.

Select whether the connector supports join operation when the connector reads from the data source.

To specify operators and expression syntax recognized by Cloud Data Integration for the join operation, select

Platform

To specify an expression for the join operation that is specific to the data source for which you build the connector, select

Native

When a connector supports platform join, you can use the default operators such as

=, !=, >, >=, <

, and

for join conditions. You can specify advanced operators such as

Contains, Starts With, Ends With, Is Null

, and

Is Not Null

for join when you define the read capability for the endpoint metadata object.

For the code changes to include the advanced operators, see the RuntimeDataAdapter class of the MySQL_Cloud sample connector in the following location:

source\ict\samples\MySQL_Cloud

Select whether the connector supports Select operation to retrieve data for select rows from the data source.

Click Next
.

To add additional metadata information for the object and fields, select

Add Record Extension

and

Add Field Extension

Add additional metadata information for the object and fields.

Click

Add

to add a record extension or field extension and configure the following properties:

Property	Description
Name	Name of the attribute.
Display Name	Display name for the attribute.
Description	Description of the attribute.
Data Type	Data type of the attribute.
Default Value	Default value for the attribute.
Min Length	Minimum length for the value of the attribute.
Max Length	Maximum length for the value of the attribute. The maximum length of any attribute cannot be greater than Integer.MAX_VALUE, which is 2,147,483,647.
Supports Parameter	Indicates whether you can parameterize the attribute. When you parameterize an attribute, you can assign values for the attribute at run time. Full Parameterization. Indicates you can parameterize the value of an attribute completely. Partial Parameterization. You can parameterize a part of the attribute value. No. The attribute does not support parameterization.
Encrypted	Indicates whether you can encrypt the attribute.
Mandatory	Indicates whether a connection attribute requires a value. If you set the Mandatory property to True but you do not display the attribute on the connection management user interface, you must set a default value for the attribute.
Hidden	Indicates whether you can hide the attribute.
Allowed Values	List of values allowed for the attribute.

Click

The following shows an example of record extension in Cloud Data Integration:

The following image shows an example of field extension in Cloud Data Integration:

Click

Generate Code

After you define the connector metadata, the Informatica Connector Toolkit generates the

<NMOName>MetadataAdapter.java

file in the

Metadata

folder. Implement the following methods in the

<NMOName>MetadataAdapter.java

file to import metadata.

populateObjectCatalog(): Populates metadata details in the import wizard for the connector consumer.
Data preview in Cloud Data Integration does not work if the values of the Record.setName and Record.setNativeName methods are different.
populateObjectDetails(): Gets metadata from the data source based on the import dialog options settings.

If you configured metadata write settings for the connector, implement the

writeObjects

method in the

<NMOName>MetadataAdapter.java

file.

Add metadata for JDBC driver-based connector

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal