JBoss SOA Platform vs. SAP NetWeaver BPM

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.

Incentivized

It is well suited when we need to integrate business processes with SAP ERP and SAP CRM - the solution can be integrated with business rules/procedures defined in SAP ERP/CRM and NetWeaver can be used to monitor the rules and flag off exceptions. When there are multiple workflows running, it tends to slow down running of these processes. Also, it entirely depends on SAP portal for it to run efficiently.

Incentivized

• 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.

Incentivized

• Virtual paper trail. Iterations of process and current documentation are all stored as "artifacts", leaving a great trail.
• Configuration of users. BPM somewhat magically determines which users will be impacted and automates rules.
• A pro (that is also a con) is the design interface. If you know what you are doing, it is incredibly powerful and malleable.

• 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

Incentivized

• Live readings would be nice.
• Easier to maneuver
• Work with all systems with the press of one keystroke

Incentivized

As a big fan of SAP in general, the BPM solution fits right in with all the other things SAP does well, and does it with incredible efficiency

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.

Incentivized

We have our own tech support for systems, I would say they probably could use more training on it, I don't really think it's anything regarding the SAP system, but more the knowledge they have on the system itself. It seems to take longer for them to fix any issues we may come across.

Incentivized

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.

Incentivized

I found the initial setup of NetWeaver is much simpler than other products especially in an SAP environment where we have SAP ERP/HRM/CRM as it can be well integrated with other SAP products. The only drawback is the need/dependency on SAP Portal. It is better suited in an environment where SAP ERP is running.

Incentivized

• Positive impact on the business by being able to use existing Java/JEE expertise to build and deploy applications and business services.
• Positive ROI due to no license cost for JBoss Enterprise SOA.

Incentivized

• Helped us harness integrated benefit from having SAP ERP/CRM by leveraging NetWeaver to define business processes/rules and monitor exceptions
• Did not have any negative experience except for the fact that at times when multiple rules run, it can be somewhat slow

Incentivized