2. Mechanisms underlying the initiation and maintenance of atrial fibrillation
2.2 Mechanisms of arrhythmias: Implications in atrial fibrillation
2.2.3 Reentry
Change the number of server processes.
1. Stop your system.
2. Optional:
Set the number of server processes to 3 at template level.
3. Set the number of server processes for the Primary Application Server to 2.
4. Start your system.
Result
You have configured the number of server processes instance-specifically and for the whole system via the template custom settings. You can now check, for example using the SAP MC, whether the configured number can also be started.
You can see, that the instance specific settings have a higher priority than the template custom settings.
Solution 5: Configuration with the Config Tool
Task 1: VM Parameters
Make changes to the VM parameters of your system.
1. Stop your system.
a) Use the SAP MC or another tool to stop your system.
2. Add the VM paramerter -Dcom.sun.management.jmxremote as a new parameter of the type System at template level.
a) Double-click the file configtool.bat in the directory \usr\sap\<SID>\<in-stance>\j2ee\configtool to start the Config Tool. Choose Yes to confirm the dialog box.
b) Use View → Expert Mode to activate Expert Mode and select the entry template - ... Choose the tab page VM Parameters.
c) Choose the entry sap under Vendor and the entry GLOBAL under Platform, and then choose the tab page System.
d) Choose New and enter the value com.sun.management.jmxremote in the field Name (without '-D'):. Leave the other fields empty and choose OK to confirm.
e) Choose File → Apply Changes to save your changes.
f) Deactivate Expert Mode under File → Expert Mode.
3. Change the maxHeapSize for the Primary Applications Server (PAS) to the value 4096.
a) Select the entry instance - ID.... of your Primary Application Server (PAS).
If required the instructor can give you the correct instance ID. Note that the leading zeros are omitted.
b) Choose the tab page VM Parameters and then the tab page Memory.
c) Select the line maxHeapSize.
d) Enter the value 4096 in the field Custom value and choose Set.
e) Choose File → Apply Changes to save your changes.
4. Start your system.
a) Use the SAP MC or another tool to start your system.
Result
The changed values are now used by the respective VM. You can check them, for example, by opening the file dev_server0 in the work directory of the PAS and searching for the entries -Xmx4096m and -Dcom.sun.management.jmxremote.
Task 2: Thread Manager
Change the properties of the Thread Manager.
1. Stop your system.
a) Use the SAP MC or another tool to stop your system.
2. Change the parameter InitialThreadCount of the Thread Manager at template level to the value 20.
a) Double-click the file configtool.bat in the directory \usr\sap\<SID>\<in-stance>\j2ee\configtool to start the Config Tool. Choose Yes to confirm the dialog box.
b) Go to template - .... → managers → ThreadManager.
c) Select the line InitialThreadCount.
d) Enter the value 20 in the field Custom value and choose Set.
e) Choose File → Apply Changes to save your changes.
3. Change the parameter InitialThreadCount of the Thread Manager for an instance of your system to the value 10.
a) Go to instance - ID.... → managers → ThreadManager.
b) Select the line InitialThreadCount.
c) Enter the value 10 in the field Custom value and choose Set.
d) Choose File → Apply Changes to save your changes.
4. Start your system.
a) Use the SAP MC or another tool to start your system.
Result
You have maintained different values for the instances of your system for the parameter InitialThreadCount.
Task 3: Filter Rules
Define your own filter rule at template level.
1. Stop your system.
a) Use the SAP MC or another tool to stop your system.
2. Define a filter rule that stops all applications with the Component Name Mask tc~sld~wd*.
a) Double-click the file configtool.bat in the directory \usr\sap\<SID>\<in-stance>\j2ee\configtool to start the Config Tool. Choose Yes to confirm the dialog box.
b) Use View → Expert Mode to activate Expert Mode and select the entry template - ... Select the tab page Filters.
c) Choose the value stop under Action. Enter the value * in the field Vendor Mask. Enter the value tc~sld~wd* in the field Component Name Mask.
Choose the value Application under Component.
d) Choose Add.
e) Choose File → Apply Changes to save your changes.
f) Deactivate Expert Mode under File → Expert Mode.
3. Start your system.
a) Use the SAP MC or another tool to start your system.
Result
You have created a filter rule, which ensures that all applications beginning with tc~sld~wd* remain stopped when the system is started. Go to Operation → Systems → Start & Stop → Java Applications in the SAP NetWeaver Administrator (NWA) to check this.
Task 4: Number of Server Processes
Change the number of server processes.
1. Stop your system.
a) Use the SAP MC or another tool to stop your system.
2. Optional:
Set the number of server processes to 3 at template level.
a) Double-click the file configtool.bat in the directory \usr\sap\<SID>\<in-stance>\j2ee\configtool to start the Config Tool. Choose Yes to confirm the dialog box.
b) Select the entry template - ... Choose the Servers tab page.
c) Enter the value3 in the field Custom Number of Server Processes.
d) Choose Set.
e) Choose File → Apply Changes to save your changes.
3. Set the number of server processes for the Primary Application Server to 2.
a) Select the entry instance - ID.... of your Primary Application Server (PAS).
If required the instructor can give you the correct instance ID. Note that the leading zeros are omitted.
b) Choose the Servers tab page.
c) Enter the value 2 in the field Custom number of server nodes.
d) Choose Set.
e) Choose File → Apply Changes to save your changes.
4. Start your system.
a) Use the SAP MC or another tool to start your system.
Result
You have configured the number of server processes instance-specifically and for the whole system via the template custom settings. You can now check, for example using the SAP MC, whether the configured number can also be started. You can see, that the instance specific settings have a higher priority than the template custom settings.
Lesson Summary
You should now be able to:
• Maintain settings for the SAP NetWeaver AS Java with the Config Tool