Messaging Infrastructure

The messaging concept should be implemented in every backend process that is run from the UX. You may use provided snippets to add messages output to your TI process. It is important to know how the messages are formulated into a JSON string and how are they stored in TM1.

Storage in TM1

The messages are stored in }APQ Process Response Message cube. The cube allows to store process parameters, start time, finish time, status, success or failure message (simple string evaluating the process run overall) and JSON message with all message details. In case of error the record contains a link to a process error file.

It is important to note the cube can store one record per each process and user. Therefore, if the process is running in parallel, the }APQ Process Response Message cube will only contain a record that aligns with the main process that initiated child threads. The responses of the child threads will be captured in the }APQ C3 Thread Control cube for each thread, including main process (always represented by thread 0). From there, the responses will be consolidated into a single message in the }APQ Process Response Message cube by the main process. The }APQ C3 Thread Control cube is used not only to capture child thread messages, but it is used to synchronize the child threads to the main process, so the main process is able to wait till all its child threads have finished.