What means that whatever happens to your RAC installation, your programs get always a JDBC working connection even when a RAC node brutally dies or that a node is simply shutdown for maintenance. Better, when the RAC node restart, the JDBC pool get balanced to use the restarted node.

Here is how to configure it:

1. Installation

You need to have :

a RAC installation of at least 2 nodes (mine is version 12.1.2.0.2)

a JDeveloper or Weblogic installation to configure the JDBC Gridlink datasource (mine is JDeveloper 12.1.3)

Add all the files of the JDeveloper application to the git repository
Menu : Team / Git / Add all…

Commit to the local repository
Menu : Team / Git / Commit all…

In DCS, Create a remote git repository in Developer Cloud Service
Copy the HTTPS url of the repository in a text editor, you will need it later.ex: https://xxx@developer.em2.oraclecloud.com/xxx/s/xxx_workbetter/scm/wb.git

Add a build.

Go to main tab “Build”

Click “New Job”

In Subtab “Main”, give a name, for ex: BuildWorkBetter

In Subtab “Source Control”, choose the GIT repository created in step 4

In Subtab “Triggers”, check the “Based on SCM polling schedule” checkbox to allow automatic compilation when the DCS GIT repository is modified. Leave the schedule empty.

In Subtab “Build Step”, set the way to build the program, for example

Add Build Step : ant

Set Targets : deploy

Set Build File : build.xml

In Post Build, define the artifacts (the result of the build)

Check “Archive the artifacts“

File to archive. This is the place where for example your ear and war file will be created. Ex: ViewController/deploy/*

In JDeveloper, push the local GIT repository of JDeveloper to the remote repository in DCS.
Menu : Team / Git / Push …
– URL use the https url of step 4
– username: use your cloud user name
– password: use your cloud password
Click Next
Click Finish

Back in DCS,
In the tab “Code”, you will see that your code is now in GIT.In the tab “Build”, you will see that the code is being build.

If it compiles, you will see the list of artifacts in build tab.

In DCS, click on the tab “Deploy” and click “New Configuration”

Configuration name : DeployWB

Application

Deployment Target (New Java Cloud Service)

Protocol SSH Tunnel

Host: your Java Cloud Service Admin Server IP (1)

HTTPS: 7002

Adminitration Port : 9001

username : <<weblogic user>>

password : <<weblogic password>>

Type: automatic

Job : BuildWorkBetter

Artifact : select the .ear file

Click “Save”

IN JCS, you can check that the deployment has succeed. Log in to the Weblogic Server Console. Go to deployment, look for your deployed project.

Get the URL of your external IP, probably a load balancer (2)
Check that it works.https://<load balancer IP>/<Application URL>