Working with Multiple Environments Follow

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

When working with different environments you may have situations where you need different settings for each environment. For example, you may have two different DBs for Test and for Production. Therefore, you may need to set different DB addresses and credentials to the DB in each environment.

Setting Environment Variables

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

You can add as many Environment Variables as you need.

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

Identifying the environment easily

In order to clearly locate your preferred environment, and to prevent confusion when working with multiple environments, a special environment variable can be found, named ENVIRONMENT_NAME. You can set it up to any name you like. For example: 

ENVIRONMENT_NAME=Integration

In this case the name Integration will be presented on all Service Manager pages.