...
| Info | ||
|---|---|---|
| ||
|
PostgreSQL Requirements test
Hardware Requirements
Requirement | Recommended |
|---|---|
| CPU | 4-cores |
| System Memory | 24GB |
| Storage Capacity | 6TB 4TB (SSD requiredpreferred) |
Software Requirements
RequirementSupported | VersionsMinimum Version | Notes |
|---|---|---|
| Operating System | RHEL /Rocky 87, Fedora 25-27, CentOS 7, Amazon Linux 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 sudo 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 | 9.4 | yum -y install \ Note: Versions 10 and above are incompatible with CLAIMS Direct. |
| IFI CLAIMS Repository | RHEL/CentOS 7 Note: CentOS 7 needs an additional repository: Amazon Linux Fedora |
...
SOLR Basic Distributed Requirements (Type 2)
...
...
Information about Solr has been deprecated and should not be implemented. Updated information will be available soon.
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:
...
Requirement | Minimum | Recommended |
|---|---|---|
| CPU | 16-cores | 32-cores |
| System Memory | 128GB | 256GB |
| Storage | Basic: 6TB 4TB (SSD) Premium: 8TB (SSD) Premium+: 8TB (SSD) |
...
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:
...
Name | Used By |
|---|---|
| java | ZooKeeper, Solr SOLR and various support tools |
| wget | Configuration tools (bootstrap-*.sh) |
| lsof | Start/stop scripts (solrctl/zookeeperctl) |
...
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:
Number | Type | Specs |
|---|---|---|
| 8 | Solr SOLR search server nodes 1-3 housing the ZooKeeper quorum | minimum:
|
| 1 | processing server | 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:
Name | Used By |
|---|---|
| java | ZooKeeper, Solr SOLR and various support tools |
| wget | Configuration tools (bootstrap-*.sh) |
| lsof | Start/stop scripts (solrctl/zookeeperctl) |
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.
...
| Requirement | Minimum Version | Notes |
|---|---|---|
| Operating System | RHEL /Rocky 87, Fedora 25-27, CentOS 7, Amazon Linux 2We do not support Ubuntu or any operating system not explicitly listedAMI | 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. |
| IFI CLAIMS Repository | RHEL/CentOS 7 Note: CentOS 7 needs an additional repository: Amazon Linux 2 RHEL/Rocky 8Fedora |
Web Server Requirements
Hardware Requirements
...
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 PostgreSQL Postgres 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:
...