Table of Contents


  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

Step 1. Create a Service Connector

Step 1. Create a Service Connector

Use the Process Designer to create a service connector that specifies parameters to connect to services and data sources.
  1. Log in to Informatica Intelligent Cloud Services, and select
    Application Integration
  2. Click
    . The
    New Asset
    dialog box appears.
  3. Click
    Service Connectors
    , and then click
  4. On the
    tab, define the following basic properties for the service connector.
    • Name by which the service connector is made available for processes.
    • Project or folder to contain the service connector.
    • Description for the service connector.
    • Indicate whether the service connector must only be available to run on the Secure Agent.
    • Properties required to connect to this service.
    The following image shows the
  5. On the
    tab, define the actions associated with the service connector.
    For more information about actions, see the
    Informatica Cloud Application Integration
  6. On the
    tab, define the input variables that are unique to the service to which you are sending data.
    For more information about input variables, see the
    Informatica Cloud Application Integration
    The following image shows the
  7. On the
    tab, define the following properties for each action in the service connector:
    • URL. URL of the Get Metadata or Search Business Entity REST web service.
      The Get Metadata URL has the following format:
      http://<host>:<port>/<context>/<database ID>/<business entity>.json?action=meta
      The following sample URL gets the metadata of a business entity or business entity view in the MDM Hub:
      The Search Business Entity URL has the following format:
      http://<host>:<port>/<context>/<database ID>/<business entity>.json?fq=<business entity field name>='<business entity field value>'
      In the Search Business Entity URL, you can use only the MDM Hub Smart Search fq query parameter and the AND logical operator.
      The following sample URL searches for records that have the last name as Joe:
    • Verb. Method to run the REST web service.
    • Multi Using. Determines how query string parameters are generated when you need to specify multiple values for a parameter.
    • Authentication. Authentication credentials to access the MDM Hub data sources.
    • Other Parameters. Input parameters required by the service.
    • HTTP Headers. If the service requires one or more HTTP headers, enter the name and the value of the parameter for each header.
    The following image shows the
  8. On the
    tab, define how the service connector parses data returned from a service and places it into variables. Specify the following properties for each output data item:
    • Name. Name of a variable into which a returned value is placed.
    • Type. Data type of the value written to the variable.
    • Description. Description of the variable.
    • Get From. Select one of the following:
      • Property. To enter a named value (which is the name used within the XML returned by the service) to be placed within the variable.
      • Expression. To parse the MDM Hub JSON response to the output variable.
        Use the following sample code to parse the response:
        { $RESTResponse/rest:metadata/text() }
      • XQuery. To write an XSLT expression to parse the XML returned by the service.
      • HTTP Response Header. To enter the part of the response header to assign to the field.
      • HTTP Response Status Code. To check the HTTP response status code.
      • Entire Response. To assign the complete contents of the response payload to the field.
      • Simplified XML. To rearrange data that can be used by process objects.
    The following image shows the
    For more information about the
    tab, see the
    Informatica Cloud Application Integration
  9. Save the service connector.
  10. On the
    Test Results
    tab, select a test server, and click
    The test result appears.


We’d like to hear from you!