Environments Overview
Fabric Environments are used for running the same project implementation on various data sources and parameters. Switching between the environments is done according to specific needs. For example:
- Defining environments for development.
- UAT testing and production.
- Switching between several different testing environments in the K2view TDM.
An environment is defined by either a partial or a full list of a project's interfaces together with their connection details (server, port, etc.), and it must be deployed to the server. Additionally, an environment can override the values in globals.
Only one environment can be active, at a specific time, after it is selected from a predefined list of environments and switched to as needed.
An environment can be deployed either from the Fabric Studio or in a target server (aka an environment's offline deployment).
An environment can be deployed either from the k2cloud UI or by an environment's offline deployment.
Explicit definition of the environments in a project is optional. When no environment is defined and a Logical Unit is deployed to a Fabric server, all the project's interfaces are deployed together with their connection details to a default _dev environment. The default environment is displayed neither in the Fabric Studio nor in the environment's configuration XML file.
An environment can be defined on a cluster level and on a session level. Therefore, a user can override an active environment per session and work on it without interacting with the changes of other users. Setting and resetting an active environment per either cluster or session, is performed using the SET environment commands.
Environments Overview
Fabric Environments are used for running the same project implementation on various data sources and parameters. Switching between the environments is done according to specific needs. For example:
- Defining environments for development.
- UAT testing and production.
- Switching between several different testing environments in the K2view TDM.
An environment is defined by either a partial or a full list of a project's interfaces together with their connection details (server, port, etc.), and it must be deployed to the server. Additionally, an environment can override the values in globals.
Only one environment can be active, at a specific time, after it is selected from a predefined list of environments and switched to as needed.
An environment can be deployed either from the Fabric Studio or in a target server (aka an environment's offline deployment).
An environment can be deployed either from the k2cloud UI or by an environment's offline deployment.
Explicit definition of the environments in a project is optional. When no environment is defined and a Logical Unit is deployed to a Fabric server, all the project's interfaces are deployed together with their connection details to a default _dev environment. The default environment is displayed neither in the Fabric Studio nor in the environment's configuration XML file.
An environment can be defined on a cluster level and on a session level. Therefore, a user can override an active environment per session and work on it without interacting with the changes of other users. Setting and resetting an active environment per either cluster or session, is performed using the SET environment commands.
