|
|
# JBoss/Wildfly Application Server
|
|
|
# Wildfly Application Server
|
|
|
|
|
|
The installation of the application server should be done according to your system requirements and the instructions manual of the product. The webregistration has been tested and deployed in an standalone and domain mode environment and works in a cluster. The "standalone-full-ha" profile is needed for the application.
|
|
|
|
... | ... | @@ -10,21 +10,6 @@ It is advisable to not directly expose the application server. Consider the use |
|
|
|
|
|
There are some configurations, that have to be done on the application server. Wildfly offers multiple ways to change the configuration. For initial configuration you can edit the standalone-full-ha.xml file directly. If you want to make configurational changes while the application server is running, you will need to use JBoss CLI or the Webinterface.
|
|
|
|
|
|
## Database
|
|
|
|
|
|
The reg-app has been used and tested with PostgreSQL and MS SQL until now. It should also work with any other JPA compliant database, which Hibernate can use.
|
|
|
|
|
|
Please create an empty database for the product you will use. For PostgreSQL this can be achieved by:
|
|
|
|
|
|
```sh
|
|
|
su postgres
|
|
|
createuser -P bwidm-user
|
|
|
createdb -O bwidm-user bwidm
|
|
|
exit
|
|
|
```
|
|
|
|
|
|
Edit your pg_hba.conf file to allow authentication via md5 for bwidm-user from your host, which is running the application.
|
|
|
|
|
|
## Datasource
|
|
|
|
|
|
The reg-app needs a datasource to function. You can easily deploy a JDBC4 compliant driver via jar deployment on CLI for example like this:
|
... | ... | @@ -52,7 +37,7 @@ After the deployment of a suitable jdbc driver, you have to add the datasource. |
|
|
|
|
|
```
|
|
|
|
|
|
You should consider to enable pool constraints and checking mechanisms. More detailed instructions on datasources can be found on the Wildfly homepage: [DataSource configuration](https://docs.jboss.org/author/display/WFLY8/DataSource+configuration)
|
|
|
You should consider to enable pool constraints and checking mechanisms. More detailed instructions on datasources can be found on the Wildfly homepage: [DataSource configuration](https://docs.wildfly.org/19/wildscribe/subsystem/datasources/index.html)
|
|
|
|
|
|
## E-Mail Server
|
|
|
|
... | ... | @@ -76,7 +61,7 @@ It is necessary to configure a connection to an email server. The email property |
|
|
</socket-binding-group>
|
|
|
```
|
|
|
|
|
|
For more information visit the JBoss documentation for the [mail subsystem](https://docs.jboss.org/author/display/AS71/Mail+Subsystem?_sscc=t).
|
|
|
For more information visit the JBoss documentation for the [mail subsystem](https://docs.wildfly.org/19/wildscribe/subsystem/mail/index.html).
|
|
|
|
|
|
## JMS
|
|
|
|
... | ... | @@ -101,7 +86,7 @@ The java messaging subsystem of the reg-app needs two queues to process jobs. If |
|
|
</subsystem>
|
|
|
```
|
|
|
|
|
|
For the extensive configuration possibilities of the messaging subsystem see the Wildfly configuration Guide: [Messaging configuration](https://docs.jboss.org/author/display/WFLY8/Messaging+configuration)
|
|
|
For the extensive configuration possibilities of the messaging subsystem see the Wildfly configuration Guide: [Messaging configuration](https://docs.wildfly.org/19/wildscribe/subsystem/messaging-activemq/index.html)
|
|
|
|
|
|
## TLS LDAP connections
|
|
|
|
... | ... | |