It’s a good idea to familiarize yourself with the default configuration settings so you can learn what parts of the UI are configurable and how to work with the tags in the task configuration file. Keep in mind that the default task configuration files cover a subset of the configuration options available to you.

As mentioned earlier, the Business Control Center comes with two task configuration files. The file in the AssetUI module provides basic settings; the file in DPS-UI module defines the appearance for additional activities and tasks. You can find the AssetUI taskConfiguration.xml in the <ATG10dir>/AssetUI/config.jar/atg/web/assetmanager/configuration directory.

The contents of the file are enclosed in a <task-configuration> tag. Inside it, the file is divided into three sections: one enclosed in a <default-activity> tag and two enclosed in <activity> tags.

The <default-activity> tag encloses the default resource bundle that contains the labels you see in the UI. An <activity> tag defines settings for a particular activity, which are combined with those provided by the <default-activity> tag. An activity can involve any operation, such as browsing targeters or modifying user items, as long as it doesn’t produce or affect versioned items. There are two types of activities:

The two activities defined in this task configuration file provide the foundation for the two types of activities used to access the Personalization parts of the Business Control Center. The first <activity> tag defines the structure of the UI—a JSP and a configuration component—and sets the mode to view-only. The second activity (assetManager.defaultEdit) inherits settings from the first (assetManager.defaultBrowse), but replaces view-only mode with edit.

The purpose of activities like these is to define settings that other activities may inherit. Generic activities exist as a mechanism for holding settings inherited by other resources and are not visible in the Business Control Center. The assetManager.defaultBrowse is the baseline for activities that provide view-only access to versionable items, and assetManager.defaultEdit is the baseline for activities that provide editable access to nonversionable items.

Some of the many configuration values specified in the default task configuration file are pointers to files used by various parts of the UI. All JSPs are located in the AssetManager.war file that you find in <ATG10dir>/AssetUI/j2ee-apps/AssetUI.ear. All other file locations are specified below.