CrossBorder-Gateway/Domibus/Server-setup-guide.md

@@ -24,6 +24,8 @@ The instructions in these guidelines use variables that must be replaced with th
 - **`{CENTRAL_HOSTNAME}`**: Denotes the public IP address/hostname of the central Domibus server.
 - **`{CENTRAL_PORT}`**: Represents the internet-accessible port of the central Domibus server.
 - **`{CENTRAL_ACCESS_POINT}`**: This serves as the designated identifier for the central Domibus Access Point. It may be commonly referred to as `europe_ap` in some screenshots, however, please note that this is not the actual Access Point name, as we refrain from sharing sensitive information on this wiki.
+- **`{MESSAGE_DISPATCHER_HOSTNAME}`**: The hostname that Domibus uses to notify your service when a message is received. Use `as4-message-dispatcher` if your connector and Domibus are on the same network. Otherwise, use the hostname that Domibus needs to reach your service.
+- **`{MESSAGE_DISPATCHER_PORT}`**: The port number on which the message dispatcher service listens for notifications from Domibus. This should be an available port that doesn't conflict with other services in your environment. Default port is `7900`
 - **`{KEYSTORE_PASSWORD}`**: Refers to the password for your Java KeyStore.
 - **`{PRIVATE_KEY_PASSWORD}`**: Refers to the password for the private key within your Java KeyStore.
 - **`{TRUSTSTORE_PASSWORD}`**: Refers to the password for your Java TrustStore.
@@ -251,7 +253,10 @@ scp {ADMIN_USER}@{DOMIBUS_HOSTNAME}:/opt/{DOMIBUS_DIRECTORY}/domibus/keystores/{
 ```
 >**Note**: We consider you created your **`{DOMIBUS_DIRECTORY}`** inside the **`/opt/`** folder like suggested earlier. If not, please adjust the command to reflect the exact location of your **`{DOMIBUS_DIRECTORY}`**
 
-## 3 - Domibus Properties
+## 3 - Domibus Configuration
+:globe_with_meridians:
+
+### A - Domibus properties
 :globe_with_meridians:
 
 In the file **`{DOMIBUS_DIRECTORY}/domibus/domibus.properties`**, locate the section labeled `Keystore/Truststore (Single Tenancy)` and set the passwords you configured on the previous step:
@@ -297,6 +302,38 @@ domibus.passwordPolicy.expiration=90
 #Password expiration policy: how many days before expiration should the system warn users at login
 domibus.passwordPolicy.warning.beforeExpiration=30
 ```
+### B - Domibus Plugins
+:globe_with_meridians:
+
+This configuration enables Domibus to send notifications when messages are received. While optional for our connector, it's recommended to avoid the `as4-message-dispatcher` polling the Domibus server periodically for new messages.
+To enable this feature, modify the **`{DOMIBUS_DIRECTORY}/domibus/plugins/config/ws-plugin.properties`** file as follows:
+
+Locate the following lines and uncomment them (remove the '#' at the start of each line)
+Replace `[ruleName]` with `notif` and set their values as shown below:
+
+```properties
+...
+wsplugin.push.enabled=true
+...
+
+#############################################################
+#Rules for dispatching notifications and messages to backend
+#############################################################
+#Description of the rule
+wsplugin.push.rules.notif=first rule description
+
+#Recipient fo the domibus message
+wsplugin.push.rules.notif.recipient=
+
+#Endpoint to be used for a given type and a given recipient
+wsplugin.push.rules.notif.endpoint=http://{MESSAGE_DISPATCHER_HOSTNAME}:{MESSAGE_DISPATCHER_PORT}/events/process-messages
+
+#Formatted description of the retry mechanism  Format: retryTimeout;retryCount;(CONSTANT - SEND_ONCE) (ex: 4;12;CONSTANT)"
+wsplugin.push.rules.notif.retry=1;5;CONSTANT
+
+#Type of notification that will trigger a dispatch (RECEIVE_SUCCESS,RECEIVE_FAIL,SEND_SUCCESS,SEND_FAILURE,MESSAGE_STATUS_CHANGE,SUBMIT_MESSAGE,DELETED,DELETED_BATCH)
+wsplugin.push.rules.notif.type=RECEIVE_SUCCESS
+```
 
 ## 4 - Users Credentials
 :globe_with_meridians: