are already configured and operational in your environment. For more information, see the
Multidomain MDM Installation Guide
.
The ORS schemas are configured and contain some test data. IDD application configuration requires the use of both the IDD Configuration Manager and the Hub Console. The Hub Console is used to create the necessary configuration elements in the target ORS (such as base objects, packages, lookups, match path components, and so on).
All base objects (and associated metadata) required for an IDD application need to be configured as SECURE in the Secure Resources tool in the Hub Console.
Configuration and initial testing should be done using an
MDM Hub
user account with unrestricted privileges for the target ORS schemas. You can either use the admin account or any other account that is configured with all privileges to the ALL_GLOBAL_RESOURCES group.
ALL_GLOBAL_RESOURCES does not include the custom resources added as part of the IDD application - those must be configured individually.
The analysis and data modeling for defining the subject areas and the business rules has been completed.
If you want to support workflows, in the
MDM Hub
you must enable state management on the target base object tables and decide which BPM tool you want to use for your workflow engine. You may need to complete integration steps for standalone BPM tools. For more information, see the
Multidomain MDM Configuration Guide
.
Other areas of the Hub Store need to be configured:
Security
Cleanse functions (if they will be used to check IDD user-entered data in an IDD application)
Hierarchy Manager (if it will be used in an IDD application).
If you enable state management on any
Hierarchy Manager
entity or relationship tables, you must enable the feature on all of them.
For more information about Hub Console tools, see the Admin Console online help or the