Connect the Cloud

Cloudlink setup

Creating AS2 cloudlinks

Creating AS2 cloudlinks

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

> Creating new B2B Directory entries

To create a new AS2 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 AS2.

  6. In the field Direction, select the direction of your messages:

    • Your system to SEEBURGER Cloud: Sending messages
    • SEEBURGER Cloud to your system: Receiving messages
    • Both: Sending and receiving messages
    Information: For receiving messages from the SEEBURGER Cloud you will need to provide the parameters of your EDI system.
  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 AS2 ID, provide the AS2 identifier for your technical connection.

  9. If you do not want to use an https connection, uncheck the checkbox of the field Use HTTPS. This configuration refers to the connection from the SEEBURGER Cloud to your EDI system.

    Note: If you want the SEEBURGER Cloud to use an https connection, you will need to provide an tsl certificate further in the process in step 19. Besides, you need to make the respective configuration in your EDI system, so you will be able to receive messages from the SEEBURGER Cloud via https.
Information: Using https will ensure a secure connection, while an http connection will reduce the security level to medium.

Note: If you have selected Your system to the SEEBURGER Cloud in step 6, skip the following steps 10 and 12-14.

  1. In the field URL, enter the URL of your EDI system which will send and/or receive the messages.

    Information: This URL requires a host (e.g. http.seeburger.cloud) and a port, (e.g. 443) and may contain an optional path (e.g. /cbr), so an example URL may look like this: https://http.seeburger.cloud:443/cbr.
  2. In the field MDN, the receipt return, you can select one of these options:

    • Asynchronous: The MDN will be sent in a different session than that of the sending process. As this is the most reliable way of receiving an MDN, we recommend to select this option.
    • Synchronous: The MDN will be sent within the same session of the sending process. Please be aware that you will not receive an MDN if the session has been closed before the SEEBURGER Cloud has sent the MDN.
  3. In the field Encryption Type, select the encryption type for receiving messages from the SEEBURGER Cloud that your EDI system supports. We recommend to select the most secure encryption type AES-256-CBC.

  4. In the field Signature Type, select the signature type for receiving messages from the SEEBURGER Cloud that your EDI system supports. We recommend to select the most secure signature type RAS-SHA512.

  5. Set a check mark in the field Use Basic Authentication if the SEEBURGER Cloud should send a specific user/password in the HTTP requests to your EDI system.

    • Enter User and Password which the SEEBURGER Cloud should send for authentication at your EDI system.
  6. 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 email. You can configure the email notifications.
  7. 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.
  8. In the field Comment, you can enter more details to specify this cloudlink.

  9. Click Next.

  10. Click Upload to add your certificates for Encryption and Signature. Upload your certificate for HTTPS, if you have activated using HTTPS in step 9.

  11. 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 is valid from.
  12. Click Next.

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

  14. 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