This appendix describes unique topics when running HATS applications on a System z platform. It is expected that you also use the HATS User's and Administrator's Guide, the HATS Programmer's Guide, and the 2HATS Rich Client Platform Programmer's Guide as sources of information on HATS, and that you review the HATS Readme.
2 2 2There can be implications installing the .ear file on a z/OS platform. 2If you use WebSphere administrative console and browse to a local copy of the file, it is likely 2that you will receive the following error message:
2BBOO0271E HTTP REQUEST EXCEEDED 10485760 BYTE INPUT BUFFER2
The explanation for this message is:
2BruceG, I added all of this based on the info you supplied from the capacity 2guide. I have a few questions:
21. The capacity guide lists Servers?Application Servers?servername?Server 2Instance?Server Instance?Minimum Number of Instances and Servers?Application 2Servers?servername?Server Instance?Server Instance? Maximum Number of Instances. 2I assume Server Instance is only in the path once and not twice as shown above.
22. In java heap sizes it says garbage collection should be no more than 215% but in garbage collection it says should be 2%-5%. Which is correct?
23. In garbage collection, where do you set -Xgcpolicy=optavgpause?
24. In WebSphere variables what does "under Manage WebSphere Variables " 2refer to?
You can use the WebSphere administrative console to adjust the following settings and values 2which can enhance the performance of HATS applications running on a z/OS platform:
2On a z/OS platform, setting the Workload Profile parameter to LONGWAIT is important for 2application processing that involves sending or receiving information across 2a network. The LONGWAIT setting allows each 2servant region to have a pool of 40 threads to handle concurrent HATS requests. 2The default pool size is 4 threads. This parameter setting is important when 2sizing the number of servant regions.
2Find this parameter by navigating to Servers>Application 2Servers>servername>ORB Service>Advanced Settings>Workload Profile, where servername represents the name of your server.
2 2On a z/OS platform, HATS applications run in the WebSphere Application 2Server servant regions. If you specify LONGWAIT for the Workload Profile parameter, each 2servant region has a pool of 40 threads, . By default, there is only one servant 2region to handle all concurrent HATS requests. You can increase the number 2of servant regions to handle your application workload by setting the following 2parameters. In the parameter locations listed below, servername represents 2the name of your server.
2Find this parameter by navigating to Servers>Application 2Servers>servername>Server Instance>Multiple Instances Enabled.
2Find this parameter by 2navigating to Servers>Application Servers>servername>Server Instance>Minimum Number of Instances.
2Find this parameter by navigating to Servers>Application Servers>servername>Server Instance>Maximum 2Number of Instances.
2The Java heap parameters influence performance and the behavior of garbage 2collection. Larger heap sizes take longer to fill and longer to garbage collect. 2With large heap sizes, applications run longer before a garbage collection 2occurs, and it takes a longer time to perform the garbage collection. You should 2monitor garbage collection and adjust your heap sizes so that no more than 215% of the total execution time is spent in garbage collection. A good way 2to see what is going on with garbage collection is to use the JVM's verbose 2garbage collection option which is enabled by adding -verbosegc to 2the JVM arguments. Verbosegc provides an output file that gives the date and 2time of each garbage collection cycle. From the output file, you can calculate 2how much of the total execution time is spent in garbage collection.
2On a z/OS platform, there is a JVM in both the controller and the servant 2region. Usually, the JVM in the controller does not need to be tuned. This 2information applies to the JVM in the servant region.
2There are two JVM parameters that specify how much memory is allocated 2for the JVM heap. The settings of these two parameters will affect the performance 2of your HATS applications. In the parameter locations listed below, servername represents the name of your server.
2Find this parameter by navigating to Servers>Application Servers>servername>Process Definitions>JVM>Initial 2Heap Size.
2Find this parameter by navigating to Servers>Application 2Servers>servername>Process Definitions>JVM>Max Heap Size.
2The JVM memory management function, or garbage collection, provides one 2of the biggest opportunities for improving JVM performance.
2Garbage collection should normally consume from 2% to 5% of the total execution 2of a properly functioning application. It takes monitoring to understand the 2effects of garbage collection.
2If you have pause time problems which are denoted by erratic application 2response times which are caused by normal garbage collection, you should set -Xgcpolicy=optavgpause.
2 2In the Manage WebSphere Variables section 2of the WebSphere administrative console, navigate to Servers>Application 2Servers>servername>Custom Properties and add the variables 2listed below:
2 2