TODO - Wildfly Application Server configuration
- Holger Hagen (Unlicensed)
- Yakup Ensar Evli (Unlicensed)
As TASKANA is a pure Java application, there is a huge variety of options how to deploy and use TASKANA on Wildfly.
However we do have an integration test to ensure a compatibility with Wildfly. In this setup we use the REST module of TASKANA and deploy it to Wildfly as a web application. You have to keep in mind that the TASKANA REST module is based on the Spring Framework. The setup we are using can be found on GitHub: taskana/rest/taskana-rest-spring-example-wildfly at master · Taskana/taskana
This setup is described in more detail on this page. However you are free and encouraged to change each configuration to your own needs.
Application Assembly
Required Dependencies
To create your own Wildfly application, you need to add this dependency for the REST controllers including the entire TASKANA functionality:
<dependency>
<groupId>pro.taskana</groupId>
<artifactId>taskana-rest-spring</artifactId>
</dependency>If you want the UI to be part of the application, add this dependency as well:
<dependency>
<groupId>pro.taskana</groupId>
<artifactId>taskana-web</artifactId>
</dependency>Thats’s all.
For the example application, we use this Maven dependency, as it contains the sample data in addition to the two mentioned dependencies above:
<dependency>
<groupId>pro.taskana</groupId>
<artifactId>taskana-rest-spring-example-common</artifactId>
</dependency>You can find the entire project structure on GitHub: taskana/rest/taskana-rest-spring-example-wildfly/pom.xml at master · Taskana/taskana
Security
TASKANA requires a initialized JAAS Subject to work - at least as long you want to use the security features.
In our setup we have a Elytron setup, which ensures that all requests are authenticated and authorized before entering our application. We can find the details of the current user in the SecurityIdentity Elytron provides. To make this information accessible to TASKANA, we have created the ElytronToJaasFilter, to initialize a valid Subject from it. This filter is configured in our WildflyWebSecurityConfig:
Configuration
application.properties
You need to configure on the appplication side is the datasource and the database schema to use:
Furthermore, if you are using LDAP, you need to configure the LDAP access:
These properties are used to do a LDAP lookup from the AccessIdController, as it is required for the Admin UI for example. It has nothing to do with the authentication of a user, which is handled by Elytron as described above.
You can find the entire example file on GitHub: taskana/rest/taskana-rest-spring-example-wildfly/src/main/resources/application.properties at master · Taskana/taskana
web.xml
Nothing specific to TASKANA but you might need to specify the realm on Wildfly. In our example we do need to do this to make the FORM login work:
jboss-web.xml
In this file you meght want to change the context-root and and security-domain to match your configuration:
Server Configuration
This page is not meant to be a guide for configuring Wildfly. We just want to point out a few things we configured for our standalone example. The configuration we are using is also fed into our automated Arquillian integration test and can be found on GitHub: taskana/rest/taskana-rest-spring-example-wildfly/src/test/resources/int-test-standalone.xml at master · Taskana/taskana
Database
We need to configure the TASKANA datasource.
Please be aware that we currently do not support XA datasources.
Security
In our example we have configured our dedicated LDAP Security Domain with all dependent configurations. The LDAP points to an embedded LDAP of our application. This is quite unusual but makes it easy to have a working security test environment without an large setup with different component.
From the TASKANA point of view, you can use every security option provided by Wildfly, as long as you have an correctly initialized SecurityIdentity object later on, which the filter can process.