This graphic illustrates how network-triggered Transaction Units are logged and handled by a Services Gatekeeper custom module. Your custom module uses its own interface and requests for this communication. The communication happens in this order:

  1. The network first sends a request to the network-facing tier of Services Gatekeeper custom module.

  2. The Services Gatekeeper custom module forwards the request to the application.

  3. The application returns a message to the Services Gatekeeper custom module.

  4. Services Gatekeeper logs the Transaction Unit.

  5. The Services Gatekeeper custom module sends a response message to the network node.