FESA Software in different Environments

Technically it is possible to release FESA software in different environments. Different environments means a test and a productive environment for example. These different environments must involve different databases and a different CMW nameserver as well. Applications must know in which environment the software runs.

For FESA software this has effects on the release procedure and the configuration of the FECs running FESA software.

During release of FESA software the state-element from the information part of a FESA design (class/deploy-unit/instance design) can be used to decide wether the FESA software is for testing or for productive purposes:

State	Meaning
development	development/test
operational	productive

Release of FESA Software

If the FESA software is released for development/test purposes the FESA designs must be written in the appropriate test database. If the FESA software is released for productive purposes the FESA designs must be written in the appropriate productive database.

The location for the FESA binaries and configuration files will stay the same for each environment.

Running FESA Software

On a FEC the FESA software must use the appropriate CMW directory server. The CMW directory server is selected using a network alias per default. If an environment variable is set another CMW directory server may be used.

The network alias could point to the productive CMW directory server.

The required environment variable for the development/test environment can be set globally on the FEC using a dedicated startup script before running the FESA initialization script in /common/export/nfsinit/<FEC name> . The startup script can be linked/unlinked during release of the FESA software depending on its state.

-- SolveighMatthies - 12 Jul 2016