v0.0.1 Python script to deploy OpenROAD Server Applications from an archive

• Usage: python orjarinstall.py [-h] orjarfile

• positional arguments:
  orjarfile archive containing the server application and other resources required, see attached orserver-add-l2pserver.zip
  This archive can have the following subdirectories that will be processed:
  - libu3gl - shared libraries/DLLs
  - netutil - netutil command scripts
  - orjsonconfig - JSON config files for OpenROAD server applications
  - orserveradm_removeapp - JSON file to be used by the "orserveradm.py" script with RemoveApp command
  - orserveradm_addapp - JSON file to be used by the "orserveradm.py" script with AddApp command
  - resource - Additional resource directories to be deployed
  - w4glapps - OpenROAD Server application images

• optional arguments:
  -h, --help show help message and exit

• Preconditions:

  • Environment variables II_SYSTEM must be set.
  • The COMPUTERNAME needs to be set if not providing a "serverlocation" when using AddApp
  • The JSON file orjarinstall_cfg.json should exist in $II_SYTEM/ingres/files directory.
    This file should contain a JSON object {...} with the following members (all optional):
    • "libu3gldir" - the directory shared libraries/DLLs are deployed into.
      This directory should be contained in LD_LIBRARY_PATH (Linux) or PATH (Windows); default: $II_SYTEM/ingres/lib (Linux) or %II_SYSTEM%\ingres\bin (Windows)
    • "orjsonconfigdir" - the directory JSON config files for OpenROAD server applications are deployed into (default: $II_SYTEM/ingres/files/orjsonconfig)
    • "resourcedir" - the directory "resource" directories (and their contents) are deployed into (default: $II_SYTEM/ingres)
    • "w4glappsdir" - the directory 4GL image files are deployed into; directory should be contained in II_W4GLAPPS_DIR (default: $II_SYTEM/ingres/w4glapps)