Domibus Upgrade Guides

Replace the Domibus war.

Replace the default DSS extension jar into /conf/domibus/extensions/lib.

Replace the Domibus war

Replace the Domibus war

Replace the Domibus war

Replace the Domibus war.

Replace the Domibus war.

Please remove the following properties from the file /conf/domibus/extensions/config/authentication-dss-extension.properties:

domibus.authentication.dss.custom.trusted.lists.list1.code

domibus.authentication.dss.lotl.country.code=EU

domibus.dss.data.loader.connection.request.timeout

Ehcache has been upgraded to version 3.8.1 affecting "/conf/domibus/internal/ehcache.xml" cache definitions file:

If you use custom caches definitions defined in this file replace the old file with the new file and perform the following steps, replace:

<cache name="policyCache"
    maxBytesLocalHeap="5m"
    timeToLiveSeconds="3600"
    overflowToDisk="false" >
</cache>

<cache alias="policyCache">
    <expiry>
    <ttl>3600</ttl>
    </expiry>
    <heap unit="MB">5</heap>
</cache>

<cache alias="dss-cache">
    <expiry>
        <ttl>3600</ttl>
    </expiry>
    <heap unit="MB">50</heap>
</cache>

If you don’t use custom caches just replace the old file with the new file version.

Replace the Domibus war and the default plugin(s) config file(s), property file(s) and jar(s) into "/conf/domibus/plugins/config" respectively into "/conf/domibus/plugins/lib".

Replace the Domibus war.

Replace the default DSS extension jar into /conf/domibus/extensions/lib.

Remove all revoked certificates from /conf/domibus/keystores/dss-tls-truststore.p12.

Replace the Domibus war.

Run the appropriate DB migration script(mysql-4.2.2-to-4.2.3-migration.ddl for MySQL or oracle-4.2.2-to-4.2.3-migration.ddl for Oracle).

Replace the Domibus war.

Replace the default plugins property files and jars into "conf/domibus/plugins/config" respectively into "/conf/domibus/plugins/lib".

Replace the default DSS extension jar into "/conf/domibus/extentions/lib".

MySQL8 only

Grant XA_RECOVER_ADMIN privilege to the user:
In MySQL 8.0, XA_RECOVER is permitted only to users who have the XA_RECOVER_ADMIN privilege. Prior to MySQL 8.0, any user could execute this and discover the XID values of XA transactions by other users. This privilege requirement prevents users from discovering the XID values for outstanding prepared XA transactions other than their own.

GRANT XA_RECOVER_ADMIN ON . TO 'edelivery_user'@'localhost';

Execute below command to flush privileges:
When we grant some privileges for a user, running this command will reloads the grant tables in the mysql database enabling the changes to take effect without reloading or restarting mysql service.

FLUSH PRIVILEGES;

Run the appropriate DB migration script(mysql-4.2.1-to-4.2.2-migration.ddl for MySQL or oracle-4.2.1-to-4.2.2-migration.ddl for Oracle)

Replace the Domibus war.

Replace the default plugins property files and jars into "conf/domibus/plugins/config" respectively into "/conf/domibus/plugins/lib".

Change the name of 'domibus.ui.resend.action.enabled.received.minutes' property to 'domibus.action.resend.wait.minutes' in domibus.properties file.

Oracle only

Grant access to your user to create stored procedures: Open a command line session and log in (edelivery_user and password are the ones assigned during the Oracle installation):

$ sqlplus sys as sysdba

Run the appropriate DB migration script(mysql-4.2-to-4.2.1-migration.ddl for MySQL or oracle-4.2-to-4.2.1-migration.ddl for Oracle)

Replace the Domibus war

Replace the default plugins property files and jars into "conf/domibus/plugins/config" respectively into "/conf/domibus/plugins/lib"

Replace the default DSS extension jar into /conf/domibus/extensions/lib

It is mandatory to update to one of the below supported servers and databases. Servers: Tomcat 9.x, WildFly 20.0.x, WebLogic 12.2.1.4 Database: MySQL 8, Oracle 12c, Oracle 19c

If you are upgrading to a new application server, the JMS messages that are not consumed in the previous server installation must be migrated to the new server installation.

It is optional to upgrade to Oracle OpenJDK 11, you can still use Domibus 4.2 with Oracle JDK 8.

