Every aspect of Arbortext Publishing Engine initialization and its operation is defined by its configuration file located in the install tree:

The XML document type it complies with is located in:

The configuration file can be edited using either a text editor or Arbortext Publishing Engine Interactive. On Windows, you can launch Arbortext Publishing Engine Configuration program, navigate to the Setup tab, and click Edit Configuration. The Configuration Guide for Arbortext Publishing Engine guide describes the e3config.xml file, its configuration settings, and how to edit it. You must restart Arbortext Publishing Engine for configurations changes to take effect.

The Arbortext PE Request Manager reads e3config.xml and parses its contents into objects as defined in the Java package com.arbortext.e3cf. During initialization, e3cf objects are passed to the init method of each dynamic component, so that they may retrieve their parameters. The e3cf objects are not used after initialization. Instead, the Arbortext Publishing Engine Request Context object offers methods for locating all instances of each type of dynamic component.

Almost every element in e3config.xml can have associated parameters. Parameters can be global or local. Global parameters are specified at the top level (descendants of the E3Config element). Local parameters are descendants of lower-level elements. Local parameters apply only to the object within which they are defined.

Every parameter is specified by a Parameter element with name and value attributes. If a local parameter has the same name as a global parameter, the local parameter value overrides the global value. For example, if the global parameter debug has the value false, you could specify a local debug parameter with the value true for a specific cache manager.