Executing a Template

Use the Configuration Template Definition page to add or delete plug-ins, check the plug-in dependency, execute a configuration, and monitor a configuration.

Access the Configuration Template Definition page using the following navigation path:

PeopleTools, and then Automated Config Manager, and then ACM Templates, and then Define ACM Templates

This example illustrates the fields and controls on the Configuration Template Definition page. You can find definitions for the fields and controls later on this page.

Configuration Template Definition page
Field or Control Description

Template Name

The name of the template that is entered while creating a template.

The template name cannot be edited.

Group

A group enables you to create a functional grouping of plug-ins related to a configuration. For example, you can group plug-ins related to Integration Broker configuration.

You may add multiple groups In a template to configure different products. For example, you can add a group of plug-ins that configure the Search Framework in addition to Integration Broker.

Plugin

Use the check box to select a plug-in that you want to include in the configuration program run.

Dependency Check iconDependency Check

Click the Dependency Check icon to review whether any dependencies exist for the current plug-in. If any dependency exists, you must execute the plug-in before you run the current configuration plug-in.

Properties iconProperties

Click the Properties icon to review the values that are defined for each property and edit if needed. If you do not edit any of the properties, the default property values will be used in the configuration program run.

Pre/Post Condition

Enables you to add control over the configuration template execution by specifying conditions that may need to be in place prior to a configuration plug-in execution or by specifying how the execution should behave after it has run. This is described in more detail in a subsequent section.

For more information on handling errors and setting preconditions and post-conditions, see Handling Errors During Plug-in Execution.

Edit Template Variables

Click the Edit Template Variables link to review the property values that will be used at run time. The template variables are common to all the groups within a template.

Configuration Monitor

After clicking the Execute button to commence a configuration program run, click the Configuration Monitor link to review the configuration program status.

See Monitoring a Configuration.

Process Monitor

Click the Process Monitor link to review the process status.

The Process Monitor link is active only if the processing mode is Scheduled.

See Scheduling An Automated Configuration in PIA.

Save

If you modify a template, save the template before running the configuration program.

Execute

Click to execute a configuration program run.

After clicking Execute and allowing processing to complete, the system displays the overall status of the request using an icon, such as the Success icon or the Error icon, with the text: Process completed. Click Configuration Monitor for details. The message that you see depends on the processing mode you selected in the ACM Options page.

Functional Validation

Click to verify the subsystems related to the product configuration. This does not report as to whether the configuration process succeeded. It reports whether the various pieces of the system interrelate successfully. You can access the report using the Configuration Monitor.

For more information on this option, see Running Functional Validation.

After clicking Functional Validation and allowing processing to complete, the system displays the overall status of the request using an icon, such as the Success icon or the Error icon, with the text: Process completed. Click Configuration Monitor for details.

Resolve Dependency

Click to resolve dependencies between plug-ins and plug-in groups within the configuration template definition. While this is a dynamic process, meta data related to plug-in dependency needs to have been established.

For more information on working with plug-in dependency, see Managing Configuration Plug-in Dependency.