Both sides previous revisionPrevious revisionNext revision | Previous revision |
711:install [2024/10/29 10:12] – Suess, Bernhard | 711:install [2025/06/12 09:34] (current) – [Stages installation on Windows] Suess, Bernhard |
---|
=== Establish database connection with MySQL === | === Establish database connection with MySQL === |
| |
* Download MySQL JDBC connector (Connector/J 8.0 Platform Independent) MySQL 8.0 | * Download MySQL JDBC connector (**Connector/J 9.x** -> **Platform Independent**) |
* Copy JDBC connector to ”<stages installation path>/stages/lib“ and rename the file mysql-connector-java-*-bin.jar to mysql.jar | * Copy JDBC connector file **mysql-connector-j-*.jar** to ”**<stages installation path>/stages/lib**“ and rename the file **mysql-connector-j-*.jar** to **mysql.jar** |
* Edit ”<Stages installation path>/stages/conf/database.properties“ appropriately like in the following example: | * Edit ”<Stages installation path>/stages/conf/database.properties“ appropriately like in the following example: |
<code> | |
| |
| <code -> |
torque.database.default.driver = com.mysql.cj.jdbc.Driver | torque.database.default.driver = com.mysql.cj.jdbc.Driver |
torque.database.default.adapter = DBMM | torque.database.default.adapter = DBMM |
torque.database.default.username = stages | torque.database.default.username = stages |
torque.database.default.password = pass | torque.database.default.password = pass |
| |
</code> | </code> |
| |
* Activate the configuration | * Activate the configuration |
* Windows Start Menu: Execute “Programs > Method Park > Stages > Update Configuration” | * Windows Start Menu: Execute “Programs > Method Park > Stages > Update Configuration” |
* Start Stages | * Start Stages |
* Windows: Start the services “Stages Search” and then “Stages” | * Windows: Start the services “Stages Search” and then “Stages” |
| |
=== Establish database connection with Oracle === | === Establish database connection with Oracle === |
* Edit ”<Stages installation path>/stages/conf/database.properties“ appropriately like in the following example: | * Edit ”<Stages installation path>/stages/conf/database.properties“ appropriately like in the following example: |
| |
<code> | <code -> |
## settings for oracle | ## settings for oracle |
torque.database.default.driver=oracle.jdbc.driver.OracleDriver | torque.database.default.driver=oracle.jdbc.driver.OracleDriver |
torque.database.default.username=<oracle-username> | torque.database.default.username=<oracle-username> |
torque.database.default.password=<oracle-password> | torque.database.default.password=<oracle-password> |
| |
</code> | </code> |
| |
| |
* Activate the configuration | * Activate the configuration |
* Windows Start Menu: Execute “Programs > Method Park > Stages > Update Configuration” | * Windows Start Menu: Execute “Programs > Method Park > Stages > Update Configuration” |
* Start Stages | * Start Stages |
* Windows: Start the services “Stages Search” and then “Stages” | * Windows: Start the services “Stages Search” and then “Stages” |
| |
| |
==== (Optional) Start without Root Privileges on Linux ==== | ==== (Optional) Start without Root Privileges on Linux ==== |
| |
Normally Stages is started by the "root" user and then drops its privileges to the "stages" user after successful startup. In high risk environments, Stages can now also be started with a user id other than root. It can be enabled via the ''STAGES_NONROOTSTART'' variable in ''…/bin/rc.conf''. If enabled, the same user id starting the service will also be used to run the service. | Normally Stages is started by the "root" user and then drops its privileges to the "stages" user after successful startup. Stages can also be started with a user id other than root. It can be enabled via the ''STAGES_NONROOTSTART'' variable in ''…/bin/rc.conf''. If enabled, the same user id starting the service will also be used to run the service. |
| |
Please note that privileged ports below 1024 cannot be opened in this configuration, so the normal HTTPS port 443 cannot be used. The non-root setting can only be used when the Tomcat connectors are configured to use ports higher than 1024 and e.g. a reverse proxy is being used to allow normal access via HTTPS. | Please note that privileged ports below 1024 cannot be opened in this configuration, so the normal HTTPS port 443 cannot be used. The non-root setting can only be used when the Tomcat connectors are configured to use ports higher than 1024 and e.g. a reverse proxy is being used to allow normal access via HTTPS. |