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. Connection attributes
  7. Type system
  8. Connector metadata
  9. Partitioning capability
  10. Manual changes to Informatica Connector Toolkit source code
  11. Runtime behavior
  12. Connector example: MySQL_Cloud
  13. Version control integration
  14. Appendix A: Metadata models
  15. Appendix B: ASO model
  16. Appendix C: Connector project migration
  17. Appendix D: Frequently used generic APIs in Informatica Connector Toolkit
  18. Appendix E: Frequently asked questions

Cloud Data Integration Connector Toolkit Developer Guide

Cloud Data Integration Connector Toolkit Developer Guide

Appendix B: ASO model

Appendix B: ASO model

The Informatica Connector Toolkit internally uses an Adapter Specific Object (ASO) model to represent operations on native metadata objects.
The ASO model serves as a container for native metadata objects and associates operations such as read, write, or lookup with the native metadata objects. A native metadata object represents the native importable metadata of a data source such as a flat file, relational data source, and nonrelational data source. An ASO model contains references to multiple native metadata objects and operations.
Do not use the ASO models directly to define operations on native metadata objects. Use the Informatica Connector Toolkit to define operations on native metadata objects.

0 COMMENTS

We’d like to hear from you!