EXODUS Knowledge

TMUX Screens

To create the EXODUS maintenance/programming environment

exodus#: ./tmux.exodus

SCREEN NAME      STANDARD PATH                            PURPOSE
#ex1_root        - /root                                  - general usage 
#exodus          - /root/exodus                           - 
#exodus src      - /root/exodus/exodus/libexodus/exodus   - LibExodus is the core EXODUS library source files (emulating AREV CRUD)
#exo cli         - /root/exodus/cli/src                   - Core EXODUS program which can be executed from bash (clearfile, edir, edic, compile)
#service         - /root/exodus/service                   - Default working environment for EXODUS only service, including EXODUS core www and data directories. Also used to keep NEOSYS database installation scripts.
#ser src         - /root/exodus/service/src               -
#neosys          - /root/neosys                           - ./doall
#neo src         - /root/neosys/src                       -
#hosts           - /root/hosts                            -   
#test src        - /root/exodus/test/src                  - 
#t10             - ~/                                     - 
#t11             - ~/                                     - 
#t12             - ~/                                     - 

Object Code/Libraries

LIVE and TEST processes use different sets of object code. TEST processes use libraries in ~/lib/, whereas LIVE processes use object code in ~/neo/lib

This means development & testing can be done stress free on TEST database, as opposed to testing on production databases.

When compiling using edic, the TEST object code is updated if the compilation is successful. (~/lib) In order to apply a tested patch to LIVE see Update LIVE programs.

Dictionaries

Dictionaries, the files used to describe the fields of a file's record. Unlike in AREV, there is a copy of all dictionaries in each pgsql database (In AREV, updating a dictionary would affect all the databases).

Processes

The TEST process for all database use the same object code stored in /root/lib, whereas all LIVE process use the object code in /root/neo/.

Postgres

Connect into postgres shell:

sudo -u postgres psql

List databases once in postgres shell:

\l

Delete a database:

sudo -u postgres dropdb <dbcode>

./doall

General

Screen 6: ./doall script contains all the necessary information(codes) to setup an installation. It includes scripts to backup, restore, create an Apache site, create/start/stop/status a service, import an AREV database into postgres and more.

backup_db

• Does a backup & restore of a LIVE database into the corresponding TEST database.
• Backup <dbcode>.sql file is written to /root/backups/sql; which is rsynced to nl19:/backups/current/exodus/
• Unlike AREV, postgres can perform a "backup" of a database whilst the system is in use.

Git

There are two repositories, one for EXODUS and the other for NEOSYS.

Using git to make changes

Before following steps you must have a tested updated to a program/file/script. Do not commit untested changes to avoid a messy git history of reverts.

Update your local repo before committing to local repo using the g alias for "git pull --ff-only ; git push && git status'":

g

Check which updates/files have not yet been staged and/or committed: Add your updates to the staged area:

git add <filename>

or if all the changes made need to be staged:

git add -a

Make a commit with a descriptive message on purpose of updates:

git commit -m <description n purpose of changes>

Again use g alias:

g

Other useful git cmds

Do not use this commands unless you know what WILL happen.

• git pull - Instead use the safe "git pull --ff-only"

Stick to the alias "g" which does "git pull --ff-only ; git push && git status'"

• git log - display history of commits to master branch
• git diff - display the differences in files between working files and files in local repo.
• git status - display: which updated files are staged/not staged(tracked)
• git stash -
• git branch - switch to a new branch
• git branch <branchname> - will switch to this branch only if it exists
• git checkout - DESTROYS/Updates the state of local working directory with the state of the files in the local repo. (YOU WILL LOSE non staged updates)
• git restore <filename> - DESTROYS/Updates the file with the version in the local repo. (like with git checkout but for a specific file)
• git checkin -
• git revert <commitHash> - reverses a specific commit (use git log to get the chosen commit hash)

Converting AREV to EXODUS

Decompile AREV to C++

(Do in win10a Maintenance mode)

1. Apply tested patch to win10a (master AREV Dev system)
2. ATTACH ADECOMC
   • ADECOM <programname> *single program
   • ADECOMALL *all programs (CHECK THIS FIRST)
   • ADECOM <prog1> <prog2> *(CHECK IF THIS WORKS)

Send c++ files from win10a to nl19

(Do in win10a Cygwin)

1. /d/exodus/arev/syncup.sh

Get c++ files from nl19 to exodus

(Do in Exodus system)

1. If cpp in SYS then: ~/exodus/service/src ./getpickos
2. If cpp in MED JOB FIN GEN AGY then: *~/neosys/src ./getpickos
3. Compile single cpp then: c <programname> e.g "c monitor2"
4. Compile all cpp then: ./compall (PENDING WHICH/WHERE? many compall)

Compile C++ files to TEST system

1. • ./test <DBNAME>
   • ~/neosys ./doall TEST <DBNAME> restart #to get one service to start start using the new lib files
   • ~/neosys ./doall TEST all restart #to get all the services to start start using the new lib files

Install C++ files to LIVE System

WARNING

1. ~/exodus/service/ ./copyall #to copy all the ~/lib and bin files to ~/live/lib and bin ... which is used by all exodus/live services

Writing Standard Exodus Core Function/Method Testing

Screen 9: ~/exodus/test/src/ There are a series of test programs that check whether methods/functions behave as intended. They do this using the function, assert.. a 1 or more argument values produce one and only one output)

e.g test_multilang.cpp or test_sort.cpp

Two methods of running test programs:

• Screen 9: make test
• after compiling using edic/compile/c, enter test_prog_name. (Since compile has moved it to ~/bin)

Difference between the two methods is make calls gdb directly; whereas ~/bin/test_prog_name uses exodus compile program

1. ~/neosys ./doall LIVE all restart

Applying changes to files that exist per database

Some files have a version of itself per client database in postgres, e.g. ALANGUAGE.

Editing this file for one database will affect that specific database only.

Below example shows how to edit the file for one database and then apply the changes to other databases:

Case: Edited ALANGUAGE file in one db and applying it to another db

1. Update the file for a specific database

   EXO_DATA=<DB_NAME> edir ALANGUAGE COSTESTIMATES*ARABIC

2. Save the file for use in future or other databases

   sudo -u postgres pg_dump <DB_NAME> -t ALANGUAGE -c > ~/neosys/src/sql/alanguage.sql 

3. Apply changes to specific database or across all databases
   • Load the file into the database where you want to apply the fix

     cat ~/neosys/src/sql/alanguage.sql | sudo -u postgres psql <TARGET_DB_NAME> 

   • If applying to all databases, use the below command

     ./doall all bash "cat ~/neosys/src/sql/alanguage.sql | sudo -u postgres psql \$EXO_DATA" 

Updating a pgsql function in an exodus dictionary

Although dictionaries reside in two central databases, exodus and exodus_live, any pgsql functions contained therein must be installed in every database in which they are used.

Therefore it is a three step process to edit and deploy exodus dictionary pgsql functions.

Edit the pgsql for test databases

Assumes EXO_DICT is not set to anything.

This will edit the dictionary file in exodus db. It will have no effect on live services since live services use exodus_live db.

edir dict.materials deadline 8

Copy all dictionaries to live

Will copy ALL dictionaries from exodus to exodus_live. Not just the specific item edited above.

cd ~/exodus/service  && ./copydict CONFIRM

Update the pgsql function in all databases

This will only update the specific function edited above. To update all pgsql functions, omit the file name and dict id.

cd ~/neosys && ./doall all bash dict2sql materials deadline

or to just update all test databases

cd ~/neosys && ./doall TEST all bash dict2sql materials deadline