Friday, May 29, 2009

Zero Administration

Use

The main goal of Zero Administration is to simplify the technical configuration within the AS Java by removing all system-dependent settings from the configuration database. This is done via dynamic configuration which adapts itself to the system environment, and template-based configuration which ensures configuration consistency.

Zero Administration supports:

Built-in configuration templates.

System copies and load based installations without the need to adapt configuration manually.

Changing the system environment (system name, instance name, hosts and so on) without changing the configuration in the database.

Adding instances with a minimum configuration overhead.

Integration

The goals and benefits of Zero Administration are achieved by a set of new features within the Configuration Manager and the infrastructure itself.

Features

Zero Administration concept is implemented in:

Configuration Templates

Dynamic System Configuration

This graphic is explained in the accompanying text

AS Java Cluster Configuration Structure

The general AS Java cluster configuration structure consists of two levels:

...

Default system-independent configuration including configuration templates, which are provided during installation. A configuration template is derived from a default configuration and overwrites the setting according to the specific usage it is assigned to.

System configuration, including the actual configuration of the specific instances, which are part of the system. The instance configuration is derived from the configuration template belonging to the corresponding use case. The system-dependent configuration dynamically adapts itself to the actual system environment without overwriting any settings inherited from the template.

If you need to customize any additional AS Java components (for example landscape connectivity), you can do custom configuration within system configuration using the Config Tool. Custom configuration is stored separately and does not affect default configuration. Custom configuration changes are visible across all instances that are configured via the same configuration template.

If you want to customize a setting for one particular instance only, apply the change on the instance level.

More information about configuring the AS Java parameters using the Config Tool: Config Tool.

End of Content Area

1 comment:

seventyros said...

For a Excellent Online Resource for SAP EP and SAP Web Dynpro ABAP, Visit Learn SAP Online

Blog Archive