Run the appropriate DB migration script(mysql-4.1.5-to-4.2-migration.ddl for MySQL or oracle-4.1.5-to-4.2-migration.ddl for Oracle).

Replace the Domibus war.

Delete the default plugins config files(ws-plugin.xml, jms-plugin.xml and fs-plugin.xml) from "conf/domibus/plugins/config".

Replace the default plugins property files and jars into "conf/domibus/plugins/config" respectively into "/conf/domibus/plugins/lib".

PMode payload profile maxSize re-enabled: remove the comment about maxSize <payloadProfile name="MessageProfile" maxSize="40894464"> <!-- maxSize is currently ignored -→ and replace the value with maxSize="2147483647" in the PMode file.

Change the name of domibus.ui.csv.max.rows property to domibus.ui.csv.rows.max in domibus.properties file.

if Oracle database is used, change oracle database configuration property domibus.datasource.xa.property.URL to domibus.datasource.xa.property.url in domibus.properties.

in file "conf/domibus/internal/activemq.xml"

remove properties-ref="domibusProperties" from the line <context:property-placeholder properties-ref="domibusProperties" ignore-resource-not-found="true" ignore-unresolvable="true"/>

run the appropriate DB migration script (mysql-4.1.5-to-4.2-multi-tenancy-migration.ddl for MySQL or oracle-4.1.5-to-4.2-multi-tenancy-migration.ddl for Oracle).

add the configuration file default-domibus.properties for the 'default' domain from the distribution.

add the configuration file super-domibus.properties from the distribution

in the domain specific configuration files(eg domain_name-domibus.properties), replace the names of the domain_name.payload.temp.* properties with domain_name.domibus.payload.temp.* .

for the domain specific configuration files, the domain name should start with a letter and it should contain only lower case letters, numbers and underscore.

as the property names in these files need to be prefixed with the domain name, this prefix needs to follow the same rules as the domain name above.

in standalone-full.xml, search for

<managed-executor-service name="quartzExecutorService" jndi-name="java:jboss/ee/concurrency/executor/QuartzExecutorService" context-service="default" hung-task-threshold="0" long-running-tasks="true" core-threads="5" max-threads="25" keepalive-time="5000"/>
and replace 'core-threads="5" max-threads="25"' with 'core-threads="100" max-threads="300"'
<managed-executor-service name="domibusExecutorService" jndi-name="java:jboss/ee/concurrency/executor/DomibusExecutorService" context-service="default" hung-task-threshold="60000" core-threads="50" max-threads="200" keepalive-time="5000"/>
and replace 'core-threads="50" max-threads="200"' with 'core-threads="200" max-threads="500"'

in standalone-full.xml, add

execute the WLST API script(from "/conf/domibus/scripts/upgrades") 4.1.6-to-4.2-WeblogicSingleServer.properties for single server deployment or 4.1.6-to-4.2-WeblogicCluster.properties for cluster deployment

Custom plugins - For custom plugins the interface to Domibus has changed. Please follow the Plugin Cookbook sections:

8. DEPRECATED API AND MIGRATING TO THE NEW API - to update the notification listener to the plugins

4. PLUGIN PROPERTIES - to update the registration of plugin properties with Domibus and their retrieval

3.9. Ehcache - to follow the new structure of ehcache if the plugin creates its own caches.

Run the appropriate DB migration script(mysql-4.2-RC1-to-4.2-migration.ddl for MySQL or oracle-4.2-RC1-to-4.2-migration.ddl for Oracle).

Replace the Domibus war.

Replace the default plugin(s) property file(s) and jar(s) into /domibus/conf/domibus/plugins/config respectively into /domibus/conf/domibus/plugins/lib.

Replace the domibus.properties file(Please comment the property 'domibus.database.schema', if Domibus is configured in single-tenancy mode with Oracle database).

execute the WLST API script(from "/conf/domibus/scripts/upgrades") 4.1.6-to-4.2-WeblogicSingleServer.properties for single server deployment or 4.1.6-to-4.2-WeblogicCluster.properties for cluster deployment.

Upgraded several libraries version: Apache CXF to 3.3.8, Hibernate to 5.4.27.Final, BouncyCastle to 1.64, etc

Replace the Domibus war.

Run the appropriate DB migration script(mysql5innoDb-4.1.3-to-4.1.5-migration.ddl for MySQL or oracle10g-4.1.3-to-4.1.5-migration.ddl for Oracle).

