Filter
Top Products
122 Building a Network Access Control Solution with IBM Tivoli and Cisco Systems
Remediation subsystem
The remediation subsystem has three components:
IBM Tivoli Configuration Manager server
Software Package Web Server
Remediation handler
IBM Tivoli Configuration Manager server
The Tivoli Configuration Manager supports a wide range of architecture types as
well as a range of installation topologies (one-node, two-node, and three-node).
The resulting multitude of combinations is well beyond the scope of this book.
While we wrote this book, the current version of the remediation server was
4.2.3. For the list of supported operating systems types consult the IBM Support
Web site at:
http://www.ibm.com/software/sysmgmt/products/support/Tivoli_Supported_Platforms
.html
We assumed that ABBC has the base IBM Tivoli Configuration Manager Version
4.2.3 server installed and configured, as it is used by the Operations department
for Software Distribution and Inventory.
In 8.2.2, “Tivoli Configuration Manager” on page 359, the installation of the
additionally required
Web Gateway component is performed. The system used by
ABBC for the remediation server is configured as follows:
Windows 2003 Server Enterprise Edition with SP1 installed
Pentium IV @ 3.0Ghz CPU
1024 MB of system memory
4 GB of free disk space
The following middleware components are installed as prerequisites:
– WebSphere Application Server 5.1.1.11
– IBM HTTP Server 1.3.28
– DB2 Universal Database™ Enterprise Edition 8.2
Software Package Web Server
This J2EE™ application is the interface element between remediation handler
and Tivoli Configuration Manager Web Gateway. It is delivered with IISSCN
extension pack2 for Tivoli Configuration Manager in the form of an installable
Note: We have tested these components also on the RedHat Linux Enterprise
Server 4.0 Update 4 running on the same type of server, but for the purpose of
the book all of the images and paths were documented from the Windows
installation.