Business 360 Events Connector > Mappings for Business 360 Events Connector > Mapping example
  

Mapping example

An organization uses Customer 360 to create and manage customer records. When records are created, updated, or deleted, the organization wants these events published to a Cloud Data Integration target, such as Amazon S3. You create a mapping to read these events from Customer 360 by using Business 360 Events Connector and publish the events to Amazon S3.
    1In the Business 360 Console, create a publishing event.
    2Create a Business 360 Events connection.
    3Create a connection to the target, Amazon S3.
    4Create a mapping.
    5Add a Source transformation, and specify a name and description in the general properties.
    6On the Source tab, perform the following steps:
    1. aIn the Connection field, select the Business 360 Events connection.
    2. bIn the Source Type field, select Single Object.
    3. cIn the Object field, select the source object from which you want to publish events and the default handler.
      4. The source object is the publishing event that you create on the Business Events page of the Business 360 Console.
      The following image shows the source publishing events:
    7Add a Target transformation, and specify the name and description in the general properties.
    8On the Incoming Fields tab, review the incoming fields.
    The incoming fields are the same as the source fields, _id, handlerData, and timestamp.
    9On the Target tab, perform the following steps:
    1. aIn the Connection field, select the connection to the target, which is Amazon S3.
    2. bIn the Target Type field, select Single Object.
    3. cIn the Object field, select the target object to which you want to publish events.
    10On the Target Fields tab, specify the target field properties.
    11On the Field Mapping tab, select and map the relevant incoming fields to the target fields.
    Map the handlerData incoming field to the data target field to publish the event data using a publish events job. The handlerData field contains the event data.
    The following image shows the incoming fields on the left pane and the target fields on the right pane:
    12Go to the Parameters panel and add the following parameters in the In-Out Parameters section:
    The input-output parameter is internally mapped to the start time and the end time of the business event publishing job. When you run the job, the Cloud Application Integration process passes the job start time and end time to the input-output parameter in Cloud Data Integration. Based on the defined taskflows, the job is executed. If you do not define the input-output parameter for the Target transformation in Cloud Data Integration, your job fails.
    The following image shows the input-output parameter dialog box:
    13Save the mapping.