The Topology Overview displays the association between one environment and one instance. An Environment Instance pair Each pair is created by either associating an Instance to an Environment on the Edit/Create Environment Wizard, or associating an Environment to an Instance on the Edit/Create Instance Wizard. Endpoints and properties values are mapped to those Environment Instance pairs.
Each Instance likely has a development environment, a production environment, and at least one testing environment. The association of Environments to Instances defines a matrix. Endpoint association and properties are defined at each intersection.
This table depicts four Environments identified as by rows, and two Instances which are identified as by columns. Each Environment Instance combination intersection defines which Endpoint(s) host the Instance for that Environment, and the Environment-specific properties which are required to communicate to the underlying technology. Note that the SOA2 Instance in the DEV and SIT Environments do not have any Endpoints or configuration properties defined because SOA2 is not associated with those Environments.
SOA1 | SOA2 | |
|---|---|---|
DEV | Endpoint(s) | N/A |
SIT | Endpoint (s) | Endpoint (s ) |
UAT | Endpoint (s) | N/A |
PROD | Endpoint (s) | Endpoint (s) |
...
Every circle on the screen represents an Environment and Instance assocation. The configuration of these pairings can be viewed and edited by clicking the circle.
Updating Environment Instance Properties
...
Icon | Description |
|---|---|
| All required properties are not setunset, and or there is no endpoint associated to the Environment Instance pair. |
| Some required properties are set, but other required properties have been left empty. At least one endpoint is associated to the Environment Instance pair. |
| All required properties are set and there is at least one endpoint associated to the Environment Instance pair. |
...
Once an Endpoint has been shuttled to Selected Endpoints, optional Resource Types can be assigned. The Resource Types indicates what type of resources the Endpoint contains, which helps in determining which Endpoints should be selected to perform particular plugin executions. For example, the Weblogic plugin has Resource Types of WLS Admin Server, WLS Managed Server, and WLS Node Manager. Selecting the Resource Type(s) for each Endpoint tells FlexDeploy a little bit more about the Topology and enables it to direct work appropriately (e.g. to the Weblogic Admin Server vs. one of its Managed Servers).
...