...
| Code Block |
|---|
yum -y install \
postgresql postgresql-contrib \
postgresql-odbc postgresql-plperl \
postgresql-server |
4. If you are using CentOS, add the epel repository. Otherwise, continue to step 5.
| Code Block | ||
|---|---|---|
| ||
yum -y install epel-release |
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.
| Warning | ||
|---|---|---|
| ||
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. |
...
| Operating System | Repository |
|---|---|
| RHEL/CentOS 7 | yum -y install \ Note: CentOS 7 needs an additional repository: |
| Amazon Linux | yum -y install \ |
| Fedora | yum -y install \ |
56. After installing the repository, run a yum update to pull in the patched version of libxml2 from the IFI CLAIMS repository.
...
| Note |
|---|
Note: Reboot if kernel was upgraded. |
67. 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 |
|---|
initdb -A trust \
-D /var/lib/pgsql/data \
-E utf8 |
78. As root, restart postgresql.
| Code Block | ||
|---|---|---|
| ||
systemctl restart postgresql.service |
89. Using a text editor, modify the IP addresses in the following configuration files.
...
| 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. |
910. Enable and restart the PostgreSQL cluster.
| Code Block |
|---|
systemctl enable postgresql.service ; systemctl restart postgresql.service |
1011. Create the role alexandria.
| Code Block | ||
|---|---|---|
| ||
echo "create role alexandria with superuser login" | psql -U postgres postgres |
1112. Change the directory to the mounted USB file system and create the database. If desired, you can redirect errors (if any) to LOG.2.
| Code Block | ||
|---|---|---|
| ||
cat alexandria-dwh.sql | psql -U alexandria postgres 2>/tmp/LOG.2 |
1213. To ensure that the database has been created, run:
...
| 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 |
1314. Run the pre-flight check script to confirm that your system is properly configured to load the data.
...
Resolve any recognized errors. For unfamiliar errors, please contact support@ificlaims.com.
1415. 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 detach the script from the terminal to allow it to run in the background. Edit the IP address in the command to reflect the IP address where postgres is installed.
| Code Block |
|---|
nohup bash ./load.sh xxx.xxx.xxx.xxx alexandria & |
1516. Use the ps command periodically to check whether the load.sh 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:
|
1617. Once the loading process is complete, you can run the count.sh 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.
...
The results should show that 37 tables have loaded. Information about the tables can be seen in Data Warehouse Design.
1718. Optional: you may want to run a simple SQL query as an additional test to confirm that the data is present.
...