Working with Multiple Environments Follow

Like in any application, we recommend working with several environments: Development, Test, Integration, Production, etc. It all depends on your work procedures, the amount of your developers, etc.

Having multiple environments, you may need different settings for each environment. For example: to use different DBs with different addresses and credentials for Test and for Production.

Environment Variables

Environment Variables are environment-specific properties that reflect the difference between different servers/environments. You can set the environment variables via Admin->System properties.  While System Properties are identical for all environments, Environment Variables are environment specific, and won’t be copied when migrating from one environment to another.

Using Environment Variables

You may use Environment Variables via ${env.VAR_NAME} reference in:

• Service Form URL / host
• Service input parameter values
• Test Case input parameter values
• Test Agent mail title
• System Properties

Environment name

To easily identify your current environment and prevent confusion, you may set an environment name - and it will appear on the top right corner of your ServiceManager interface.
It may be set via the ENVIRONMENT_NAME environment variable:

You may use any environment name you like, however there are a few pre-defined environment names - which will be automatically highlighted with a colored background - to help identifying them even better:

The predefined colors are set to the following names (substring match):

['Dev'],                           //green
['Test', 'Tst', 'QA'],             //teal
['Stg', 'Staging', 'Integration'], //yellow
['Prd', 'Prod']                    //orange