Connect Free Oracle Autonomous Database from MuleSoft

 A database is the most commonly used backend in the integration world. We often build a lot of integrations with databases (be it as a source or target system). Likewise, working on a proof-of-concept, we always find it hard to have a database that we can use on a local machine or on the cloud. If we install a database on a local device it will consume a lot of resources. Not only that connecting from a cloud integration platform i.e. MuleSoft cloudhub is always tricky.

Oracle has an always free-to-use Autonomous Database instance available on the cloud with limited features but is really a powerful database to use. We would say, it is one of the best suitable for doing proof of concepts and validation before working on an actual use case.

We thought of giving it a try to connect MuleSoft to the Free version of the Autonomous Oracle database. We created a free trial account for Oracle and an always-free autonomous database instance. Once we have the instance created, we can connect using SQL developer easily. But now the question is 

How to connect this database using MuleSoft?

Let's start with prerequisites.

Prerequisites

1. Log in to the oracle cloud instance and navigate to the autonomous database instance.

2. Click on the database connection. Then click on Download wallet.

3. Enter the wallet password (and make a note of it, which will be used in later steps)and click on Download. The wallet.zip file will be downloaded.

4. Extract the downloaded zip file. We will see below files extracted.

To connect to Oracle Autonomous Database, we can use either 
  1. mTLS, enabled by default.
  2. TLS

The below steps will be familiar to both configurations

1. To fetch the connection URLs, we can either get them from the database instance page. Click on Database connection and scroll down to connection strings.

2. Select either TLS or mTLS under TLS authentication.

3. There will be 5 TNS(database service names) names available: high, low, medium, tp, and tpurgent. Click on the show, the TNS we may want to use, and copy the string. The string will contain all the details like host, port, service name, etc.

 4. We can also get all these details from the file tnsnames.ora extracted from the wallet.

Connect using mTLS configurations

Whenever we create a new autonomous DB instance, only mTLS is enabled by default. To connect to the database, we need to configure 2 way SSL along with database credentials in MuleSoft.
  • Copy the keystore.jks and truststore.jks under the "src/main/resources" directory of the mule project. We can also keep it under a separate directory. In this example, we will be using the "wallet" folder to store these files.
  • Configure the database connection as below:
  • By providing these details, we will not be able to connect to DB as we have not configured mTLS. Click on the TLS tab and configure the details below.
Note: Keystore password, Keystore key password, and trust store password will be equal to the wallet password which we gave while generating the wallet on the OCI console.
  • Click on Test Connection, and we will see the connection is successful.

Connect using TLS configurations

To enable connectivity through TLS, we need to update the Access Control List(ACL) in the database instance under networking.

Please refer below link to configure TLS in the Oracle Autonomous database instance.

Once TLS is enabled at Oracle Cloud Autonomous database, we can configure TLS. The only difference in the configuration will be to use only the trust store instead of configuring both the key store and the trust store.


Thank you for reading and please share any thoughts or comments.



-

Comments

Post a Comment

Popular posts from this blog

DateTime formatting using xp20:format-dateTime ()

xs:dateTime Format In XML, we generally use xs:dateTime(xs:xmlns="http://www.w3.org/2001/XMLSchema") data type to store date time data. The generic representation of date time, that is supported by xs:dateTime in xml: YYYY-MM-DDThh:mm:ss[.SSS][Z|(+|-)hh:mm] Example :  2019-09-11T10:16:31.943+05:30 Code Description Example YYYY represents a 4-digit year 2019 MM represents a 2-digit month 09 DD represents 2-digit date 11 hh represents 2-digit hours 10 mm represents minutes in 2-digits 16 ss represents seconds in 2-digits 31 SSS represents milliseconds 943 T represents time separator T Z represents UTC time zone or 0 time zone offset (+|-)hh:mm represents time zone offset +5:30 Few more valid examples : 2019-09-11T21:32:52, 2019-09-11T21:32:52+02:...
Read more

Create Delimited String from XML Nodes and Vice Versa in SOA 12c

A delimited string is a string representation of data separated by a delimiter(e.g. ","). A simple representation of the delimited string will look like. Delimited String Examples Sample-1-- Delimiter as ","        Value1,Value2,Value3   Sample-2-- Delimiter as "|"        Value1|Value2|Value3 If we want to represent the above set of delimited values in the form of an XML document under some root and parent tag. The representation will look like this. XML Example <root xmlns="http://test.com/sample/xml">   <Values>     <value>Value1</value>     <value>Value2</value>     <value>Value3</value>   </Values> </root> Sometimes we may need to convert values coming in delimited string to an xml document or vice versa. Since delimited strin...
Read more

Import and Export MDS artifacts in SOA 12c

Image
Oracle SOA-MDS (Metadata Store) repository can be used to access artifacts that can be shared among various SOA composites. For example, we have one common schema for a business fault that is consumed by various applications. Instead of having a localized copy of that schema file in each SOA composite, we can have it in a centralized repository (SOA-MDS). Another benefit of using SOA-MDS is that we can change the file at runtime and need not redeploy the complete code. While developing SOA composites, we use SOA design-time repository, later these changes can be synced to the SOA servers. In this article, we will discuss 2 ways to sync the artifacts available in the SOA design-time repository and the SOA servers. Establishing the connection to SOA-MDS in Jdeveloper. Using SOA em console or Fusion Middleware control console. Moving a file between SOA composite to SOA design-time MDS repository Let's assume, we created a businessFault.xsd which wi...
Read more