Updating J2EE parameters

To improve the performance and stability of the SAP J2EE engine the configuration parameters need to be updated.

This document relates to SAP instance: PRK

Document prepared by: BP ISDC Basis (Yong Chong Wee)Date: 11th May 2011

Contents1) Background...................................................................................................................................2

2) Updating the Dispatcher parameters of sapprkpas_PRK_00........................................................2

3) Updating the Server0 parameters of sapprkpas_PRK_00.............................................................4

4) Updating the Dispatcher parameters of sapprksas_PRK_00.........................................................6

5) Updating the Server0 parameters of sapprksas_PRK_00..............................................................8

6) Stop / Start SAP...........................................................................................................................10

1) Background

The SAP Max Attention report has highlighted a number of J2EE parameter changes required to improved performance and stability.

2) Updating the Dispatcher parameters of sapprkpas_PRK_00

To update the dispatcher parameters logon to SAP application instance server as <sid>adm and start the j2ee config tool.

2.1) Update Java start parameters

Once the j2ee config tool has started on the left hand pane click on instance_IDnnnnn -> dispatcher_IDnnnnnnn to bring up the current dispatcher start parameters

In the ‘Max heap size (in MB) field update the value from 170 to 256.

In the ‘Java Parameters’ section, make the following changes:

Current Parameter Value New Parameter value-Xms170M -Xms256M-XX:+PrintGCDetails <delete entry as not required for the dispatcher>-XX:+PrintGCTimeStamps <delete entry as not required for the dispatcher>

-XX:NewSize=28m <delete entry as not required for the dispatcher>-XX:MaxNewSize=28m <delete entry as not required for the dispatcher>

Press ‘Apply’ to save your changes.

2.2) Change the Log settings

Start the SAP j2ee Visual administrator and navigate to Dispatcher -> Services -> Log Configurator -> Runtime -> Categories. Select ‘Root Category’ and set the Severity to ‘ERROR’

Click the button ‘Copy severity to subtree’. Press ‘Yes, to the pop-up ‘Are you sure you want to set severity “ERROR” to all controllers under ‘“ROOT CATEGORY”?’. Then press save and select “Apply to all dispatcher nodes”

Now select Dispatcher -> Services -> Log Configurator -> Runtime -> Locations. Select ‘Root Location’ and set the Severity to ‘ERROR’. Click the button ‘Copy severity to subtree’. Press ‘Yes, to the pop-up ‘Are you sure you want to set severity “ERROR” to all controllers under ‘“ROOT LOCATION”?’. Then press save and select “Apply to all dispatcher nodes”

2.3) ThreadManager Properties

Property Name Description Current Value Recommended ValueInitialThreadCount Initial size of thread pool 40 50MinThreadCount Minimum size of thread

pool30 50

MaxThreadCount Maximum size of thread pool

70 200

ChangeThreadCountStep Number of threads added/removed when resizing the thread pool

10 50

I. Choose cluster-data ® template ® instance - <n> ® managers ® ThreadManager .II. From the list of properties, select the property whose value you want to change.

III. In the Custom value field, set the required value.

IV. To apply the new value, choose Set Custom Value.

V. To save the changes, choose Apply Changes.

3) Updating the Server0 parameters of sapprkpas_PRK_00

To update the Server0 parameters logon to SAP application instance server as <sid>adm and start the j2ee config tool.

3.1) Update Java start parameters of Server0

Once the j2ee config tool has started on the left hand pane click on instance_IDnnnnn -> server_IDnnnnnnn to bring up the current server start parameters

In the ‘Max heap size (in MB) field update the value from 1024 to 2048.

In the ‘Java Parameters’ section, make the following changes:

Current Parameter Value New Parameter value-Xms1024M -Xms2048MNot Set -Dfile.encoding=ISO-8859-1Not Set -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.s

