Table of Contents


  1. Introduction
  2. Configuring Hub Console Tools
  3. Building the Data Model
  4. Configuring the Data Flow
  5. Executing Informatica MDM Hub Processes
  6. Configuring Application Access
  7. MDM Hub Properties
  8. Viewing Configuration Details
  9. Search with Solr
  10. Row-level Locking
  11. MDM Hub Logging
  12. Table Partitioning
  13. Collecting MDM Environment Information with the Product Usage Toolkit
  14. Glossary

Guidelines for Implementing User Exits

Guidelines for Implementing User Exits

Implement user exits in a way that does not decrease
performance unnecessarily.
Consider the following guidelines when you implement user exits:
Consider how user exits affects performance.
When you implement user exits, you affect
performance. Consider if you need to use a user exit to accomplish what you want to do, or if you can do the same thing asynchronously without relying on user exits.
For example, when you load data, you might want to create tasks for the pending records. Although it is possible to create tasks with a user exit, it is unnecessary. You create a bottleneck in the process and unnecessarily decrease performance. You can create the tasks later because these tasks are not critical at that point in the process.
Use the database connection to query or update the database.
The Java user exit context provides a database connection. Use this database connection to query the database or update the database through direct JDBC calls or SIF API calls.
Consider how SIF API calls from a user exits affects batch performance.
When you call SIF APIs from a user exit, consider how these calls affect batch processes.
Use SIF APIs when possible.
Do not use the MDM Hub tables directly if you can use an equivalent SIF API.
Do not explicitly commit or roll back changes made in a user exit.
If you use the database connection to make SIF API calls or direct JDBC calls, the calls participate in the same transaction as the user exit caller. The user exit caller maintains the changes made in the transaction. Do not explicitly call commit or rollback on the connection passed to the user exits.
The MDM Hub does not authenticate or authorize user exits.
User exits run with full access to MDM Hub objects. User exits run with full access to MDM Hub Object regardless of the context. You can use the user exit SIF client to call a subset of supported SIF APIs. Only the supported SIF APIs can participate in the same transaction as the user exit caller. You cannot use the user exit SIF client to access unsupported SIF APIs.


We’d like to hear from you!