Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Table of Contents

Search

  1. Preface
  2. Introduction to Informatica Connector Toolkit
  3. Before you begin
  4. Develop a connector for Cloud Data Integration
  5. Import a connector
  6. Debug the connector code
  7. Connection attributes
  8. Type system
  9. Connector metadata
  10. Partitioning capability
  11. Manual changes to Informatica Connector Toolkit source code
  12. Runtime behavior
  13. Connector example: MySQL_Cloud
  14. Version control integration
  15. Appendix A: Metadata models
  16. Appendix B: ASO model
  17. Appendix C: Connector project migration
  18. Appendix D: Frequently used generic APIs in Informatica Connector Toolkit
  19. Appendix E: Frequently asked questions

Cloud Data Integration Connector Toolkit Developer Guide

Cloud Data Integration Connector Toolkit Developer Guide

Runtime behavior

Runtime behavior

Use the functions in the Informatica Connector Toolkit API to specify the runtime behavior of the connector. You must write the code to define how the connector connects, disconnects, reads from and writes to the data source.
The run-time functions are available in Java. Within the run-time functions, you can use any API that is appropriate for communicating with the data source. You must implement all the run-time functions.
The run-time functions use character string arguments and character data buffers in UCS-2 format. If the database API communicates with the data source through the UCS-2 character set, then pass the character strings and data buffers directly to the database API. If the database API does not use the UCS-2 character set, you must convert the data to UCS-2 format before you pass the data to the database API.
To reduce complexity, design the connector so that it does not require the end user to specify any character set information. Use the Unicode mode if the database client API provides a Unicode mode. Or, query the database to determine the correct character set to use when reading or writing data to the database. If you require input from the end user about the correct character set, define a custom connection attribute to store this information.
You can define the connector run-time behavior to support pre-SQL and post-SQL commands to perform tasks before and after a mapping run. For example, you can define the connector run-time behavior to support a pre command that initializes environment variables before the mapping run.

0 COMMENTS

We’d like to hear from you!