1. Babelway
  2. Babelway User Guide
  3. Chapter 3. Monitor

3.2. Gateway Status

This page will list all the gateways that could potentially have runtime problems, in the sense that : 

  • The configuration of the gateway is valid (and for this reason, the gateway could be deployed).
  • But anyway, the gateway is currently having problems to fully achieve its task.

These gateways are typically gateways that needs to connect to some external systems, because these systems can be (temporarily) unavailable, or could refuse the calls for any reason (like invalid credentials). 

In details, this page will list all the following gateways : 

  • Poller gateways IN (ex: FTP client, HTTP client, ...). These gateways needs to connect to some external system at predefined intervals to retrieve messages, rather than passively waiting for messages to arrive. They can fail from time to time due to some temporary problems (network issue, or remote host temporary down) or even for some permanent problems (ex: credentials wrongly configured).
  • Peppol gateways IN. These gateways will act as servers to receive the messages : they will not actively connect to some other system, but wait that the senders connect to them and transmit the messages. But prior to this, they need to register the participants on the Peppol network, so that anyone wanting to send a message to such a participant knows that we are the server to which it must be sent. It can happen that problems occur during this registration (for example because the participant is already registered by another provider, and we can not take it over) or simply that this registration takes a few minutes to be effective.

It must be noted that this page will only list gateways IN, and not the equivalent OUT gateways. These gateways OUT can also have similar problems (like invalid host or credentials), but these errors will always occur on a specific message. For this reason, the delivery errors will always be reported directly in the message, that will be set in error with a clear message indicating the delivery problem. We will only consider that the status of the gateway is problematic, and mention it here, for gateways that have runtime problems without that they can be related to any message.

 

This page will list all the gateways listed above, and provide a comprehensive overview of their current statuses. The status will be 'Success' if everything works perfectly, or 'Failure' if any anomaly has been detected. Failure doesn't mean that the gateway is not working at all, but that there is at least one problem. For example, a Peppol gateway IN could be configured to manage 10 participants, with 9 being fully ok, and 1 that we can't register. Such a gateway will be indicated here with a problematic status.

 

When the user clicks on a gateway in the table, an overlay will be shown with all the details available.

 

Peppol gateways

For a Peppol gateway, the status will like this : 

Here are the most common problems, and how you can fix them : 

  • Registration in progress.
    You just deployed a new participant, and the process to register it is still running. You should just wait until the process is finished. It should never last more than a few minutes.
  • Registration of our SMP requested in the SML, but doesn't seem to be effective yet. Participant is currently not registered (waiting to be to eu1-smp.babelway.net).
    We just registered successfully as your Peppol provider for the participant (in the SML). But it can take a few minutes before the info is propagated everywhere (due to some caching). Everything should be ok in 5 minutes.
  • SMP is not ours (smp.codabox.com instead of eu1-smp.babelway.net), and not pointing to us (PEPPOL_BIS3_INVOICE_EN16931_V2_1 : https://peppol.codabox.com/peppol/as4).
    This message means that we could not register Babelway as your Peppol provider for this participant (in the SML), because this participant is already registered to another provider. In that case, you should contact this provider and ask him to unregister the participant.
  • Insertion/update/deletion in Peppol directory requested, but not yet effective.
    We have requested a change for the publication of the participant in the Peppol Directory, but this change is not yet visible. First of all, it is important to remind here that publications in the Peppol Directory are only targeting humans searching for participants, but will not affect in any case the sending or reception of your messages. Also, it is very common that Peppol Directory takes a lot of time before publishing the requested changes (up to 1 day). For these reasons, you should not worry and probably just wait until the publication is effective. Contact Babelway support if this message remains like this for more than 1 or 2 days.
  • Peppol directory registration requested from 2 gateways (123456 and 234567) with conflicting names ('My nice company name' vs 'Test')
    The participant is managed by 2 different gateways, with each one supporting different document types (ex: 1 gateway for invoices, and 1 for orders). But in both gateways, you asked us to publish the participant to the Peppol Directory, but providing different names. This can't be accomplished, as the participant can only be published once, with a single name, hence the error. If you don't need one of the gateways (maybe it was a test), just undeploy it. If you still need both, change the name of the participant, so that it is equal in both configurations.

 

 

Poller gateways

For a poller gateway, it will show additional infos like when the last poll was done, when the next poll will be done, or all the downtime periods. You will also be able to trigger an immediate poll, or export all the downtimes history (if you need more than the last 10 displayed on the screen).