Table of Contents

Search

  1. Preface
  2. Understanding Data Types and Field Properties
  3. Designing Processes
  4. Using and Displaying Data
  5. Designing Guides
  6. Designing Process Objects
  7. Designing Service Connectors
  8. Using Connectors
  9. System Services, Listeners and Connectors

2. Design

2. Design

Output Tab

Output Tab

Use the
Output
tab to define how the service connector will parse data returned from a service and place it into variables. Typically, the returned data is XML or JSON converted to XML. You can map this XML to output fields in two ways:
  1. Directly map the data to a property based on XML tag names or JSON properties.
  2. Use
    Expression
    to extract elements.
For example:
For each output data item, specify:
  • Name
    : The name of a variable into which a returned value is placed.
  • Type
    : The data type of the value being written to the variable. If the type is
    objectLlist
    or reference, Process Designer displays a list of Process Objects so you can choose one of the objects defined within the Process Objects tab.
  • Description
    : Text describing the variable
  • Get From
    : 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 write an XSLT expression to parse the XML returned by the service. In the example figure, we use the XSLT
      count
      function to return one value for the
      AllModelsCount
      variable. The expression used for the
      CarMakesList
      returns a list. Click
      ...
      to open an XQuery Editor tab appears where you can type the query.
    • HTTP Response Status Code
      : To check the HTTP response status code.
    • HTTP Response Header
      : To enter the part of the response header to assign to the field. See the details below.
    • 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. For more information, see Simplified XML.
    • Entire Response As Attachment
      : To handle the entire response as an attachment.
      The
      Entire Response As Attachment
      option preserves backward compatibility. If you had created a service connector with a single attachment in a previous release, it will continue to work as is, and no manual changes are needed. However, Informatica recommends that you redesign your service connector to handle multipart responses as multiple attachments so that you do not have to manually split attachments. You can also use the processing logic for attachments within the service connector itself instead of doing it within a process. Therefore, you can use a service connector within multiple processes without having to design the processing logic in multiple processes. You can also use the functions available to work with output attachments.
    • Attachments
      : To work with multiple attachments and pass the entire list of attachments to the selected variable except the part used as the payload.
For details on handling HTTP errors, see Checking for HTTP Errors.