System maintenance

Monitoring

Monitoring

Note: The monitoring of the iPaaS system is the responsibility of SEEBURGER. The monitoring of the processes within the iPaaS workflow is in your responsibility.

SEEBURGER provides an automatic real-time monitoring which is available 24/7. The standard monitoring checks are configured during the provisioning of the iPaaS system, the custom process monitoring checks are configured during the Go-Live period.

    The SEEBURGER monitoring system covers the following areas:

  • Monitoring of the core components of the iPaaS platform: network components, data base and server environment, and applications operated by SEEBURGER

  • Monitoring of the KPIs for performance and availability

    > Accounting and reporting

  • Evaluation and management of events triggered by the monitoring system

An automatic monitoring check is implemented on the iPaaS system which monitors for error events. An error event triggers the event management. In the event management, events are evaluated and aggregated. The event management decides if an incident is created in case of system errors or the event can be ignored.

If necessary, incidents are created in the SEEBURGER Service Desk. Here, the incidents are analysed and the system errors are resolved. You are informed via email about the incident and its solution.

    Categories for notifications on system errors can be:

  • Availability

  • Backend system availability (network)

  • Availability of the external communication interface

  • General service performance

In case of process errors, events are aggregated as well. You get an alert via email, and you are responsible for resolving the error.

Information: Besides of the error alerts, the monitoring system also sends important maintenance information via email. For these purposes, you need to provide an email address to which these notifications can be sent.

We recommend to use a generic address, e.g. the email address of your helpdesk and not the email address of a single person.

    Categories for alerts on process errors can be:

  • Processing rules are missing

  • Communication errors

  • Conversion errors

  • Stopped processing (pause)

  • Long running processes

You can find an explanation of processing errors in your B2B Packaged Solution user manual.

You can find user manuals for the BIS Front End and the B2B Packaged Solution in the app Documentation in your BIS Portal. Search for the manuals Front-end/B2B Sol. Documentation.

Note: After a downtime/maintenance, you have to check the system for stopped processes and continue the necessary processes. In addition, you might need to inform your trading partners after such downtimes to check their outbound processes.

Find more information here:

> Process monitoring via BIS Front End

> Process monitoring via Message Tracking