Multidomain MDM SaaS Best

Practices
10th Aug 2023

Prashant Gupta `
Adhish Mahajan
Agenda
Overview
Set up Applications
 Data Modelling
 SDLC Asset Migration
 Secure Agent Best Practices
 Ingress (FEP Mapping, DQ rules)
 Egress Job
 Relationship & Hierarchies
 Business UI Configurations (Application & Pages)
 Reports
 Reference 360 SDLC
 Reference 360 Data Import and Export
 Known Limitations

2 © Informatica. Proprietary and Confidential.

Overview
 Informatica Master Data Management Cloud (MDM SaaS) is
a cloud-based Master Data Management (MDM) solution.

 MDM SaaS - Customer 360 is an enterprise cloud-based

customer data management solution which uses MDM SaaS -
Customer 360 Records for creating a single source of truth
for data as well as onboarding, consolidation, enrichment,
governing, and distributing such data.

3 © Informatica. Proprietary and Confidential.

Set up Applications
For any New Org activation – It’s a 3 Step process.

 A Customer Success Manager (CSM) will reach out

to customer to get the administrator user details.
(Email, First Name, Last Name, Phone no,
Address).
 After the CSM creates org account, administrator
user will receive an email to confirm your account.
The account confirmation link is valid for 48 hours
 After you activate the account, customer can log in
to Informatica Intelligent Cloud Services and set up
the business applications

4 © Informatica. Proprietary and Confidential.

Key Points
 User should perform the Set-up Applications before doing any code migration of any asset in org.

 User should have "Admin" role and a group assigned.

 Org should be upgraded to latest release from Business 360 before performing Set up Applications.

 All Business 360 processes in the Application Integration chicklet, should be in Published State.

 Create other projects for all additional required assets such as mappings, mapping tasks, task flows or even
other MDM SaaS assets and avoid using OOTB (Business 360, Customer 360, MultiDomain MDM, Reference
360, Supplier 360, Product 360) projects for these assets

 There should not be any permissions set on the OOTB folders in Explorer Tab in B360. (Business 360,
Customer 360, MultiDomain MDM, Reference 360, Supplier 360, Product 360)

5 © Informatica. Proprietary and Confidential.

Data Modelling
 Pivoted data modelling strategy from relational database modelling to more advanced Document database style
modelling to overcome data modelling challenges
 Providing "Out of the Box” Data Models for easier modelling experience
 Introducing “Smart Fields” to provide low effort enjoyable modelling experience
 Enhanced Basic Fields & Field Groups to provide better flexibility
 Bringing in Reference Data Assets for easy Lookups

From Traditional “Relational Database style” To Advanced “Document Database style”

6 © Informatica. Proprietary and Confidential.

 OOTB  Predefined data model that customers can customize to manage their data needs.
Data
 In GA, Providing 2 OOTB Business Entities – Person and Organization
Model

 The idea behind smart field is how can we make the Smart fields Available in GA
modelling experience super easy for a user by freeing
them from worry of choosing data types and need to
Smart
configure validation rules for fields
Fields Postal eMail Phone
Address

Data
Types

7 © Informatica. Proprietary and Confidential.

Key Points
 For Customer 360 a data dictionary can be used as a guide to map source system attributes with MDM
attributes. Please refer KB Article

 Once we have the Data Model finalized and we create respective Assets in the ORG, for any new Business use
cases, we recommend to create a new Assets as part of Data Model.

 Recommend NOT to delete/remove any existing Assets (Business Entity, FieldGroup, Attributes) from Data
Model. That may lead to meta data corruption. Please use disable for now.

 Follow the proper naming conventions while creating the assets, to differentiate between OOTB assets and
custom assets.

Ex: For Custom Attribute: X_<FieldGroupName> or X_<Attribute>

FAQ KB FAQ-SAAS-Data-Model-for-OOTB-BE-s?

8 © Informatica. Proprietary and Confidential.

SDLC Asset Migration
Assets are as follows :-

1. Business Entity and all customizations within it which includes –

• Custom fields, field groups , smart fieldgroup instances
• Light weight DQ rules, Advanced DQ rules , DaaS Configurations
• Match Rules and Configurations
• Survivorship Configurations
• Search Configurations.
2. Business Application
3. Pages
4. Components
5. Job definitions
6. Source System
7. Business Event definitions
8. Reference Data Set and crosswalk configuration (Code Lists- Enterprise and Custom)
9. Hierarchies
10. Custom BE
11. Relationships
12. Authorization Configuration (Custom Roles with IICS and MDM Privileges)

9 © Informatica. Proprietary and Confidential.

Key Points
 SDLC to be performed between same modelled versioned orgs.
 Before import of assets into target org, take an export of target assets which in turn can be used to import
back during any failures.
 Move assets into target through SDLC
 Don’t make breaking changes from R360 like Renaming RDA, deleting RDA which would create
inconsistency in C360
 Admin Role to be used for SDLC of Authorization asset which will export roles and associated IICS and
MDM privileges.
 For first time movement of assets between orgs- If Admin user is being used for SDLC then entire projects
can be selected and exported which will in turn take care of Assets import in particular order including
Authorization and Business Events.
 If Designer and MDM Designer roles are used make sure all assets are exported and imported first
excluding Authorization asset and Business Events. Post successful import of other assets Authorization
asset can be exported and imported using Admin role and at last Business Events can be exported and
imported.
 9. Use same level of roles to make changes in source and also to perform SDLC.
 For ex: If user with Admin role is being used to make changes, make sure user with Admin role is used to do SDLC.
Same goes with user mapped with Designer + MDM Designer roles. When changes are done with Admin and for
SDLC if Designer +MDM Designer roles get used very high probability of hitting into errors like protected metadata.

Note: SDLC of MDM Assets works on GUID, whereas SDLC Of RDA works on Name.
10 © Informatica.
© Informatica.
Proprietary
Proprietary
and and
Confidential.
Confidential.
Secure Agent
 DIS service heap space. Need to increase if we see java heap space
related message at :
• Test connection
• Metadata fetch
• Agent logs(tomcat logs or tomcat out)
• Designing mapping

 DTM - If you hit java out of memory or java heap error messages at run
time of a mapping task execution(observed in session log), then
memory attributes need to be defined as JVMOptions under DTM.
• Need to defined under JVMOption like under JVMOption1,
JVMOption2 and so on.
• Each JVMOption parameter accepts one JVM parameter only.
• JVMOption5 is the last default one, custom property under Type
DTM and subtype INFO can be added to add further JVM
parameter.
• -Xmx****m can be added with required value.


11 © Informatica. Proprietary and Confidential.
Contd..
 maxDTMProcesses Custom Property
 By default, a Secure Agent can schedule only two mapping tasks for execution.
 Additional tasks are queued and becomes eligible for execution when slot is free.
 Better CPU utilization and higher degree of concurrency.

 Recommended value is 0.75 of the number of CPU cores on SA machine.

 Guidelines when setting this property value :

• Do not exceed the terms of your license agreement.

• Setting property value > No. of CPU can increase parallelism but can cause performance bottlenecks
in execution time.

12 © Informatica. Proprietary and Confidential.

Contd..
 DTM Buffer Size

DTM Buffer size holds the actual data in blocks for processing.
DTM Buffer size is automatically calculated based on Buffer block size.
DTM Buffer Size = (DTM Buffer Block Size) * 10* N, where N is the number of partitions.
Can be increased to increase number of blocks.

 DTM Buffer Block Size

Generally calculated as 2*X, where X is the maximum row size of any

transformation

13 © Informatica. Proprietary and Confidential.

Ingress
 Business 360 FEP connector is recommended connector to Ingress data.
 Less computing requirement at SA machine.
 Simplified logic of mapping.
 Parallel execution.
 Joining parent and child data complexity is taken care at Cloud server.

 Business 360 Hierarchal connector is not recommended for higher data loads
 More computing requirements at SA machine.
 Requires joining parent and child data at SA side using mapping logic.
 Not scalable for higher data loads.
Refer KB
https://knowledge.informatica.com/s/article/FAQ-Difference-between-Business-360-connector-Business-360-FEP-con
nector?language=en_US&type=external

 SourcePkey length should not exceed 255 bytes.

 May cause source pkey truncation.
 Transform step failures.

14 © Informatica. Proprietary and Confidential.

Contd..
 Multibyte data loading requires performing below :

 Set the INFA_CODEPAGENAME = UTF-8 in the Custom Configuration Details of the Secure Agent
 Source and Target connection code page is set to UTF-8.
 LC_LOCALE, LC_ALL to en_US.UTF-8 for Unix machine.
 INFA_CODEPAGENAME=UTF-8 environment variable Windows machine.

Refer KB:
https://knowledge.informatica.com/s/article/Multibyte-characters-not-loading-properly-with-Ingress-when-using-B360
-connector?language=en_US

 SourcePkey field name contains only alphanumeric characters and the following special characters:

.~!/'={}|:@#$^&*()-_+,<>?`

