Global and Local Properties 

Use

The SAP J2EE Engine components have two types of properties: global and local. Global properties are common for all cluster elements while local properties are only valid for a specific cluster element.

Each property has a default and a custom value. The default value of a property is assigned by the time of its creation. A subsequent change to the value of this property assigns and changes its custom value, without affecting the default one. When, for example, a property value is changed using the SETSP and SETMP shell commands or the Visual Administrator, this property is saved as a local property for the cluster element on which the change is made. If this property already exists as a local property, the value is stored as local custom, else new property is created and the value is stored as local default.

For more information about changing properties with shell commands, see ADMIN command group in the Reference Manual.

For more information about changing properties with the Visual Administrator, see Accessing Components in the Administration Manual.

Features

The value of a property is formed in the following way: if a custom value exists, this is the actual value of the property, else the default value is used.

The properties of the services and managers are formed by posting their local properties upon their global ones.

The property priority is as follows:

...

       1.      local custom – the highest priority;

       2.      local default

       3.      global custom

       4.      global default – the lowest priority;

All properties can be changed using the Configuration Editor (for more information about viewing or changing properties, see Configuration Adapter Service in the Administration Manual). If you have changed the default properties, you have to restart all cluster elements in order to apply the changes. Otherwise, you can only restart the cluster elements whose local properties have been changed.

Viewing Property Configurations

The global properties are common for all dispatcher and server elements. The configurations of this properties are situated in the following configuration Propertysheets (this Propertysheets can be seen using the Configuration Adapter Service):

...

       1.      Dispatcher elements:

                            a.      for managers: cluster_data/dispatcher/cfg/kernel/<manager_name>

                            b.      for services: cluster_data/dispatcher/cfg/services/<service_name>

       2.      Server elements:

                            a.      for managers: cluster_data/server/cfg/kernel/<manager_name>

                            b.      for services: cluster_data/server/cfg/services/<service_name>

The local properties are used on a particular dispatcher or server. The configurations of this properties are situated in the following configuration files:

...

       1.      Dispatcher elements

                            a.      for managers: cluster_data/dispatcher/<cluster_id>/kernel/<manager_name>

                            b.      for services: cluster_data/dispatcher/<cluster_id>/services/<service_name>

       2.      Server elements:

...

                            a.      for managers: cluster_data/server/<cluster_id>/kernel/<manager_name>

                            b.      for services: cluster_data/server/<cluster_id>/services/<service_name>