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

Phase 2: Define the metadata

The connector metadata represents the metadata in the data source for which you build the connector. You can define metadata definitions to represent the differently structured metadata objects of the data source.

Use the

Informatica Connector Toolkit

to define the connector metadata. You can represent the metadata for data sources in which data is stored as records and for procedures in data sources. You can manually create native metadata for procedures or use swagger specifications to define the native metadata.

You can use the procedure pattern to define endpoint metadata objects for Informatica Intelligent Cloud Services connectors.

Define the following connector components to specify the connector metadata:

Endpoint metadata definition for the connector. You can define multiple native metadata definitions for a connector. For example, you can create different endpoint metadata objects for tables, views, and synonyms in a relational data source.

Record extensions and field extensions. You can define record extensions and field extensions to define additional metadata for records and fields.

Read and write capability for the connector. You can add attributes that you can use to read from or write to the data source.

Pushdown capability for the connector. You can add attributes that you can use to push as much of the transformation logic as possible to the target database.

Before you enable pushdown capability for the connector, you must copy the

com.infa.products.expr.jexpr.jar

file from

<ICT installation directory>/CCI/plugins/infa

<ICT installation directory>/ICT/Application/plugins

and restart the Informatica Connector Toolkit.

If you regenerate code for the endpoint metadata definition project, the Informatica Connector Toolkit does not regenerate code for the user-exposed source code visible in the Informatica Connector perspective. You have to manually edit the source code and make changes if you add, remove, or change the endpoint metadata attributes.

Develop a connector for Cloud Data Integration

Define the data types

Add metadata for JDBC driver-based connector

Add metadata for third-party library-based connector

Add metadata for REST API-based connector

Test the metadata

Package the resource or configuration files

Enable metadata logger

Download Guide

Watch

Comments

Communities