IFI CLAIMS will create a single tar.gz file that includes a subdirectory of tar.gz files for each of the tables in the PostgreSQL data warehouse. We will provide you with a link to access and download the file. Alternately, if you have received the data on a USB, connect it to your intended PostgreSQL machine and mount the drive so that it can be read.
Panel | ||
---|---|---|
| ||
|
Note |
---|
Note: It is recommended to copy and paste the code provided in these instructions. |
1. IFI CLAIMS will create a single tar.gz file that includes several bash scripts that are used during implementation and a subdirectory of tar.gz files for each of the tables in the PostgreSQL data warehouse. This file will be placed into an S3 bucket and we will provide you with a link for you to access and download the file.
2. Extract the tar.gz file into your local environment. The receiving drive will require approximately 3TB of free space to download and extract the file.
3. Use yum to install PostgreSQL.
Code Block |
---|
yum -y install \
perl-devel \
postgresql postgresql-contrib \
postgresql-odbc postgresql-plperl \
postgresql-server |
4. If you are using CentOS 7, add the epel repository.
Code Block | ||
---|---|---|
| ||
yum -y install epel-release |
If you are using RHEL 7, use the following code to add the epel repository. Otherwise, continue to step 5.
Code Block | ||
---|---|---|
| ||
yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-$(rpm -E '%{rhel}').noarch.rpm |
5. 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.
...
|
...
...
...
|
...
|
...
|
...
...
...
...
Note: This installs EPEL and the PowerTools repositories
|
...
|
...
...
...
...
...
Note |
---|
Note: It is recommended to copy and paste the code provided in these instructions. |
1. If you received the data as a tar.gz file, extract it into your local environment. The receiving drive requires approximately 4TB of free space to download and extract the file. The extracted file will consist of a number of smaller tar.gz files. There is no need to extract each of these smaller files.
2. Prepare repositories and run a yum
update to pull in the patched version of libxml2 from the IFI CLAIMS repository .
Code Block |
---|
yum update |
Note |
---|
Note: Reboot if kernel was upgraded. |
7. CLAIMS Direct requires a working PostgreSQL cluster. If you do not have an initialized cluster, the following commands will initialize the cluster and give you rudimentary authentication and access levels needed to run CLAIMS Direct. Note that the initdb
command has to be run by the user who owns PostgreSQL (user postgres). Enter:
Code Block |
---|
su - postgres |
followed by:
Code Block |
---|
initdb -A trust \
-D /var/lib/pgsql/data \
-E utf8 |
8. Using a text editor, modify the IP addresses in the following configuration files.
Note |
---|
Note: If you are installing the client tools on a separate machine, other hosts will be required. Be sure to remove the hash (#) at the start of the ‘other hosts’ entry if you need to enable access for other hosts or subnets. |
/var/lib/pgsql/data/pg_hba.conf
Code Block | ||
---|---|---|
| ||
# Allow trusted local access
local all all trust
# IPv4 local connections
host all all 127.0.0.1/32 trust
# Other hosts on subnets that may require access, for example
# host all all xxx.xxx.xxx.xxx/xx trust |
/var/lib/pgsql/data/postgresql.conf
Code Block |
---|
listen_addresses = '*' # what IP address(es) to listen on; |
Note |
---|
Note: If you already have an initialized cluster, please be certain that local access is enabled for stand-alone installation. In either distributed install, if a separate services machine is created, its IP address needs access. This is imperative for the client update procedures. |
9. Enable and any other pending updates. Adjust the code if you are using a different version of PostgreSQL.
Code Block | ||
---|---|---|
| ||
# Amazon Linux 2
sudo amazon-linux-extras install epel
sudo amazon-linux-extras enable postgresql14
sudo yum clean all
sudo yum update
# RHEL/CentOS 7
sudo yum -y install epel-release
sudo yum clean all
sudo yum update
# Rocky
sudo dnf -y install epel-release
sudo dnf config-manager --set-enabled powertools
sudo dnf clean all
sudo dnf update
# RHEL
sudo subscription-manager repos --enable codeready-builder-for-rhel-8-x86_64-rpms
sudo dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
sudo dnf clean all
sudo dnf update |
Note |
---|
Note: Reboot if kernel was upgraded. |
3. CLAIMS Direct requires a working PostgreSQL cluster. If you have a working cluster, skip to step 5. If you do not have an initialized cluster, the following commands install PostgreSQL and initialize the cluster. The initdb
command has to be run by the user who owns PostgreSQL (user postgres).
Install:
Code Block | ||
---|---|---|
| ||
# Note: this installs the default version of your distribution. If you would like a higher version,
# please see: https://www.postgresql.org/download/linux/redhat/
sudo yum -y install postgresql postgresql-contrib postgresql-plperl postgresql-server |
Initialize:
Code Block | ||
---|---|---|
| ||
sudo -u postgres initdb -A trust -D /var/lib/pgsql/data -E utf8 |
Note |
---|
Note: PostgreSQL, by default, only allows local connections. If you would like to open access to network clients or are installing the Client Tools on a separate server, please see Allowing Remote Access to PostgreSQL Alexandria. |
4. Enable and restart the PostgreSQL cluster.
Code Block | ||
---|---|---|
| ||
sudo systemctl enable postgresql.service ; sudo systemctl restartstart postgresql.service |
105. Create the role alexandria and load the SQL via psql
into the instance.
Code Block | ||
---|---|---|
| ||
echo "create role alexandria with superuser login;" \ | psql -Upostgres postgres U postgres postgres |
Install the schema and tools.
Code Block | ||
---|---|---|
| ||
sudo yum -y install alexandria-schema-tools gunzip -c |
Create the database.
Code Block | ||
---|---|---|
| ||
cat /usr/share/alexandria-schema-tools/alexandria-dbs-10.x.gz \ | psql -Ualexandria -h <POSTGRESQL-HOST> postgres # There's also support for 9.x, # gunzip -c /usr/shareschema-xml/alexandria-schema-tools/alexandria-dbs-9.x.gz \ # xml.sql | psql -Ualexandria -h <POSTGRESQL-HOST>U alexandria postgres |
116. To ensure To ensure that the database has been created, run:
Code Block | ||
---|---|---|
| ||
psql -U alexandria --list |
The results should show the alexandria database.
Code Block | ||
---|---|---|
| ||
List of databases Name | Owner | Encoding | Collate | Ctype | Access privileges -----------------+------------+----------+-------------+-------------+----------------------- alexandria |alexandria | UTF8 | en_US.UTF-8| en_US.UTF-8 | postgres |postgres | UTF8 | en_US.UTF-8| en_US.UTF-8 | template0 |postgres | UTF8 | en_US.UTF-8| en_US.UTF-8 |=c/postgres + | | | | | postgres=CTc/postgres template1 |postgres | UTF8 | en_US.UTF-8| en_US.UTF-8 |=c/postgres + | | | | | postgres=CTc/postgres |
12. Run pgtune. Note that this requires Python. You can also use the online tool 7. Tune the database before loading.
In postgresql.conf
, adjust the autovacuum settings as follows:
Setting | Recommended | Notes |
---|---|---|
autovacuum_max_workers | 5 | This is the recommended setting for a 16-core machine. For a 4-core machine, a setting of 2 is recommended. |
autovacuum_vacuum_scale_factor | 0.02 | This setting indicates the threshold which determines when autovacuum needs to run per table. |
autovacuum_analyze_scale_factor | 0.01 | This setting tells the autovacuum process to analyze the table (i.e., update query planner statistics) when the fragmentation percentage reaches 1% (the default is 10%). |
For other performance tuning, use the online tool https://pgtune.leopard.in.ua/#/ and fill . Fill in the required values as well as those that correspond to your system. Add or change the appropriate settings and restart PostgreSQL.the suggested changes to the bottom of postgresql.conf
.
Note | |||||
---|---|---|---|---|---|
Note: For changes to be applied, PostgreSQL needs to be restarted:
|
...
|
8. Run the pre-flight check script to check script to confirm that your system is properly configured to load the data.
Code Block | ||
---|---|---|
| ||
cd-pre-flight-check.sh |
The sample output of a properly configured system would look looks like this:
Code Block | ||
---|---|---|
| ||
# Testing localhost/alexandria ... # OK : procedual language sql # OK : procedual language plpgsql # OK : procedual language plperl # OK : procedual language plperlu # OK : XML capability (test 1/libxml): # OK : XML capability (test 2/libxml): |
Resolve any recognized errors. For unfamiliar errors,
...
contact support@ificlaims.com.
...
9. Switch to the directory which holds the backfile you extracted in step 1. Use the load script to load the CLAIMS Direct data into PostgreSQL tables. Since
...
the loading process will take 1-2 days, we recommend that you use the nohup
command to detach the script from the terminal and allow it to run in the background.
Code Block | ||
---|---|---|
| ||
nohup cd-load.sh & |
15. Use the ps
command periodically to check whether the loading process has completed.
Note | ||
---|---|---|
Note: If you want to check on the process while it is running, use the following command to show the progress of the tables which are being copied:
|
1610. You can monitor the load using pg_stat_activity.
Code Block | ||
---|---|---|
| ||
select query_start, state, query from pg_stat_activity where datname = 'alexandria'; |
11. Once the loading process is complete, you you can run the cd-count.sh
script script, a simple QA of table counts, to ensure that the tables have loaded correctly. Modify the IP address to reflect the PostgreSQL server. This may take an hour or more to run.
Code Block | ||
---|---|---|
| ||
cd-count.sh |
The results should show that 39 xml tables and 4 cdws tables have loaded. The following tables will show a count of 0:
...
More information about the tables can be seen in Data Warehouse Design.
1712. Optional: you may want to run a simple SQL query as an additional test to confirm that the data is present.
Code Block | ||
---|---|---|
| ||
echo "select * from xml.t_patent_document_values where ucid = 'US-5551212-A'" | psql -U alexandria |
Note |
---|
Note: For new installations as well as any changes to your subscription, it may take 24 hours for full synchronization of your on-site instance. |
Panel | ||
---|---|---|
| ||
Once the data has been loaded, proceed to Client Tools Installation. Familiarize yourself with the PostgreSQL Schema and Tools. |