First things first, you will need a Microsoft Azure subscription before proceeding. If you don’t already have one, you can create one for using the link below:
So now that you have an Azure account let’s get started.
Create an Azure storage account
From the Azure portal, select All Services and then search for Storage accounts. From here, select New to create a new storage account.
Your new storage account can reside in any resource group, but we generally recommend creating a new resource group. The names can be anything desired, and standard tier performance is adequate in all but the most extreme circumstances.
The account kind should be general purpose v1. The storage redundancy should be selected based on the criticality of the environment.
The storage account must be accessible from all networks. Finally, create the new storage account.
Once created (this may take a few minutes), you will then need to open the Access Keys section of the storage configuration page. In this section you will find a primary and secondary connection string. Copy the primary connection string, we will use this later in the setup.
Create an EIS QBridge subscription
Next step is to create an EIS subscription, that can be done either through the Azure portal, or the Azure market place (it makes no difference).
After selecting a subscription, you will be taken to an Azure setup page. Follow the link provided to complete the subscription setup on the QBridge portal:
When first loading the QBridge dashboard, you will be presented with the New Application page. From here, you can provide:
Instance name: The name for this instance of QBridge . This would usually be something like Contoso Production.
Description: Text that can be useful for DevOps engineers or other users e.g. a description of what systems are using this AS2 EDI service.
Company Name: The company name may be used for reporting purposes.
Once your subscription has been created, you can review the configuration by selecting Subscription Setup from the left hand menu.
The configuration shown will reflect those values entered when creation the subscription. You will however need to save an Azure storage connection string value. This value comes from the Access Keys page on your storage configuration (copied previously). Add the value and save. Note, once the value has been saved, for security reasons you cannot retrieve this value again, this field will show you the name of the storage account, but not access keys.
Configuring local AS2 parameters
Within the AS2 data interchange standard, both the sender and receiver must have a unique identifier, this is called the AS2 Name. To configure the AS2 name, select the Local Host option under AS2 Configuration:
In addition to setting up the AS2 Name, you can also upload certificates for use in encryption and signing. For more details on message security in AS2, please visit the AS2 introduction page at https://eis-web.azurewebsites.net/whatisas2/. You do not have to provide any certificates, and message exchange can still be secured with encryption using the HTTPS protocol (in the same way that visiting a secure website (i.e. your bank) does not require you to provide a certificate, it is managed via PKI).
When creating a certificate, you will have 2 files, one being the public key (usually a .crt file), and the other being the private key (usually a .p12 file). On the local host configuration, you will be uploading the private key of a certificate (usually in a p12 file format)
This private key certificate will be used to decrypt messages that have been sent to you from another party. The other party will have been provided your public key certificate, which they will use for encrypting messages.
This private key certificate will be used to sign messages that are being sent from you to any another party. The other party will have been provided your public key certificate, which they can use to verify that the message was sent by you.
For the complete guide on setting up certificates, visit https://enterpriseintegrationsolutions.com/secure-edi-with-certificates/
Configure an AS2 partner
An AS2 partner is a set of configuration properties that define how QBridge will send or receive electronic data from another system (another business partner). All of these details should be provided to you by your business partner (they define the values, not you, you just need to add them to your AS2 portal).
Used for reporting and display purposes, not sent to partner.
This value uniquely identifies an AS2 partner, and must be provided to you by them.
The is the URL where outbound AS2 messages are sent. Again, provided by the parner.
When enabled, outbound messages are compressed before transmission. Please ensure your AS2 partner sup[port compression before enabling (most will). Any inbound message will be automatically decompressed no matter what is configured here.
Please read our introduction to AS2 for more details on MDN (https://eis-web.azurewebsites.net/whatisas2/). We recommend a Synchronous MDN pattern.
Default message subject
This is the HTTP subject that is sent with every message. If this field is left blank, then the value from the QBridge windows service will be used (more details below on configuring this). Some partners require the AS2 subject to be a value such as ‘SALESORDER’.
Default message content type
This is the encoding of outbound messages. We recommend this is left with its default value unless your AS2 partner request something different.
Request MDN Message Signing
When enabled, outbound messages are marked with a request for all MDN responses to be signed. The signature of the response messages is then checked against the Inbound Signature certificate that is uploaded (below). This certificate will have been provided by your AS2 partner.
This enables outbound message encryption. You must upload the public key certificate provided by your AS2 partner for message encryption.
Certificate is provided by your AS2 partner and is used for checking inbound message signatures. This certificate will usually be in a .crt or .cer format.
Certificate is provided by your AS2 partner and is used for checking outbound message encryption. This certificate will usually be in a .crt or .cer format. Note, if the endpoint address setup above starts with HTTPS, then the communications channel is already encrypted, and that using outbound encryption here results in double message encryption.
You will need to select the format of encryption used, this will usually be specified by your AS2 partner, but if it’s not, we recommend AES256.
This private key certificate will be used to decrypt messages that have been sent to you from another party. This certificate is defined on your ‘Local Host’ configuration page. This is your private key certificate. See https://enterpriseintegrationsolutions.com/secure-edi-with-certificates/
This private key certificate will be used to sign messages that are being sent by you. It is defined on your ‘Local Host’ configuration page. This is your private key certificate. See https://enterpriseintegrationsolutions.com/secure-edi-with-certificates/
You will need to select the format of signing used, this will usually be specified by your AS2 partner, but if it’s not, we recommend SHA256.
Configure the on-premise Windows service
With the QBridge subscription now configured, you now need a way of pulling received messages onto an server that will be loading the messages (or sending them). This is accomplished with the QBridge client.
The complete guide to setting up the QBridge client can be found here.