• Ingress from July release, B360 connector by default connects to Mongo via datastore service. Whitelisting of MDM
Static IP to be done if domain specific whitelisting not allowed.

 Characters like tab \t should not be part of Pkey as that’s not valid and cause parsing issue.
It should be escaped in the mapping logic(if CDI used) or cleanse such character from pkey at
the source side.

15 © Informatica. Proprietary and Confidential.

Contd..
 CDI taskflow goes into suspended state when underlying mapping task fails with error. This
causes MDM side B360 Ingress job to remain in Running state at Extract step.

Happens due to Data Task ->Error Handling -> Suspend Taskflow radio button checked.

Two options available to fail the taskflow when underlying mapping task fails :

1. Under Data Task -> Advanced -> “Suspend on Fault” checkbox is unchecked.

Under Error Handling -> On Error “Ignore” option -> Fail task on completion “if
this task fails”

Cons: All other Data task in taskflow will also be executed before marking
taskflow as failed.

2. Under Data Task -> Error Handling -> Custom Error Handling.
This will create a new pipeline in that step. Add Throw step to that pipeline.

Or if Throw step is not added, connect pipeline to End however Fail task on
completion “if this task fails” checkbox to be checked.

As soon as throw step executes, no other Data task will be executed and
taskflow fails when this data task fails.

