Missing /standalone/tmp/dcm4chee-arc/xsl directory after deployment (dcm4chee-arc 5.34.2)

[Alieksandr Kuznietsov]

Hello,

I installed dcm4chee-arc 5.34.2 following the official installation guide.

Environment:OS: Debian 13

• Application server: WildFly 38.0.1

• Database: PostgreSQL 17

• LDAP: OpenLDAP (from Debian repository)

The installation and deployment completed without obvious errors. The archive server starts and works normally for storing and querying studies.

However, I noticed that the directory

/opt/wildfly/standalone/tmp/dcm4chee-arc

was not created after deployment.

In particular, the following files were missing:

/opt/wildfly/standalone/tmp/dcm4chee-arc/xsl/dsr2html.xsl

Because of this, the web viewer (Oviyam) could not display the contents of DICOM SR objects.

As a temporary workaround, I copied the entire dcm4chee-arc directory from another working server where the same version of dcm4chee is installed. After copying the directory into:

/opt/wildfly/standalone/tmp/

SR rendering started working correctly in Oviyam.

My questions:

1. Under normal circumstances, should the directory
   /standalone/tmp/dcm4chee-arc be automatically created during deployment or startup?

2. What component of the deployment process is responsible for extracting the XSL files such as dsr2html.xsl?

3. Is it expected that these files are located in standalone/tmp, or should they normally come from another location?

4. Could this be related to the combination of Debian 13 + WildFly 38 + PostgreSQL 17?

5. Is it safe to manually place this directory there, or is there a recommended way to regenerate it?

Any advice on how to properly diagnose this would be appreciated.

Thank you.