5. Discusión global de los resultados de los trabajos compendiados
5.3 Cardiovasc Res 2011:89;843-851
You can use the Config Tool to edit the secure store of the AS Java on the one hand and the system settings for the AS Java (cluster-data) on the other. The area on the left in the Config Tool shows the breakdown of the structure of the cluster-data into “template settings” and “instance-specific settings”. You can make settings for applications (applications), managers (managers), services (services) and the log configuration (log configuration) at template level and individually for each instance.
The instances are displayed in the Config Tool with the instance number (leading zeros are omitted). See also the figure “Window Sections in the Config Tool”. The parameters of the selected elements are displayed and maintained in the window on the right of the Config Tool.
Caution: You may only use the Config Tool to change parameters if the affected instances of an SAP NetWeaver AS Java are stopped.
Figure 53: Window Sections in the Config Tool
In Release 7.10, the concept of Zero Administration was introduced in the AS Java. The aim is to simplify the technical configuration of the AS Java and to adjust it dynamically to changes in the system environment. Configuration templates are provided to implement the concept; they enable a simple adjustment of the AS Java configuration to the requirements of the installed product. In addition, dynamic configuration parameters that can be used to make changes, for example, to the hardware without reconfiguring the AS Java are introduced.
For example, the heap memory of the VM can be configured as a fraction of the physical RAM available or the number of server processes as a multiple of the available CPU.
The customer can continue to adjust the default settings that are delivered. However, the amount of effort required to make changes is less than in previous releases.
Furthermore, the template concept also enables the default settings to be updated smoothly via Support Packages without overwriting customer settings. The following figure shows the infrastructure of the AS Java configuration.
Figure 54: Configuration infrastructure
The developer determines the potential configuration settings of an application or a manager, or services and their default values (Default level). Changes to these default settings that are valid throughout the system can be made at Custom Global level.
The changes made there are retained if you switch from the template that is currently active to another template (and if these settings are not overwritten at template level).
Caution: Customer changes at Custom Global level are allowed but only if expressly instructed by SAP (documentation, SAP notes, SAP Support). For example, this is the case for some special configuration settings of the User Management Engine (UME).
SAP provides concrete default configuration settings for individual products with the templates (Template Default). The corresponding template is activated by the installation program (SAPinst) during the installation of the product. There are different templates for different products. For example, there is a large number of templates for SAP NetWeaver CE but not for SAP NetWeaver PI or SAP NetWeaver Portal. In the template, filter rules are used to decide which applications and services are already started when the system is started.
At template level, customer changes can be made using the Config Tool (Template Custom). These changes override the settings of the previous levels. If no instance-specific customer changes are made (Instance Custom), the settings apply at template level throughout the system.
Certain system parameters can be used for the dynamic configuration that are evaluated dynamically at runtime; for example, the number of processors, the working memory of the host that is physically available or the instance number. These parameters can also be set when customer changes are made.
You can display the parameters and their values in the Config Tool by selecting an instance in the Config Tool and then choosing the Instance Profile tab page. Some of these parameters can be set by setting profile parameters in the default profile or in the instance profile of the system.
Caution: The term Instance Profile is used in two ways. On the one hand, you have the Instance Profile as a file on the operating system with the name
<SID>_<instance name>_<host name>, for example P7T_J00_twdf9999.
On the other hand, the term Instance Profile refers to the collection of the dynamic configuration parameters of the AS Java.
Note: The dynamic parameters of the Instance Profile of the AS Java are named differently from the related profile parameters that are used in the profile files (default profile, instance profile) of the system.
The settings that can be configured on the different levels can be divided into the following areas:
• Number of Server Processes
• Runtime Filters
• Shared Memory
• Configuration of the Managers
• Configuration of the Services
• VM Parameters
– Memory Parameters – System Parameters – Additional Parameters
• Log Configuration
• Configuration of the Applications
The runtime filters are used to determine which applications and services are started when the system is started. The log configuration settings can also be made online using the SAP NetWeaver Administrator (NWA). The configuration of the applications is usually carried out using a special UI of the application, in some cases online in the NWA. Some services, for example the User Management Engine, provide an individual UI for online configuration.
Some of these settings options are described in more detail below, starting with the VM parameters. We will first take a look at the SAP JVM memory management to get a better understanding of these parameters.