IBM Tivoli and Cisco manual Building the remediation workflows, 417

You can build similar pages for all of the compliance checks described in your policy. In the next section we provide the detailed steps to build the remediation workflows called when the user clicks the Fix Now button on the remediation user interface.

8.4 Building the remediation workflows

The complexity of creating the actual remediation packages can vary greatly depending on what you are trying to achieve and your Tivoli Configuration Manager skills.

The remediation packages are called remediation workflows because of the Tivoli Provisioning Manager heritage. In the current version of the solution they resemble the normal software package block files published on the Tivoli Configuration Manager Web Gateway server and installed locally on the

noncompliant workstation using the standalone Tivoli Configuration Manager commands. However, in this book we use the terms remediation workflow and remediation package interchangeably.

Software package block (SPB) is a native format of the Tivoli software distribution products, used with Tivoli Configuration Manager as well as with the latest version of Tivoli Provisioning Manager and Tivoli Provisioning Manager for Software.

You can create and edit SPB packages using several different tools, like:

￿The Java-based Software Package Editor included with Tivoli Configuration Manager

￿Command-line tools

￿The Eclipse-based Software Package Editor included with Tivoli Provisioning Manager for Software

In addition to the choices listed above you can use the sputil.sh utility provided with the IISSCN extension pack2 for Tivoli Configuration Manager, which is a

wrapper for Tivoli Configuration Manager commands.

As this book is not meant to be a comprehensive Tivoli Configuration Manager manual, in the next paragraphs we describe how to use this utility to build the remediation packages required for the policies we have defined in 6.2.4, “Customization of compliance policies” on page 161.

Chapter 8. Remediation subsystem implementation 417