16 © Informatica. Proprietary and Confidential.

Egress
 Web Service response Cache size. Value should be set to maximum record size document
available.

 Setting it too low value can result in Data Truncation.

 Setting it too high  impact buffer size calculation, performance and memory utilization.
 Request GCS to get the document size once data is ingressed to get approx value.

 During mapping design, check precision of input ports. Default 255 for all columns, decrease and
set it based on data.

 Consider mapping of only required input fields to further transformation.

 Joiner and Aggregator if used in mapping logic, please consider using sorted input. Sorter
transformation based on keys used in before Joiner and Aggregator.

 Enough disk space for Joiner, Sorter and Aggregator.

 FEP connector is not supported yet for Egress. B360 Hierarchal connector to be used.

 Egress filtering based on data at source is not available. Logic to filter based on data to be
implemented in CDI mapping logic.

17 © Informatica. Proprietary and Confidential.

Relationships & Hierarchies
 Create a sperate mapping and mapping to create Hierarchy Instance, Root Record and relationship
using FEP connector. Invoke all the mapping task in one taskflow.

 Not recommended to use Hierarchal connector for Hierarchy assets import as creating root in
existing instance has issues.

 Relationship pkey used should be unique for creating relationship between 2 entities.

 Relationship import is possible only through Entity 1 and Entity 2 sourcePkey while using CDI
Ingress and IFI support. Using Entity 1 and Entity 2 BusinessID is not supported.

 IFI doesn’t support creating relationship between 2 Entities across different source system.

18 © Informatica. Proprietary and Confidential.

UI Configuration - Application & Pages

19 © Informatica. Proprietary and Confidential.

Reports
 User can be able to create a maximum of 100 Reports per solution.
 User creating the report should have the mentioned roles (Admin, Customer360 Data Steward, Customer360
Manager, MDM Business User, Customer360 Analyst, Designer)
 If the user won’t select configure Chart and directly click on save, then the user can’t add a report to the dashboard it
will be added in the reports table.
 Only Admin role user can Schedule Reports.
 Users can add one Dimension, maximum of five measures and at most 6 dashboards only.

20 © Informatica. Proprietary and Confidential.

Reference 360 SDLC
 Reference Data Asset/Codelist to be used within BE data model can be created in SaaS MDM (B360 console) or
Reference360 UI.

 Extending the reference data asset/codelist (along with any other subsequent metadata changes) such as creating
additional attributes within RDA/Codelist, adding description etc. should be done via Reference360 UI.

 Reference Data Asset/Codelist used in SaaS MDM, must be exported via B360 console a.k.a. SDLC. Note that there is
no specific step is needed to export Codelist metadata, and exporting BE and its dependencies will be sufficient .
Exported assets must be imported via SaaS MDM (B360 console). If there are additional attributes use V3 APIs

 Note that with SDLC we are just importing metadata, so code values will not be exported/imported.

21 © Informatica. Proprietary and Confidential.

Reference 360 Data Import & Export
 Loading/Addition of RDA(codelist) values ( a.k.a. Lookup values) can be done in ( typically done in First
Environment)
 Via API to add data into RDA values
 Via Reference360 UI
 Via Batch Job via Reference360 UI
 Via File Import in R360 with source system "rdm.system.default" selected.
 Export code values from a source Env
 Via Reference360 UI
 Via Egress job from Reference360 UI
 Import Code values into a target Env in bulk
 Via Reference360 UI
 Via Batch Job via Reference360 UI
 Updates to Reference data ( Code values ) will not update existing MDM BE records data where the code values are
already part of. For new MDM BE records and updated MDM BE records will see updated lookup data but existing
read on records will keep seeing old lookup value

22 © Informatica. Proprietary and Confidential.

23 © Informatica. Proprietary and Confidential.
Thank You