Stages Documentation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
75:install [2020/05/14 08:07] – [Install Fonts] twn75:install [2020/09/10 09:39] – [Perform basic installation] iolr
Line 75: Line 75:
 torque.database.default.username=<oracle-username> torque.database.default.username=<oracle-username>
 torque.database.default.password=<oracle-password> torque.database.default.password=<oracle-password>
 +
 +## hint: ensure that torque.database.default.adapter = DBMM is commented out or deleted
  
 </code> </code>
Line 95: Line 97:
  
 <code> <code>
-$JAVA_HOME/bin/keytool -importcert -alias MySQLCACert -file ca.pem -keystore truststore -storepass mypassword+$JAVA_HOME/bin/keytool -importcert -alias MySQLCACert -file ca.pem -keystore truststore.jks -storepass mypassword
  
 </code> </code>
Line 102: Line 104:
  
 <code> <code>
-&clientCertificateKeyStoreUrl=file:/opt/stages/conf/truststore&&useSSL=trueclientCertificateKeyStorePassword=mypassword+&clientCertificateKeyStoreUrl=file:/opt/stages/conf/truststore.jks&useSSL=true&clientCertificateKeyStorePassword=mypassword
  
 </code> </code>
Line 156: Line 158:
       * Execute command:** stages update**       * Execute command:** stages update**
       * Restart the Stages service: **stages start**       * Restart the Stages service: **stages start**
- 
- 
- 
  
 ===== Install Fonts ===== ===== Install Fonts =====
Line 184: Line 183:
       * Open file: "<Stages installation path>/stages/conf/config.xml"       * Open file: "<Stages installation path>/stages/conf/config.xml"
       * Adjust the following property: //<property name="pdf.font.list" value="/usr/share/fonts/TTF/arialuni.ttf"/>//       * Adjust the following property: //<property name="pdf.font.list" value="/usr/share/fonts/TTF/arialuni.ttf"/>//
- 
  
 ===== Install Stages license ===== ===== Install Stages license =====
Line 200: Line 198:
  
   * Ask for a DNS alias for the server, e.g. "stages.company.com"   * Ask for a DNS alias for the server, e.g. "stages.company.com"
-  * Ask for a SSL certificate for the server which refers to the above alias. Depending on your local procedures, this might require creating a certificate request (see [[https://www.digicert.com/csr-ssl-installation/tomcat-keytool.htm|https://www.digicert.com/csr-ssl-installation/tomcat-keytool.htm]] for more info).+  * Ask for a SSL certificate for the server which refers to the above alias. Depending on your local procedures, this might require creating a certificate request (see [[https://www.digicert.com/csr-ssl-installation/tomcat-keytool.htm|https://www.digicert.com/csr-ssl-installation/tomcat-keytool.htm]] for more info). If you are seeing "Invalid Certificate" errors in Chrome or Edge, add the "-ext SAN=dns:stages.yourcompany.com" argument to the keytool command and replace stages.yourcompany.com with the offical alias you use for accessing Stages.
   * Import the SSL certificate into a keystore (see link above for more info)   * Import the SSL certificate into a keystore (see link above for more info)
   * Configure Tomcat to use this SSL certificate (see link above for more info). The relevant Tomcat config file is located in ''conf/server.xml''  and the SSL info needs to be configured for each ''<Connector>''  section. After updating the config file, run ''bin/update.sh''  or ''bin\update.bat''  to install it at the correct location.   * Configure Tomcat to use this SSL certificate (see link above for more info). The relevant Tomcat config file is located in ''conf/server.xml''  and the SSL info needs to be configured for each ''<Connector>''  section. After updating the config file, run ''bin/update.sh''  or ''bin\update.bat''  to install it at the correct location.
-  * To enforce redirection from http to https add the following to ''conf/web-customer.xml''. This needs a Stages Version > 7.4.2.0.<code>+  * To enforce redirection from http to https add the following to ''conf/web-customer.xml''.<code>
  
 <security-constraint> <security-constraint>
Line 215: Line 213:
     </user-data-constraint>     </user-data-constraint>
 </security-constraint> </security-constraint>
- 
-</code> 
- 
-  * Enable global secure mode for Stages to set the neccessary headers for cross site scripting prevention in config.xml 
- 
-<code> 
-[...] 
-<properties> 
-    [...] 
-   <property name="global.secureMode.enabled" value="true"/> 
-</properties> 
-[...] 
  
 </code> </code>
Line 247: Line 233:
  
 Please contact your Method Park Product Consultant to further adapt the Stages process content for productive usage. Please contact your Method Park Product Consultant to further adapt the Stages process content for productive usage.
- 
-