Deploying Next Step on JBoss / Wildfly

Edit on Github Send Feedback v2.2.0

Next Step is a backend service which manages operation steps and authentication methods. This chapter describes how to configure and deploy the Next Step application on JBoss / Wildfly.

JBoss Deployment Descriptor

Next Step contains the following configuration in jboss-deployment-structure.xml file for JBoss / Wildfly:

<?xml version="1.0"?>
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.3">
<deployment>
<exclude-subsystems>
<!-- disable the logging subsystem because the application manages its own logging independently -->
<subsystem name="logging" />
</exclude-subsystems>

<dependencies>
<module name="com.wultra.powerauth.nextstep.conf" />
</dependencies>

<local-last value="true" />
</deployment>
</jboss-deployment-structure>

The deployment descriptor requires configuration of the com.wultra.powerauth.nextstep.conf module.

JBoss Module for Next Step Configuration

Create a new module in PATH_TO_JBOSS/modules/system/layers/base/com/wultra/powerauth/nextstep/conf/main.

The files described below should be added into this folder.

Main Module Configuration

The module.xml configuration is used for module registration. It also adds resources from the module folder to classpath.

Next Step module configuration:

<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.3" name="com.wultra.powerauth.nextstep.conf">
    <resources>
        <resource-root path="." />
    </resources>
</module>

Logging Configuration

Use the logback.xml file to configure logging, for example:

<?xml version="1.0" encoding="UTF-8"?>
<configuration scan="true" scanPeriod="30 seconds">

        <property name="LOG_FILE_DIR" value="/var/log/powerauth" />
        <property name="LOG_FILE_NAME" value="nextstep" />
        <property name="INSTANCE_ID" value="${jboss.server.name}" />

        <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
                <file>${LOG_FILE_DIR}/${LOG_FILE_NAME}-${INSTANCE_ID}.log</file>
                <immediateFlush>true</immediateFlush>
                <rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy">
                        <fileNamePattern>${LOG_FILE_DIR}/${LOG_FILE_NAME}-${INSTANCE_ID}-%d{yyyy-MM-dd}-%i.log</fileNamePattern>
                        <maxFileSize>10MB</maxFileSize>
                        <maxHistory>5</maxHistory>
                        <totalSizeCap>100MB</totalSizeCap>
                </rollingPolicy>
                <encoder>
                        <charset>UTF-8</charset>
                        <pattern>%d{ISO8601} [%thread] %-5level %logger{36} - %msg%n</pattern>
                </encoder>
        </appender>

        <logger name="com.wultra" level="INFO" />

        <root level="INFO">
                <appender-ref ref="FILE" />
        </root>
</configuration>

Application Configuration

The application-ext.properties file is used to override default configuration properties, for example:

# Database Configuration
spring.datasource.jndi-name=java:/jdbc/powerauth

# PowerAuth Client configuration
powerauth.service.url=http://[host]:[port]/powerauth-java-server/rest

Mind that you should specify spring.datasource.jndi-name to use the application server datasource (its declaration is out of the scope of this guideline). When configure spring.datasource.url, the hikari connection pool is used. Spring Boot running on WildFly or JBoss initializes JtaTransactionManager.

The Next Step Spring application uses the ext Spring profile which activates overriding of default properties by application-ext.properties.

Last updated on Jun 23, 2026 (05:23) Edit on Github Send Feedback