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 write capability

When you test the write capability of the connector, you test the components of the connector and write sample data to the data source. After you specify the test settings and run the test, you can view the result of the write operation, write operation statistics, and the log file.

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 Write

dialog box to test the write capabilities of the connector.

Uunder

Test Write 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. This is the default tracing level.
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 an endpoint metadata object to test the write operation.

The metadata of the endpoint metadata object along with the data type, scale, and precision appears in the

Test Write

page.

Select the columns to which you want to write data.

Click

The

Test Data

page appears.

In the Test Data page, you can load test data from a file or you can generate test data.

To load the test data from a file, perform the following steps:

Select the

Load from a File

option. You must load a comma-delimited TXT file or CSV file.

The date and time data types in the file must have the following timestamp format: MM/DD/YYYY hh24:mm:ss

Click

Browse

and select the file that contains the test data.

To generate test data, perform the following steps:

Select the

Auto generate data

option.

Enter the number of rows to generate. You can specify a maximum of 1000 rows.

Click

Generate

. The test data appears in the

Data Preview

section.

If required, you can edit the test data that appears in the

Data Preview

section.

Select an insert, update, or delete operation that you want to perform on the target object.

To perform an update or delete operation, the target object must contain a primary key. If you auto-generate the data, edit the value of the primary key column in the preview section to match with a record in the target object.

After you load a test data file or generate test data, click

The

Write Capability

page appears.

Specify values for the write capability attributes and then click

Run

The

Result

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

Result

page.

Click