JSON use cases

These use cases cover:

  • Raw routing a JSON message from one system to another.
  • Storing a JSON transaction in SMAT.
  • Delivering the translated JSON to a remote endpoint.

Use case 1: To raw route a JSON message from one system to another

  1. Create two threads, json_in and json_out.
  2. Configure the protocol properties of each thread to comply with each JSON endpoint.
  3. Configure JSON as Trx ID determination. Alternatively, you can select UPoC for custom Trx ID on the json_in thread.
  4. Configure a static route with Raw translation between json_in and json_out.

Use case 2: Storing a JSON transaction in SMAT

Enable inbound and outbound saved messages for the json_in thread that was created in the first use case. The JSON data is then written to the SMAT archive.

Use case 3: Delivering translated JSON to a remote endpoint

To translate a JSON message from one system to another:

  1. Create two JSON message models using the JSON record layout tool:
    • json_in.json
    • json_out2.json
  2. Create a translation called json.xlt. Configure the translation to use json_in.json as the input record layout and json_out2.json as the output record layout.
  3. Configure the translation to convert the data from input to output. Operations such as BULKCOPY and PATHCOPY are supported.
  4. Create a new thread json_out2.
  5. Configure the protocol properties of json_out2 to comply with the endpoint.
  6. Add a new route to the json_in thread, routing all data to json_out2 using the json.xlt translation.