inet.env

inet.env is a Lycia configuration file that contains environment variables used at runtime when running applications via LyciaDesktop and LyciaWeb.

What you must know about inet.env

Querix Package Manager doesn't create inet.env.

By default, 4gl applications are successfully executed at runtime and do not need a custom environment.

However, you might need to change your Lycia environment, for example,

• to write specific debugging information to application logs,
• to build debug cache,
• to specify the end-user format for DATE values,
• to turn on the compatibility mode,
• to customize your MDI container, etc.

This can be easily done in custom inet.env by setting different environment variables.

Contents of inet.env

These are environment variables that are most often set in inet.env:

• PATH, FGLIMAGEPATH, FGLLDPATH, DBPATH, CLASSPATH, LD_LIBRARY_PATH, FGLSOURCEPATH
• QXDEBUG, LYCIA_SEVERITY, LYCIA_POST_MORTEM_LENGTH
• QX_COMPAT
• DBDATE, DBFORMAT, DBMONEY

Here you can read more about different environment variables and their possible values.

Structure of inet.env

inet.env doesn't have any specific structure.

When you have only created it, inet.env is absolutely empty and doesn't include any environment variables.

You must add environment variables according to their definition rules.

For example, different environment variables can take these kinds of parameters:

• any non-empty value:

  QX_UNL = 1

• a list of one or more characters:

  QXDEBUG = mv

• one or more predefined values:

  LYCIA_SEVERITY = error

• a path / paths to a file or a folder:

  FGLIMAGEPATH=%FGLIMAGEPATH%;.;C:\Program Files\Querix\Lycia\images

You can read these definition rules in every page about environment variables, e.g., here, here, here, or here.

 

At runtime, environment variables are applied one-by-one in the order they are defined in inet.env.

For example, here QXDEBUG will be applied before QX_COMPAT:

There is no specific order in which you must define environment variables in inet.env.

But there are moments you should keep in mind:

1. If you accidentally define one and the same environment variable multiple times in one inet.env, the last value will be applied at runtime.

   For example, in this situation:

   QXDEBUG = UuBbSsEedPptLlCcmGOzAzKzQzTzVv

   QX_COMPAT = Informix4GL

   QXDEBUG = mv

   you will get less detailed logs (as compared to the original value).

2. If you use the value of one environment variable (= v1) as a value for another environment variable (= v2), v1 must go before v2.

   Correct order:

   LYCIA_DIR=C:\Program Files\Querix\Lycia

   FGLLDPATH=%LYCIA_DIR%\my_4gl_libs;%LYCIA_DIR%\my_4gl_libs

   Wrong order:

   FGLLDPATH=%LYCIA_DIR%\my_4gl_libs;%LYCIA_DIR%\my_4gl_libs

   LYCIA_DIR=C:\Program Files\Querix\Lycia

inet.env and application server instances

As inet.env is used to configure the environment in which your 4gl applications are executed, it is tightly bound with application server instances.

This means that every inet.env must be

• created for a specific application server instance, and

• specified for this application server instance in listener.xml:

  <envfile>C:\my_projects\my_configs\my_environment</envfile>

By default, Lycia comes with two application instances – default and secure.

Default location for custom inet.env is

We recommend you to work with these two in-box application server instances and save your inet.env in the default location.

 

However, if you want to save your inet.env to any other location, you must specify this location in listener.xml.

If you do not specify it in listener.xml., your inet.env will not be loaded and applied at runtime.

How to create your inet.env

There are two ways to create custom inet.env:

• from LyciaStudio, and
• in any text editor.

Method 1.

To create inet.env from LyciaStudio, please follow these steps:

Step 1. Exit all 4gl applications, if any.

Now you can add all the necessary environment variables and set their values.

Step 6. Save your changes.

Step 7. Rerun you 4gl applications, if any.

This method works only for creating the first custom inet.env. If you already have one such file and want to create the second, you must use another method (below).

 

Method 2.

To create inet.env in a text editor, please follow these steps:

Step 1. Exit all 4gl applications, if any.

Step 2. Open your favorite text editor.

Step 3. Set all the necessary environment variables in a new file.

Step 6. Rerun you 4gl applications, if any.

How to manipulate your inet.env

To modify an existing AppServer instance, please follow these steps:

Step 1. Exit all 4gl applications, if any.

Corresponding inet.env will be opened in LyciaStudio.

Step 4. Add all the necessary environment variables and set their values.

Step 5. Save the changes.

Step 6. Rerun you 4gl applications, if any.

 

You cannot delete inet.env from LyciaStudio.

To delete your inet.env, please follow these steps:

Step 1. Exit all 4gl applications, if any.

Step 3. Delete inet.env from this folder.