...
...
...
...
...
...
...
...
...
...
...
...
...
...
At the completion of this section, you will:
- understand the use of environments in the deployment process
- be able to create/modify an environment
Now we need to create an environment in FlexDeploy that mimics the structure of the customer's actual environments. Environments are a logical grouping of servers, technologies and applications that form an independent solution for development, testing and production. Deployment of a composite to different environments allows developers to simply develop new features in Dev, without interfering with the QA group testing services. We will create three environments in order to show the deployment of a composite across multiple environments.
...
An Environment is a logical name given to a group of servers, applications, and technologies which work together to provide a software solution for the purpose of development, testing, or a production implementation. Typical Environments include, but are not limited to, Development (DEV), System Integration Testing (SIT), User Acceptance Testing (UAT), and Production (PROD).
For this tutorial we will create four environments - Dev, Test, QA, and Production. These environments host our physical EBS installations for our logical global EBS instance.
| Tip | ||
|---|---|---|
| ||
We will deploy our customizations into Test, QA, and Production. Since development typically occurs directly in the Development environment it would not make sense to deploy there. For web applications, deploying into Development makes much more sense. For EBS, we will execute our builds in the Development environment. This would allow us to extract the customizations for Development EBS during the build phase. For the example in this tutorial we will source all of the customizations from GitHub, so technically we could execute our builds anywhere. |
You can view the list of defined environments by selecting Topology from the menu, and then
...
selecting the Environments tab from the left-hand pane. There are no environments with a new installation, so next we will create them.
Click on the + in the upper right corner to create and configure a new Environment. Configure the following:
- environment code
- environment name
- build environment, this indicates whether this environment will appear in the drop down during the build execution.
For the SOA Suite build, a SOA Suite installation is required because the build utilizes installed libraries and files. Instead of having a seperate SOA Suite installation in a BUILD environment, we will utilize the DEV environment as both a BUILD and DEV environment. This is accomplish by changing the Build Environment dropdown to Yes.
We will create two additional Environments for QA and PROD so we can deploy to multiple environments. The Build Environment drop down should be No for these Environments, otherwise these Environments will appear in the drop down during build execution.
After creating these, the Environment screen should look like this.
| Completed 5 of 10 Sections | Continue to Environment Instance Configuration | Back to Instance Creation |
|---|
...