Setup and Configuration › Web Option Considerations › Web Option Environments

Web Option Environments

When installing Web Option for the first-time, create a Web Option Environment data library, known as the environment library. The environment library is used to hold any user data that you create, such as HTML skeletons, screen cross-reference data, and element customization data. The environment library is linked to the Web Option product and LDO libraries through data areas in the environment library.

The combination of an environment library, LDO library, and product library is referred to as the Web Option environment, and it has the same name as the environment library it contains.

In addition to the data areas in the environment library that link to the product and LDO libraries, the environment library contains the WEB2E_SVR job description. WEB2E_SVR includes the Web Option libraries in the following order:

<environment-library>
<ldo-library>
<product-library>

The Web Option runtime retrieves the data it requires to function from all three libraries, with any data in the environment library overriding the data in the LDO library or the product library.

When you generate an HTML skeleton from a CA 2E model, you specify the name of the environment to use (by referencing the YW2ELIB model value held in the CA 2E model). When you start a Web Option server, you specify the name of the environment to start.

After you install Web Option and create the initial environment, you can create additional environments by using the Create Web Option Environment (YCRTW2EENV) command. You might do this to have separate Development, Test, and Production environments that divide out your development processes. Alternately, you can have different environments for different areas of your business; for example, Marketing, Sales, Finance environments.

Each of these environments can have the same LDO and product libraries, so they would all use the same programs. However, each environment uses its own environment library defaults to provide the look, feel, and functionality of the web pages that it delivers. Each environment can be defined to be accessed using the same HTTP server or different HTTP servers. This allows you to limit who can access each environment and from where – on your Intranet or outside your corporate firewall, for example.

Note: Throughout this document, we use the example environment library name of MYWEBENV for code samples and command examples. You can name your Web Option environment libraries any way you want, but remember to adjust the samples and examples accordingly to your library names.