Replace the Domibus war and the default plugin(s) config file(s), property file(s) and jar(s) into /domibus/conf/domibus/plugins/config respectively into /domibus/conf/domibus/plugins/lib.

In case of Dynamic Discovery where the trust for SMP certificate is established only by issuer certificate, now the whole chain must be imported in to the truststore.

Replace the Domibus war and the default plugin(s) config file(s), property file(s) and jar(s) into /domibus/conf/domibus/plugins/config respectively into /domibus/conf/domibus/plugins/lib.

In file "conf/domibus/internal/activemq.xml", remove the attribute rmiServerPort="${activeMQ.rmiServerPort}" from the managementContext element

In file "/conf/domibus/domibus.properties", remove the property "activeMQ.rmiServerPort" and update the JMX URL property to "activeMQ.JMXURL=service:jmx:rmi:///jndi/rmi://${activeMQ.broker.host}:${activeMQ.connectorPort}/jmxrmi".

Run the appropriate DB migration script(mysql5innoDb-4.1.1-to-4.1.2-migration.ddl for MySQL or oracle10g-4.1.1-to-4.1.2-migration.ddl for Oracle).

Replace the Domibus war and the default plugin(s) config file(s), property file(s) and jar(s) into /domibus/conf/domibus/plugins/config respectively into /domibus/conf/domibus/plugins/lib.

Replace the current logback.xml file with the newer version optionally keeping the existing configuration.

In case you are using multitenancy please make the following modifications:

Replace the Domibus war.

Run the appropriate DB migration script(mysql5innoDb-4.0.2-to-4.1-migration.ddl for MySQL or oracle10g-4.0.2-to-4.1-migration.ddl for Oracle).

Replace the Domibus war and the default plugin(s) config file(s), property file(s) and jar(s) into /domibus/conf/domibus/plugins/config respectively into /domibus/conf/domibus/plugins/lib.

Replace the current logback.xml file with the newer version optionally keeping the existing configuration.

In case you are using multitenancy please perform the following modifications:

In case the probe URL is used, the new probe URL is /domibus/services/msh.

In execute the WLST API script(from "/conf/domibus/scripts/upgrades") 4.0.2-to-4.1-WeblogicSingleServer.properties for single server deployment or 4.0.2-to-4.1-WeblogicCluster.properties for cluster deployment.

In case the probe URL is used, the new probe URL is /domibus/services/msh

In file "cef_edelivery_path/domibus/standalone/configuration/standalone-full.xml":

add the following queues

<!-- -->
<subsystem xmlns="urn:jboss:domain:messaging-activemq:3.0">
<server name="default">
    <!-- -->
    <address-setting name="jms.queue.DomibusSendLargeMessageQueue" expiry-address="jms.queue.ExpiryQueue" redelivery-delay="1000" max-delivery-attempts="0"/>
    <address-setting name="jms.queue.DomibusSplitAndJoinQueue" expiry-address="jms.queue.ExpiryQueue" redelivery-delay="60000" max-delivery-attempts="3"/>
    <address-setting name="jms.queue.DomibusPullReceiptQueue" expiry-address="jms.queue.ExpiryQueue" redelivery-delay="1000" max-delivery-attempts="3"/>
    <address-setting name="jms.queue.DomibusRetentionMessageQueue" expiry-address="jms.queue.ExpiryQueue" redelivery-delay="10000" max-delivery-attempts="0"/>
    <address-setting name="jms.queue.DomibusFSPluginSendQueue" expiry-address="jms.queue.ExpiryQueue" max-delivery-attempts="0"/>

    <jms-queue name="DomibusSendLargeMessageQueue" entries="java:/jms/domibus.internal.largeMessage.queue java:/jms/queue/DomibusSendLargeMessageQueue" durable="true"/>
    <jms-queue name="DomibusSplitAndJoinQueue" entries="java:/jms/domibus.internal.splitAndJoin.queue java:/jms/queue/DomibusSplitAndJoinQueue" durable="true"/>
    <jms-queue name="DomibusPullReceiptQueue" entries="java:/jms/domibus.internal.pull.receipt.queue java:/jms/queue/DomibusPullReceiptQueue" durable="true"/>
    <jms-queue name="DomibusRetentionMessageQueue" entries="java:/jms/domibus.internal.retentionMessage.queue java:/jms/queue/DomibusRetentionMessageQueue" durable="true"/>
    <jms-queue name="DomibusFSPluginSendQueue" entries="java:/jms/domibus.fsplugin.send.queue java:/jms/queue/DomibusFSPluginSendQueue" durable="true"/>
    <!-- -->
