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

Test the read capability

When you test the read capability of the connector, you test the connection definition, metadata of the data source, and operations that the connector supports. After you specify the test settings and run the test, you can view the result of the read operation, read operation statistics, and the log file. You can test the read capability of the connector only for the Windows platform.

To debug the code, use the same debug configuration that you used to test the connection and metadata components of the connector. You can also set breakpoints in the code that you want to debug.

After you define the debug configuration, you can launch the

Test Read

dialog box to test the read capabilities of the connector.

Under

Test Read Capability

, click

Test Runtime Behavior

The default JVM environment settings and tracing level are displayed. The Informatica Connector Toolkit uses the JVM settings to run the debug configuration.

If required, edit the JVM environment settings. Ensure that you use the same port number that appears in JVM settings for the connection properties in the debug configuration.

Select the required tracing level. The default is normal. Based on the amount of detail that you require in the log file, you can override the default tracing level.

You can set the following types of tracing level:

None: Does not override the default tracing level.
Terse: Logs initialization information and error messages and notification of rejected data.
Normal: Logs initialization and status information, errors encountered, and skipped rows due to transformation row errors. Summarizes mapping results, but not at the level of individual rows. Default is normal.
Verbose Initialization: In addition to normal tracing, logs additional initialization details, names of index and data files used, and detailed statistics.
Verbose Data: In addition to verbose initialization tracing, logs each row. You can also get detailed statistics on where string data was truncated to fit the precision of a column.

Click

The connection attributes that you defined for the connector appears.

Enter values for the connection attributes to test the connection to the data source.

Click

Connect

The

Test Metadata

page appears with the metadata imported from the data source.

Select the endpoint metadata objects and the corresponding endpoint metadata fields to test the read operation.

Click

The

Filter Condition

page appears.

Select the

Configure Filter

option in the

Filter Condition

page and specify the filter condition.

To specify an Informatica platform expression for the filter operation, perform the following steps:

In the

Definition

section, click

Add

to add an Informatica platform expression.

In the

Field

column, select the field to use in the expression.

In the

Operation

column, select a conditional operator to use in the expression.

In the

Value

column, enter a value for the conditional expression.

To specify a native expression for the filter operation, enter the expression in the

Definition

section.

After you specify expressions for the endpoint metadata object, click

The

Read Capability

page appears.

Specify values for the read capability attributes, and then click

Run

The

Result

page appears. You can view the result of the read operation, read operation statistics, and the log file in the

Result

page.

Click

Test runtime behavior

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal

0 COMMENTS

We’d like to hear from you! Log in to comment.

Rename Saved Search

Table of Contents

Cloud Data Integration Connector Toolkit Developer Guide

Cloud Data Integration Connector Toolkit Developer Guide

Test the read capability

Test the read capability