Page History
...
When operating services on an E2E a Bridge, it might happen that unexpected errors occur. In such cases, as a rule the system should respond on such incidents, for example send a message to the system administrator. The built-in monitoring feature gives you a global monitoring functionality, which can catch failure events for any service running on the Bridge. Such events can be errors that were not caught within a service and are written to its Bridge server log, a service that terminates unexpectedly or an adapter call that does not return within a given length of time. The monitoring is defined globally for all deployed services and is not set up for a single service only.
...
After you have deployed the monitoring service to the Bridge, you need to register it with the E2E Bridge at the node preferences page. For that purpose, you have to define the SOAP URL of the monitoring service. Usually, the SOAP URL of the monitoring service is http://<hostname>:<port>/<package name(s)>/<E2ESOAPPortType>.
Figure: Node Instance with Monitoring Service Registered
Actually, it is even possible that the monitoring service fails. Thus, a fallback monitoring service can optionally be specified in field Monitoring SOAP URL Fallback. This fallback service can even run on another Bridge.
...
Overview
Content Tools