</server>
</subsystem>
<!-- -->

In the file "cef_edelivery_path/domibus/conf/domibus/internal/activemq.xml", in the destinations section add the following queues:

<!-- -->
<destinations>
 <!-- -->
<queue id="sendLargeMessageQueue" physicalName="domibus.internal.largeMessage.queue"/>
  <queue id="splitAndJoinQueue" physicalName="domibus.internal.splitAndJoin.queue"/>
  <queue id="retentionMessageQueue" physicalName="domibus.internal.retentionMessage.queue"/>
  <queue id="sendPullReceiptQueue" physicalName="domibus.internal.pull.receipt.queue"/>
  <queue id="fsPluginSendQueue" physicalName="${fsplugin.send.queue:domibus.fsplugin.send.queue}"/>
 <!-- -->
</destinations>
<!-- -->

in the redeliveryPolicyEntries section add the following entries:

<!-- -->
<redeliveryPolicyEntries>
<!-- -->
<redeliveryPolicy queue="domibus.internal.largeMessage.queue" maximumRedeliveries="0"/>
<redeliveryPolicy queue="domibus.internal.splitAndJoin.queue" maximumRedeliveries="3"/>
<redeliveryPolicy queue="domibus.internal.retentionMessage.queue" maximumRedeliveries="0"/>
<redeliveryPolicy queue="domibus.internal.pull.receipt.queue" maximumRedeliveries="3"/>
<redeliveryPolicy queue="${fsplugin.send.queue:domibus.fsplugin.send.queue}" maximumRedeliveries="0"/>
<!-- -->
</redeliveryPolicyEntries>
<!-- -->

Rename the property "message.retention.downloaded.max.delete" to "domibus.retentionWorker.message.retention.downloaded.max.delete" in your domibus.properties file. If the property is not defined, do nothing. Default value "50" has not been changed.

Rename the property "message.retention.not_downloaded.max.delete" to "domibus.retentionWorker.message.retention.not_downloaded.max.delete" in your domibus.properties file. If the property is not defined, do nothing. Default value "50" has not been changed.

Remove domibus.msh.retry.tolerance from domibus.properties, if set. This property is not used anymore.

Replace the Domibus war and the default plugin(s) config file(s), property file(s) and jar(s) into /domibus/conf/domibus/plugins/config respectively into /domibus/conf/domibus/plugins/lib.

Run the appropriate DB migration script(mysql5innoDb-4.0-to-4.0.1-migration.ddl for MySQL or oracle10g-4.0-to-4.0.1-migration.ddl for Oracle).

Replace the Domibus war and the default plugin(s) config file(s), property file(s) and jar(s) into /domibus/conf/domibus/plugins/config respectively into /domibus/conf/domibus/plugins/lib.

In case you are using multitenancy please make the following modifications:

Run the appropriate DB migration script(mysql5innoDb-3.3.4-to-4.0-migration.ddl for MySQL or oracle10g-3.3.4-to-4.0-migration.ddl for Oracle).

Replace the Domibus war and the default plugin(s) config file(s), property file(s) and jar(s) into /domibus/conf/domibus/plugins/config respectively into /domibus/conf/domibus/plugins/lib.

The following changes have been implemented in the Default WS Plugin which is not backward compatible. The client of the Default WS Plugin need to take into account the following changes:

Replace the Maven dependency commons-lang with commons-lang3 like below:

<dependency>
   <groupId>org.apache.commons</groupId>
   <artifactId>commons-lang3</artifactId>
   <scope>provided</scope>
</dependency>

PEPPOL dynamic discovery was updated to the PEPPOL profile requirements. The value of eb:UserMessage/eb:CollaborationInfo/eb:Service matches now the entire Scheme::ProcessIdentifier construction while the Service@type is not taken into consideration and therefore can take any needed value.

Modify the XA datasource "cipaeDeliveryDs" settings in the WebLogic Console

Modify file "/conf/domibus/domibus.properties":

Modify file "/conf/domibus/domibus.properties":

In file "cef_edelivery_path/domibus/conf/domibus/internal/activemq.xml", in the destinations section add the following queues:

In the redeliveryPolicyEntries section add the following entries:

