|
|
[[_TOC_]]
|
|
[[_TOC_]]
|
|
|
|
|
|
|
|
# Introduction
|
|
# Introduction
|
|
|
This guide outlines the steps for deploying and configuring **Domibus version 5.1.1** as a CrossBorder Gateway, specifically tailored for each Access Point enabling the exchange of messages with the EU Access Point.
|
|
This guide outlines the steps for deploying and configuring **Domibus version 5.1.1** as a CrossBorder Gateway, specifically tailored for each Access Point enabling the exchange of messages with the Central Access Point.
|
|
|
|
|
|
|
|
The deployment and configuration instructions draw inspiration from the official documentation of eDelivery Domibus, accessible on the official website.
|
|
The deployment and configuration instructions draw inspiration from the official documentation of eDelivery Domibus, accessible on the official website.
|
|
|
|
|
|
|
|
Throughout this process, you will:
|
|
Throughout this process, you will:
|
|
|
|
|
|
|
|
- Establish a single-instance Domibus on your server using Docker.
|
|
- Establish a single-instance Domibus on your server using Docker.
|
|
|
- Configure the KeyStore and TrustStore to enhance message security with the EU Access Point.
|
|
- Configure the KeyStore and TrustStore to enhance message security with the Central Access Point.
|
|
|
- Adjust the PMode file to reference the parties you want to exchange with.
|
|
- Adjust the PMode file to reference the parties you want to exchange with.
|
|
|
- Activate authentication of a Plugin Users for accessing your Domibus through APIs.
|
|
- Activate authentication of a Plugin Users for accessing your Domibus through APIs.
|
|
|
- Conduct AS4 message exchanges with the eDelivery Domibus Access Point using SoapUI and the Web Service Plugin.
|
|
- Conduct AS4 message exchanges with the eDelivery Domibus Access Point using SoapUI and the Web Service Plugin.
|
| ... | @@ -28,7 +28,7 @@ The instructions in these guidelines use variables that must be replaced with th |
... | @@ -28,7 +28,7 @@ The instructions in these guidelines use variables that must be replaced with th |
|
|
## Requirement:
|
|
## Requirement:
|
|
|
Before proceeding with the above steps, ensure that your server environment meets the following prerequisites:
|
|
Before proceeding with the above steps, ensure that your server environment meets the following prerequisites:
|
|
|
|
|
|
|
|
Provision a Linux server. As a reference, the EU Domibus server is running with the following specifications:
|
|
Provision a Linux server. As a reference, the National Domibus server is running with the following specifications:
|
|
|
- 3 CPUs
|
|
- 3 CPUs
|
|
|
- 4 GB of RAM
|
|
- 4 GB of RAM
|
|
|
- 40 GB of storage
|
|
- 40 GB of storage
|
| ... | @@ -328,7 +328,7 @@ http://<EU-HOSTNAME>:<EU-PORT>/domibus/services/msh |
... | @@ -328,7 +328,7 @@ http://<EU-HOSTNAME>:<EU-PORT>/domibus/services/msh |
|
|

|
|

|
|
|
|
|
|
|
|
>**Note**:
|
|
>**Note**:
|
|
|
You can include the IP address of the specific Access Point you wish to establish communication with. However, in our scenario, it's essential to add only the IP address of the EU Access Point, which serves as the central hub.
|
|
You can include the IP address of the specific Access Point you wish to establish communication with. However, in our scenario, it's essential to add only the IP address of the Central Access Point, which serves as the central hub.
|
|
|
The <EU-HOSTNAME> and <EU-PORT> should be furnished by the Central Service Team.
|
|
The <EU-HOSTNAME> and <EU-PORT> should be furnished by the Central Service Team.
|
|
|
|
|
|
|
|
Import the [EU Access Point Certificate](https://drive.google.com/file/d/1jduYescq5XkJ8PPoMamWBDjOFoAY9GNO/view?usp=drive_link)
|
|
Import the [EU Access Point Certificate](https://drive.google.com/file/d/1jduYescq5XkJ8PPoMamWBDjOFoAY9GNO/view?usp=drive_link)
|
| ... | |
... | |
| ... | | ... | |