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
- Create two threads,
json_in
andjson_out
. - Configure the protocol properties of each thread to comply with each JSON endpoint.
- Configure JSON as Trx ID
determination. Alternatively, you can select UPoC for custom Trx ID on the
json_in
thread. - Configure a static route with Raw translation between
json_in
andjson_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:
- Create two JSON message models using the JSON record layout tool:
- json_in.json
- json_out2.json
- 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.
- Configure the translation to convert the data from input to output. Operations such as BULKCOPY and PATHCOPY are supported.
- Create a new thread
json_out2
. - Configure the protocol properties of
json_out2
to comply with the endpoint. - Add a new route to the json_in
thread, routing all data to
json_out2
using the json.xlt translation.