Table of Contents

Search

  1. Preface
  2. Part 1: Introduction
  3. Part 2: Configuring Hub Console Tools
  4. Part 3: Building the Data Model
  5. Part 4: Configuring the Data Flow
  6. Part 5: Executing Informatica MDM Hub Processes
  7. Part 6: Configuring Application Access
  8. Appendix A: MDM Hub Properties
  9. Appendix B: Viewing Configuration Details
  10. Appendix C: Row-level Locking
  11. Appendix D: MDM Hub Logging
  12. Appendix E: Table Partitioning
  13. Appendix F: Collecting MDM Environment Information with the Product Usage Toolkit
  14. Appendix G: Informatica Platform Staging
  15. Appendix H: Informatica Platform Mapping Examples
  16. Appendix I: Glossary

ORS-specific APIs Overview

ORS-specific APIs Overview

You can generate APIs for specific objects such as base objects, packages, and cleanse functions in an
Operational Reference Store
. Use the SIF Manager tool of the
Hub Console
to generate ORS-specific APIs.
Configure the base objects and packages of the
Operational Reference Store
before you generate ORS-specific APIs. The ORS-specific APIs are available with SiperianClient through the client JAR file and as a web service. When you generate ORS-specific APIs the
MDM Hub
associates a version ID with the ORS-specific APIs client JAR file.
ORS-specific APIs act on specific
Operational Reference Store
objects. For example, a generic API might place data in the database record that you specify. An ORS-specific API identifies the same data as a name and an email address and places those fields into a customer record, as defined in the
Operational Reference Store
.
Use the ORS-specific APIs through the
Services Integration Framework
(
SIF
) SDK or as a SOAP web service. If you use the SIF SDK, you need to install the Java Development Kit and the Apache Jakarta Ant build system.

0 COMMENTS

We’d like to hear from you!