Installation Container
Orchestra Container
The Orchestra Container may include Orchestra Juno or an Orchestra installation with Tomcat as the application server.
The second option requires access to an external database and the appropriate configuration as described in the "Database Installation" chapters, including the corresponding database username and password.
Ports
The following ports can be forwarded:
- 8080:8080 --> cell.tunnel.client.http.port
- 8090:8090 --> ExtendedWebApp.servlet.port.http
- 8091:8091 --> ExtendedWebApp.servlet.port.https
- 8019:8019 --> Http.servlet.port.http
- 8894:8894 --> runtime.local.port
- 8443:8443 --> Http.servlet.port.https
- 8444:8444 --> servlet.port.https.auth
Non-Juno Container
A container with an Orchestra and Tomcat installation does not include the database within the container itself; it must connect to a database outside the Orchestra container.
The most common source of error is that the container cannot reach the database. Check if the environment settings are correct.
It is good practice to always start a container with the required settings (dependencies) defined in or taken from a compose file.
Starting with default settings may lead to issues with your projects if the container's dependencies change. The default dependencies belong to the image holder, who can modify these dependencies, potentially disrupting your project.
In the "docker-compose.yaml," all startup parameters and environment settings are stored.
Start the container with the command docker compose up or podman-compose up.
Configuration
To configure the environment, scenario, etc., use the Automatic Configuration feature.