In the discardingDLQBrokerPlugin update the dropOnly parameter value as below:

<discardingDLQBrokerPlugin dropAll="false" dropOnly="domibus.internal.dispatch.queue domibus.internal.pull.queue" reportInterval="10000"/>
-new configuration:
<discardingDLQBrokerPlugin dropAll="false" dropOnly="domibus.internal.dispatch.queue domibus.internal.pull.queue domibus.internal.alert.queue" reportInterval="10000"/>

Modify file "/conf/domibus/domibus.properties":

in file "cef_edelivery_path/domibus/standalone/configuration/standalone-full.xml":

Authentication uses BCryptPasswordEncoder, similar to the UI users. TB_AUTHENTICATION_ENTRY table was restored t*defaults, having tw*users 'admin' and 'user' with default password '123456' encrypted using the new algorithm. Custom users should be recreated using the new functionality in the Domibus Admin Console.

Remove from PartInfo the Description and Schema headers from the SOAP messages. These headers were deprecated in ebMS3 and as a result were removed from the WS-Plugin XSD. When received on the MSH side, they are simply ignored.

Description is no longer available as a property of a payload, remove it from the input message.

Modify file "/conf/domibus/domibus.properties":

Add property : domibus.entityManagerFactory.jpaProperty.hibernate.id.new_generator_mappings=false

Add a new property "domibus.database.schema" for defining the database schema and modify the "domibus.datasource.xa.property.url" and "domibus.datasource.url" properties t*re-use it. Eg: #MySQL

domibus.datasource.xa.property.url=jdbc:mysql://${domibus.database.serverName}:${domibus.database.port}/${domibus.database.schema}?pinGlobalTxToPhysicalConnection=true
domibus.datasource.url=jdbc:mysql://${domibus.database.serverName}:${domibus.database.port}/${domibus.database.schema}?useSSL=false

Delete properties
domibus.backend.jmsInQueue
domibus.pmode.dao.implementation

Optional changes (only if Domibus is used in multi-tenancy mode):

Modify the file "/conf/domibus/domibus.properties":

Modify the "domibus.datasource.xa.property.url" and "domibus.datasource.url" properties and set the default general schema in the URL Eg: #MySQL

domibus.datasource.xa.property.url=jdbc:mysql://${domibus.database.serverName}:${domibus.database.port}/${domibus.database.general.schema}?pinGlobalTxToPhysicalConnection=true
domibus.datasource.url=jdbc:mysql://${domibus.database.serverName}:${domibus.database.port}/${domibus.database.general.schema}?useSSL=false
domibus.datasource.url=jdbc:mysql://${domibus.database.serverName}:${domibus.database.port}/${domibus.database.general.schema}?useSSL=false

(Optional) Security policies were updated and renamed. Change your pMode to use eDeliveryAS4Policy.xml instead of eDeliveryPolicy.xml and eSensPolicy(.v2.0).xml. Replace both eDeliveryPolicy_CA.xml and eSensPolicy.v2.0_CA.xml, by eDeliveryAS4Policy_BST.xml.

Run the appropriate DB migration script

In the file /conf/domibus/domibus.properties add the following properties:

If used, rename the following properties ("." was removed between dynamic and discovery):

Replace the Domibus war and the plugin(s) jar(s) into /domibus/conf/domibus/plugins/lib.

In the file "/conf/domibus/domibus.properties" add the following properties, in the security section:

Run the appropriate DB migration script,

In the file "/conf/domibus/logback.xml" at line 22 replace <marker>LOGGED_MARKER</marker> with

[Wildfly only] In standalone/configuration/standalone-full.xml update "max-delivery-attempts" to 0 for

DomibusPullMessageQueue and DomibusSendMessageQueue:
<address-setting match="jms.queue.DomibusSendMessageQueue">
<max-delivery-attempts>0</max-delivery-attempts>
</address-setting>
<address-setting match="jms.queue.DomibusPullMessageQueue">
<max-delivery-attempts>0</max-delivery-attempts>
</address-setting>

Replace the Domibus war and the plugin(s) jar(s) into /domibus/conf/domibus/plugins/lib

In the file /conf/domibus/domibus.properties add the following properties, in the security section:

Run the appropriate DB migration script(mysql5innoDb-3.3-to-3.3.1-migration.ddl for MySQL or oracle10g-3.3-to-3.3.1-migration.ddl for Oracle)

