Share your experience using Managed Methods JaxView

I implemented this hybrid integration platform for the finance sector at one of the big banks in Egypt. I used it inside the services exposed from the banking sector only, not for the asset management inside the bank. We use the service registry because we have a lot of services that need to be made available for every party.

The governance is the best value. CentraSite is necessary for the governance and service registry. The governance is powerful, and you can look up services very easily, which may reduce some development cycle time.

Policy management is very good and simple to use. It's easy to make a lot of policy management and create policies from scratch.

It's also good because it's based on Kibana, making it good to use Elasticsearch. This makes the Software AG and CentraSite dashboards different from any other party.

There is a big difference in deployment modules and different deployment scenarios. It can be adapted to any environment, not only finance or government. The deployment can be made for each data center.

CentraSite should be integrated with an open-source registry like UDDI.

It would be good to integrate with IBM solutions.

I have been using this solution for one year.

I didn't test it for stability, but it's still working right now, so I can rate it seven or eight out of ten.

The functionality is good. It has support from IBM and support from Software AG as well. I think it's fully supported by IBM right now. If you have a product working with a service registry and repository and supported by the vendor, you can trust the functionality.

If you compare CentraSite to WSRR, the former IBM WSRR, CentraSite is the best. It's better than WSRR for simplicity and deployment. If you compare it to open sources like UDDI, CentraSite is good because it's supported by IBM and has many more functionalities that don't exist in UDDI.

I also work with WSRR, WebSphere Service Registry and Repository from IBM. It's now retired and out of support.

The setup is mild. It's not so simple and not very difficult. You can make it happen with some configuration, but it's not easy for non-professional people.

I have worked with WSRR, WebSphere Service Registry and Repository from IBM, which is now retired and out of support.

webMethods is better than the webMethods API Gateway from my point of view. The webMethods API Gateway is the best API Gateway for performance and simplicity.

I work with GraphQL, REST API, and SOAP services as well. API Connect works with GraphQL and can deploy GraphQL services. I also work with GraphQL in Software AG webMethods API Gateway.

I'm working with DataPower. I have experience with IBM API Gateway, API Connect, Event Stream, and App Connect, the Cloud platform integration. I didn't involve DataPower with BPM before. I have used the webMethods API Gateway.

I have used an open-source framework that is not a product for a specific vendor. I work with GraphQL in three different products: API Connect, the API Gateway of the webMethods Software AG, and the Java Spring framework.

I work with CentraSite and also work with the Integration Server, webMethods Integration Server, and Universal Messaging. The governance is powerful.

I can recommend CentraSite for any industry working with service registry and repositories. I would rate it eight out of ten.

I have seven years of experience with IBM solutions and rate them nine or ten out of ten. I have one year of experience with webMethods and rate it eight out of ten. I have five years of experience with other solutions.

The overall review rating for this product is seven.

I can describe several use cases for Oracle SOA Suite; it is fundamentally a middleware product. In software architecture, we refer to it as middleware. Middleware is an application that lies between multiple applications as a broker or message flowing platform.

For example, if an ERP system holds the data, we do some reporting. Ideally, middleware does not handle that work, but when ERP systems require data from multiple systems, middleware comes into the picture to take the data from multiple sources and send it to multiple targets.

That's where the job ends; once the data is received by the target application, they will do whatever the use case or requirement is.

The main benefits I've seen from using Oracle SOA Suite arise in a large enterprise landscape where multiple applications such as Salesforce, Oracle ERP cloud, SAP, and Workday exist. In such setups, Oracle SOA Suite effectively facilitates communication between different systems. For instance, your employee payroll data should flow from Workday to Oracle ERP.

Oracle SOA Suite serves as the best-fit product to eliminate point-to-point integration, consolidating this flow logic, filtering, and ensuring messages are transferred to target applications. Ultimately, the source system does not need to know whether the message reached the target.

The best features of Oracle SOA Suite, during the initial times around 2010 to 2015, made it a very robust platform as middleware. It has multiple built-in adapters, a strong WebLogic server, an easy-to-understand user development interface, and quick development timelines. Moreover, it offers excellent monitoring for applications, providing real-time insights and details about the successful and failure flows.

These were the good parts about this product, with many in-built technology and application adapters, and a stable server.

I have utilized Oracle Business Activity Monitoring in Oracle SOA Suite, which is another product available within this suite. The Business Activity Monitoring, or BAM, gives you real-time monitoring and sensor data if activated in our process. The data flow, payload, and all transformations get stored in a database, allowing you to see what has happened in that flow through your BAM application web page.

The integration capabilities of Oracle SOA Suite in connecting disparate systems within the organization are excellent. There are numerous features still available, and it has a cloud platform as well. It's beneficial that we can install Oracle SOA Suite in OCI cloud. Oracle SOA Suite was primarily on-premises, but now there's a cloud version, allowing us to take a marketplace and use an initial license or buy a new license to deploy the application on the OCI platform.

The current product Oracle provides, called Oracle Integration Cloud, is also very robust and offers more adapter connectivity features. However, the challenge is that Oracle SOA Suite is a stateful application, meaning it persists data and keeps transactions open, while Oracle Integration Cloud is more serverless or stateless, acting as a fire and forget method.

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.

I have been working with Oracle SOA Suite since 2008, making it approximately 14 to 15 years of experience.

Product-wise, Oracle SOA Suite is stable, but it requires knowledgeable individuals to navigate its complexities. It's not something that anyone could manage; you need someone with experience, which is true for other platforms.

The scalability of Oracle SOA Suite is high; it allows for extensions and the addition of new interfaces without requiring server shutdowns, resulting in a highly scalable environment.

I have escalated questions to Oracle customer service and technical support, and I would say that their customer service is moderately responsive. There have been many instances where I've been stuck for longer periods awaiting resolutions.

Neutral

I haven't worked with competitors of Oracle directly, but I know there are many competitive products in the market that offer features similar to Oracle SOA Suite.

The initial setup of Oracle SOA Suite is complex; while the standalone environment might be straightforward for developers, production environments with clustering and load balancing require dedicated infrastructure administrators for proper setup.

Our customers always deal directly with Oracle when purchasing; we do not utilize partners or different marketplaces such as AWS Marketplace or Azure Marketplace.

I have not exactly calculated the ROI or found it cost-effective; it doesn't provide a clear return on investment to my customers.

The setup cost of Oracle SOA Suite is relatively high since various components, including database licenses, WebLogic licenses, VM costs, and SOA licenses based on enterprise and Oracle negotiations, contribute to expenses. Overall, customers often find the costs for Oracle SOA Suite higher than for Oracle Integration Cloud.

On a scale of 1 to 10, I rate Oracle SOA Suite an 8 out of 10.

My advice to organizations considering Oracle SOA Suite is to ensure they have a strong infrastructure support team capable of managing applications and servers, which is critical.