Cybersecurity
DevOps Cloud
IT Operations Cloud
OpenText product name changes coming to the community soon! Learn more.
The Network Automation (NA) property files use the .rcx
extension. NA reads .rcx
files in reverse alphabetical order. If a given setting is in multiple .rcx
files, NA uses the last-read value. Thus, the settings in the adjustable_options.rcx
file take precedence over the settings in the other .rcx
files installed with NA.
At startup, NA reads all files in the jre
directory and interprets their contents for NA configuration options. For this reason, save all backup copies of .rcx
files outside the root NA directory.
In Horizontal Scalability environments, NA shares the actual values of most settings, not the .rcx
files, across the NA cores. When a setting is modified on one NA core, that setting is replicated to the other NA cores. If an NA core is not operational during the change replication, that NA core does not receive the change. In that case, at a later time, use the Admin > Distributed > Renew Configuration Options page to pull changes from other NA cores.
The distributed system options section of the appserver.rcx
file lists the settings that are specific to one NA core and are not shared across the NA cores.
Some configuration changes require .rcx
file modifications. The .rcx
files are located in the following directory:
<NA_HOME>\jre
<NA_HOME>/jre
Always edit .rcx
files with care. These files use XML format. If a .rcx
file change results in invalid XML, the NA console might not start correctly.
It is recommended to make all configuration changes in the adjustable_options.rcx
file. NA patch installations and product upgrades might overwrite any of the other NA-installed .rcx
files.
The general procedure for changing .rcx
files is as follows:
Back up the .rcx
file to a location outside the <NA_HOME>
directory.
NA reads all .rcx
files within the NA directory structure.
.rcx
file.Reload the .rcx
settings by doing one of the following:
reload server options
command from the NA proxy.Some changes do not take effect until the NA services have been restarted.
For more detail: https://docs.microfocus.com/doc/Network_Automation/2022.05/RCXFiles