Architecture

1 General Information
2 Central Database Servers
3 High Available Architecture
- 3.1 Database
- 3.2 Application server
- 3.3 Loadbalancer
- 3.4 Internet / Intranet

General Information

The application needs two components in order to be able to run.

Application Server (JBoss)
Database Server

Please refer to the https://tim-doc.atlassian.net/wiki/spaces/eng/pages/228036838 for detailed information on what versions are supported.

Please refer to https://tim-doc.atlassian.net/wiki/spaces/eng/pages/227675389 for detailed information on what hardware is required.

Central Database Servers

Most companies provide one or multiple central Database Servers which can be used in order to run the application with it. In this case, the data source just has to be set to the server of the central one. Detailed information can be found on the https://tim-doc.atlassian.net/wiki/spaces/eng/pages/227675389 page.

High Available Architecture

If it's necessary to make the application available for complex processes, a lot of users or just make it highly available it's possible to use this architecture in order to split resources and availability.

Database

It is possible to run the database as a standalone server or as a highly available system. In any way, the application is only able to connect to one database in order to run if there are multiple databases behind the balancing (e.g. Always-On).

Application server

Every application server must run in standalone mode for its own. If there are multiple nodes all of them connect to the same database even if it's clustered/always-on. For detailed information what hardware is required please refer to the .

Loadbalancer

When there are multiple nodes of the application server deployed it is recommended to establish a load balancer in front of them. If so the following Endpoint has to be forwarded:

/loom-portal/
/loom-ws/
/dashboard/
/dashboard-ws/
/tim/

The Loadbalancer has to be session sticky!

The timeout of requests should be unlimited because some requests take more than 5 minutes and the load balance must not kill the request!

Internet / Intranet

Both scenarios are possible and supported. If there is only one application server and no loadbalancer it depends on the company how the server is reachable from outside of the company. The most common way is a reverse proxy which tunnels the traffic.