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:
...
Change the branch name to match the git repositories branch name. Click on Save.
...
Target Properties
Select Topology from Topology from the menu and then select Topology Overview from choose a Target Group on the left menu. You will see a table that has Instances as the rows and Environments as the columns list of Environments on the right with colored circles representing the Environment Instanceeach Target.
...
Color coding represents:
RED - no required properties are set and/or the The Endpoint is not configured
YELLOW - some of the required properties are set and/or the Endpoint is not configurednot set,
GREEN - all required properties are set and the Endpoint is configured
Selecting Clicking the GREEN circle environment row for DEV will display the configurable properties/allows modifying the Endpoint and allows for the configuration of the properties.
...
Build Execution
...
The Build Request Form will appear and we need to:
select the environment we want to build the application in, the environments that had the Build Environment checkbox will appear in the dropdown.
select the SCM Branch that was configured on the project, this will be pre-populated if there is only one configured 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 successful.
...
We'll start by creating a Workflow Property for the datasource password.
Go back to the Main tab of the Workflow
Under Workflow Properties, choose open the Add men.
From the Add menu, we can add an existing property, or create a new one. Select New Property
Properties must each have a unique code, give a meaningful code for the new property
A property display name does not have to be unique and can contain spaces. This is the name that will be displayed on the Environment Instance screen
Select the property scope, this defines where the property will be configured. We're using Target because this property will be different for each environment
This property is a password, so we'll set Encrypted to Yes. This will keep the value hidden from screens and logs
...
With the Datasource Password property created, we will also need to create one more property – SOA_TARGET. This property will be used as the target for the datasource FlexDeploy creates. We will create it the same way as the last property, except this time we can leave Encrypted set to No, because we don't need to encrypt the server name. If you have many plain text values that differ between environments, you can also use folders stored in Git to handle them.
...
Select Topology from the menu and then select Topology Overview from the left menu. You will see a table that has Instances as the rows and Environments as the columns with colored circles representing the Environment Instance and select the YELLOW circle under the DEV environment.
...
Now the properties artifacts can be deployed to an environment by selecting the icon as shown in the below screenshot.
The Deploy Request Form will appear and we need to:
Select the Project Version. The form will default to the latest Project Version but the dropdown will contain all previously create Project Versions.
Select the Environment that the deployment will be executed in.
Select the Deploy Instance, which will be defaulted from the Project configuration. Deployments can happen on multiple instances.
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 instance in the Dev environment, utilizing the SOADEV endpoint. Upon completion of the workflow, the execution status will be successful.
...
The Execution Id is a link to all of the execution data related to each request, such as
The workflow execution steps
The logs for each workflow step, click on the link under step
The artifact which can be downloaded
The project and environment instance property values at the time of execution
...
Congratulations! You have successfully completed the WebLogic Resource tutorial.
...