What is your primary use case for Oracle Service Bus?

In previous organizations, Oracle Service Bus was predominantly used to build integration pipelines between many applications present in the network. In current organizations and projects, it remains in extensive use, providing various integrations needed for application landscapes and supporting different business operations.

We use the solution for alerts and triggers with the help of API.

I am using the solution to support core banking systems by managing the APIs. Whenever web services need to be deployed in the Service Bus we are using the solution.

The use case involves tasks such as determining the appropriate licensing size, collaborating on firewall projects, and constructing the infrastructure to support the product. In most cases, I focused on integrating Oracle Service Bus to address issues, primarily with local ISPs and one ISP in Colombia. For larger projects covering all offices in Colombia, as well as two or three other projects, my involvement extended to local ISPs in Buenos Aires, specifically with Firecorp, a service provider catering to various companies within the country.

We are using Oracle Service Bus to connect multiple applications with multiple environments. So it's like we are connecting ServiceNow to Salesforce and ServiceNow to a legacy system.

We use Service Bus to expose our service endpoints.

I use Service Bus to integrate multiple applications at an enterprise level. I work in the telecom sector and we integrate multiple applications and build PRM and CRM inventory systems. We are customers of Oracle and I'm the integration lead.

I'm using Oracle Service Bus for all real-time web services.

We use Oracle Service Bus to send data to ServiceNow because we needed to connect Salesforce to ServiceNow, so that's our use case for the solution.

It becomes the platform for all managed file transfers. If you're looking at a high-speed managed file transfer or solution around that, it becomes a basic layer, or especially in use cases in payment gateways, or API-based types of solutions, probably this becomes a default there.

We are doing lots of aggregation and routing – the two most important features that we are using it for – and transformation of the services and data. I am using the latest version, 12.1.4. It's deployed on AWS cloud and on-prem.

The middleware provides the service from our core banking and manages the equipment from the satellite system to the core banking SMS or to any other system. Any system can communicate to another system through the solution.

The solution is primarily used for the ESB. When we want to integrate applications with each other, they want to communicate with each other, we use this. If one application wants to send a message to some other applications. It's used for transformation and integration.

We use the solution for message processing.

This solution can be used for internal connectivity between enterprise applications and a Telco client.

We are currently primarily using the solution for an energy company that is looking to remove the endpoint integration that they have. They want to move to an Applications Federation BOT. That's how we are seeing critical severity loss into the solution. Instead of having the point-to-point integration, we want to implement it as an Enterprise Service Bus.

We are using Oracle Service Bus to connect between API management and microservices. For example, we use it for data transformation, bringing data from a specific form in one service to another form in a different service.

I'm an integration architect and we're a customer of Oracle.

We are an IT solution provider and this is one of the products that we implement for our clients. We have competencies in different ESB products including Mulesoft ESB, Oracle Service Bus, and Microsoft BizTalk.

I am a part of the software developing team and I mainly use this solution for the integrating applications.

I use this solution for development with complex integration.