The Config Tool provides offline configuration of the AS Java instances. It allows you to modify the properties of all services, managers, and applications. It also enables you to manage log configurations offline, add filters, and edit the JVM parameters.
When you run the AS Java Config Tool via a GUI or text-only interface, it connects to the database and scans the server configuration.
Each change you perform corresponds to a particular task in the BatchConfig tool. All modifications made using Config Tool can be exported to an XML file for later use.
Note
When you work offline, you do not need to have the AS Java running.
Config Tool connects directly to the database and applies the changes.
Config Tool Architecture
When Config Tool is running, it displays the cluster data and the secure store.
It contains the configuration template that is chosen during installation time. This template consists of:
Log configurations, applications, managers and services
These nodes contain template default data and custom data that is valid for all instances within the system.
All instances available in the cluster
Each instance contains a list of managers, services, log configurations and applications. These nodes have:
Inherited property data - this data corresponds to template default data.
Custom property data - consists of both inherited and custom values. The inherited values correspond to template custom ones. In case, there are no template custom values, the inherited values correspond to the template default ones.
The priority of the property values, in descending order, is:
. That is, for a certain property, the template default value is not valid if there is a template custom value, which is not valid if there is an instance value.This template is configured to apply the most suitable settings for a given configuration. Nevertheless, if you want to edit a property value, you can set a custom value to this property and it will have priority over the default value.
Use this tab to administer the secure store data of the AS Java system. You can also provide additional encryption of the secure store content.
More information: Managing Secure Store Data.
To start the Config Tool, double click the configtoolscript file from <SAP_install_dir>/<system_name>/<instance_name>/j2ee/configtool directory.
More information: Basic Features of the Config Tool
Example
If you set a custom value to a property in a manager in a particular instance, this value is valid only for this instance.
Example
If you set an inherited custom value to a property in a manager in a particular instance, this value is visible as an inherited value in the custom property data of the same manager in any instance. This value is valid only for instances that do not have a custom value previously set for this property.
To configure your AS Java, use the following options: