Modernize On-Premises Objects > Modernize on-premises objects > Modernization strategies for on-premises objects
  

Modernization strategies for on-premises objects

You can choose a modernization strategy based on your business needs and on-premises MDM configuration.
Use the following strategies to modernize MDM Hub objects:
You can also use a combination of these strategies. You can use Business 360 Console or third-party tools for migrating the MDM Hub objects to MDM SaaS. You can contact Informatica Global Customer support or third-party partners to follow reimplementation or modernization strategies.
The following table describes the modernization strategies for supported MDM Hub objects:
Supported MDM Hub Object
Description
Data models
Use the reimplementation or migration strategy to modernize data model objects, such as business entities.
Match Rule Sets
Use the migration strategy to modernize the match rule sets from the MDM Hub to MDM SaaS.
The modernization process migrates the match rule sets associated with the business entity fields.
Survivorship Rules and Trust Settings
Use the migration strategy to modernize survivorship rules and trust settings from the MDM Hub to MDM SaaS.
When you use Business 360 Console to migrate the survivorship rules and trust settings, the modernization process automatically migrates the rules and settings associated with each business entity field in the MDM Hub to MDM SaaS.
Note: In the MDM Hub, you can configure survivorship rules for each field. However, in MDM SaaS, smart fields and field groups are a single unit for which you can configure survivorship rules at the field group level.
Validation Rules
Use the reimplementation strategy to validate rules from the MDM Hub as data quality rules in MDM SaaS. Use Business 360 Console for creating basic rules and Cloud Data Quality for creating advanced rules.
User Accounts and User Roles
Use the migration strategy to modernize user accounts and roles from the MDM Hub to MDM SaaS.
The following table describes the modernization strategies for unsupported MDM Hub objects:
Unsupported MDM Hub Object
Description
Data Standardization and Enrichment
Use the reimplementation strategy for standardizing and enriching data from the MDM Hub.
To validate, cleanse, transform, standardize, and enrich data, MDM Hub uses Informatica Data Quality rules, while MDM SaaS uses Cloud Data Quality.
Siperian Mapping
In the MDM Hub, Siperian mapping manages the mapping between landing and staging tables. In MDM SaaS, the ingress process loads data from external applications and the mapping between staging and landing tables is handled internally without user intervention.
Business Entity Services
Use the Cloud Application Integration and reimplement the MDM Hub Business Entity Services APIs in MDM SaaS.
To access external applications, MDM Hub uses Business Entity Services APIs. However, MDM SaaS uses only REST APIs for accessing external applications.
Additionally, the authorization and authentication process differs between the MDM Hub and MDM SaaS APIs. For more information about using REST APIs in MDM SaaS, see Business 360 REST API.
Service Integration Framework
MDM Hub uses the Service Integration Framework APIs to invoke the MDM Hub operations from external applications in real time. However, MDM SaaS doesn’t support Service Integration Framework APIs. You can use Business Entity Services in MDM SaaS to access external applications.
Use the Cloud Application Integration and reimplement the MDM Hub Business Entity Services APIs in MDM SaaS.
Subject Area-Based Data Models
Effective with MDM Hub version 10.4, subject area-based data models are deprecated. To modernize subject area-based data models, upgrade to MDM Hub version 10.5 and migrate subject area-based data models to business entity-based data models.
You can then modernize these data models using reimplementation or migration strategy. If the data model includes customizations, you can't modernize it to MDM SaaS because MDM SaaS doesn’t support customizations.