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
faq [2023/03/24 09:44] – [JIRA ticket with “stable URL” links] mdhtfaq [2024/03/20 12:30] (current) – [PDF Print is Running Forever] Geupel, Christian
Line 5: Line 5:
 ===== Generating Stages runtime information ===== ===== Generating Stages runtime information =====
  
-To analyze or reproduce a problem the Stages Support Team often asks to send the Stages runtime information to [[http://stages-support@ul.com|stages-support@ul.com]]. This is an archived set of Stages configuration and logfiles that gives detailed information on the Stages environment and can only be opened by the Stages Support Team.+To analyze or reproduce a problem the Stages Support team often asks to send the Stages runtime information to [[http://stages-support@ul.com|stages-support@ul.com]]. This is an archived set of Stages configuration and logfiles that provides detailed information on the Stages environment and can only be opened by the Stages Support team.
  
-If the .pks/.pks2 file created is too big for email transfer please use our upload form: [[https://upload.methodpark.de|https://upload.methodpark.de]]\\ +If the .pks/.pks2 file created is too big for email transfer please use our upload form: [[https://upload.methodpark.de|https://upload.methodpark.de]]\\  The requested **Ticket ID** to upload data is visible in the mail subject of the respective Stages Support mail:** [SupportID#1234567812345678]**
-The requested ** +
- <font inherit/inherit;;#c0392b;;inherit>Ticket ID</font>  **  to upload data is visible in the mail subject of the respective Stages Support mail:** [SupportID# +
- <font inherit/inherit;;#c0392b;;inherit>1234567812345678</font>  ]**+
  
 **Inside the Stages WebGUI** **Inside the Stages WebGUI**
  
-To create the Stages runtime information please login to Stages and click Administration > Search for Widget: Further Information > click: Runtime Information Download+To create the Stages runtime information please login to Stages and click Administration > search for widget: Further Information > click: Runtime Information Download
  
 **Manually on the Stages server** **Manually on the Stages server**
  
-If a login to the Stages WebGUI is not possible please proceed as follows:\\ +If login to the Stages WebGUI is not possible please proceed as follows:\\  \\  __Windows:__
-\\ +
-__Windows:__+
  
-   - Connect to your Stages Server e.g. via Remote Desktop Connection or login to your Stages Server directly+  - Connect to your Stages Server e.g. via Remote Desktop Connection or login to your Stages Server directly
   - On your Stages Server please open a command shell with administrative permissions   - On your Stages Server please open a command shell with administrative permissions
   - Navigate to folder: //<stages-installation-directory>\stages//\bin   - Navigate to folder: //<stages-installation-directory>\stages//\bin
Line 29: Line 24:
  
 __Linux:__ __Linux:__
 +
   - Connect to your Stages Server with a linux shell or login to your Stages Server directly   - Connect to your Stages Server with a linux shell or login to your Stages Server directly
-  - Navigate to folder: //<stages-installation-directory>/stages//  /etc +  - Navigate to folder: //<stages-installation-directory>/stages//  /bin 
-  - Execute command: **.\supportInfo.sh** +  - Execute command: **./supportInfo.sh** 
-  - Stages runtime information is created in the current directory. Filename is: **supportinfo-<timestamp>.pks2**+  - Stages runtime information is created in //<stages-installation-directory>//. Filename is: **supportinfo-<timestamp>.pks2** 
  
 ===== PDF Print is Running Forever ===== ===== PDF Print is Running Forever =====
Line 38: Line 35:
 PDF prints are running for a very long time and do not seem to ever finish. \\  \\ **Explanation:** \\ PDF prints are running for a very long time and do not seem to ever finish. \\  \\ **Explanation:** \\
 In order to print a PDF file the server may have to send requests to itself. However, in some network configurations with a proxy server it may not be able to do that, resulting in the server re-trying each request for a certain time before giving up (IO exception) and going on to the next request. \\  \\ In order to print a PDF file the server may have to send requests to itself. However, in some network configurations with a proxy server it may not be able to do that, resulting in the server re-trying each request for a certain time before giving up (IO exception) and going on to the next request. \\  \\
-In this case, adding the following property to config.xml will solve the problem: \\  \\ ''<property name="pdf.serverAddress" value="http:<Stages-Server-IP><:PORT (optional)>"/>'' \\  \\+In this case, adding the following property to config.xml will solve the problem: \\  \\ ''<property name="pdf.serverAddress" value="http://<Stages-Server-IP><:PORT (optional)>"/>'' \\  \\
 You may need to add the port; usually this is 8080 or 80 (depending on your configuration). \\ You may need to add the port; usually this is 8080 or 80 (depending on your configuration). \\
 Stages must be restarted after adding the property. Stages must be restarted after adding the property.
Line 97: Line 94:
 ===== STARTUP ERROR: "Couldn’t retrieve trigger: ..." ===== ===== STARTUP ERROR: "Couldn’t retrieve trigger: ..." =====
  
-After starting the Stages service the following error appears: \\ //org.quartz.JobPersistenceException: Couldn’t retrieve trigger: Table ‘stages.QRTZ_TRIGGERS’ doesn’t exist [See nested exception: java.SQLSybtaxErrorException: Table ‘stages.QRTZ_TRIGGERS’ doesn’t exist]// \\  \\ **Explanation:** \\ +After starting the Stages service the following error appears: \\ //org.quartz.JobPersistenceException: Couldn’t retrieve trigger: Table ‘stages.QRTZ_TRIGGERS’ doesn’t exist [See nested exception: java.SQLSybtaxErrorException: Table ‘stages.QRTZ_TRIGGERS’ doesn’t exist]// \\  \\ **Explanation:** \\  The following should be added to the [mysqld] section of your MySQL configuration: 
-The following should be added to the [mysqld] section of your MySQL configuration:+ 
 +''lower_case_table_names = 1'' \\  \\ **NOTE:** If you do this under Linux after MySQL has (ever) been started on the system you must reinstall MySQL, then insert the line in my.cnf, and only then start MySQL.
  
-''lower_case_table_names = 1'' \\  \\ 
- <font inherit/inherit;;#c0392b;;inherit>NOTE:</font>  If you do this under Linux after MySQL has (ever) been started on the system you must reinstall MySQL, then insert the line in my.cnf, and only then start MySQL. 
  
 ===== Is my Stages version compatible with oracle 19c? ===== ===== Is my Stages version compatible with oracle 19c? =====
Line 132: Line 128:
 The stable URL always contains the “Version number” embedded in link: The stable URL always contains the “Version number” embedded in link:
  
-stages.example.com/stages/#/workspace/100/ for%2025.01 /(process/activity/_LT2BcM7j89iq0vSy_p5cRA)+''stages.example.com/stages/#/workspace/100/**for%2025.01**/(process/activity/_LT2BcM7j89iq0vSy_p5cRA)''
  
-The link is stable in regard to__ releases of new process versions__. It is **not **stable in regard to __renaming process versions__.\\ +The link is stable in regard to__ releases of new process versions__. It is **not **stable in regard to __renaming process versions__.\\  We would generally advise against renaming process versions that have already been released or reviewed, as the corresponding version can then no longer be found under the released names. (So not only via link, but also from any review protocols in which the name is written).
-We would generally advise against renaming process versions that have already been released or reviewed, as the corresponding version can then no longer be found under the released names. (So not only via link, but also from any review protocols in which the name is written).+