An Axional Studio application server requires a bootstrap database server where store the enterprise metadata. Enterprise metadata includes the available database servers, database users, application users, user roles, and so on.

On the database server, it must exists the following dbspaces where allocate the configuration databases:

The name of chunks and its size can be different from this definition. The name of chunks is not relevant and the size will depend on the intended content.

To run Axional Studio web applications you need to load the appropriate dictionary database, according to application natures, into the database server.

  Required   Optional

The next schema shows the dictionaries relationship.

• The metadata to handle the wic_conf database forms is defined in a database dictionary called wic_admin.
• The wic database stores the metadata for the whole set of other dictionaries.
• The rest of wics databases store the metadata and programs to handle the application forms.

This database contains critical information needed by the server to operate, including users and their properties, database servers and database schemas, application CSS styles, etc. Many servers sharing the same configuration are considered a cluster.

The following table shows the main tables defined in the wic_conf database.

You can use the installation tool or contact with the provider to request the database exports.

Download the installation tool using the curl command:

$ curl -k -s -o "axional-install.tar.gz" "https://bitbucket.org/deister/axional-install/get/master.tar.gz"

or, using the command wget:

$ wget -q -O "axional-install.tar.gz" "https://bitbucket.org/deister/axional-install/get/master.tar.gz"

Extract the files using the tar command:

$ tar -x -z --strip-components=1 --exclude ".hg*" --exclude ".project" -f "axional-install.tar.gz"

Firstly, use axional installer to setup the remote software repository and the credentials.

Use the shell to install the product

$ ./install.sh download

* Looking for curl...
* Looking for unzip...
* Check Java ...
  = Found java executable in PATH
  = Java version 1.8.0_91
* Looking for gradle
* Trying to download gradle 3

First time you execute the installer, it will ask for some parameters to configure the installation framework. You also need to request a nexus user and password to the deister support team, to enter the software repositories.

The installer will prompt for connection parameters to the Nexus repository such as the url, user and password.

================================================================
CONFIGURATION
================================================================

Nexus Base URL [http://nexus.deistercloud.com/]:
Nexus User [deister-software-dist]: UserProvided
Nexus User Password []: PassProvided
                

Next the installer will prompt for product. We will enter studio.

Choose the product studio-only-exports.

Before using the setup tool, a minimum preparation is needed in your database server. This will include the creation of the appropriate dbspaces and loading the database dictionaries.

1. Select your primary database server.
2. Ensure that exists a bts VP.
3. Import the wic dictionary database.
4. Import the wic_admin dictionary database.

A bts VP is needed to import the catalog databases. You can check it executing the command:

onstat -g sch | grep bts

If there is not the VP then edit the $ONCONFIG file and add the following line (close to the another VPCLASS definition):

VPCLASS bts,num=1,noage

This actions requires a restart of database service.

To import each database use the command dbimport. The dictionaries wics will be allocated at the d_wics dbspace. It is necessary to set the environment variables values:

CLIENT_LOCALE=en_us.UTF8
DB_LOCALE=en_us.UTF8
DBMONEY=.

To import the required databases execute the following commands:

dbimport -i dir_exports wic -d d_wics

dbimport -ci wic -d d_wics

dbimport -ci wic_admin -d d_wics

Execute the update statistics.

echo "update statistics low drop distributions" | dbaccess wic

echo "update statistics low drop distributions" | dbaccess wic_admin

Execute this command to change to unbuffered logging the databases.

ontape -s -U wic -t /dev/null

ontape -s -U wic_admin -t /dev/null

To import the rest of dictionaries iterate the same command by replacing the argument dbname with the corresponding name of database:

dbimport dbname -d d_wics

If in your database server already exists a databases named wic or wic_admin it is necessary to rename the new databases. Naming must be unique. For example you can rename the wic database to wic17 and wic_admin database to wic17_admin.

The following example shows a way to change the database name. In this example, assume that the dbexport unloaded the database wic_admin into the directory /work/exports/wic_admin.exp. Thus, the data files (the .unl files) are stored inside the /work/exports/wic_admin.exp, and the schema file is /work/exports/wic_admin.exp/wic_admin.sql.

1. Change the name of the .exp directory. That is, change /work/exports/wic_admin.exp to /work/exports/wic17_admin.exp.
2. Change the name of the schema file. That is, change /work/exports/wic_admin.exp/wic_admin.sql to /work/exports/wic17_admin.exp/wic17_admin.sql. Do not change the names of the .unl files.
3. Import the database with the following command:
   Copy

   dbimport -i /work/exports wic17_admin

Please notice that the schema of the wic_conf database assumes the standard names for wic and wic_admin. Thus, changing their names will also involve declaring the new ones inside the wic_conf database.

Here the table [wic_dbms_objects] indexes the set of available database. For wic or wic_admin it is necessary to populate their new names in the field obj_physname.