Content of the delivery

New configuration requirement – obligatory transaction manager node ID setting (starting with 9.14.2.12)

A unique identifier for the WildFly/JBoss transaction manager instance must be defined. In a multi-node environment, each application server instance must have a unique value. This also applies when instances use different database schemas (effectively representing different ImageMaster environments) but connect to the same database server. This identifier distinguishes a given server’s transactions from all others and enables correct XA recovery. Once set, this value must not be changed for a server that has pending or in-doubt transactions.

• Recommended:

  Pass the value as a JVM system property configured in standalone.conf using:

  -Djboss.tx.node.id=<unique-node-id>

• Not recommended:

  Setting it in the <system-properties> section of standalone.xml because the transactions subsystem may initialize before that section is parsed.

Default configuration change starting with 9.13.1.2

HTTP2 in combination with Firefox and WildFly 26.1.3 can lead to blocked responses. (JBoss is not affected.) As a consequence, HTTP2 is disabled by the installation scripts starting with 9.13.1.2 and should not be enabled manually.

ImageMaster Processing Services

ImageMaster Processing Services provide a powerful, scalable platform for asynchronous document processing flows. This component enables organizations to design, implement, and manage complex document processing pipelines with visual flow-based programming.

The Processing Services support typical enterprise content management operations through specialized processor groups:

• Document Processing Services: Handles document lifecycle operations including creation, update, deletion, and export flows

Key capabilities include:

• Visual flow design and monitoring through an intuitive user interface

• Scalable batch processing for high-volume document operations

• Support for complex transformations with multi-file attachments (zip/tar containers)

• Flexible attribute mapping between source systems and ImageMaster document types

• Smart update functionality that automatically creates new documents or updates existing ones based on configurable search criteria

• Error handling capabilities through dedicated error queues

• Performance-optimized for processing millions of documents per day

The Processing Services integrate seamlessly with existing ImageMaster components, respecting all permission models, retention rules, and audit requirements. Custom processors can be developed to address specific project requirements while maintaining compatibility with the standard ImageMaster processing framework.

A dedicated delivery package is provided for the Processing Services, which includes developer documentation:

• Processing Services delivery package:

  ima-processing-services-assembly-<version>.zip

• HTML help artifact included in ZIP file in delivery package [WS PS]:

  ImageMaster-Document-Processing-Services-Help-<version>.html

  This HTML help also lists the prerequisites (e. g. required JDK and NiFi framework version).

Also see the Integration Service system manual Applicable documents, section “Processing Services”, for some technical background.