Installation of Catalog QT requires multiple components to be installed and configured to be fully operational. This is due to the fact that numerous, external, components are required during build procedure and during runtime. All these elements are described below.

one account with root privileges - you will have to create db schema

one account with normal user privileges - this user must have access to all tables inside DB

Since now, I am referring to sources inside: https://gforge6.eufus.eu/svn/catalog_qt/branches/R1.0.imas

> cd docs/dbschema
> mysql -h $HOST_NAME -u $UAL_USER itmcatalog -p < create_db.sql
 
# You have to alter table where some config info is stored make sure to call
 
> cat alter_00.sql | \
      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 itmcatalog -p < variables.sql
 
# double check that all tables are in proper place
 
> mysql -h $HOST_NAME -u $UAL_USER itmcatalog -p
> ...
> mysql> show tables;
+----------------------+
| Tables_in_itmcatalog |
+----------------------+
| annotations          |
| catalog_parameters   |
| entry                |
| entry_data           |
| intervals            |
| machines             |
| outcome              |
| scheduler            |
| users                |
| variables            |
+----------------------+
10 rows 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.

> module load imas
> imasdb test
 
# For bash
 
> export CATALOG_QT_HOME=`pwd`
> export CATALOG_QT_STORAGE=/this/is/the/location/where/all/users/can/write
> 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
> 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
> make

> service apache2 restart