Multiple Environment Configuration

Multiple Environments may be configured with a single application server instance supporting multiple Environment installations.

Each Environment must belong to one WebSphere server and profile, since system libraries must be loaded into the JVM. The WebSphere profile for the Environment is uniquely assigned to a node that is federated into the deployment manager cell.

Deploying multiple Environments into separate WebSphere profiles offers the advantage of a single administrative console for management of all installed Environments. It also allows for independent file system artifacts for each profile definition.

When multiple Environments are installed, they can be uniquely accessed with a single web server employing unique virtual hosts, or through unique web servers, possibly deployed on separate machines. These approaches may be combined as needed to meet your computing environment requirements.

When using profiles to manage multiple Environments within one WebSphere installation, all profiles must be maintained at the same WebSphere patch level.

Multiple Environments per Single WebSphere Instance

The following illustration shows a system that has one installation, or instance, of WebSphere managing both the Landmark and Infor Lawson System Foundation Environments through the creation of multiple profiles. The Environments share the same %WAS_HOME% value.

Each profile is mapped to a unique node, and assigned to a unique Landmark or Infor Lawson System Foundation Environment, or other Lawson web application component. These nodes are federated into a common management cell.

Using this approach, any number of Environments can be managed by the same Deployment Manager. This type of configuration could be used to create a test and production configuration, or a production and development configuration.