Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
faq [2023/03/24 09:33] – [JIRA ticket with “stable URL” links] mdht | faq [2024/03/20 12:30] – [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 | + | To analyze or reproduce a problem the Stages Support |
- | If the .pks/.pks2 file created is too big for email transfer please use our upload form: [[https:// | + | If the .pks/.pks2 file created is too big for email transfer please use our upload form: [[https:// |
- | The requested ** | + | |
- | < | + | |
- | < | + | |
**Inside the Stages WebGUI** | **Inside the Stages WebGUI** | ||
- | To create the Stages runtime information please login to Stages and click Administration > Search | + | To create the Stages runtime information please login to Stages and click Administration > search |
**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: | + | |
- | - 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: //< | - Navigate to folder: //< | ||
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: //< | + | - Navigate to folder: //< |
- | - Execute command: **.\supportInfo.sh** | + | - Execute command: **./supportInfo.sh** |
- | - Stages runtime information is created in the current | + | - Stages runtime information is created in //< |
===== 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: \\ \\ ''< | + | In this case, adding the following property to config.xml will solve the problem: \\ \\ ''< |
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: " | ===== STARTUP ERROR: " | ||
- | After starting the Stages service the following error appears: \\ // | + | After starting the Stages service the following error appears: \\ // |
- | The following should be added to the [mysqld] section of your MySQL configuration: | + | |
+ | '' | ||
- | '' | ||
- | < | ||
===== Is my Stages version compatible with oracle 19c? ===== | ===== Is my Stages version compatible with oracle 19c? ===== | ||
Line 128: | Line 124: | ||
On the 15th of each month (or, if the 15th is on a weekend, on the following workday) Stages updates and OS security updates are performed on the productive SaaS servers. Therefore short outages may occur on these days. So please check a little later if the service is back up and running. | On the 15th of each month (or, if the 15th is on a weekend, on the following workday) Stages updates and OS security updates are performed on the productive SaaS servers. Therefore short outages may occur on these days. So please check a little later if the service is back up and running. | ||
- | ====== JIRA ticket with “stable URL” links ====== | + | ===== JIRA ticket with “stable URL” links ===== |
+ | |||
+ | The stable URL always contains the “Version number” embedded in link: | ||
- | The stable URL always contains the “Version number” embedded in link: [[https://stages.example.com/ | + | '' |
- | < | + | |
- | 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). | + | |