1 1 Directory Structure for LANSA under Linux

Deploying Visual LANSA Applications on Linux

1.1 Directory Structure for LANSA under Linux

The installation of LANSA will create a set of directories under $LANSAXROOT.

For each partition imported into LANSA, a new directory called x_ppp (where ppp is the 3 character partition identifier) will also be created.

The main directory structure is shown below:

The following directories are used to store information common to all partitions:

   $LANSAXROOT/x_lansa

   $LANSAXROOT/x_lansa/source

   $LANSAXROOT/x_lansa/bin

For example, libx_bif.so (the BIF shared library) resides in x_lansa/bin because it is composed of common routines shared by all LANSA generated applications.

Some of the types of objects stored in the source and bin sub-directories are:

Directory

File Type

Description

source

.c

C Code

.h

C Code header

.stg

C Code header - storage definitions

.unx

Compiler/linker make file

.xqi

DBID=*NONE useable read only index file

.xqd

DBID=*NONE useable read only data file

.xqf

DBID=*NONE useable read only flat file

.ctd

Common table definitions

.dat

Saved data for reload after table creation

.txt

UTF-8 user-defined text strings

.utx

C header for user-defined text strings

.log

Log from Deliver To processing

bin

.so

Executable shared library (equivalent to a Windows .DLL)

None

Executable object (equivalent to a Windows .EXE)

.sh

Shell script (equivalent to a Windows .CMD or .BAT file)

log

x_err.log

Fatal error log

lroute.*

Comms log and trace files.

tmp

x_trace*

Trace files for LANSA runtime, when ITRO=Y is specified.

.tmp

Temporary files

 

Ý 1. Deploy LANSA Applications to a Linux Server