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.

As of 22/08/21, each repo has three main branches

• master - not used
• 21.08 - live on ex1
• dev - the development branch

As of 22/08/21, ex1b is a clone of ex1 but used as the development environment. In order to use ex1b as development environment the ex1b has to be rebuilt every morning to get the development branch working otherwise it is a pure clone of ex1 except disabled that is usually done early in the morning and may be automated in future using ~/neosys/onboot.sh there is no issue running all processes on ex1b actually since even live process emails to users are all deflected to sysmsg ie neosys to rebuild as the development branch in ex1b

<bold>DONT DO THIS IN ex1!!!!!!!!!!!!</bold>

1. in ~/neosys screen 6
2. git stash && git pull && git switch dev
3. ./reinstall dev dev o-
4. ./reinstall first switches exodus to its dev branch and rebuilds it

Git commands

1. Show log of commits (inc commit ID/msg)

git log

1. Show changes of a particular commit

Identify commit of interest and copy first 6 char of its ID. (use git log)

git show <ID>  

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. Load the file into the database where you want to apply the fix

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

4. If applying to all databases, use the below command

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