Create Mappings

This step is to create mappings between the source and target data structures in the integration. It includes the following three mappings:

  • Map the data for the request message

  • Map the data for the response message

  • Map the data for the fault

Create mappings for the request message:

  1. In the middle of the integration, click the Mapper icon for the request.

    Click Create (the + icon) to display the mapper.


    Description of map_diagram.gif follows
    Description of the illustration map_diagram.gif
  2. Create the mappings between the source and target elements:

    • In the Source section, expand the execute node, then the request-wrapper node, then the PROCESS_ORDER_Input node, and then the InputParameters node.

      Select the P_API_VERSION_NUMBER element.

    • In the Target section, expand the PROCESS_ORDER_Input node, and then the InputParameters node.

      Select the P_API_VERSION_NUMBER element.

    Drag the P_API_VERSION_NUMBER element from the Source section to the P_API_VERSION_NUMBER element in the Target section to map the data.

    Once you complete this step, the mapped source value and the corresponding target element are connected by a green line.


    Description of mapping_request.gif follows
    Description of the illustration mapping_request.gif

    Similarly, use the same approach to complete the mappings for the elements listed in the following table.

    Source Path Source Element Target Path Target Element
    execute/equest-wrapper/ PROCESS_ORDER_Input/RESTHeader Responsibility PROCESS_ORDER_Input/RESTHeader Responsibility
    execute/equest-wrapper/ PROCESS_ORDER_Input/RESTHeader RespApplication PROCESS_ORDER_Input/RESTHeader RespApplication
    execute/equest-wrapper/ PROCESS_ORDER_Input/RESTHeader SecurityGroup PROCESS_ORDER_Input/RESTSecurityGroupHeader SecurityGroup
    execute/equest-wrapper/ PROCESS_ORDER_Input/RESTHeader NLSLanguage PROCESS_ORDER_Input/RESTHeader NLSLanguage
    execute/equest-wrapper/ PROCESS_ORDER_Input/RESTHeader Org_Id PROCESS_ORDER_Input/RESTHeader Org_Id
    execute/equest-wrapper/ PROCESS_ORDER_Input/InputParameters P_INIT_MSG_LIST PROCESS_ORDER_Input/InputParameters P_INIT_MSG_LIST
    execute/equest-wrapper/ PROCESS_ORDER_Input/InputParameters P_RETURN_VALUES PROCESS_ORDER_Input/InputParameters P_RETURN_VALUES
    execute/equest-wrapper/ PROCESS_ORDER_Input/InputParameters P_ACTION_COMMIT PROCESS_ORDER_Input/InputParameters P_ACTION_COMMIT

    Notice that a green check mark icon appears for the element that has a mapping created. Additionally, the mapped data appears in the Mapping column of the Target section.

  3. Once the mapping is complete, click Save to save your work.

  4. Click Exit Mapper.

Create mappings for the response message:

  1. In the middle of the integration, click the Mapper icon for the response.

    Click Create (the + icon) to display the mapper.

  2. Create mappings to map the source and target elements.

    • In the Source section, expand the PROCESS_ORDERResponse node, and then the OutputParameters node.

      Select the X_RETURN_STATUS element.

    • In the Target section, expand the executeResponse node, then the response-wrapper node, and then the Output Parameters node.

      Select the X_RETURN_STATUS element.

    Drag the X_RETURN_STATUS element from the Source section to the X_RETURN_STATUS element in the Target section to map the data.

  3. Use the same approach to complete the mappings for the elements listed in the following table.

    Source Path Source Element Target Path Target Element
    PROCESS_ORDERResponse/OutputParameters/X_MESSAGES/X_MESSAGES_ITEM MESSAGE_TEXT executeResponse/response-wrapper/OutputParameters/X_MESSAGES/X_MESSAGES_ITEM MESSAGE_TEXT
    PROCESS_ORDERResponse/OutputParameters/X_HEADER_REC ORDER_NUMBER executeResponse/response-wrapper/OutputParameters/X_HEADER_REC ORDER_NUMBER

    Description of mapping_response.gif follows
    Description of the illustration mapping_response.gif

    Click Save to save your work.

  4. Click Exit Mapper.

Create mappings for the fault message:

  1. In the middle of the integration, click the Mapper icon for the fault.

    The Fault Mappings dialog appears.

  2. Under the Route To, select "APIInvocationError" as the fault type.

  3. Under Map, click the Mapper (+) icon to create mapping.

  4. Create the mapping between the source and target elements:

    • In the Source section, expand the fault node.

      Select the errorCode element.

    • In the Target section, expand the APIInvocationError node.

      Select the errorCode element.

    Drag the errorCode element from the Source section to the errorCode element in the Target section to map the data.

  5. Use the same approach to complete the mappings for the elements listed in the following table.

    Source Path Source Element Target Path Target Element
    fault reason APIInvocationError/errorDetails instance
    fault details APIInvocationError/errorDetails errorPath

    Description of mapping_fault.gif follows
    Description of the illustration mapping_fault.gif
  6. Click Save to save your work, and then click Exit Mapper.

The mappings for the request, response, and fault are all created successfully.

Click Save to save your work.