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

Code changes for object path override

When you enable the object path override capability for the connector, you must manually modify the Informatica Connector Toolkit classes and methods to implement the object path override logic.

Add the following code changes to implement the object path override capability for the connector:

Declare the following variable in the RuntimePlugin, RuntimeOperationAdapter, and RuntimeDataAdapter classes:

private InfaUtils infaUtils;

Initialize the

infaUtils

variable in the initPlugin() method of the runtime plugin class.

The following code snippet shows an example of how to initialize the

infaUtils

variable for MySQL_Cloud Connector:

@Override
    public int initPlugin(PluginInfo pluginInfo, InfaUtils infaUtils){
    		this.logger = infaUtils.getLogger();
    		this.infaUtils=infaUtils;
    		pluginInfo.setPluginDescription("");
    		pluginInfo.setPluginName("com.infa.adapter.mysql_cloud.libraryInfo.TABLEMYSQL_CLOUDLIBRARYINFO");
    		pluginInfo.setPluginVersion("1.0.0");
    		return EStatus.SUCCESS;
    }

Add the

infaUtils

variable as a constructor argument in the RuntimeOperationAdapter and RuntimeDataAdapter classes.

The following code snippet shows how to add the

infaUtils

variable as a constructor argument for MySQL_Cloud Connector:

public MySQL_CloudTableOperationAdapter(Logger infaLogger,InfaUtils infaUtils ){
     	this.logger = infaLogger; 
     	this.infaUtils=infaUtils;
    }
	
		MySQL_CloudTableDataAdapter(InfaUtils infaUtils){
		this.infaUtils=infaUtils;
		
	}

Update the constructors for the operation adapter and data adapter objects in the getDataAdapter() and getDataSourceOperationAdapter methods in the RuntimePlugin class.

The following code snippet shows an example for MySQL_Cloud Connector:

@Override
    public DataAdapter getDataAdapter(){
    	return new MySQL_CloudTableDataAdapter(infaUtils);
    }

 @Override
    public DataSourceOperationAdapter getDataSourceOperationAdapter(){
    	return new MySQL_CloudTableOperationAdapter(logger,infaUtils);
    }

Add an import statement in the RuntimeOperationAdapter class to access the

infaUtils

variable:

import com.informatica.sdk.adapter.javasdk.common.InfaUtils;

Access the value of the object path overridden parameters in the initDataSourceOperation() method of the RuntimeOperationAdapter class:

objectPathWrite =this.infaUtils.getObjectParameters();

//objectPathWrite is a Map with Native name of the object as key and overriden parameter value as the value.
//Check if the overriden value is valid.

Rename Saved Search

Table of Contents

Cloud Data Integration Connector Toolkit Developer Guide

Cloud Data Integration Connector Toolkit Developer Guide

Code changes for object path override

Code changes for object path override