Outbound Integration Points

This integration point gives an overview of all endpoints an Oracle Health Insurance applications sends messages to. This IP is a runtime catalogue that shows all outbound integration points, their endpoints and the endpoint characteristics. The IP helps in setting up- and diagnosing network connectivity.

Future versions of the Oracle Health Insurance applications may contain features to send test messages to selected endpoint(s) to test and monitor connectivity.

Background

The Oracle Health Insurance applications are part of a landscape of applications with which they communicate by sending and receiving messages. Getting the connectivity set up and right can be challenging:

  1. The Oracle Health Insurance application has to be able to reach the other applications which may run in another network segment, or Cloud provider, or even on-premises.

  2. Network engineers have to make sure that traffic can reach the other application as typically due to security outbound traffic is restricted to known hosts.

  3. It is not easy to find out for a given Oracle Health Insurance setup where all messages are being sent to. This information needs to be gathered from different places: URL’s are defined in various system properties and configuration (like Claim Event Rules or Callout Rules) is of influence.

  4. To test the connectivity, the business flow that sends the message must be invoked. This is something that requires complete setup and knowledge of Oracle Health Insurance to trigger.

This IP is the first step in addressing those challenges: it gives a single complete overview of all defined endpoins in an Oracle Health Insurance application with their key characteristics. This IP helps to fix challenge 3.

As said, a future step is to enable the sending of test messages for a given endpoint. Combined, setting up and testing connectivity can be verified without the need to trigger Oracle Health Insurance business flow and without the need to have configured the Oracle Health Insurance application in place. Those test messages can also be used for daily monitoring of the connectivity.

Getting an Overview of all Defined Endpoints

To retrieve all the defined endpoints, GET request has to be sent to the following URI:

http://<host>:<port>/<context-root>/outboundintegrationpoints

The response returned shows all integration points, their endpoints with the attributes of the endpoints. See example below:

{
  "items": [
    {
      "name": "Claims Event IP",
      "endpoints": [
        {
          "useCase": "CLAIM_EVENT_CODE",
          "authenticationFeature": "BasicAuthentication",
          "HTTPMethod": "POST",
          "messageMediaType": "application/json",
          "destinationURL": "<some URL>"
        }
      ]
    },
    {
      "name": "Claims Out IP",
      "endpoints": [
        {
          "useCase": "ClaimsTransactionOutNotificationClient",
          "authenticationFeature": "BasicAuthentication",
          "HTTPMethod": "POST",
          "messageMediaType": "application/json",
          "destinationURL": "<some URL>"
        }
      ]
    }
  ]
}

Meaning of the attributes:

  • "useCase": an identification of the use case that sends the message

  • "authenticationFeature": the authentication mechanism used for sending the message.

  • "HTTPMethod": is the message delivered using PUT or POST

  • "messageMediaType": the type of payload. JSON or XML.

  • "destinationURL": where the message is sent to.