Table of Contents

Search

  1. Preface
  2. Introduction
  3. Configuring the Data Director Application
  4. Establishing a Root Node
  5. Defining the Business Entity Model
  6. Configuring Business Entity Properties
  7. Configuring Reference Entity Properties
  8. Transforming Business Entities and Views
  9. Configuring Hierarchy and Network Relationships
  10. Creating Match Rule Sets
  11. Configuring Search
  12. Configuring Tasks
  13. Configuring Security and Data Filters for Business Entities
  14. Integrating Data as a Service
  15. Configuring External Calls
  16. Designing the Data Director User Interface
  17. Localizing Data Director
  18. Appendix A: Provisioning Tool Frequently Asked Questions

Transforming XML Data to Business Entity

Transforming XML Data to Business Entity

To use the DaaS services, you must define the mappings for the response that the service returns. Map the fields in the response to the business entity fields. Specify which fields from the XML output of the service you would like to store in your business entity.
  1. Click
    Business Entity
    Transformations
    , and then select
    XML to Business Entity
    .
  2. Click
    Create
    .
  3. In the properties panel, specify the following properties:
    Property
    Description
    Name
    Name for the transformation.
    URL
    Identifies the namespace where the SOAP operation is defined.
    Type
    Select the namespace.
    Business Entity
    Business entity you want to transform.
    Expose As Service
    If set to true, the transformation is exposed as two business entity services, Import and Update. These services accept XML data, transform it into business entity data, and save it as a business entity record.
    Source
    Element in the response object. Click the
    Browse
    button to search for the element.
  4. Click
    Apply
    .
    The following image shows a sample XML data to business entity transformation: A screenshot showing sample XML data to business entity transformation.
  5. To configure the transformation for the root node, select
    Transformations
    in the tree view panel, and then click
    Create
    .
  6. In the properties panel, specify the following properties:
    Property
    Description
    Name
    Name for the transformation. For example, transformation for root.
    Status Output
    Name of the cleanse output parameter. Used in cleanse transformations. Not applicable to transformations for DaaS.
    Status Success
    A regular expression. When the cleanse operation successfully completes, it returns a value in the cleanse output parameter that matches the regular expression. Not applicable to transformations for DaaS.
    Type
    Type of transformation to directly map data from a business entity field to the XML. Direct transformations keep the data unchanged.
  7. Map the XML elements in the service response to the business entity fields:
    1. In the
      Input Fields
      column, click the
      Browse
      button.
    2. Select the field, and then click
      Select
      .
    3. In the
      Output Fields
      column, click the
      Browse
      button.
    4. Select the business entity field to which you want to map, and then click
      Select
      .
    5. To map additional information, click the
      Add
      icon, and then follow steps
      a
      to
      d
      .
    6. Click
      Apply
      .
    The following image shows a sample mapping of fields for the root node:
    A screenshot showing the mapping of XML and business entity fields.
  8. To configure the transformation for child nodes of the business entity, add the node to a group, and then configure the transformations:
    1. Select the
      Groups
      folder, and then click
      Create
      .
    2. In the properties panel, enter a name for the node as you want it to appear in the group folder.
    3. In the
      Source
      field, select a field, and in the
      Target
      field, select the child node in the business entity. Repeat for each child node.
    4. Click
      Apply
      .
    5. Expand a
      child node
      , select
      Transformations
      , then click
      Create
      .
    6. In the properties panel, enter a name for the transformation.
    7. From the
      Type
      list, select
      Direct
      .
    8. In the
      Input Fields
      column, click the
      Browse
      button.
    9. Select the field, and then click
      Select
      .
    10. In the
      Output Fields
      column, click the
      Browse
      button.
    11. Select the business entity field to which you want to map, and then click
      Select
      .
      You can specify Service Data Object (SDO) XML path directly in a
      field
      attribute. When a field contains
      /
      , it indicates the XPath of the SDO. If you use a cleanse transformation before you populate the business entity with the XML data, you might require some parent XML elements in the child node mappings. However, parent XML elements are not available for selection in the transformation of child nodes. You must manually type the path to the required parent XML element in the
      Field Name
      . Use the Service Data Object (SDO) XPath expression to access a parent element, where
      /
      represents the root element. For example, when you configure the transformation of the address child node, you might concatenate the
      dunsNumber
      element with the
      city
      element. Because the
      dunsNumber
      element is a parent element, it is not available for selection. To access the
      dunsNumber
      element, use the path
      /OrderCompanyProfileResult[1]/ServiceResult[1]/OrderProductResponseDetail[1]/InquiryDetail[1]/DUNSNumber[1]
    12. Repeat Steps
      h
      to
      k
      for other fields.
    13. Click
      Apply
      .
  9. Repeat Step
    9
    for each child node.
    The following image shows a sample transformation and mapping of fields for a child node:
    A screenshot showing the mapping of XML fields to business entity fields for the child addr.

0 COMMENTS

We’d like to hear from you!