Replace the Domibus war and the plugin(s) jar(s) into /domibus/conf/domibus/plugins/lib

Run the appropriate DB migration script(mysql5innoDb-3.2.5-to-3.3-migration.ddl for MySQL or oracle10g-3.2.5-to-3.3-migration.ddl for Oracle)

[ALL Databases]:

INSERT INTO TB_USER_ROLE (ID_PK, ROLE_NAME) VALUES ('1', 'ROLE_ADMIN');
INSERT INTO TB_USER_ROLE (ID_PK, ROLE_NAME) VALUES ('2', 'ROLE_USER');
INSERT INTO TB_USER (ID_PK, USER_NAME, USER_PASSWORD, USER_ENABLED) VALUES ('1', 'admin', '$2a$10$5uKS72xK2ArGDgb2CwjYnOzQcOmB7CPxK6fz2MGcDBM9vJ4rUql36', 1);
INSERT INTO TB_USER (ID_PK, USER_NAME, USER_PASSWORD, USER_ENABLED) VALUES ('2', 'user', '$2a$10$HApapHvDStTEwjjneMCvxuqUKVyycXZRfXMwjU0rRmaWMsjWQp/Zu', 1);
INSERT INTO TB_USER_ROLES (USER_ID, ROLE_ID) VALUES ('1', '1');
INSERT INTO TB_USER_ROLES (USER_ID, ROLE_ID) VALUES ('1', '2');
INSERT INTO TB_USER_ROLES (USER_ID, ROLE_ID) VALUES ('2', '2');

[MySQL only] Execute the command: alter schema your_domibus_schema_name default charset=utf8 collate=utf8_bin;

in the location "/conf/domibus" delete the log4j.properties file and copy the logback.xml distributed in the domibus configuration specific to each server

in file "/conf/domibus/plugins/config/ws-plugin.xml" locate the following section and add the following interceptors:

<jaxws:endpoint id="backendInterfaceEndpoint" implementor="#backendWebservice" address="/backend">
    <!-- -->
    <jaxws:outInterceptors>
        <ref bean="clearAuthenticationMDCInterceptor"/>
    </jaxws:outInterceptors>
    <jaxws:outFaultInterceptors>
        <ref bean="clearAuthenticationMDCInterceptor"/>
    </jaxws:outFaultInterceptors>
</jaxws:endpoint>

Add the following lines to "/conf/domibus/internal/ehcache.xml"

<cache name="dispatchClient"
    maxBytesLocalHeap="5m"
    timeToLiveSeconds="3600"
    overflowToDisk="false">
    <sizeOfPolicy maxDepthExceededBehavior="abort"/>
</cache>

If not already the case modify the certificate alias from the keystore in order to match the party name of the sender AP.

The external Spring configuration files(domibus-configuration.xml, domibus-datasources.xml, domibus-plugins.xml, domibus-security.xml, domibus-transactions.xml, persistence.xml) are not used anymore. All the properties defined in those files have been externalized in a new property file named "domibus.properties" which is specific to each supported server(Tomcat/WebLogic/WildFly). In order to perform the upgrade procedure please copy the file "domibus.properties", distributed in the domibus configuration specific to each server, to "/conf/domibus" and adapt the properties values based on the configured properties defined in the old Spring configuration files. After this action is completed the old Spring configuration files (domibus-configuration.xml, domibus-datasources.xml, domibus-plugins.xml, domibus-security.xml, domibus-transactions.xml, persistence.xml) can be deleted.

In the file "/conf/domibus/domibus-configuration.xml" all the properties defined in "<util:properties id="domibusProperties">" have been copied such as with the following exception:

In the file "/conf/domibus/domibus-security.xml"

In the "<util:properties id="keystoreProperties">" section:

In the "<util:properties id="trustStoreProperties">" section:

In file "/conf/domibus/domibus-datasources.xml", in the "entityManagerFactory" section:

Run the appropriate DB migration script.

Replace the war file and the default plugins: domibus-default-ws-plugin and domibus-default-jms-plugin jar files.

Replace the war file and the default plugins: domibus-default-ws-plugin and domibus-default-jms-plugin jar files.

Replace the war file and the default plugins: domibus-default-ws-plugin and domibus-default-jms-plugin jar files.

