Red Hat JBoss SOA Platform drives business execution, responsiveness, and flexibility in an open platform. It delivers what the vendor describes as an easy-to-consume service-oriented architecture (SOA) integration suite that lets users build, deploy, integrate, and orchestrate applications and services.
N/A
Oracle WebLogic Server
Score 7.4 out of 10
N/A
Oracle WebLogic Server is a unified and extensible platform for developing, deploying and running enterprise applications, such as Java, for on-premises and in the cloud. WebLogic Server offers a scalable implementation of Java Enterprise Edition (EE) and Jakarta EE.
N/A
Pricing
JBoss SOA Platform
Oracle WebLogic Server
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
JBoss SOA Platform
Oracle WebLogic Server
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
JBoss SOA Platform
Oracle WebLogic Server
Features
JBoss SOA Platform
Oracle WebLogic Server
SOA Governance
Comparison of SOA Governance features of Product A and Product B
JBoss SOA Platform
7.6
Ratings
13% above category average
Oracle WebLogic Server
-
Ratings
Service registry
7.00 Ratings
00 Ratings
Service management
6.00 Ratings
00 Ratings
Service discovery
7.00 Ratings
00 Ratings
Dependency management
9.00 Ratings
00 Ratings
Policy management
9.00 Ratings
00 Ratings
Application Servers
Comparison of Application Servers features of Product A and Product B
JBoss Enterprise SOA Platform is great when you are looking at building more or less pure Java applications and SOA micro-services that may integrate with multiple external data sources. It is less useful when you are looking to build simple SOA applications that are simple in nature since the overhead associated with deploying as well as learning BPEL.
I see Oracle WebLogic Application Server being appropriate when an application needs several different data sources and messaging providers configured and accessible, with a configured level of control of resources (connection pools) and timeouts. It is also advisable to create distributed resources that you can configure as always active to provide more processing power, or as failover for situations of availability in case of disaster recovery, for example. An application where the number of required resources configured is very small and almost non-changeable, and no scalability is required, some other options exist in the market with less cost.
JBoss is open source so the cost overhead to deploy and build application is very low.
JBoss Enterprise SOA Platform and its parent Redhat are reputed and well adapted in the industry so it is easy to find best practices documentation for complex deployments of JBoss middleware.
I love that the weblogic dashboard allows you to manage applications and see the status of each application.
Oracle WebLogic Application Server simplifies usage periods in the development and production of business applications.
Oracle WebLogic Server allows me to define various aspects of data source entry, including creating a specific multiple connection to facilitate data entry.
Performance and administration are highlighted in weblogic.
JBoss Enterprise SOA Platform is dependent and build for JEE/Java application so using a different programming paradigm will be much harder.
There is still a learning curve to get familiar with BPEL making it harder to get an SOA micro-service up and running compared to a fully cloud-based service
The Admin UI should be further simplified, the UI design was not too user-friendly— too many options and clicks required, difficult for the new beginners to figure out what they are looking for.
The admin server becomes the single failure point, although Oracle suggested some workarounds by setting VIP and VHost, it was not quite easy and straight forward.
Domain replication is hard, requiring a lot of knowledge and scripts efforts.
Admin will hang if the node manager communication encounters some issues for one or some nodes in the domain/cluster.
Not able to kill/terminate the stuck thread, the only way is to restart the managed server (JVM)
Oracle WebLogic Server has so many features that sometimes it's hard to find the right place to setup things, I think the dated user interface does not help with that either. This has a direct impact when deciding to use it as your application server, you'd need to have the right people and invest the time needed to master it. If you're application justifies it then it will definitely be a great choice in the long run.
Redhat support generally is great and that is true for the JBoss Enterprise SOA Platform as well. Even if you do not buy support from Redhat, you can reply on the discussion board and bug fixes via the open-source JBoss without much trouble.
Oracle SOA Suite (Oracle BPM + Oracle BPEL + other components) and IBM WebSphere middleware is most costly and suited if you are already using applications and other middleware components from these vendors. Mulesoft (Salesforce Mule ESB) is best when you need deep integration with one of Salesforce's existing products. JBoss and Apache Web Server are best when you do not want to invest infant CapEx/OpEx on license fee. Apache Web Server based middleware is best for simple SOA applications.
I wasn't involved in selecting the server we were using but in our team we've made some efforts to improve the local deployment process by trying some other Applicational servers too. Apache Tomcat was a more lightweight solution for sure, and it coped well with our applications needs, configuration and performance wise. Despite that, since we didn't got clearance to change that into our local servers, we kept using Weblogic to guarantee compliance between the testing environments and production.
