Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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. It is a best practice to name the Project with the same name as the SOA Composite, a FlexDeploy property (ProjectName and FD_PROJECT_NAME) will be automatically set and can be utilized during the configurationName the Project well to describe what configurations you are managing.

...

Project Info

Property Name

Value for this tutorial

Description

Project Name

HRWLSConfigurations

The name for the project for WebLogic Configurations.

WebLogic COnfigs Description

Order

Brief description of the project for WebLogic Configurations.

Oracle WebLogic Install Name

SOAHR

This value will provide environment independent name for SOA install (eg. SOA, SOAHR ).

...

Property Name

Values for this Tutorial

Description

WebLogic Domain Directory

locate this value from your server.

The WebLogic Domain Directory for managed servers.

WebLogic Home Directory

locate this value from your server.

Weblogic Home Directory. Subfolders such as ‘common’, ‘modules’, and ‘server’.

Domain Name

soa_domain

The WebLogic Domain Name.

Oracle MiddleWare Home (MW_HOME)

locate this value from your server.

The oracle middleware home (which has subfolders such as oracle_common, wlserver, coherence*, etc.)

For example: /u01/oracle/products/fmw

Admin Server Listen Address

soalt03.flexagon

The listener address for the WLS Admin Server.

Admin Server Listen Port

7001

The port for the WLS Admin Server.

Admin User

weblogic

The admin username for the WLS Admin Server.

Admin Password

locate this value from your WLS admin server.

The admin password for the WLS Admin Server.

 The Project Name will be auto updated to HRWLSConfigurations since it takes the value same as Application Nameis HRWLSConfigurations.

The Folder path is auto-updated to FlexDeploy/WebLogic/ and click on “Create

Click Create.

...

We can see the Folder hierarchy on the top of the project.

...

We're going to be creating WebLogic datasources, and more often than not require a password, EIS, and JMS configurations. Some of the values that are required to create them are passwords. It would be much too insecure to store these passwords in plaintext in the properties file we check out from Git. That's where FlexDeploy's workflow properties come in. We can create a property to store the password encrypted in FlexDeploy, then use a placeholder in the file for FlexDeploy to replace with the password during the deployment. This is useful not only for security, but also for any value that may change across environments (e.g. server names).

...

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.

...

Make sure to save the workflow after adding the properties.

...

Now that you have configured FlexDeploy for one WebLogic Configuration, it is extremely easy to add more configurations.  Simply use the Copy Project feature and a new project will be created with all of the configuration completed already.  Just name the new project and select the appropriate FlexDeploy application.  With everything copied, you can simply change the configuration as needed and be ready to build/deploy in minutes.