Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Customer 360 for Salesforce Summer 2023
  • All Products

Table of Contents

Search

  1. Preface
  2. Introduction to Informatica Customer 360 for Salesforce
  3. Configuring the Data Cleansing Settings
  4. Managing Batch Jobs
  5. Verifying Addresses, Email Addresses, and Phone Numbers
  6. Synchronizing Salesforce Records with Customer 360 for Salesforce
  7. Managing Duplicate Records
  8. Consolidating Records
  9. Converting External Records to Salesforce Records
  10. Managing Hierarchies
  11. Integrating Customer 360 for Salesforce with Multidomain MDM
  12. Managing Multi-Org
  13. Troubleshooting
  14. Appendix A: Custom Settings
  15. Appendix B: Glossary

Administrator Guide

Administrator Guide

Back Next

Step 3. Creating a Search Connection

Step 3. Creating a Search Connection

A search connection acts as a channel through which you can search for data or import data from MDM Hub. The search connection uses the search parameters to create a connection between
Customer 360 for Salesforce
 and MDM Hub.
  1. From the
    Setup
     section of the
    CC360 Admin
     tab, click
    Run the Setup Wizard
    .
  2. In the
    Service Setup
     section, click
    Multidomain MDM
    .
    The
    Service: Informatica Multidomain MDM
     page appears.
  3. To create a search connection, click
    New Search Connection
    .
    You can also edit an existing search connection.
  4. In the
    Search Service Information
     section, perform the following tasks:
    1. Activate the search connection.
    2. Configure the following connection details:
      Name
      Name of the search connection.
      User ID and Password
      Authentication credentials to access Informatica Cloud.
      Business Entity/View
      Business entity type of the data in
      Multidomain MDM
       business entity or business entity views.
      Object Class
      Object class used in the matching settings to compare
      Multidomain MDM
       and
      Customer 360 for Salesforce
       records.
      Metadata URL
      URL to access the metadata of the MDM Hub.
      Use one of the following values based on how you deploy the MDM Hub:
      • If the
        Multidomain MDM
         is deployed on AWS, use URL of the Get Metadata REST web service.
        The following URL is an example service URL that gets the metadata of a business entity view in the MDM Hub: 
        http://mdm-nonprod.informaticacloud.com/suenonprod/cmx/cs/orcl-CMX_ORS/SA_Emp.json?action=meta
      • If the
        Multidomain MDM
         is deployed locally, use the service URL from the meta service parent process you published in
        Informatica Cloud Application Integration
        .
        The following URL is an example service URL that accesses the metadata of a business entity: 
        https://ps1w2.rt.informaticacloud.com/active-bpel/rt/MDMDev003-Hybrid-ProcessCloud-Person-Meta
      Search URL
      URL to search for records in the MDM Hub.
      Use one of the following values based on how you deploy the MDM Hub:
      • If the
        Multidomain MDM
         is deployed on AWS, use the URL of the Search REST web service.
        The following URL is an example service URL to search for records in the MDM Hub data sources: 
        http://mdm-nonprod.informaticacloud.com/suenonprod/cmx/cs/orcl-CMX_ORS/SA_Emp.json?fq=
        In the example,
        fq
         is a query parameter of the Search REST web service.
      • If the
        Multidomain MDM
         is deployed locally, use the service URL from the service parent process that you published in
        Informatica Cloud Application Integration
        .
        The following URL is an example service URL to search for records in the MDM Hub data sources: 
        https://ps1w2.rt.informaticacloud.com/active-bpel/rt/MDMDev003-Hybrid-ProcessCloud-Person-Search?icrtInput=
        In the example URL
        icrtInput
         is the input variable defined in the parent process that you created in
        Informatica Cloud Application Integration
        .
  5. Click
    Get Fields
    . Gets the business entity service fields from
    Multidomain MDM
    .
  6. In the
    Field Mapping and Priority Information
    , perform the following tasks:
    1. Map the bean fields to the business entity service fields.
    2. Enable search for the fields.
    3. Assign priorities for each field.
    If you map date or time fields, ensure that you use the following format:
    For Date field.
    <yyyy>-<mm>-<dd>T<hh>:<mm>:<ss>Z
    For DateTime field.
    <yyyy>-<mm>-<dd> <hh>:<mm>:<ss>Z
    For example,
    2014-12-26 10:10:10Z
  7. Click
    Save
    .
    After you save the search connection,
    Customer 360 for Salesforce
     uses the field mapping and the priority information to create synchronization and data source settings for the
    Multidomain MDM
     business entity.
0 COMMENTS
We’d like to hear from you!