Differences

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

Link to this comparison view

Next revision
Previous revision
72:general_configuration [2018/07/16 19:06] – created bkkr72:general_configuration [2024/02/15 00:00] (current) – external edit 127.0.0.1
Line 5: Line 5:
 === Configuration File === === Configuration File ===
  
-Stages can be configured in the <StagesInstallDir>/tomcat/webapps/pkit/WEB-INF/conf/ PKitConfig.xml configuration file. In its properties section some parameters can be configured by introducing name-value pairs. For information about existing configuration parameters and their effect please contact the Stages support.+Stages can be configured in the ''<StagesInstallDir>/conf/config.xml'' configuration file. In its properties section some parameters can be configured by introducing name-value pairs. For information about existing configuration parameters and their effect please contact the Stages support.
  
 The following code configures a value of “value.of.property” for the configuration property “name.of.property”: The following code configures a value of “value.of.property” for the configuration property “name.of.property”:
  
-<code><properties>+<code> 
 +<properties>
  <property name="name.of.property" value="value.of.property"/>  <property name="name.of.property" value="value.of.property"/>
 </properties> </properties>
 +
 </code> </code>
 +
 === Configuration of Stages Service Parameter === === Configuration of Stages Service Parameter ===
  
-Stages service can be configured in the tomcat service configuration GUI<StagesInstallDir>\tomcat \bin\tomcatw.exe. To start the tomcat GUIplease run the following command in MS-DOS shell: +For configuring Stages service please proceed as follows:
- +
-''bin>tomcatw.exe //ES//projectkit'' +
- +
-In the Java tab you can configure additional Java start parameter for Stages that are listed below: +
- +
-  * +
- +
-Xmx (Max memory pool): 1024 MB +
- +
-  * +
- +
-Xms (Initial memory pool): 512 MB +
- +
-  * +
- +
-Remote monitoring of Stages application via JConsole or SVisualVM +
- +
-      * +
- +
-​​​Dcom.sun.management.jmxremote.port=8055 +
- +
-      * +
- +
-Dcom.sun.management.jmxremote.authenticate=false +
- +
-      * +
- +
-Dcom.sun.management.jmxremote.ssl=false +
- +
-  * +
- +
-Set Option for not garbage collected Java heap size, the so called permanent generation: +
- +
-      *+
  
-XX:MaxPermSize=256m+  * Windows: 
 +      * Open file "<Stages installation path>\stages\config.bat" 
 +      * Modify the red colored setting: //set TOMCAT_OPTS=–JvmMx=<RAM in MB>// 
 +      * Open a cmd with administrative permissions and navigate to folder "<Stages installation path>\stages\bin" 
 +      * Reinstall the Stages service: **reinstallService.bat** 
 +      * Restart Stages service: **net start stages** 
 +  * Linux: 
 +      * Open file "<Stages installation path>/stages/bin/rc.conf" 
 +      * Modify the red colored value: //CONF_TOMCAT_OPTS="-Xmx<RAM in MB>m -XX:+UseG1GC -XX_-OmitStackTraceInFastThrow"// 
 +      * Restart the Stages service:** stages restart**
  
-      *+You can configure additional Java start parameter for Stages that are listed below:
  
-XX:PermSize=256m+  * -Xmx (Max memory pool)4048 MB 
 +  * -Xms (Initial memory pool): 4048 MB 
 +  * Remote monitoring of Stages application via JConsole or JVisualVM 
 +      * ​​​-Dcom.sun.management.jmxremote.port=8055 
 +      * -Dcom.sun.management.jmxremote.authenticate=false 
 +      * -Dcom.sun.management.jmxremote.ssl=false