| Table of Contents | ||
|---|---|---|
|
Objective
You have a given WebLogic Resource properties file stored in a Git repository. This properties file will define several data sources we want to deploy to a WebLogic server. The WebLogic servers we will be using in this tutorial are running Oracle SOA Suite, but this tutorial can be used for all WebLogic servers, regardless of installed technology. The goal of the tutorial is to automate the deployment of the configuration across multiple environments. This automation will include:
...
Scroll through this guide to fill in the blueprint properties. Name the Project well to describe what configurations you are managing.
...
Select Topology from the menu and choose a Target Group on the left. You will see a list of Environments on the right with colored circles representing each Target.
...
Color coding represents:
...
Select the Environment we want to build the application in. All active environments that have been marked as build Environments will appear in the dropdown.
Select the SCM branch that was configured on the project. This will be defaulted to the main branch.
Submit the request. This will initiate the Build WebLogic Configurations workflow.
...
Upon submission, the build workflow is initiated and the workflow steps are executed on the SOA instance in the Dev environment utilizing the SOADEV endpoint. Upon completion of the workflow, the execution status will be shown as successful or failed.
...
With the successful execution of the build, a few property file artifacts are created, stored in the artifact repository and marked with the Project Version. Every build will generate a new Project Version. The generated properties artifact can be viewed from the Execution Id link and the Artifacts tab.
...
Select the Project Version. The form will default to the latest Project Version but the dropdown will contain all previously created Project Versions.
Select the Environment that the deployment will be executed in.
Select the Deploy Target Group(s). Deployments can happen on multiple Target Groups.
Submit the request, which will initiate the Deploy Config Configurations workflow.
...
Upon submission, the deploy workflow is initiated and the workflow steps are executed on the SOA target group in the Dev environment, utilizing the SOADEV endpoint. Upon completion of the workflow, the execution status will be successful or failed.
...