There are areas of Oracle SOA Suite I would like to see improved or enhanced in the future, particularly regarding its adapter capabilities. The popularity of Oracle Integration Cloud nowadays arises from its larger set of adapter capabilities, including numerous application adapters. In contrast, Oracle SOA Suite provides a limited number of adapters. I would like to see more REST-based features added to Oracle SOA Suite, currently lacking, along with an enhancement of file size or payload capability, as the existing limitation is a 10 MB payload size. Additionally, Oracle SOA Suite licensing cost tends to be higher, adhering to a fixed pricing model rather than a pay-per-use basis, which might not be suitable for smaller organizations.
The solution’s initial setup is complex and could be improved. A big challenge for Oracle SOA Suite is that you don't get too many technical resources.
Director of Tech and Consulting Services at Oriontax
Reseller
Sep 28, 2023
The features we've been installing are really, really robust. The only challenge that we have down here is that most individuals have not improved so much. But the features are quite mature. The only tenant is that they would not have enough knowledge to be able to interact with those features and integrate them with their systems. So, to improve other than the training or the performance of those that are using the package. Another area of improvement is performance. Because with multiple solutions connecting to the SOA platform, in time, the performance of the SOA platform can be affected. So, that could be one area that could be improved with the SOA. Also, licensing is another area of improvement. It seems to be a high cost, especially for our customers. So that is something that we might look at improving.
The deployment could be made easier by including add-ons like Hudson and Maven. The add-ons and tools for deployment need to be improved. Patches should also be improved. Most of our clients are heading towards the cloud. The cloud integration features need to be improved. Almost most of the integration solutions are UI based. Those are very lightweight solutions, whereas SOA Suite is heavyweight. The product should become more lightweight, and it should be UI based.
I would like to see divided containers more separately as a microservice. Try to convert more in microservices and be less monolith than it is, because at this time it is more monolith than microservice.
IT Systems Director at a energy/utilities company with 1,001-5,000 employees
Real User
Dec 1, 2022
An area for improvement in Oracle SOA Suite is the cost. It could be lower. My company even thought about moving to an open-source product, WSO2, but decided that microservice architecture would be best for the company's architectural approach and use cases, such as building systems.
An important area that can be improved is the product's data monitoring. When we use the solution for interfacing or end-to-end data monitoring, we want to know exactly where the data is going and exactly where it is failing, or where there is an issue.
Oracle Training Consultant at a financial services firm with 501-1,000 employees
Consultant
Dec 27, 2021
The resiliency of this application can have problems with a downstream system., sometimes it's unable to recover quickly. You have to restart the services. However, this is most likely because I'm using an old version, which is 12.1.3, but if I upgrade to 12.2, then that will problem will be resolved. I'm in the process of thinking of upgrading it.
Application Engineer at a manufacturing company with 1,001-5,000 employees
Real User
Dec 1, 2020
There are networking and firewall issues that tend to delay our projects. I believe that is the case with any middleware. The documentation and details can be a little better, and more user-friendly. They supply lots of documentation but finding what we need is challenging at times. There is room for improvement in terms of support. In the next version of this solution, I would like to see improvements made to the test environment for real-time testing. There is a lot of new software that isn't there until you deploy, which means that you cannot test real-time.
With respect to the feature that allows each process to be accessible and reviewed at a later time, it is a great debug option, but we did notice the database size getting larger by the day. Is there any option available that will allow the process history to be moved to a different schema? If so, it would not affect the performance. If the disk space expansion can be made more flexible, not requiring a database restart, it would be a major benefit.
The product is very good considering tracing, ease of use and troubleshooting. However, the development environment requires a big machine with potent CPU/memory, and SOA server takes many minutes to be up, you can't run anything else on the computer. In production, when you have lots of composites running on the SOA server, it takes up to 30 min to restart the server. Microservice was created to solve these weaknesses of standard SOA approach.
retired at Centro de Estudios y Promoción del Desarrollo - DESCO
User
Jun 24, 2018
This solution should allow for data output to spreadsheets and other formats. During training, it is necessary to be closer to the end user to properly manage the product.
Various parts of SOA, BPEL, and so on, each have their own consoles which need to be accessed individually with different logins. It would be better from an admin perspective if all the consoles were accessible via a single login.
Solution Architect at a tech services company with 201-500 employees
MSP
Mar 31, 2016
The Integrated Development Environment (IDE), which is JDeveloper in this case. Also, the integrated development environment could be better in some points such as the stability and the comprehensibility of errors. EDIT: The Maven integration in JDeveloper is very basic and might be enhanced to allow the proper use of Maven.
Oracle SOA Suite is a comprehensive, standards-based software suite to build, deploy
and manage integration following the concepts of service-oriented architecture (SOA).
The components of the suite benefit from consistent tooling, a single deployment and
management model, end-to-end security and unified metadata management.
Oracle SOA Suite helps businesses lower costs by allowing maximum re-use of existing
IT investments and assets, regardless of the environment (OS, application server,...
There are areas of Oracle SOA Suite I would like to see improved or enhanced in the future, particularly regarding its adapter capabilities. The popularity of Oracle Integration Cloud nowadays arises from its larger set of adapter capabilities, including numerous application adapters. In contrast, Oracle SOA Suite provides a limited number of adapters. I would like to see more REST-based features added to Oracle SOA Suite, currently lacking, along with an enhancement of file size or payload capability, as the existing limitation is a 10 MB payload size. Additionally, Oracle SOA Suite licensing cost tends to be higher, adhering to a fixed pricing model rather than a pay-per-use basis, which might not be suitable for smaller organizations.
The solution’s initial setup is complex and could be improved. A big challenge for Oracle SOA Suite is that you don't get too many technical resources.
The features we've been installing are really, really robust. The only challenge that we have down here is that most individuals have not improved so much. But the features are quite mature. The only tenant is that they would not have enough knowledge to be able to interact with those features and integrate them with their systems. So, to improve other than the training or the performance of those that are using the package. Another area of improvement is performance. Because with multiple solutions connecting to the SOA platform, in time, the performance of the SOA platform can be affected. So, that could be one area that could be improved with the SOA. Also, licensing is another area of improvement. It seems to be a high cost, especially for our customers. So that is something that we might look at improving.
The product is not user-friendly. It is very complicated. It is very hard to get the reports.
The deployment could be made easier by including add-ons like Hudson and Maven. The add-ons and tools for deployment need to be improved. Patches should also be improved. Most of our clients are heading towards the cloud. The cloud integration features need to be improved. Almost most of the integration solutions are UI based. Those are very lightweight solutions, whereas SOA Suite is heavyweight. The product should become more lightweight, and it should be UI based.
The solutions can improve the communication or translations between formats, such as JSON and XML. The JSON REST API could improve.
I would like to see divided containers more separately as a microservice. Try to convert more in microservices and be less monolith than it is, because at this time it is more monolith than microservice.
An area for improvement in Oracle SOA Suite is the cost. It could be lower. My company even thought about moving to an open-source product, WSO2, but decided that microservice architecture would be best for the company's architectural approach and use cases, such as building systems.
There needs to be separate guided learning for the usage of tools. It's also not developer-friendly.
An important area that can be improved is the product's data monitoring. When we use the solution for interfacing or end-to-end data monitoring, we want to know exactly where the data is going and exactly where it is failing, or where there is an issue.
The resiliency of this application can have problems with a downstream system., sometimes it's unable to recover quickly. You have to restart the services. However, this is most likely because I'm using an old version, which is 12.1.3, but if I upgrade to 12.2, then that will problem will be resolved. I'm in the process of thinking of upgrading it.
There are networking and firewall issues that tend to delay our projects. I believe that is the case with any middleware. The documentation and details can be a little better, and more user-friendly. They supply lots of documentation but finding what we need is challenging at times. There is room for improvement in terms of support. In the next version of this solution, I would like to see improvements made to the test environment for real-time testing. There is a lot of new software that isn't there until you deploy, which means that you cannot test real-time.
With respect to the feature that allows each process to be accessible and reviewed at a later time, it is a great debug option, but we did notice the database size getting larger by the day. Is there any option available that will allow the process history to be moved to a different schema? If so, it would not affect the performance. If the disk space expansion can be made more flexible, not requiring a database restart, it would be a major benefit.
The product is very good considering tracing, ease of use and troubleshooting. However, the development environment requires a big machine with potent CPU/memory, and SOA server takes many minutes to be up, you can't run anything else on the computer. In production, when you have lots of composites running on the SOA server, it takes up to 30 min to restart the server. Microservice was created to solve these weaknesses of standard SOA approach.
This solution should allow for data output to spreadsheets and other formats. During training, it is necessary to be closer to the end user to properly manage the product.
Various parts of SOA, BPEL, and so on, each have their own consoles which need to be accessed individually with different logins. It would be better from an admin perspective if all the consoles were accessible via a single login.
The Integrated Development Environment (IDE), which is JDeveloper in this case. Also, the integrated development environment could be better in some points such as the stability and the comprehensibility of errors. EDIT: The Maven integration in JDeveloper is very basic and might be enhanced to allow the proper use of Maven.