4.2.3 Comparing Configuration Files

Advanced File Configurator provides a tool for comparing and modifying files and folders. Using this tool, you can perform the following actions:

  • Compare a file with the same file from a specific device. You can select a folder also for comparison. If you select a folder, all files of that folder become available in the tool for comparison. You can compare the files one after the other.

  • Modify a file.

  • Undo changes you made in a single file or multiple files.

  • Download files for offline modifications.

You can access the tool on the following pages:

  • Add Configuration

  • Edit Configuration

Understanding the Compare View

Files are highlighted in different colors based on the comparison between the current and server files. The following table lists various indicators on the File Editor page:



No color

Both the current file and the fetched file are identical.


This is a new file in Advanced File Configurator for this cluster. This file is not available on the server selected for comparison.


The file exists on the server and Advanced File Configurator. However, the content of files or folders differ.


The current file is modified in File Editor.

Comparing and Modifying Files and Folders in File Editor

  1. On the Add Configuration or Edit Configuration page, turn on File Editor.



    Compare a file while adding it

    Turn on the File > File Editor toggle on the Add Configuration page. See Adding Configurations to a Cluster.

    Compare a file while editing it

    Turn on the File > File Editor toggle on the Edit Configuration page. See Modifying Configurations.

  2. In File Editor, turn on Compare with a server file.

  3. In Select Device, select the device from which you want to import files to compare, and click Fetch.

  4. In Files, select the file that you want to compare. The file opens in Current File.

    If you have imported a folder for comparison, select files one after the other for comparison.

  5. The corresponding fetched file opens in Server File. For example, if you have selected web.xml in Files, Server File displays web.xml imported from the selected device.

  6. Now, you can perform the following actions:

    • Compare both files.

    • Modify the current file.

    • Undo changes made in the current file. If you have made any change in the current file and want to undo it, click the revert icon in Current File. To undo all changes, click the revert icon in Files.

    • Download files for offline modifications. You can fetch a file or folder and download it for offline modification.

      For example, you can fetch and download files if you require making considerable changes in configurations. You can modify files offline, verify the changes, and then upload it to the appropriate cluster.

      The files are downloaded in the ZIP format. The ZIP file contains the file that you select for the comparison and the file from the server. Similarly, you can download multiple files also if you have selected a folder for comparison.

  7. Click Save.

Managing server.xml Changes

The server.xml file contains keystore passwords and IP addresses specific to each server. The changes from server.xml are distinctly sent to each server. While applying changes from this file, IP addresses and keystore passwords available in the server.xml connectors for that device will be fetched and merged to the new server.xml.

Addresses are retained based on the port number mentioned in the connectors. Keystore passwords are retained based on the keystoreFile names in the connectors.

For example, the Identity Server cluster has three nodes: IDP 1, IDP 2, and IDP 3. The following are the snippets from server.xml of each Identity Server:

IDP 1:

<Connector NIDP_Name="connector_2" address=""
keystoreFile="/opt/novell/devman/jcc/certs/idp/provider.keystore" keystorePass="efg"
maxThreads="600" port="8444" ... />

IDP 2:

<Connector NIDP_Name="connector_2" address=""
keystoreFile="/opt/novell/devman/jcc/certs/idp/connector.keystore" keystorePass="hij"
maxThreads="600" port="8443" ... />

IDP 3:

<Connector NIDP_Name="connector_2" address=""
keystoreFile="/opt/novell/devman/jcc/certs/idp/provider.keystore" keystorePass="klm"
maxThreads="600" port="8444" ... />

Now, you modify server.xml of IDP 1 and increase MaxThreads to 800 through Advanced File Configurator as follows:

<Connector NIDP_Name="connector_2" address=""
keystoreFile="/opt/novell/devman/jcc/certs/idp/provider.keystore" keystorePass="efg"
maxThreads="800" port="8444" ... />

After applying this change to the cluster, server.xml of other Identity Servers are modified as follows:


<Connector NIDP_Name="connector" address=""
keystoreFile="/opt/novell/devman/jcc/certs/idp/connector.keystore" keystorePass="hij"
maxThreads="800" port="8443" ... />


<Connector NIDP_Name="connector_2" address=""
keystoreFile="/opt/novell/devman/jcc/certs/idp/provider.keystore" keystorePass="klm"
maxThreads="800" port="8444" ... />

The address and passwords are retained in the modified files. However, the required MaxThreads value is appropriately modified in each server.xml.