So far in topology we have completed the following tasks:

Created Endpoint connections to the application-tier nodes of our EBS servers
Create four logical Environments - Development, Test, QA, and Production
Create a logical Instance, Global EBS, and associated to our four environments

At the completion of this section, you will:

understand the relationship between environments, instances, and endpoints
learn how to map environment/instance combinations to physical endpoints
learn how to configure property values for environment/instance properties

The next step is to bind the instance to the physical endpoint(s) for each environment. By associating instances to environments, a matrix is formed in the Topology Overview. To view the matrix, select Topology from the main menu, and then click on the Topology Overview from the left-hand pane.

For each environment which we mapped to our instance, a "balloon" icon appears in the matrix. Click on the balloon to map its endpoints and configure its properties.

First we will configure Global EBS in Development. Click on the balloon, then select the Endpoints tab.

Next click on the Properties tab. Here we see the properties which are mapped to the instance. These properties are gathered from workflows associated to our instance, and any plugin operations used by those workflows. We do not have any properties defined on our build and deploy workflows, but the mapped EBS plugin operations define three properties.

Property	Description
EBS Database User	The user id used to connect to the EBS database. Defaults to "apps", and would rarely be changed.
EBS Database Password	The password for the EBS Database User.
EBS Source Script	The unix source script which sets up the environment and sets a host of EBS related properties.

Click Save to apply the changes.

Repeat the steps above for Test, QA, and Production.

Tip - EBS 12.2.x

Note that our QA environment is running EBS 12.2.6, which uses RUN and PATCH editions for online patching. In this tutorial we are deploying directly to the RUN edition and will avoid online patching. This is the approach that more customers are following, and utilizing online patching only for application of Oracle patches. However, FlexDeploy has support for both models. To deploy directly to the run edition, we supply the run parameter to the EBS Source script. If you were to use online patching, you would leave off the parameter and let FlexDeploy inject the proper edition at runtime.

FlexDeploy also has plugin operations to help automate the online patching (ADOP) phases. See the Oracle EBS Plugin Guide for details.

The Topology Overview is now complete.

Tip

Note the coloring scheme for the balloons. The balloons were red when no configuration was started, and green when endpoints were associated and required property values entered. Yellow indicates that the configuration is partially completed.

Completed 6 of 11 Sections	Continue to Git Integration	Back to Instances

Browser not supported