Table of Contents

Search

  1. Preface
  2. Introduction to Informatica Cloud MDM - 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 CC360
  7. Managing Duplicate Records
  8. Consolidating Records
  9. Converting External Records to Salesforce Records
  10. Managing Hierarchies
  11. Integrating Cloud MDM - Customer 360 for Salesforce with Multidomain MDM
  12. Managing Multi-Org
  13. Custom Settings
  14. Glossary

Step 1. Create a Service Connector

Use the Process Designer of Informatica Cloud to create a service connector that specifies parameters to connect to services and data sources. The binding for the service connector action tells the REST service what request you want to send.
  1. Log in to Informatica Cloud.
  2. To open the Process Designer, from the
    Design
    menu, select
    Service & Process Design
    .
  3. On the
    Design Home
    page, click
    New
    Service Connector
    .
  4. On the
    Definition
    tab, enter a name and description for the service connector..
  5. Optionally, define tags to logically group service connectors and other objects such as connections and processes.
    The following image shows the
    Definition
    tab:
    In the Definition tab, you can enter the name and description for the service connector. You can also enter the connection properties required to connect to the service.
  6. Click the icon to enter the following connection properties required to connect to the service:
    Name
    Name of the property.
    Test With
    The fully qualified domain name or the IP address of the machine that runs MDM Multidomain Edition.
    Type
    Data type of the value that you entered in the
    Test With
    field.
  7. Click
    Actions
    .
  8. On the
    Action
    tab, enter an action name.
    The following image shows the
    Action
    tab:
    You can configure the Input, Binding, and Output settings in the Action tab.
  9. On the
    Input
    tab, define input variables that are unique to the service to which you are sending data.
    You can configure the following settings for each input data item:
    • Name. Name of the input data item.
    • Label. Name of the item to display within a process.
    • Type. Data type of the item.
    • Required. Indicates that a value is required for the parameter.
    • Description. Description of the input parameter.
    • Parameter. If selected, the service connector passes this parameter to the service. If the parameter is only used when constructing another parameter and does not need to be passed to the service, clear this field.
    • Test with. Process Designer uses the Test with value to test the action.
  10. On the
    Binding
    tab, configure the following fields:
    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:
    http://10.65.112.181:8080/cmx/cs/orcl-CMX_ORS/SA_Emp.json?action=meta
    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
    :
    http://10.65.112.181:8080/cmx/cs/orcl-CMX_ORS/SA_Emp.json?fq=lastName=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.
    You can select one of the following options:
    • Semicolon separated. For a semicolon-separated multiselect list, Process Designer adds input parameter values as a single string. Default.
    • Comma separated. For comma-separated multiselect list, Process Designer adds input parameter values as a single string.
    • Append brackets. For a semicolon-separated multiselect list, Process Designer maps semicolon-separated values to multiple query parameters of the same name, and appends
      []
      to the parameter name.
    • Append numbers. For a semi-colon separated multiselect list, Process Designer maps semicolon-separated values to multiple query parameters of the same name and adds a number to the end of the field name, that is,
      1..N
      .
    Authentication
    Authentication credentials to access the MDM Hub data sources.
    HTTP Headers
    If the service requires one or more HTTP headers, enter the name and the value of the parameter for each header.
    To define a SOAP-based service connection, you must add both the "SOAPAction" and "Content-Type" headers. The value of SOAPAction can be empty, dynamically set using GET, or defined in the WSDL.
    The following image shows the
    Binding
    tab:
    You can specify the interface and parameters required to communicate with a service in the Binding tab. You can configure binding properties such as URL, Verb, Multi Using, and Authentication.
  11. On the
    Output
    tab, define how the service connector parses data returned from a service and place it into variables.
    You can configure the following settings 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. You can select one of the following options:
      • 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 so it can be used by process objects.
    • Test with. Process Designer uses the Test with value to test the action.
    The following image shows the
    Output
    tab:
    You can configure settings for each output data item in the Output tab. You can configure settings such as the name, type, and description.
  12. Click
    Save
    .
  13. To test the service connector design, click
    Test
    .
  14. To view the test results, click the
    Test Results
    tab.
    You can view the process objects defined for the service connector.

0 COMMENTS

We’d like to hear from you!