Setup

Creating REST cloudlinks

Creating REST cloudlinks

Note: To create a new cloudlink, you need to have at least 1 B2B Directory entry.

> Creating new B2B Directory entries

To create a new REST cloudlink, follow these steps:

  1. Open the app B2B Directory.

  2. Open the menu item Cloudlinks > Own Cloudlinks.

  3. Click New.

  4. In the field B2B Directory Entry, select the entry from or to which messages should be sent.

  5. In the field Type, select REST.

  6. In the field Direction, the option Both is the default value, because REST connections always include sending and receiving messages.

  7. In the field Usage, select how you want to use your cloudlink:

    • Content-Based: This is the default way of communicating with the SEEBURGER Cloud. It includes content-based routing as well as the new function metadata-based routing. With the option Content-Based, you can use all available functions of the Communication Service.
    • Published Address: The usage Published Address supports specific additional Cloud services like MaKo Cloud Service or Invoice Portal Cloud Service. If you are not using one of these services, select Content-Based.
  8. In the field Connection Name, enter the name for this cloudlink, so you can later identify it in the list of your cloudlinks.

  9. In the section SEEBURGER Cloud Access, you will find the information needed to configure your EDI system:

    • URL: In the field REST, click the link in your preferred language to download the datasheet which includes the URL needed to configure your EDI system.
    • In the field Username, the user name will appear after you have created the cloudlink. By default, the value of the field Connection Name will be used as the user name.
    • In the field Password, you can see the password to include in your EDI system together with the user name. You can make the password visible by setting a check mark in the field Display Password or generate a new password by clicking Generate New.
  10. In the section Your System Access, provide the information for the SEEBURGER Cloud to connect to your system in the following steps.

  11. In the field URL, enter the URL of your EDI system which will send and/or receive the messages. The URL may look like this: https://http.seeburger.cloud/tst_bis/http

  12. In the field Client Authentication, you can select between these options:

    • Use Client Certificate: Authentication takes place by means of a certificate. If you select this option, you can continue with step 15. You can download the SEEBURGER certificate to import it in your EDI system.
    • Use Username and Password (Basic Authentication): Authentication takes place via a user name and password provided in step 13 and 14.
  13. In the fields Username and Password, enter the user name and password which should be used by the SEEBURGER Cloud to send files to your EDI system.

  14. In the field HTTP Header Parameters, enter the header parameters that should be included in the messages sent from the SEEBURGER Cloud to you.

  15. In the field Time to live (minutes), enter the time after which messages will expire if they cannot be delivered to your routing partner. Your routing partners can find expired messages in the app B2B Routing if they are registered in the SEEBURGER Cloud. The default value is 5760 minutes which equals 4 days. Until the expiration date has been reached, the SEEBURGER Cloud will periodically retry to send your messages to your partner. This helps bridging outage times of your partner‘s system without manual intervention.

    Information: You will be informed about expired messages via an email. You can configure the email notifications.
  16. In the field Error Alert E-Mail(s), enter the email addresses to which notifications in case of communication errors will be sent. Only notifications about communication errors concerning this cloudlink will be sent.

    Note: Multiple email addresses must be separated by a semicolon.
  17. Set a check mark in the field Asynchronous Status Message Enabled to receive an additional status message concerning the processing and sending of your message to your partner. If you do not set a check mark, you will only receive the default http status code 200. The field Rest Cloudlink becomes active, so you can select the cloudlink which should be used to receive status messages.

    Information: The status message will be of a custom XML format.
  18. In the field Comment, you can enter more details to specify this cloudlink.

  19. Click Next.

  20. Click Upload to add your certificates for HTTPS.

  21. In the field Use from, you can enter the date and time of the certificate activation.

    Information: The default value is automatically set to the date and time the certificate starts to be valid.
  22. Click Next.

  23. Click the link in your preferred language to download the data sheet and certificates for your REST connection to configure your connection to the SEEBURGER Cloud in your EDI system.

  24. Click Finish.

Your cloudlink is created.Set up your connection to the SEEBURGER Cloud in your EDI system with the datasheet and certificates linked in step 22 before you activate the test service or the cloudlink.

Find more information here:

> Activating the test service

> Activating cloudlinks

> Setting up email notifications for errors and agreement changes

> What does an XML status message for my REST cloudlink look like?