In case of Weblogic cluster uncomment and configure the "domibus.deployment.cluster.url" property. and uncomment/comment the xml parts as indicated into ws-plugin.xml and domibus-datasources.xml.

Replace the war file and the default plugins: domibus-default-ws-plugin and domibus-default-jms-plugin jar files

Add the following lines to conf/domibus/internal/ehcache.xml:

<cache name="lookupInfo"
maxBytesLocalHeap="5m"
timeToLiveSeconds="3600"
overflowToDisk="false">
</cache>

To use the Dynamic Discovery copy conf/domibus/policies/eDeliveryPolicy_CA.xml to conf/domibus/policies.

[WebLogic only]

Execute the WLST API script(from "/conf/domibus/scripts/upgrades") 3.2-to-3.2.1-WeblogicSingleServer.properties for single server deployment or 3.2-to-3.2.1-WeblogicCluster.properties for cluster deployment.

In the WebLogic console, in the page "Home >Summary of Security Realms >myrealm", enable the flag "Use Authorization Providers to Protect JMX Access" flag; for more info please check the Administration Guide.

In the WebLogic console, in the page "Home >Summary of JDBC Data Sources >cipaeDeliveryDs", tab "Configuration/Connection Pool/Advanced" enable the "Test Connections On Reserve" flag and add "SQL SELECT 1 FROM DUAL" in the "Test Table Name".

Replace the war file.

in file "/domibus/conf/domibus/plugins/config/ws-plugin.xml": o replace

<jaxws:endpoint id="backendInterfaceEndpoint" implementor="#backendWebservice" address="/backend">
...
</jaxws:endpoint>

<jaxws:endpoint id="backendInterfaceEndpoint" implementor="#backendWebservice" address="/backend">

<jaxws:properties>
  <entry key="schema-validation-enabled" value="true"/>
  <entry key="mtom-enabled" value="false"/>
</jaxws:properties>

<jaxws:schemaLocations>
  <jaxws:schemaLocation>schemas/domibus-header.xsd</jaxws:schemaLocation>
  <jaxws:schemaLocation>schemas/domibus-backend.xsd</jaxws:schemaLocation>
  <jaxws:schemaLocation>schemas/xml.xsd</jaxws:schemaLocation>
  <jaxws:schemaLocation>schemas/xmlmime.xsd</jaxws:schemaLocation>
</jaxws:schemaLocations>
<jaxws:inInterceptors>
    <ref bean="customAuthenticationInterceptor"/>
</jaxws:inInterceptors>

</jaxws:endpoint>

In file "/domibus/conf/domibus/internal/ehcache.xml":

In file "/domibus/conf/domibus/domibus-configuration.xml":

In file conf/domibus/domibus-security.xml, replace all from the comment:

 <!-- Administration GUI user credentials-->
 ...

<!-- Administration GUI user credentials-->
 <bean name="bcryptEncoder"
       class="org.springframework.security.crypto.bcrypt.BCryptPasswordEncoder"/>
 <sec:authentication-manager>
     <sec:authentication-provider ref="allowAllAuthenticationProvider"/>
 </sec:authentication-manager>
 <sec:authentication-manager id="authenticationManagerForAdminConsole">
     <sec:authentication-provider>
         <sec:password-encoder ref="bcryptEncoder"/>
         <sec:user-service>
             <sec:user name="user" password="$2a$10$HApapHvDStTEwjjneMCvxuqUKVyycXZRfXMwjU0rRmaWMsjWQp/Zu"
                       authorities="ROLE_USER"/>
             <sec:user name="admin" password="$2a$10$5uKS72xK2ArGDgb2CwjYnOzQcOmB7CPxK6fz2MGcDBM9vJ4rUql36"
                       authorities="ROLE_USER, ROLE_ADMIN"/>
         </sec:user-service>
     </sec:authentication-provider>
 </sec:authentication-manager>
 <sec:global-method-security pre-post-annotations="enabled"/>

[Tomcat only] in file "/domibus/conf/domibus/domibus-datasources.xml", replace

<amq:xaConnectionFactory id="xaJmsConnectionFactory" brokerURL="tcp://localhost:61616" userName="domibus" password="changeit"/>

<amq:xaConnectionFactory id="xaJmsConnectionFactory"
                 brokerURL="tcp://localhost:61616"
                 userName="domibus" password="changeit">
            <!-- do not remove this! otherwise the redeliveryPolicy configured in activemq.xml will be ignored -->
            <amq:redeliveryPolicy>
                <amq:redeliveryPolicy/>
            </amq:redeliveryPolicy>
        </amq:xaConnectionFactory>

