In following section I assume that

$HOST_NAME            - points to location of MySQL/MariaDB server
user_with_root_access - is a name of MySQL's user name with root privileges
$UAL_USER    

         - is the name of the user who has access to itm_scheduler_db
                        (this user is create using create_scheduler_db.sql script)

I am using -p option while calling mysql - it means that you will be asked for password each time you want to log in to MySQL machine. Thus, it is not possible to use following samples in batch mode.

> cd docs/dbschema
> mysql -h $HOST_NAME -u user_with_root_access itm_scheduler_db -p < drop_scheduler_user.sql
> mysql -h $HOST_NAME -u user_with_root_access itm_scheduler_db -p < create_scheduler_db.sql
 
# Make sure you can access itm_scheduler_db DB
sed 's|@FULL_PATH_FOR_STORAGE@|/this/is/the/location/where/all/users/can/write|' > \
      alter_00_modified.sql
    mysql -h itmmysql1 -u ual_user_s itmcatalog -p < alter_00_modified.sql
 
# /this/is/the/location/where/all/users/can/write - is a place on your machine (where users are calling
#                                                   scheduler application). Each user has to have write
#                                                   access there.
 
> mysql -h $HOST_NAME -u $UAL_USER itmcatalog -p < alter_00_modified.sql
 
 
# make sure to create list of variables that are stored inside DB
 
> xsltproc ./getFieldsIMAS.xsl \
      $IMAS_HOME/core/installer/src/$IMAS_VERSION/ual/$UAL_VERSION/xml/IDSDef.xml | \
      grep "summary" > \
      variables.sql
> mysql -h $HOST_NAME -u $UAL_USER itmcatalogitm_scheduler_db -p
Enter < variables.sql
 
# double check that all tables are in proper place
 
> mysql -h $HOST_NAME -u $UAL_USER itmcatalog -p
> ...
> mysql> show tables;
+password: 
...
...
mysql> show tables;
+----------------------------+
| Tables_in_itm_scheduler_itmcatalogdb |
+----------------------------+
| access_list  annotations          |
| catalog_parameters   |
| entrydb_authorization                |
| entry_data           |
| intervals            |
| machines             |
| outcome              |
| scheduler            |
| users                |
| variables            |
+----------------------+
10 rows in set (0.00 sec)

> cd docs/dbschema

# this script will produce SQL script for creating machine
# dependent databases

> ./create_db.sh --db-user=ual_user_001 \
                 --db-name=jettc \
                 --host-name=$HOST_NAME \
                 --schema-name=itm_catalog_001 \
                 --ws-address=https://address.of.itmcatalog.installation/itmcatalog/api \
                 --storage=/this/is/the/location/where/all/users/can/write/to

> mysql -h $HOST_NAME -u user_with_root_access -p < drop_db_user_modified.sql
> mysql -h $HOST_NAME -u user_with_root_access -p < create_db_modified.sql

# Once database is created, make sure you can log in

> mysql -h $HOST_NAME -u ual_user_001 -p itm_catalog_001
Enter password: 
...
...
mysql> show tables;
+---------------------------+
| Tables_in_itm_catalog_001 |
+---------------------------+
| annotations               |
| catalog_parameters        |
| entry                     |
| entry_data                |
| intervals                 |
| machines                  |
| outcome                   |
| scheduler                 |
| users                     |
| variables                 |
+---------------------------+
10 rows in set (0.00 sec)

> xsltproc ./getFieldsIMAS.xsl \
      $IMAS_HOME/core/installer/src/$IMAS_VERSION/ual/$UAL_VERSION/xml/IDSDef.xml | \
      grep "summary" > \
      variables.sql

> mysql -h $HOST_NAME -u ual_user_001 itm_catalog_001 -p < variables.sql

# Make sure you can see variables inside DB

> mysql -h $HOST_NAME -u ual_user_001 itm_catalog_001 -p
Enter password: 
...
...
mysql> select count(*) from variables;
+----------+
| count(*) |
+----------+
|     2511 |
+----------+
1 row in set (0.00 sec)

gSOAP library requires WSDL location used for compilation of the codes. It is not possible to proceed any further without server components. This is related to the fact that gSOAP library requires WSDL location, where SOAP based specification is stored.

# Make sure to load IMAS environment - following command may be system dependent
> module load imasenv
> imasdb test
 
# For bash
 
> export CATALOG_QT_HOME=`pwd`
> export CATALOG_QT_STORAGE=/this/is/the/location/where/all/users/can/write/to
> export CATALOG_QT_DB_PROPERTIES=${CATALOG_QT_HOME}/dbAPI
 
# For tcsh
> setenv CATALOG_QT_HOME `pwd`
> setenv CATALOG_QT_STORAGE /this/is/the/location/where/all/users/can/write/to
> setenv CATALOG_QT_DB_PROPERTIES ${CATALOG_QT_HOME}/dbAPI
 
# setting target machine
#
# unfortunately, there are few places where machine dependent locations are used
# at the moment, two options are available:
#
# setenv MACHINE gateway
# setenv MACHINE jet
#
# it might be, we need yet another one, with new machine settings
 
# make sure to create and properly configure gSOAP module
# this way, you will be able to use pkg-config, etc.
> module load gsoap/2.8
> make

> svn co https://gforge6.eufus.eu/svn/catalog_qt

src
|-- api_1_0			- API routines
|-- client			- nusoap wrappers
|-- config.php		- main configuration file
|-- inc				- auxiliary scripts
|-- nusoap			- nusoap library
|-- test.php		- nusoap testing script
`-- ui2				- main UI scripts and web page

> service apache2 restart

./src/ui2/config.php
./src/config.php

./src/config_scheduler_db.php

> service apache2 restart

sequenceDiagram
    Client->>Catalog API: SOAP request [header with Qdb variable]
	Catalog API->>Scheduler DB: ask for DB configuration
	Scheduler DB->>Catalog API: send DB configuration
	Catalog API->>Catalog API: switch to chosen DB
	Catalog API->>Chosen DB: request/command to execute
	Chosen DB->>Chosen DB: execute request/command
	Chosen DB-->>Client: send feedback

sequenceDiagram
    Client->>Catalog API: SOAP request [header with Qdb variable]
	Catalog API->>Scheduler DB: request/command to execute
	Scheduler DB->>Scheduler DB: ignore header [Qdb variable]
	Scheduler DB->>Scheduler DB: execute request/command
	Scheduler DB-->>Client: send feedback
	participant Other Databases