The error handling capability can be improved, but the present capacity just meets the requirements. The error should be properly displayed in Oracle Service Bus instead of the user's need to search in logs.
Sales Manager/ VBM at a tech services company with 51-200 employees
MSP
Top 10
2024-02-21T13:24:00Z
Feb 21, 2024
There is significant room for improvement in the monitoring capabilities. Enhancing this aspect of our monitoring process is essential for effectively pinpointing the root cause of issues accurately and resolving issues in our system.
In my opinion, Oracle needs to improve its connectivity with the new applications, like, ServiceNow Salesforce, and it needs to be improved more adapters so that it can easily connect with others. Moreover, there is room for improvement in customer service and support.
J2ee solution architect at a tech services company with 201-500 employees
Real User
Top 20
2023-02-07T17:08:00Z
Feb 7, 2023
The weak point of OSB is that it is not suitable for modern application implementation like microservices which need smart endpoints. With a dumb pipe through and rest API or lightweight message, Bus is not.
Solution architect at a comms service provider with 501-1,000 employees
Real User
Top 5
2022-12-01T16:27:29Z
Dec 1, 2022
Service Bus lacks two main elements. The first is accessibility with the REST services and JSON. These are things that are generally available in most of the APIs address space nowadays. The second would be improved cloud compatibility. Oracle sometimes lags behind when it comes to newer formats.
Vice President Information Technology at Bharat Financial Inclusion Ltd
Real User
Top 20
2022-11-07T13:53:03Z
Nov 7, 2022
An area for improvement in Oracle Service Bus is the roadmap for its product launch. Currently, it's unclear, so Oracle should develop a roadmap for version 12c, so people can see what's coming out of that version of Oracle Service Bus. Cloud hosting is an additional feature I'd like to see in the next release of Oracle Service Bus.
What needs improvement in Oracle Service Bus is the connectivity between adapters such as the Salesforce adapter and database adapters. The limited number of adapters compatible with Oracle Service Bus makes you want to switch to a different solution.
Senior Manager Enterprise Architecture at a individual & family service with 1,001-5,000 employees
Real User
2021-12-15T21:36:00Z
Dec 15, 2021
The tracing. Some unknown errors will sometimes happen and the error message isn't clear. The security process to protect the servers also needs improvement. Sometimes, you need to open the whole project and complete another setup in the server, then hurry back and go through the service application to complete the security setup. If Oracle SB had one button to complete this process in one step, it would be better. For the next update, I'd like to see event-driven architecture.
Middleware Specialist at a financial services firm with 1,001-5,000 employees
Real User
2021-10-05T13:32:45Z
Oct 5, 2021
There are several improvements that could be made to the product. Security needs to be more integrated, there are so many new security techniques on the market that could be integrated. They should also be embedding API key and other security mechanisms. I find the solution to be somewhat lightweight.
Principal Lead at a tech services company with 51-200 employees
Real User
2021-02-23T05:59:11Z
Feb 23, 2021
I can't recall coming across any missing features. There isn't anything glaring that is lacking in the product. The initial setup is likely complex for many organizations. In terms of the solution itself, they should be more open with the information that they provide about the licensing process. It's incredibly difficult to understand the licensing for Oracle Service Bus and it's a whole long process to get the information from Oracle itself.
Oracle Fusion Middleware Technical Lead at Saint-Gobain ADFORS CZ s.r.o.
Real User
2021-02-04T17:30:28Z
Feb 4, 2021
Mainly our integrations are under JMS. We are looking at some products which have good features and performance related to the JMS. Even if tomorrow if you're planning to replace JMS with Kafka or some other product, then it will be feasible to do it very quickly. However, in Oracle, we have seen a lot of difficulties when we go to integrate Kafka with the replacement of JMS. The personal settings are not up-to-date, in terms of orchestration. In Italy, we use SOA, however, we have faced a lot of difficulties when we have orchestration projects. The interface console is very slow. Even in production, we need to increase the RAM or CPU. And even after that, the performance is still not good in production. Sometimes, we have seen data loss from the EM. We can't even recover the data from the back end table. Even if we ask the Oracle support team to get a patch they're taking one or two months for the production issue to resolve. These issues are killing the business and productivity. For this reason, management decided to replace Oracle with some other products that are also based on the current application - such as SAP and TIBCO. We're updating our system anyway, so it is a good time to get rid of Oracle. With Oracle right now, we have to hire more people in the support team to look into all the issues we're facing. That is killing our delivery times and everything. If I want to do certain integrations or use certain plugins, it occasionally can be really difficult to do the configuration in Oracle Service Bus.
Lead Tech of Oracle Service Bus with 51-200 employees
Real User
2020-02-26T05:55:54Z
Feb 26, 2020
I had a problem with one of my projects because OSB cannot send cookies to the RESTful services. This solution should work better with RESTful services.
The main inconvenience is the composition between services. Using software initiation, occupation with BPM, or BPI is better. There are issues, especially if you want to create some compensation in your service bin. If you have six or seven services you call in the same process, it's very difficult and that's the main issue. I get compensation with the WBS tool. Another point relates to monitoring. When you want to show what's happened in your system, you have to deploy a direct system on each service. It's simple to put the monitoring on your BPM and that's the main difference for me. Also, connectors can be on Apache Kafka, on Oracle, or OpenESB, or on Mule, it's the same thing. It's how you execute the process. For example, OpenESB support is the difference between the interface with the service and the implementation. Oracle is more intelligent. When you want to invoke a service B, for example, you don't directly invoke service B but ask the system for the best and most accurate implementation of B for your system and it provides that. You can't do that with a simple ESB. For additional features, if I compare OpenESB, there is the possibility to define policy between services so that when you create a connection, you can't associate the connection with the policy. That could be included in the solution.
The connectivity with the solution is an area that needs to be improved. On occasion, requests are lost due to losing connectivity. Also, there should be proper monitoring of what is coming into and going out of the Service bus and it should be logged. Every request should be logged. Technical support on the Oracle site needs improvement. When we have an issue, we create an SR for Oracle. The read the request, but they do not respond properly. When creating the SR, they ask for a lot of information from us. The requested information is provided to them but still, a solution is not provided. It would be a benefit to have proper instruction on the different types of configuration or to have an example or suggestion for different types of Scenarios and how to configure them. I would like the configuration information provided to us.
There are times when I select components in composite and they do not appear, and I cannot figure out why. This can happen when you develop a big project and clone it, then look for a service. Sometimes, you cannot find your work. It's a big problem.
Oracle Service Bus transforms complex and brittle architectures into agile integration networks by connecting, virtualizing, and managing interactions between services and applications. Oracle Service Bus delivers low-cost, standards-based integration for mission critical SOA environments where extreme performance, scalability and reliability are critical requirements.Oracle Service Bus enables companies to use the values of their enterprise applications portfolio. From on-premise, to the...
The error handling capability can be improved, but the present capacity just meets the requirements. The error should be properly displayed in Oracle Service Bus instead of the user's need to search in logs.
There is significant room for improvement in the monitoring capabilities. Enhancing this aspect of our monitoring process is essential for effectively pinpointing the root cause of issues accurately and resolving issues in our system.
In my opinion, Oracle needs to improve its connectivity with the new applications, like, ServiceNow Salesforce, and it needs to be improved more adapters so that it can easily connect with others. Moreover, there is room for improvement in customer service and support.
If they can containerize this, that would be nice. If they can provide docker images and offer support for those containers, that would be great.
The weak point of OSB is that it is not suitable for modern application implementation like microservices which need smart endpoints. With a dumb pipe through and rest API or lightweight message, Bus is not.
Service Bus lacks two main elements. The first is accessibility with the REST services and JSON. These are things that are generally available in most of the APIs address space nowadays. The second would be improved cloud compatibility. Oracle sometimes lags behind when it comes to newer formats.
An area for improvement in Oracle Service Bus is the roadmap for its product launch. Currently, it's unclear, so Oracle should develop a roadmap for version 12c, so people can see what's coming out of that version of Oracle Service Bus. Cloud hosting is an additional feature I'd like to see in the next release of Oracle Service Bus.
What needs improvement in Oracle Service Bus is the connectivity between adapters such as the Salesforce adapter and database adapters. The limited number of adapters compatible with Oracle Service Bus makes you want to switch to a different solution.
The solution is quite expensive. It would be ideal if they could optimize it a bit.
The tracing. Some unknown errors will sometimes happen and the error message isn't clear. The security process to protect the servers also needs improvement. Sometimes, you need to open the whole project and complete another setup in the server, then hurry back and go through the service application to complete the security setup. If Oracle SB had one button to complete this process in one step, it would be better. For the next update, I'd like to see event-driven architecture.
The pricing of the product could be better. It's a bit high.
There are several improvements that could be made to the product. Security needs to be more integrated, there are so many new security techniques on the market that could be integrated. They should also be embedding API key and other security mechanisms. I find the solution to be somewhat lightweight.
The support for GraphQL needs to be improved, and the response time for global support could be faster.
I can't recall coming across any missing features. There isn't anything glaring that is lacking in the product. The initial setup is likely complex for many organizations. In terms of the solution itself, they should be more open with the information that they provide about the licensing process. It's incredibly difficult to understand the licensing for Oracle Service Bus and it's a whole long process to get the information from Oracle itself.
Mainly our integrations are under JMS. We are looking at some products which have good features and performance related to the JMS. Even if tomorrow if you're planning to replace JMS with Kafka or some other product, then it will be feasible to do it very quickly. However, in Oracle, we have seen a lot of difficulties when we go to integrate Kafka with the replacement of JMS. The personal settings are not up-to-date, in terms of orchestration. In Italy, we use SOA, however, we have faced a lot of difficulties when we have orchestration projects. The interface console is very slow. Even in production, we need to increase the RAM or CPU. And even after that, the performance is still not good in production. Sometimes, we have seen data loss from the EM. We can't even recover the data from the back end table. Even if we ask the Oracle support team to get a patch they're taking one or two months for the production issue to resolve. These issues are killing the business and productivity. For this reason, management decided to replace Oracle with some other products that are also based on the current application - such as SAP and TIBCO. We're updating our system anyway, so it is a good time to get rid of Oracle. With Oracle right now, we have to hire more people in the support team to look into all the issues we're facing. That is killing our delivery times and everything. If I want to do certain integrations or use certain plugins, it occasionally can be really difficult to do the configuration in Oracle Service Bus.
I had a problem with one of my projects because OSB cannot send cookies to the RESTful services. This solution should work better with RESTful services.
The main inconvenience is the composition between services. Using software initiation, occupation with BPM, or BPI is better. There are issues, especially if you want to create some compensation in your service bin. If you have six or seven services you call in the same process, it's very difficult and that's the main issue. I get compensation with the WBS tool. Another point relates to monitoring. When you want to show what's happened in your system, you have to deploy a direct system on each service. It's simple to put the monitoring on your BPM and that's the main difference for me. Also, connectors can be on Apache Kafka, on Oracle, or OpenESB, or on Mule, it's the same thing. It's how you execute the process. For example, OpenESB support is the difference between the interface with the service and the implementation. Oracle is more intelligent. When you want to invoke a service B, for example, you don't directly invoke service B but ask the system for the best and most accurate implementation of B for your system and it provides that. You can't do that with a simple ESB. For additional features, if I compare OpenESB, there is the possibility to define policy between services so that when you create a connection, you can't associate the connection with the policy. That could be included in the solution.
This solution would benefit from having more cloud-based adapters.
The connectivity with the solution is an area that needs to be improved. On occasion, requests are lost due to losing connectivity. Also, there should be proper monitoring of what is coming into and going out of the Service bus and it should be logged. Every request should be logged. Technical support on the Oracle site needs improvement. When we have an issue, we create an SR for Oracle. The read the request, but they do not respond properly. When creating the SR, they ask for a lot of information from us. The requested information is provided to them but still, a solution is not provided. It would be a benefit to have proper instruction on the different types of configuration or to have an example or suggestion for different types of Scenarios and how to configure them. I would like the configuration information provided to us.
There are times when I select components in composite and they do not appear, and I cannot figure out why. This can happen when you develop a big project and clone it, then look for a service. Sometimes, you cannot find your work. It's a big problem.