ap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializerNot Set -XX:+HandlePromotionFailure-XX:MaxNewSize = 170m -XX:MaxNewSize = 341m-XX:NewSize = 170m -XX:NewSize = 341mNot Set -XX:ReservedCodeCacheSize = 64MNot Set -XX:CodeCacheMinimumFreeSpace=2M-XX:PermSize=192m -XX:PermSize=512m-XX:MaxPermSize=192m -XX:MaxPermSize=512m

Press ‘Apply’ to save your changes.

3.2) Change the Log settings

Start the SAP j2ee Visual administrator and navigate to Server 0 -> Services -> Log Configurator -> Runtime -> Categories. Select ‘Root Category’ and set the Severity to ‘ERROR’

Click the button ‘Copy severity to subtree’. Press ‘Yes, to the pop-up ‘Are you sure you want to set severity “ERROR” to all controllers under ‘“ROOT CATEGORY”?’. Then press save and select “Apply to all dispatcher nodes”

Now select Server 0 -> Services -> Log Configurator -> Runtime -> Locations. Select ‘Root Location’ and set the Severity to ‘ERROR’. Click the button ‘Copy severity to subtree’. Press ‘Yes, to the pop-up ‘Are you sure you want to set severity “ERROR” to all controllers under ‘“ROOT LOCATION”?’. Then press save and select “Apply to all dispatcher nodes”

3.3)Application ThreadManager Properties

Property Name Description Current Value Recommended ValueInitialThreadCount Minimum size of thread pool 40 10

I. Choose cluster-data ® template ® instance - <n> ® managers ®Application ThreadManager .

II. From the list of properties, select the property whose value you want to change.

III. In the Custom value field, set the required value.

IV. To apply the new value, choose Set Custom Value.

3.4) HTTP Provider Service Properties (Server Part)

Use the Visual Administrator and navigate to the HTTP provider service of the server.The "Cachecontrol" and "SapCacheControl" parameters are displayed on the "Properties" tab page.Parameter Description Current Value Recommended Value

CacheControl Static content expiration time in seconds (for browser cache)

N/A 604800

SapCacheControl Static content expiration time in seconds (for ICM

N/A 604800

cache)

Change the properties as recommended and press "Save".

3.5) Maximum JDBC ConnectionsUse the Config Tool to change the properties of the JDBC Connector (DB pool) globally. Open the Global Server Configuration and expand the "Services" and "dbpool" sections. Here you can change the value globally.

Parameter Description Current Value Recommend ValuesysDS.maximumConnections Maximum DB

connectionsN/A 50

4) Updating the Dispatcher parameters of sapprksas_PRK_00Once the j2ee config tool has started on the left hand pane click on instance_IDnnnnn -> dispatcher_IDnnnnnnn to bring up the current dispatcher start parameters

In the ‘Max heap size (in MB) field update the value from 170 to 256.

In the ‘Java Parameters’ section, make the following changes:

Current Parameter Value New Parameter value-Xms170M -Xms256M-XX:+PrintGCDetails <delete entry as not required for the dispatcher>-XX:+PrintGCTimeStamps <delete entry as not required for the dispatcher>-Xmx170m Do not set.Set Max heap size instead.

Press ‘Apply’ to save your changes.

4.1) Change the Log settings

Start the SAP j2ee Visual administrator and navigate to Dispatcher -> Services -> Log Configurator -> Runtime -> Categories. Select ‘Root Category’ and set the Severity to ‘ERROR’

Click the button ‘Copy severity to subtree’. Press ‘Yes, to the pop-up ‘Are you sure you want to set severity “ERROR” to all controllers under ‘“ROOT CATEGORY”?’. Then press save and select “Apply to all dispatcher nodes”

Now select Dispatcher -> Services -> Log Configurator -> Runtime -> Locations. Select ‘Root Location’ and set the Severity to ‘ERROR’. Click the button ‘Copy severity to subtree’. Press ‘Yes, to the pop-up ‘Are you sure you want to set severity “ERROR” to all controllers under ‘“ROOT LOCATION”?’. Then press save and select “Apply to all dispatcher nodes”

4.2) ThreadManager Properties

