Oracle makes adapters that work with a ton of software, so it makes it a lot easier to integrate with other systems.
It is stable.
Oracle makes adapters that work with a ton of software, so it makes it a lot easier to integrate with other systems.
It is stable.
It's hard to find developers to work on it, and it's also very expensive to license in the cloud.
The pricing is high.
It's very complex and hard to learn. There's a steep learning curve.
The solution is complex to set up.
I've been using the solution for six or seven years.
It's definitely stable. It's fast and it's definitely heavily supported. That's definitely something I would describe it as. The reliability and performance are good.
While it is not scalable in the cloud, it is scalable outside of that.
We have 45 users on the solution currently.
Support is pretty fast and they do work to fix bugs in a timely manner.
I replaced this solution with a Red Hat product.
It's more mature than Red Hat. They have a whole process that you go through. If the bug is their fault, you'll get a fixed board within one to two days, which is great if it's a major issue. I'd say support is a little better than the Red Hat solution.
The initial setup is not straightforward. It's very complex.
The cost of the solution is too high. I can't remember the exact pricing, however, it is extremely expensive. There are cheaper better solutions out there.
We're just a customer or end-user.
I'd rate the solution five out of ten.
It's sort of a one-stop shop for web services. All of our web services interact with each other. Instead of calling specific server host names and specific URLs, we call the OSB service bus URL that's configured for that specific client. It's very simple to know where things are going because we can generate the URL specifically with our naming convention, so that we know where it goes, who's calling it, what environment it's for.
With the most recent version, 12c, I'm still getting use to using it, learning how to use it, how to configure it. The Oracle documentation is OK, but there aren’t a lot of good examples for me to follow. It describes the concepts and what it can do, but how to apply them has been a struggle, so far. I'm still looking for help in that area.
I have been using it for at least eight years.
It is very stable. It processes hundreds of thousands of transactions per month. Once, with our primary system for handling customers coming into our site for orders and order information, the customer would come in and send an email to our internal users; that crashed our Exchange server but OSB kept running. It was fine. It's very stable and it has to be for what it does. It's kind of like a load balancer in a way; if it goes down, then everything behind it will stop operating.
It can meet our scaling needs moving forward. I would be surprised to see it have a problem with scalability.
Technical support is OK. We know what to expect from Oracle support. You're going to ask a question. Generally, you're provided with a document: "Check out this support doc. Does this answer your question?" If it doesn't right away, then they'll take a closer look.
It's OK. It's not ideal, but after working with it for so many years, I know what to expect out of it.
Initial setup is pretty straightforward for an Oracle product. Again, we know what to expect with it and it works well.
When I select a vendor to work with, I look for reliability and ease of use. Performance is everything and this has proven itself over the years. That's why we keep using it.
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.
The most valuable feature is the adapters.
This solution can be easily integrated.
The reporting is very good.
This solution would benefit from having more cloud-based adapters.
I am a solution architect and while my background is mostly in Microsoft solutions, I am familiar with the Oracle products as well. Our company has dedicated teams that are specialized in many different solutions. The choice is driven by the client. For example, if a customer mostly has Oracle products then that is the solution that we implement.
This client for Oracle Service Bus was having trouble with point-to-point integrations, so everything was being done at the back end and it affected the ability to do jobs. This is the reason that they adopted this solution.
The initial setup is a little bit complex. One of the ways it is complex is that there are a lot of features and the customer may not want all of them. Once you figure out which ones the customer doesn't want, they have to be disabled.
The price of this solution is better than the subscription-based Mule ESB.
Mule ESB is another solution that we have a dedicated team for and a lot of experience with. It is very powerful and we felt that in this particular scenario, Oracle had an edge. Mule out-of-the-box is missing a lot of features that Oracle has, and we see this year that Oracle is getting much better than Mule.
Another reason that Oracle was selected over Mule ESB is because of the pricing.
The suitability of this solution depends on the customer's environment and requirements. For situations where they are many integration points, whether they are on-premises or in the cloud, this is a good solution.
Overall, this is a good solution from the user's perspective, but it is a little bit complex to manage.
I would rate this solution a nine out of ten.
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.
The solution will provide a visual view of your total process, which is where, and why it is stuck somewhere and probably where it is. You gain a real-time understanding of where the process is. The reporting around what is happening and if it is stuck, where it is stuck, and what actions to be taken is useful.
Overall, the solution is quite good and has lots of great features. There are always continuous improvements that are happening.
The solution is quite expensive.
It would be ideal if they could optimize it a bit.
I've worked with Oracle for the last seven-and-a-half years.
Any new deployment I've seen has been stable. It's not a problem. There are no bugs or glitches and it doesn't crash or freeze. It's reliable.
The solution is scalable. I've seen banking institutions use it and scale it quite well.
If we are putting this up on the cloud, now they've released something similar to a support cost. They have to give us yearly support. You can actually buy the cloud credits probably if somebody wants to be on the cloud. However, normally you will get support, yearly support. What they've done is you buy back that support using Oracle cloud. With the cloud, you don't need support the way you do with the on-prem models. Support contracts are offered yearly with an annual subscription.
When you need support, you raise a ticket. It's very simple. You follow up and send the logs. It's a long process. People may sometimes try to take Oracle Consulting Services which can also help with various types of things.
The initial setup process depends on project to project, however, typically, everything is paid for. Probably if you want to sell something, everything which is currently being sold in Oracle is specific to the cloud. If they want to move their on-prem to cloud, or they have services, free services, lift and shift services, and of course open-source. You name it and within a month maybe, or three months, depending on the type of job but other than that, everything is costed. Basically, everything, whatever resources you have to buy from Oracle is available and can be taken care of.
Any maintenance requirements are related to whatever package the client decides on.
Oracle can deploy engineers to help with the deployment.
This is a very, very expensive solution. It will cost a company a lot.
It only is available on-premises; it is not subscription-based. These are perpetual licenses. Whether you take it to the cloud or not, with Oracle, you have to pay perpetual licensing. Oracle does not have the cloud as a subscription model.
This was a company that was acquired earlier, from DevLogic. Now people are asking for microservices-based architecture which currently is not an option. Especially, they use SOA services. Everything is not microservices-based architecture today. People who have been in banks, telcos, finance companies, even the government, those who have been using it for a long time, are the people probably who are the target audience right now. However, in the future, people are looking at types of services with architecture systems, which currently, SOA is not.
I'd rate the solution seven out of ten.
I am a part of the software developing team and I mainly use this solution for the integrating applications.
The features most valuable are all of the features relating to the integration of applications.
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.
I have been using this solution for ten years.
The solution is stable.
We have a lot of customers and we have several enterprise applications.
This solution is scalable. We can add to it and we have multiple interfaces.
We have a lot of users, although I am not sure how many.
We have a team of thirty people working and maintaining this solution. Some are developers and some are part of the administrative team.
The technical support is good.
Technical support on the Oracle site is not as good, sometimes we will get our issues resolved but not always.
It may not be for others but I feel that the initial setup is straightforward. It is not complex.
Once I put in a request and it is approved by a manager, it takes ten to fifteen minutes to deploy.
We deploy both on-premises and Cloud. It's a private company cloud, not public.
Oracle a good product. It can be used for the integration of this solution.
I have only received positive feedback for this solution. The features are good. It's sufficient for us.
I would rate this solution a seven out of ten.
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.
The solution is quite stable overall. We haven't witnessed any performance issues so far.
The features on offer are very complete. It's a very good product overall.
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.
This is a very stable solution. Mostly it's focused on attending companies with high availability. There aren't bugs or glitches. It doesn't crash or freeze. It's very reliable.
We have about ten users engaged in the solution currently.
It's my understanding that the solution isn't straightforward. It's actually quite complex.
The setup and onboarding process is hard, and it's made more difficult by a murky licensing process that needs to be clarified.
The licensing process needs to be simplified. It's confusing and tedious. It's very hard to get concrete details out of Oracle in a timely manner. It would be ideal if they could be more exact and specific.
I'm not a customer. I represent a company in charge of integrating solutions for customers, specifically for our customers. We're a partner and implementor.
In general, I would rate the solution at an eight out of ten. Even with the difficulties around licensing, the solution itself is quite good and reliable.
I use this solution for development with complex integration.
This product is not complicated and very easy to learn.
Integrating this solution with other technologies is not difficult.
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.
This solution is stable, although sometimes we see some strange behavior in the developer, where some parts do not appear. In cases like this, we need to reset.
I have not contacted technical support.
Prior to this solution, we used Java and Java Brains suite. Using Java is more complicated, and these things are taken care of by Oracle Service Bus.
Overall, this product is quite good and I feel comfortable when I use it.
I would rate this solution a nine out of ten.
Integration. Writing of services. It's a proxy layer.
It helps in building reusable, well-defined services.
It is lightweight and one can easily integrate with different applications, databases, JMS, or Web services through different protocols.
It needs to support more adapters, because the integration points keep changing and new things keep coming up. It also needs to be more scalable.
Stability is very good.
I have seen that it is able to perform under high-load transactions. It was very good at supporting high transactions, up to 300 transactions per second. That requires more servers, obviously.
Sometimes we have issues, so we'll raise them with Oracle. I would say their support rates eight out of 10.
It needs some knowledge of different artifacts and you also need to have some knowledge of Web servers, the application server, something about the database; at least some knowledge. It is not very difficult and not easy. I would put it somewhere between easy and medium complexity.
When selecting a vendor, at least from the architecture and the developer's standpoints, looking at the implementation and scalability are the two most important things.
Oracle provides good documentation, look through that. This solution is advisable when you need some kind of layer in between, so that it acts as middleware for different systems. That's where you will need to use this.