All companies, large and small, manage multiple environments for the purpose of development, testing, or hosting production solutions. Each of these environments comprise a number of platforms, technologies, and packaged applications across a varying number of servers (whether physical, virtual, or in the cloud). The centralized FlexDeploy server requires configuration information to be able to communicate across this broad topology.

Let's checkout an example of environments below. You may have completely different names and number of environments. FlexDeploy allows for configurations of environments which is further used for You can configure permissions, approvals, schedule windows, pipeline configurations etc, and other settings on specific environments.

Now each Each environment will generally have some technology components. As environments are used for different purposes, it is very likely that same application applications installed in various environments may be configured differently even in terms of capacity. Our goal is to promote code and configurations through environments for various applications, middleware, databases. FlexDeploy calls such each individual track of technology across environments "a Target Groups". See example below for horizontal cross sections through environmentsGroup. The wide rectangles that go through multiple environments below are Target Groups. Each Target Group is uniquely identified in FlexDeploy.

Now that we have Environments and Target Groups, it is easy to realize that there is intersection for both logical constructs. This intersection is known as an Environment-Instance or Environment-Target Group. Each Environment Instance represents physical installation of some technologyThe intersection of an Environment and Target Group is known as a Target or Environment-Instance. A target is the installation of a technology in a specific environment. You will configure each Environment Instance for various configuration Target with properties and endpoints, which will allow allows FlexDeploy to communicate with that specific installation to perform necessary actions. Note that Build and Deploy actions are also invoked in the context of a specific Environment Instance, i.e. Target. For example, you may be deploying an EAR to the DEV environment of the WLS1 Target Group.

So, FlexDeploy allows customers to describe their topology using Environments, Target Groups, andEndpoints. This topology definition provides the necessary mechanics for configuring Endpoints and properties to effectively manage your enterprise network of platforms, technologies, applications and servers. Builds, Deployments, Utility Executions, and Test Executions are run on Targets, the intersection of an environment and Target Group.

Screens used to configure and maintain Topology Settings

...