Page tree
Skip to end of metadata
Go to start of metadata
Before you start
  • The Alexandria client tools can be installed on the PostgreSQL machine or on a separate processing server for security purposes.
  • All commands, unless otherwise noted, must be run as root.
  • If you are installing the client tools on the same machine as PostgreSQL and have already installed the IFI CLAIMS repository on this machine, skip to step 4.

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.

yum -y install epel-release

If you are using RHEL, use the following code to add the epel repository. Otherwise, continue to step 2.

yum -y install$(rpm -E '%{rhel}').noarch.rpm

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.

yum -y update

Note: If there are conflicts, change the command line to yum --allowerasing update as directed. Reboot if kernel was upgraded.

4. Install the Alexandria client tools package.

yum -y install perl-Alexandria-Client-Tools

5. Run acfg to make sure the tools can see the configuration file correctly.


This will display the configured databases and indices.

Using configuration from: /usr/share/perl5/vendor_perl/auto/share/dist/Alexandria-Library/alexandria.xml
Configured databases:
    alexandria: [alexandria;; 5432]
    customers: [customers;; 5432]
Configured Indices:
    alexandria (

6. If you want a central location for the configuration file which is immune to software updates, copy it to /etc.

cp /usr/share/perl5/vendor_perl/auto/share/dist/Alexandria-Library/alexandria.xml /etc

If you run acfg again, the "Using configuration" line should reflect the new location: /etc/alexandria.xml

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, the configuration entry would look like this:

<database name="alexandria" host="" port="5432" user="alexandria" password="alexandria">
      <atts pg_errorlevel="0" AutoCommit="1" RaiseError="1" PrintError="0" LongTruncOk="0" LongReadLen="10485760" />

7. Test the update process.

apgup --user=USER --password=PASSWORD --check

With an empty database, the output would resemble:

[localhost] [2018/06/23 04:28:57] [INFO      ] [total load-ids available: 170438 (start=125234 end=312262)]

8. Once you have completed the initial load of the database, test whether the update runs.

apgup --user=USER --password=PASSWORD --update

9. Start the update daemon. See apgupd for more information.

apgupd --user=USER --password=PASSWORD
Next Steps

Once the client tools have been installed, proceed to SOLR Installation (if desired).

  • No labels