...
The agent communicates with the billing system using SOAP over HTTP. In order to retrieve responses from the billing system, a separate service needs to be configured for the Execution Context. For further information, see the section below, Preparations. This service is shared by all RTBS agents running on the same EC.
Preparations
When installing the RTBS agent for the first time, properties must be added to configure the ECs.
For each Execution Context that the RTBS workflows will execute on, two Execution Context properties for callback has to be added to the relevant pico configuration files:
Callbackhost, defines the name or IP address of the interface that should receive responses from the machine hosting the EC.Code Block language text theme Eclipse mzsh topo set topo://container:<container>/pico:<pico name>/val:config.properties.rtbs.callbackhost <ip address>
Callbackport, defines the port that responses should be sent to.Code Block language text theme Eclipse mzsh topo set topo://container:<container>/pico:<pico name>/val:config.properties.rtbs.callbackport <port>
Startup the ECs:
Code Block language text theme Eclipse $ mzsh startup <ec> <ec>
Transaction Overview
Asynchronous Request
The RTBS agent (Parlay) uses both synchronous and asynchronous requests. It is important to understand the differences between them, since it affects the requirements on the business logic in the workflow.
...
For a list of requests and the category that each of them belongs to, see the section below, Request/Response Mapping. Basically, UDRs ending with Req represents an asynchronous request and UDRs starting with Get represents a synchronous request.
Request/Response Mapping
The RTBS agent contains a number of different UDRs. The UDRs in turn contain a set of fields corresponding to the fields required by the billing system. The UDRs also contain a few internal fields that can be used by the workflow logic.
There are also additional types that the agent provides, which are used to populate the request and response. These data types are prefixed Tp.
RTBS Related UDR Types
In the UDR Internal Format Browser a detailed view of the available fields is displayed. To open the browser, click the menu and select the option and then right-click in the editing area and select the option UDR Assistance... .
...
| Other Request | Other Error |
| ReleaseSession | N/A |
| Allows the workflow to tell the agent that an ongoing RTBS session should be released, normally not needed since the billing system will manage this. | |
| Any request | RequestException |
| Error that can be sent from the agent whenever an abnormal error has occurred. | |
| Any request | SessionAborted |
| Possible response from the billing system if an ongoing session must be aborted, e g, when a session has been idle for some time. |
Error Management
The agent will, to the extent possible, manage errors without aborting the workflow. Errors related to the communication between the agent and the billing system are sent to the system log and routed into the workflow via the RequestException UDR where the two fields errorMessage and errorDetails contain the details of the error. The RequestException type is also used for invalid requests detected by the agent. Other errors are only written to the System Log.
...