[Tomcat only] in file conf/domibus/persistence.xml, add to the <persistence-unit> tag: <class>eu.domibus.plugin.ws.entity.AuthenticationEntry</class>.

Run the appropriate DB migration script.

Replace domibus.war and the plugin(s) jar(s) into /domibus/conf/domibus/plugins/lib"

Update the configuration file following these steps:

In file conf/domibus/internal/ehcache.xml, add

in file conf/domibus/domibus-security.xml, replace all from the comment

<!-- Administration GUI user credentials-->
...

<!-- Administration GUI user credentials-->
 <bean name="bcryptEncoder"
       class="org.springframework.security.crypto.bcrypt.BCryptPasswordEncoder"/>
 <sec:authentication-manager>
     <sec:authentication-provider ref="allowAllAuthenticationProvider"/>
 </sec:authentication-manager>
 <sec:authentication-manager id="authenticationManagerForAdminConsole">
     <sec:authentication-provider>
         <sec:password-encoder ref="bcryptEncoder"/>
         <sec:user-service>
             <sec:user name="user" password="$2a$10$HApapHvDStTEwjjneMCvxuqUKVyycXZRfXMwjU0rRmaWMsjWQp/Zu"
                       authorities="ROLE_USER"/>
             <sec:user name="admin" password="$2a$10$5uKS72xK2ArGDgb2CwjYnOzQcOmB7CPxK6fz2MGcDBM9vJ4rUql36"
                       authorities="ROLE_USER, ROLE_ADMIN"/>
         </sec:user-service>
     </sec:authentication-provider>
 </sec:authentication-manager>
 <sec:global-method-security pre-post-annotations="enabled"/>

[Tomcat only] in file conf/domibus/persistence.xml, add to the <persistence-unit> tag: <class>eu.domibus.plugin.ws.entity.AuthenticationEntry</class>.

Run the appropriate DB migration script.

Replace domibus.war and the plugin(s) jar(s) into /domibus/conf/domibus/plugins/lib"

For Tomcat installations only, the activemq.xml file has to be replaced and re-configured according to your environment (transportConnector uri, authenticationUser, redeliveryPolicy).

Update the configuration file following these steps:

In file "/domibus/conf/domibus/internal/ehcache.xml", add <cache name="certValidationByAlias" maxBytesLocalHeap="5m" timeToLiveSeconds="3600" overflowToDisk="false"/>.

In file "/domibus/conf/domibus/domibus-configuration.xml", replace class="eu.domibus.common.dao.CachingPModeProvider"/> by class="eu.domibus.ebms3.common.dao.CachingPModeProvider"/> or by class="eu.domibus.common.dao.PModeDao"/> if you are using Oracle DB:

Only for Tomcat users: in file "/domibus/conf/domibus/domibus-datasources.xml", replace

<amq:xaConnectionFactory id="xaJmsConnectionFactory" brokerURL="tcp://localhost:61616" userName="domibus" password="changeit"/>

<amq:xaConnectionFactory id="xaJmsConnectionFactory"
             brokerURL="tcp://localhost:61616"
             userName="domibus" password="changeit">
<!-- do not remove this! otherwise the redeliveryPolicy configured in activemq.xml will be ignored -->
<amq:redeliveryPolicy>
    <amq:redeliveryPolicy/>
</amq:redeliveryPolicy>
</amq:xaConnectionFactory>

Replace the war. This release updated the type of one column for the MySQL db. Please run the migration script.

Re-install the domibus-security.xml and re-configure the properties according with the installed Truststore and Keystore.

For Tomcat installations only, the activemq.xml has to be re-installed and re-configured and the domibus-ActiveMQ-ThroughputLimiter jar can be deleted.

There have been some changes to the database, please use the new scripts.

Run the migration script if you are upgrading from 3.0 to 3.1.

Replace the war and jar(plugins) files.

There have been some changes to the MessageFilter, please use a clean database.

Domibus 3.1 is a major release that has to be installed from scratch.

There have been some changes to the database, please use the new script.

There is a new PMode generation plugin available (BETA-3), use this to regenerate your PMode files.

Replace the war file.

Domibus 3.0 is a major release that has to be installed from scratch.

There is no available upgrade path.