Using REST APIs to manage Connections in OIC

In cases, when we have many connections created on the OIC instance, it becomes hard to manage connections using the OIC console. Also, to achieve automation, manually going and updating each and every connection is never a feasible task. OIC provides various REST APIs to fetch connection details, update connection properties and delete connections. With the help of these APIs, we can overcome such scenarios.

In this blog, we will be discussing how to use various OIC connections REST APIs. A postman collection in the public workspace, which contains some of the use cases for this and can be forked, updated, and used accordingly.

Below are various REST APIs, that are covered in this blog.

  1. Retrieve Connections
  2. Retrieve a Connection
  3. Update a Connection
  4. Test a Connection
  5. Refresh Metadata for a Connection
  6. Delete a Connection
In this blog, we will be using Postman to test and run various APIs. Below is the link to the Postman collection, which will be helpful to try and test different REST APIs.

Authentication for REST APIs

To invoke OIC connections REST APIs, BASIC AUTH can be used to authenticate and authorize calls. The user whose credentials are used to call these APIs must have access to edit the connection.
OAuth can also be used to authenticate to REST APIs. In this blog, we will be using Basic Auth to authenticate/authorize API calls.

1. Retrieve Connections

[GET] {oic_host}/ic/api/integration/v1/connections

{oic_host} - Host URL for OIC instance

This API lets to get all available connections available on the OIC instance. This API provides support for pagination also. The default number of connection information returned without using the limit query parameter is 101.

We can use the limit query parameter to limit the number of records returned. For example:


  As in the above example, we have kept the limit as 5, if we want to get the next 5 connection details, we need to update the request as below

 [GET] {oic_host}/ic/api/integration/v1/connections?limit=5&offset=5

 This will return the connections 6-10.

To make this response even more readable, we have added a Visual table using the Postman visualizer. Once you click the Visualize under the response the section after sending the request from this Postman collection, the below tabular representation is shown.

2. Retrieve a Connection

[GET] {oic_host}/ic/api/integration/v1/connections/:id

{oic_host} - Host URL for OIC instance.

:id - Connection ID of the connection in OIC instance, to be passed as the path parameter.

This API lets you fetch connection details of a specific connection by adding Connection ID as a path parameter to the request URL.

To make this response even more readable, we have added a Visual table using the Postman visualizer. Once you click the Visualize under the response section after sending the request from this Postman collection, the below tabular representation is shown.

3. Update a Connection

[POST]{oic_host}/ic/api/integration/v1/connections/:id

{oic_host} - Host URL for OIC instance.
:id - Connection ID of the connection in OIC instance, to be passed as the path parameter.

This API helps to update the connection properties of a particular connection in the OIC instance. Let's take an example to update the REST Connection properties that include Base path and Basic Auth user credentials.

Request Headers: 

X-HTTP-Method-Override: PATCH

Request:
{
    "connectionProperties": {
        "propertyGroup": "CONNECTION_PROPS",
        "propertyName": "connectionUrl",
        "propertyType": "URL",
        "propertyValue": "{{CONN_REST_URL}}"
    },
    "securityPolicy": "BASIC_AUTH",
    "securityProperties": [
        {
            "propertyGroup": "CREDENTIALS",
            "propertyName": "username",
            "propertyValue": "{{CONN_USERNAME}}"
        },
        {
            "propertyGroup": "CREDENTIALS",
            "propertyName": "password",
            "propertyValue": "{{CONN_PASSWORD}}"
        }
    ]
}
Here, {{CONN_REST_URL}} will be the base URL of the REST endpoint. {{CONN_USERNAME}} and {{CONN_PASSWORD}} will be the credentials for BASIC Authentication for invoking the REST endpoint.

4. Test a Connection

[POST] {oic_host}/ic/api/integration/v1/connections/:id/test

{oic_host} - Host URL for OIC instance.
:id - Connection ID of the connection in OIC instance, to be passed as the path parameter.

This API is an alternative to the TEST button on OIC Connection page for a particular connection. Below is an example of successful testing of a Connection.


5. Refresh Metadata for a connection.

[POST] {oic_host}/ic/api/integration/v1/connections/:id/metadata

{oic_host} - Host URL for OIC instance.
: id - Connection ID of the connection in OIC instance, to be passed as the path parameter.

Sometimes, we may cache metadata for a connection, and if for some reason metadata is changed but our connection is still referring to old metadata. This API can come in handy. Below is the sample invocation of REST API in postman to refresh the metadata of a connection.

6. Delete a Connection

[DELETE]{oic_host}/ic/api/integration/v1/connections/:id

{oic_host} - Host URL for OIC instance.
:id - Connection ID of the connection in OIC instance, to be passed as the path parameter.

This API can be used to delete a connection available on the OIC instance. This API saves a lot of time to perform delete operations rather than going to UI and manually deleting a connection. All you need to know is the connection id of the connection. Below is an example of the successful deletion of Connection by triggering the API using Postman.


To Validate if the Connection is deleted or not we can use a retrieve a connection API and check if the connection is available or not.

References:

https://docs.oracle.com/en/cloud/paas/integration-cloud/rest-api/api-integrations-connections.html

Please share your valuable feedback in the comments section below 😊


-

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 string is similar to csv format. We can create
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