The Axional Studio uses several databases where store the configuration and the applications. This guide shows how to install these databases.

1 Pre-requisites

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:

Database Dbspace Description Chunk Size
wic_conf d_conf data-dbspace specific for data of the wic_conf database d_conf_00 512MB
s_conf smart-blobspace specific for the clobs and blobs of the wic_conf database s_conf_00 512MB
wics d_wics data-dbspace for the data of any other dictionary of databases (even wic_admin) d_wics_00 1024MB
s_wics smart-blobspace for the clobs and blobs of any other dictionary of databases (even wic_admin) s_wics_00 1024MB

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.

2 Application database dictionaries

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

Dictionary Install Description Size
wic   System database for dictionaries (wics) 32MB
wic_admin   System database for wic_conf 25MB
wic_icon   Finances 100MB
wic_iges   Purchases, sales and distribution. 280MB
wic_icrm   Customer relationship management 32MB
wic_itra   Transportation management system 15MB
wic_iman   Computerized maintenance management system 12MB

  Required   Optional

2.1 Relationship

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.

Dictionary relations


2.2 The wic_conf database

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.


Within the wic_conf database resides the environment configuration, logical topology and the definitions of rights granted for each user. Key definitions are the users and their roles, the company databases and their permissions. The database wic_conf is not imported. It is created from the setup utility. In order to this step, it is necessary to have already installed the wic and the wic_admin databases on your server.

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

Table Description
Master data
wic_role The roles for the application and the tools
web_os_lbldata Labels for all desktop tools
wic_user Registered users
wic_user_role The application roles of the users
wic_user_groups User groups
wic_user_desk Portal desktops of the users
wic_user_pt_boxs Channels of the portal desktops
wic_user_props_desk Properties for portal desktops
wic_user_props_apps Properties for the enterprise application
wic_user_props_print Properties for printed documents
wic_group_role The user group application roles (the roles assigned to the groups)
wic_dbms_servers Available database servers in the cluster
wic_dbms_objects Available database schemas for each database server
wic_dbms_locales Available languages for the application
wic_dbms_users Definition of logical users granted to connect to the database server
wic_dbms_usersdb List of accessible databases for each logical database user
Device synchronization
wic_sync_crontab The scheduler to synchronize the tables for the mobile devices
wic_sync_rules Synchronization rules for the mobile devices
CSS Styles
wic_styles_jrep Styles for standard enterprise reports
wic_styles_app_csshead_v2 Styles for enterprise forms
wic_styles_app_cssitem_v2 Elements for each style enterprise form
wic_styles_app_cssicon_v2 Icons used from styles
wic_styles_app_cssvargroup_v2 Variable groups to show the variables grouped in the style editor
wic_styles_app_cssvars_v2 Variables of style. This variables are parsed the first time that the style is requested to create the full text CSS compiled
wic_styles_app_cssdata_v2 The CSS data referenced by items of styles. Can be structured in components on wic_styles_app_cssdata_item_v2
wic_styles_app_cssdata_item_v2 The CSS data for the components

3 Download databases

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" ""

or, using the command wget:

$ wget -q -O "axional-install.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.

You need to ask for a nexus username and password to access deister nexus software repository

Use the shell to install the product

$ ./ 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.

3.1 Connection details

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


Nexus Base URL []:
Nexus User [deister-software-dist]: UserProvided
Nexus User Password []: PassProvided

3.2 Choose product

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

Choose the product studio-only-exports.

4 Import databases

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:


To import the required databases execute the following commands:

dbimport -i dir_exports wic -d d_wics

dbimport '-i' option

You can avoid to use the -i option if you are located on the same directory than the dbexport directory.
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

4.1 Database renaming

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:
    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.

4.2 Troubleshooting

Action Exception Description
Importing a catalog database 9799 - User Defines Routine (bts_createstorage) VP context switch failed It is needed to configure a bts VP. 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.