Lab tests prove having more processing power and memory increases performance. Increasing RAM by itself will provide a boost to performance numbers and help cache more screens.
Monitor the CPU usage over time and if the CPU % is consistently higher than 80%, it may indicate a need for more servers.
Monitor the total RAM used by the system. If the total RAM used by the system is 85% of the total available, then you will need to add more memory to the server. To find the memory used by HxGN EAM application, check the consumption by the process called Java.exe. The number of java processes is equal to the number of JVMs installed.
Total memory used by each JVM is calculated as follows:
JVM memory = JVM Max Size (MB) + MaxPermSize (MB)
Disk space
Ensure to have at least 5GB disk space available on the servers at all times.
SERVSTAT
Keep a log of the servstat activity on the server. The load average should be less than the total number of CPUs + 1 on the server to ensure optimal performance.
JBOSS JVM health check
systemCheck.jsp is available as part of the base install that can help in checking the overall health of the JVM on the application, web services and databridge server. This jsp exists to allow monitoring of the health of the application. When required URL parameters are added, it will invoke a java bean which will get a value from the database and respond with a numeric code (see error codes table) to indicate the result.
Example URL
http://myserver.HxGN.com/web/jsp/systemCheck.jsp?tenant=DS_MP_1&code=DEFLANG&value=EN&ports=1099,1199&minpercentfreemem=15
Example responses
Response |
Explanation |
Comment |
---|---|---|
jvm1=0,jvm2=0 |
Both jvms are successful |
jvm1 refers to the first port specified in the URL, jvm2 is the second, and so on. The successful response will always have each jvm# equal to zero and comma delimited. |
jvm1=0,jvm2=0 |
First jvm successful and second unsuccessful |
The response will usually indicate which jvm failed |
7 |
Invalid tenant specified in URL |
Some errors don't require attempt for each jvm, therefore the response will be a single error code |
Input parameters
Parameter |
Description |
---|---|
tenant |
The tenant to check |
code |
The install parameter code to get |
value |
The expected value of the install parameter |
ports |
Comma delimited ports. Specify the remote JNDI port for each jvm on the server. A single request to this jsp will check each specified port. Typically, for JBoss the first jvm would have the port 1099. Add 100 for each subsequent jvm. |
minpercentfreemem |
The minimum percentage of free jvm memory before receiving the low memory error code. Specify a value in the range 1 to 100. The default is 10. |
Error codes
Error code |
Description |
---|---|
0 |
Success |
1 |
Invalid or lost database connection |
2 |
Expected and actual install parameter values are different |
3 |
Invalid install parameter code |
4 |
JVM down or invalid port |
5 |
Application not deployed |
6 |
Required parameter missing |
7 |
Invalid tenant |
8 |
Unhandled exception |
9 |
Low memory |