IBM Business Automation Workflow is a solution that helps users automate digital workflows to increase productivity, efficiency and insights — on premises or on cloud.
N/A
Oracle SOA Suite
Score 8.0 out of 10
N/A
The rapid adoption of cloud-based applications by the enterprise, combined with organizations’ desire to integrate applications with mobile technologies, is dramatically increasing application integration complexity. Oracle SOA Suite 12c, the latest version of the company's unified application integration and SOA solution, offers a simplified cloud, mobile, on-premises and Internet of Things (IoT) integration capabilities within a single platform.
Have your process first on paper Its important to first document the process before venturing into BPMS. It will save a lot of pain and heartaches. A BPM tool is no magic bullet, it merely automates your process. Its upto you to put visibility and tracking on top of it. Provide monitoring so that you get a chance to improve your process continously. BPM is not an application If you are trying to build an application with BPM, chances are that your are alraedy failing. BPM must be a strategic initiative for an organization. Yes, you build Dashboards, Reports and other software in BPMS, however you do it at a process level not at an application level. http://bpmstech.blogspot.com/2011/05/bpm-initiative.htmlKnow the difference between process data and business datahttp://bpmstech.blogspot.com/2011/05/lombardi-best-practices.htmlhttp://bpmstech.blogspot.com/2012/02/bpm-system-architecture.html
Oracle service bus is great to quickly proxy any legacy services exposed as soap service. It's well suited for aggregating multiple services on a single endpoint. We can point to multiple endpoints on the business service and use a round-robin approach to access the endpoints. It's not well suited for data transformation and quick preview of mappings and transformations. It's not great on path to cloud transformation.
System does a great job normalizing business process and automating order processing tasks. Before TeamWorks, the process was much more manual and more expensive staff ($65k to $70K) were required to manage the process. Since implementing TeamWorks, we need much lower-skilled workers to manage order processing.
System ensures that we have consistent data across all systems.
Rules engine is really the “company playbook” – it is the heart and soul of how the company works. It handles thousands of orders per day
The Oracle Service Bus makes the management of web services extremely easy. Through its point and click interface, the web service endpoints can be easily modified.
The administration console provides useful dashboards to diagnose any service issues.
The system gets crashed when many instances go into the queue stage. The system even crashes and sometimes restarts automatically when the load on the server increases. We had to develop a separate software for this and maintain the same.
We cannot manipulate the data during run time. It is difficult to develop user-interfaces with complex functionality.
In order to consume external services that follow HTTP protocol, we need to use IDE for that, and consuming services from IDE takes a lot of time to give a response.
Message reporting tied to a database seems counter productive. Better options to eliminate that would not only minimize the maintenance hassle but also gives more ease to manage the product.
Polling feature isn't very efficient where the end point JMS queues may still have JMS connections despite not enabling the corresponding poller proxy services.
Unable to deploy multiple web services in one go from the OSB Web console.
This particular decision will be made by other people. Overall IBM BPM is the best BPM engine that I have worked with. It is implemented at our company and IT and business are already somewhat familiar with it. Therefore if asked I will recommend renewal as long as the price is reasonable.
We have had not many issues with Oracle Service Bus and it's very stable for our requirements. It's highly available and helps us implement Tier1 applications on it.
• The system is easy enough to use but, by definition, is a complex tool. However, they have done a good job generally balancing tool complexity / capability with usability. When comparing to MS Biz Talk, for example, Biz Talk has less functionality but is actually harder to use. • Software is very flexible. For somebody with the right technical background, it’s quite easy to write some Java code to overcome any hurdles or make the product do what is needed
It's an excellent enterprise service bus and has very stable features. We have been using it since 2008. We did hit into some issues. But, recreating the service helped fix many issues. Also, deployment to various environments was easy. Also, the plugin on Eclipse helps to build proxy and business services quick and easy.
Issues can be raised through tickets and it works based on the priority of the issue. The Support Team response is also good and the solution is provided in a short span of time. In a case where the issue is serious, they try to find out the root cause and provide an alternative for it.
We had some issues with MQ connectivity through OSB and our experience was poor with the support team. They do respond. But, it felt like we are ignored and we had bad support. We had to escalate and things used to get dragged for weeks before we get more quality questions on how to pursue investigation.
• Attended on premise sysadmin training for 4 days, 8 hours per day. Although further follow-up training was available, I never felt the need to go back. Training was very hands-on with real modeling (rather than just following a manual). Very effective.
• Very satisfied – not too difficult at all. • We had a consultant available as part of our contract, but we didn’t really need to use (except for some advice on ActiveDirectory and single sign-on)
Pega Pega is a comprehensive suite which offers a unique theme of BPM development in the market. A no-coding approach based on rules with inheritance makes Pega a very powerful product. However Pega, falls short on integration centric capabilities and very rigid to customize. On the other hand IBM comes with array of products which suits needs of varying degree. Advanced integration is solved by BPEL Process Server which has support for state based patterns and mediation. Dynamic rules and event management can be solved with WODM, Cloud to on-premise connectivity with Cast Iron, Enterprise gateway and security usecases with DataPower, Social BPM with IBM BPM , WODM, mobify with Worklight. Pega has a little bit of eveything here and there. It solves the dynamic rule management, brings out the flavor of Social BPM and mobility with Antenna ( I guess) and predictive analytics as well in one single suite. There are certain usecases which needs to have a little bit of everything, however this little bits and pieces of functionality when its blows, Pega would have problems to scale. With IBM its a bit nightmare to maintain a variety of technologies, however you can wish to go for one without the other and go for something only when you truly need it. Pega vs IBM Its difficult to pick a winner. In nutshell when you want a full scale BPM with rich integration capabilities go for IBM BPM. On the other hand if you hava mature integration capability already, Pega can yield quick results for you as well. Pega's strength is its methodology. IBM BPM's strength is integration. Actually you can't go wrong with both in terms of implementation. My strong recommendation is to invest time to process analysis and pick a good vendor to support consulting and implementation.
It scales from small team interactions to business processes serving thousands of employees, as well as straight-through-processing needs that go well beyond. Of course, scale is always in the eye of the beholder, but IBM BPM does a good job of giving you all of the hooks, APIs, and data that you need to take on whatever scaling approaches you need to meet the load
