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

Finding Out-of-Sync Objects

Finding Out-of-Sync Objects

You use Find Out Of Sync Objects to determine if the event schema needs to be re-generated to reflect changes in the system.
The JMS Event Schema Manager displays a list of packages and remote packages that have changed since the last schema generation.
The Out of Sync Objects function compares the generated APIs to the database objects in the schema so both must be present to find the out-of-sync objects.
To find the out-of-sync objects:
  1. Start the JMS Event Schema Manager.
    The Hub Console displays the JMS Event Schema Manager tool.
  2. Acquire a write lock.
    In order to make any changes to the schema, you must have a write lock.
  3. Click
    FindOut of Sync Objects.
    The JMS Event Schema Manager displays all out of sync objects in the lower panel.
Once you have evaluated the impact of the out-of-sync objects, you can then decide whether or not to re-generate the schema (typically, external components which interact with the Hub are written to work with a specific version of the generated schema). If you regenerate the schema, these external components may no longer work.
If the JMS Event Schema Manager returns any out-of-sync objects, click Generate and Deploy ORS-specific Schema to re-generate the event schema.


We’d like to hear from you!