...

PostgreSQL Requirements

...

Hardware Requirements

Software Requirements

 yum -y install \
    postgresql postgresql-contrib \
    postgresql-odbc postgresql-plperl \
    postgresql-server

Amazon Linux 2
sudo yum -y install \
 https https://repo.ificlaims.com/ifi-claims-direct/amazonamzn2/x86_64/ifi-claims-direct-beta-01.0.2-1.amzn1amzn2.x86_64.rpm 
Fedora
yum
RHEL/Rocky 8
sudo dnf -y install \
 https://repo.ificlaims.com/ifi-claims-direct/fedorarocky/278/x86_64/ifi-claims-direct-beta-01.0.2-1.fc27el8.x86_64.rpm

...

Solr Basic Distributed Requirements (Type 2)

Hardware Requirements

Since CLAIMS Direct SOLR Solr is a pre-configured, bundled distribution of Apache SOLRSolr, it can be deployed on any number of nodes (individual instances). This documentation describes installation and configuration on a single node without the use of SolrCloud.

There are many scenarios for a CLAIMS Direct deployment that range from indexing the entire content of CLAIMS Direct XML to the sparse indexing of certain fields and ranges of publication dates for application-specific usage. There could also be specific QoS requirements: minimum supported queries per second, average response time, etc. All of these factors play a role in planning for a CLAIMS Direct SOLR Solr deployment. Generally speaking, a stand-alone full index with the entire content of CLAIMS Direct XML requires, at a minimum, the following:

...

...

The minimum required storage allows for a full index and approximately 1-2 years of growth. It doesn't allow space for SOLR Solr optimization (see "Commit and Optimize Operations" in Uploading Data with Index Handlers) unless carefully planned. Please contact support@ificlaims.com for more information about optimization with minimum requirements.

Currently, the delivery of a fully populated CLAIMS Direct index requires the above SOLR Solr hardware requirements. A customized deployment with select data to index is currently not offered fully populated. With a custom configuration, hardware requirements are dependent on use case and complete indexing will need to be done at the installation site.

Software Requirements

The CLAIMS Direct SOLR Solr installation is a self-contained package suitable for deployment on any Linux server running Java 8. The simple prerequisite tool list follows:

...

...

Solr Advanced Distribution Requirements (Type 3)

Hardware Requirements

As CLAIMS Direct SOLR Solr is a pre-configured, bundled distribution of Apache SOLRSolr, it can be deployed on any number of nodes (individual instances). A group of nodes function to expose a collection. Further, multiple collections could be searched across the distribution.


There are many scenarios for a CLAIMS Direct deployment that range from indexing the entire content of CLAIMS Direct XML to the sparse indexing of certain fields and ranges of publication dates for application-specific usage. There could also be specific QoS requirements: minimum supported queries per second, average response time et al. All of these factors play a role in planning for a CLAIMS Direct SOLR Solr deployment. Generally speaking, a full index with the entire content of CLAIMS Direct XML requires, at a minimum:

The ZooKeeper quorum could be placed together on SOLR Solr search servers or, optionally, you could break out the ZooKeeper configuration into an additional 3 separate servers.

...

Currently, the delivery of a fully populated CLAIMS Direct index requires the above SOLR Solr and ZooKeeper configuration (8 SOLR Solr servers + 3 ZooKeepers). Load balancers and web servers are required only if CLAIMS Direct Web Services (CDWS) will be installed as well. A customized deployment with select data to index is currently not offered fully populated. With a custom configuration, complete indexing will need to be done at the installation site.

Software Requirements

The CLAIMS Direct SOLR Solr installation is a self-contained package suitable for deployment on any Linux server running Java 8. The simple prerequisite tool list follows:

The configuration script setup.sh assumes that each node in the cluster will have the same directory structure. For example, if you download to a machine and unpack the archive into path /cdsolr, the full path to the package will be /cdsolr/alexandria-solr-v2.1.2-distribution. Each node must have the path /cdsolr available for deployment. You are free to choose any mount point or path as long as they are uniform across all nodes in the cluster and as long as the mount point or path for each SOLR Solr node has at least 1TB of available disk space.

...

RHEL/CentOS 7
yum -y install \
 https://repo.ificlaims.com/ifi-claims-direct/centos/7/x86_64/ifi-claims-direct-beta-0.0.2-1.el7.centos.x86_64.rpm

Amazon LinuxAmazon Linux 2
yum -y install \
 https https://repo.ificlaims.com/ifi-claims-direct/amazonamzn2/x86_64/ifi-claims-direct-beta-01.0.2-1.amzn1amzn2.x86_64.rpm Fedora

RHEL/Rocky 8
yum -y install \
 https://repo.ificlaims.com/ifi-claims-direct/fedorarocky/278/x86_64/ifi-claims-direct-beta-01.0.2-1.fc27el8.x86_64.rpm 

Web Server Requirements

Hardware Requirements

...

If you want to customize logging, copy the distribution alexandria-log.conf file to /etc.

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

...

If you make no changes, default logging is output to /tmp/alexandria.log.

For more information about how the alexandria tools log, see:

...

1. --IFIuser/--IFIpassword passed to apgupd – issued by IFI CLAIMS
2. --PGSuser/--PGSpassword used to connect to postgresql – postgresql – created during the Postgres PostgreSQL database installation

apgupd requires the IFIuser / IFIpassword, e.g.,

...

If you used a different user to create and load the alexandria database, you will need to modify the database entry in the file pointed to by:

...