- Introduction & WOW Environments

Introduction

[PRO] WOW Environment Modes requires WOW Professional or Enterprise Editions.

In enterprise level development, organizations will often have multiple systems and databases (or environments) allowing a separate DEVELOPMENT, and PRODUCTION environment. This allows developers and users to properly test new code without affecting production users. WOW supports this need by allowing specification of the environment that various configurations belong to.

Using a WOW Environment Mode allows connections/field descriptors/operations to be designated as belonging to one particular environment or another. An instance of WOW can also be associated with a particular environment, and will use that environment when selecting which connection/field descriptor/operation to use. For example, a metadata schema might have two connections with the alias "MY_CONN"; one of the connections could be associated with the DEV environment and the other associated with the PROD environment. When a DEV WOW instance is asked for the MY_CONN connection, it would return the first (DEV) connection. A PROD WOW instance reading from the same metadata schema would retrieve the second (PROD) connection. In this way, the same metadata can be used by both a development server and a production server.

A WOW Environment Mode only needs to be set when a single metadata schema (or two identical schemas) are used in two different WOW environments.

Note: Using a WOW Environment Mode is an advanced technique which is not necessary for most WOW installations.

WOW environments

There are 3 specific WOW Environment Modes:

• DEV (Development)

• PROD (Production)

• TEST (Testing)