Property Name Description Current Value Recommended ValueInitialThreadCount Initial size of thread pool 40 50MinThreadCount Minimum size of thread

pool30 50

MaxThreadCount Maximum size of thread pool

70 200

ChangeThreadCountStep Number of threads added/removed when resizing the thread pool

10 50

I. Choose cluster-data ® template ® instance - <n> ® managers ®ThreadManager .II. From the list of properties, select the property whose value you want to change.

III. In the Custom value field, set the required value.

IV. To apply the new value, choose Set Custom Value.

V. To save the changes, choose Apply Changes.

5) Updating the Server0 parameters of sapprksas_PRK_00

To update the Server0 parameters logon to SAP application instance server as <sid>adm and start the j2ee config tool.

5.1) Update Java start parameters of Server0

Once the j2ee config tool has started on the left hand pane click on instance_IDnnnnn -> server_IDnnnnnnn to bring up the current server start parameters

In the ‘Max heap size (in MB) field update the value from 1024 to 2048.

In the ‘Java Parameters’ section, make the following changes:

Current Parameter Value New Parameter value-Xms1024M -Xms2048MNot Set -Dfile.encoding=ISO-8859-1Not Set -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.s

ap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializerNot Set -XX:+HandlePromotionFailure-XX:MaxNewSize = 160m -XX:MaxNewSize = 341m-XX:NewSize = 160m -XX:NewSize = 341mNot Set -XX:ReservedCodeCacheSize = 64MNot Set -XX:CodeCacheMinimumFreeSpace=2M-XX:PermSize=256m -XX:PermSize=512m-XX:MaxPermSize=256m -XX:MaxPermSize=512mNot Set -XX:ReservedCodeCacheSize=64MNot Set -XX:CodeCacheMinimumFreeSpace=2M

Press ‘Apply’ to save your changes.

3.2) Change the Log settings

Start the SAP j2ee Visual administrator and navigate to Server 0 -> Services -> Log Configurator -> Runtime -> Categories. Select ‘Root Category’ and set the Severity to ‘ERROR’

Click the button ‘Copy severity to subtree’. Press ‘Yes, to the pop-up ‘Are you sure you want to set severity “ERROR” to all controllers under ‘“ROOT CATEGORY”?’. Then press save and select “Apply to all dispatcher nodes”

Now select Server 0 -> Services -> Log Configurator -> Runtime -> Locations. Select ‘Root Location’ and set the Severity to ‘ERROR’. Click the button ‘Copy severity to subtree’. Press ‘Yes, to the pop-up ‘Are you sure you want to set severity “ERROR” to all controllers under ‘“ROOT LOCATION”?’. Then press save and select “Apply to all dispatcher nodes”

5.2)Application ThreadManager Properties

Property Name Description Current Value Recommended ValueInitialThreadCount Minimum size of thread

pool40 10

I. Choose cluster-data ® template ® instance - <n> ® managers ®Application ThreadManager .

II. From the list of properties, select the property whose value you want to change.

III. In the Custom value field, set the required value.

IV. To apply the new value, choose Set Custom Value.

For the changes to take effect, restart the cluster

5.3) HTTP Provider Service Properties (Server Part)

Use the Visual Administrator and navigate to the HTTP provider service of the server.The "Cachecontrol" and "SapCacheControl" parameters are displayed on the "Properties" tab page.Parameter Description Current Value Recommended Value

CacheControl Static content expiration time N/A 604800

in seconds (for browser cache)

SapCacheControl Static content expiration time in seconds (for ICM cache)

N/A 604800

Change the properties as recommended and press "Save".

5.4) Maximum JDBC ConnectionsUse the Config Tool to change the properties of the JDBC Connector (DB pool) globally. Open the Global Server Configuration and expand the "Services" and "dbpool" sections. Here you can change the value globally.

Parameter Description Current Value Recommend ValuesysDS.maximumConnections Maximum DB

connectionsN/A 50

6) Stop / Start SAP

To pick up the changes please stop and start the SAP instance. If it is easier you can just stop/start the Java part of the instance.