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

Naming Convention

Naming Convention

A naming convention makes it easy to identify the files that belong to a connector.
Use the following guidelines when you name the connector files:
  • Determine a name for the connector. Use the connector name as a prefix for the connector file names. The connector name is an alphanumeric string that can include the uppercase and lowercase letters A to Z and the numbers 0 to 9. The first character of the name must be a letter.
  • Determine a unique name to identify the company building the connector. The company name is included in the package name for the connector classes.
  • Use the connector name when you create a directory for the connector in the Informatica directory:
    INFA_HOME\plugins\dynamic\
    ConnectorName
The following table lists the recommended naming convention for connector files:
Component
Naming Format
Package for the connector definition and type system classes
com.vendorname.connectorname.connection
Connector definition class
ConnectorNameDefn
Type system class
ConnectorNameTypeSystem
Resource file for the connection management user interface
ConnectorNameBundle.properties or ConnectorNameBundle_lang.properties

0 COMMENTS

We’d like to hear from you!