[DIRECTORIES]

The installation routine now allows separate the program area from the data area.

This separation becomes useful in the cases witch the network administrator wants to give access permission as also set different politcs for different backup programs and data.

If the storage is done both on the same disk, we suggest the following structure:

PORTABILITY

Inside the file config.ini (which is created in the program), there is a section [directories] in which the respective folders (as shown above) can be associate with logical variables. This provides portability to the application developed with the BXBMaster. Explaining: If against a set of cubes and queries were raised in an environment of testing/development, production environment, to go where the application were to be home, need not necessarily have the same disc and folder structure.

For example:

A query (query1.bxb) was created in the folder C:\BXBmaster\data (development environment basead on a cube and inserted into base1.cub favorites. After this consultation needs to be ported to another environment (production) and copied to a folder D:\BI\DATA.

What needs to be done: 

1. Before creating base1.cub and consulta.bxb, insert (or check if they already are) in file COFING.ING of development environment, the following row in section.

[Directories]:

Datadir=C:\BXBmaster\Data

1. In production, edit config.ini and add / change within the section [Directories] the following line:

Datadir=D:\bi\data

Thus the application in production environment will find the Base1.cube and Consulta1.bxb in D:\BI\DATA (through variable datadir).

Thus, it is recommended that, just before starting an application for an area not serviced (we will take RH as an example), to create an entry to define the folder where the hub assemblies and consultations will be recorded, thereby, e.g.:

 [directories]

RH=c:\bxbmaster\data

Likewise, the documentation folder, (originally C:\bxbmaster\docs) can be renamed or moved. But remember to always make the proper adjustment in the section [directories] file cofing.ini.

Increasingly, therefore, remember that whenever there is a change in location of the folder, or project files are transferred to another folder, it is essential to review (and adjust if necessary) the sections [directories] in COFING.INI file.

More details about the config.ini file and BXBMaster associating objects to their respective folders are described and illustrated in the document BXBMASTER_Administrador.pdf.