IBM Tivoli and Cisco manual 399, Directory structure for Html pages

The checks defined by the particular compliance objects within the policy relate to the data gathered by one posture collector. This means that the individual violations are collector-related, and this determines the way the HTML pages are organized. Figure 8-33shows the directory structure that is required for the pages to be displayed properly.

Figure 8-33 Directory structure for HTML pages

The first directory level below the scripts directory must be named after the collector (for example, nac.win.any.service.PostureServices). The next level below has to contain a separate directory for each language setting. For this book we use US English, so the subdirectory is named en_US.

The HTML displayed to the user is determined by searching the scripts tree starting with a best-case (most specific) match, and working upwards until a worst-case (default, no specific) match is found.

All pages must be named one of the following case-sensitive names:

￿default.html

￿PASS.html

￿WARN.html

￿FAIL.html

￿ERROR.html

Additionally, all pages must be located in a subdirectory named from the ISO language/locale code the pages are written and encoded in. For example, Polish

Chapter 8. Remediation subsystem implementation 399