...
Info | ||
---|---|---|
| ||
|
...
Requirement | Recommended |
---|---|
CPU | 4-cores |
System Memory | 24GB |
Storage Capacity | 4TB 6TB (SSD preferredrequired) |
Software Requirements
RequirementMinimum | VersionSupported Versions | Notes | |
---|---|---|---|
Operating System | RHEL 7, Fedora 25-27, CentOS 7, /Rocky 8, Amazon Linux AMI | If you are using Fedora, you must use version 27 or below. Installing Fedora v28 and above will install a version of PostgreSQL that is incompatible with CLAIMS Direct. | |
PostgreSQL | Distribution version | yum -y install \ | |
IFI CLAIMS Repository | RHEL/CentOS 7 Note: CentOS 7 needs an additional repository: 2 | We do not support Ubuntu or any operating system not explicitly listed. | |
PostgreSQL | 11 - 14 | For the appropriate repository see https://www.postgresql.org/download/linux/redhat/ | |
IFI CLAIMS Repository | Amazon Linux 2 |
SOLR Basic Distributed Requirements (Type 2)
Hardware Requirements
Since CLAIMS Direct SOLR is a pre-configured, bundled distribution of Apache SOLR, 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 deployment. Generally speaking, a stand-alone full index with the entire content of CLAIMS Direct XML requires, at a minimum, the following:
...
Requirement
...
Minimum
...
Recommended
...
The minimum required storage allows for a full index and approximately 1-2 years of growth. It doesn't allow space for 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 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 installation is a self-contained package suitable for deployment on any Linux server running Java 8. The simple prerequisite tool list follows:
...
Name
...
Used By
...
SOLR Advanced Distribution Requirements (Type 3)
Hardware Requirements
As CLAIMS Direct SOLR is a pre-configured, bundled distribution of Apache SOLR, 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 deployment. Generally speaking, a full index with the entire content of CLAIMS Direct XML requires, at a minimum:
...
Number
...
Type
...
Specs
...
SOLR search server
nodes 1-3 housing the ZooKeeper quorum
...
- CPU: 2 cores
- RAM: 16GB
- Disk: 1TB
...
- CPU: 4 cores
- RAM: 16GB
- Disk: 1TB
The ZooKeeper quorum could be placed together on SOLR search servers or, optionally, you could break out the ZooKeeper configuration into an additional 3 separate servers.
...
Number
...
Type
...
Specs
...
- CPU: 1 core
- RAM: 2GB
- Disk: 50GB
Currently, the delivery of a fully populated CLAIMS Direct index requires the above SOLR and ZooKeeper configuration (8 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 installation is a self-contained package suitable for deployment on any Linux server running Java 8. The simple prerequisite tool list follows:
...
Name
...
Used By
...
Processing Server Requirements
Hardware Requirements
CPU | 2-cores |
System Memory | 8GB |
Storage Capacity | 500GB (100GB SSD for fast temporary processing space) |
Requirement | Recommended |
---|
Software Requirements
Requirement | Minimum Version | Notes | |
---|---|---|---|
Operating System | RHEL 7, Fedora 25-27, CentOS 7, /Rocky 8, Amazon Linux AMIIf you are using Fedora, you must use version 27 or below. Installing Fedora v28 and above will install a version of PostgreSQL that is incompatible with CLAIMS Direct2 | We do not support Ubuntu or any operating system not explicitly listed. | |
IFI CLAIMS Repository | RHEL/CentOS 7 Note: CentOS 7 needs an additional repository: Amazon LinuxAmazon Linux 2
|
Web Server Requirements
Hardware Requirements
Requirement | Recommended |
---|---|
CPU | 2-cores |
System Memory | 4GB |
System Storage | 100GB |
Software Requirements
Requirement | Recommended | Notes |
---|---|---|
Apache httpd | Distribution version | yum -y install httpd |
Perl Modules | Distribution version | yum -y install \ |
CLAIMS Direct Library | Latest Version | Contact support@ificlaims.com for link to latest version |
CLAIMS Direct CDWS | Latest Version | Contact support@ificlaims.com for link to latest version |
...
If you want to customize logging, copy the distribution alexandria-log.conf
file to /etc.
Code Block |
---|
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:
...
- --IFIuser/--IFIpassword passed to apgupd – issued by IFI CLAIMS
- --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:
...
Panel | ||
---|---|---|
| ||
|
...
Info | |
---|---|
IFI Claims has produced a patched release of libxml2-2.9.2 as an RPM. We recommend locally installing this package and replacing the package in the distribution. Download the RPM at: http://alexandria.fairviewresearch.com/software/libxml2/f20/libxml2-2.9.2-1.fc20.x86_64.rpm. Contact support@ificlaims.com if other versions are required. |