4.1 Managing Files: Older Approach versus Using Advanced File Configurator

The following table lists the differences between the older way of managing files and managing through Advanced File Configurator:

Task

Older Approach

Advanced File Configurator

Tracking the customizations made in various files

Manual or script-based

Only administrators who modify the file are aware of changes.

Centralized

A list of all customizations is available in one place for tracking.

Improves efficiency and makes configuration management easy.

Restoring custom files while performing any of the following actions:

  • Upgrade

  • Revert

  • Disaster recovery

  • Add a node to a cluster

Manual and error-prone

Simplified

  • Reduces the possibilities of omissions of any configuration update due to human error after the product upgrade.

  • Enables to download all customized files together. The downloaded files can be used as a configuration backup.

  • Backs up all default files automatically that can be used for revert or recovery if needed.

Applying changes of a configuration file to all nodes in a cluster

Manual and time-consuming.

  • Difficult when the file is device-specific, such as server.xml.

  • Some files require manual changes using the vi editor instead of replacing it with the latest copy. For example, server.xml.

Changes in the file are applied to all cluster devices together by clicking Send Configurations to Servers.

No need to log in to each device separately and make the change on devices directly.

For example, to change the JVM heap memory size for Identity Server or Access Gateway, you can edit tomcat.conf in one place and send the change to all devices. You do not need to modify the file directly on each device.

While applying changes from server.xml, keystore password and server address in connector elements of server.xml is retained in each device. No need to manage this manually.

Logging

Not available

Automated