Important: Do not start the update process until you have completed the initial load of the database.
Note: It is recommended to copy and paste the code provided in these instructions.
1. If you are using CentOS, add the epel repository.
If you are using RHEL, use the following code to add the epel repository. Otherwise, continue to step 2.
2. Install the appropriate repository for your operating system using the command listed in the Repository column below. If necessary, adjust the code to reflect the version you are using.
3. After installing the repository, run a yum update to pull in the patched version of libxml2 from the IFI CLAIMS repository.
Note: If there are conflicts, change the command line to
--allowerasing update as directed. If you are using Fedora, the command will be
–-best --allowerasing update. Reboot if kernel was upgraded.
4. Install the Alexandria client tools package.
5. Run acfg to make sure the tools can see the configuration file correctly.
This will display the configured databases and indices.
6. If you want a central location for the configuration file which is immune to software updates, copy it to
If you run acfg again, the "Using configuration" line should reflect the new location:
Note: If you are installing the client tools on a different machine from your PostgreSQL instance, you will need to change the database entry in the configuration file
etc/alexandria.xml, e.g., the default should reflect the host (IP address) of your PostgreSQL instance. If you added a password for user alexandria (or changed user at all), you would modify @user/@password entries as well. For example, if your PostgreSQL instance is running on 10.234.211.3, the configuration entry would look like this:
7. Test the update process.
With an empty database, the output would resemble:
8. Once you have completed the initial load of the database, test whether the update runs.
9. Start the update daemon. See apgupd for more information.