Unlike a lot of other BPM engines, you don’t actually have to buy big hardware to size your Camunda environment. It really only hinges on two factors. The container\application server you want to useThe amount of Java working your application has to do. Normally, this is your Delegation code.

Testing BPM applications requires you sort of changing your mindset. Unlike most conventional applications, which I tend to think of as two-dimensional, BPM applications are n-dimensional. With your traditional applications, You usually have your UI and your integrations. Workflow applications, on the other hand, are a lot more powerful, but harder to test. You’ve got business rules, dynamic roles, Security, multiple integrations, the workflow itself, Timers, Events, retries. It can be overwhelming.

Apigee is an API Management platform, so it’s more than a gateway. It does support authentication, and Nother/South traffic, but it’s an entire offering, which includes a gateway. DataPower, on the other hand, is really just a gateway. When used in conjunction with IBM Connect, DataPower supports the larger API Platform by acting as the front door.

The intended audience for this podcast and I may extend this into a series, are basically my geeky brethren. Java Developers who want to start using Camunda. So, in order to follow along, you should probably be at least two years into your career as a java developer, and be comfortable with Java, Spring, Maven, etc. I’m not going to be teaching those, because better teachers than me have already created excellent free content on that. 

RPA is projected to control an almost 3 Billion dollar market by the end of fiscal 2021, so I think it’s fair to say that it’s found its place in our ecosystem. And why not? With the volatile nature of the work world these days, Bots offer consistency and predictability that's in high demand. Today, I want to talk about how RPA and Process Engines like Camunda can work together.

In this Podcast episode, Stuart and Max explore the 5 things that you need to know when considering Camunda BPM as part of an enterprise business process project based on the open-source Camunda Platform, an Enterprise Platform for Workflow and Decision Automation.

Even if you have been modeling processes and workflows for a long time, you’re creating processes from a human perspective. It would help if you made sure that your customers understand what’s happening and that your models represent the logical flow of how the system operates. Unfortunately, BPM engines do not always comprehend this. These engines interpret your models without guiding heuristics which can lead to performance issues. Moreover, as a modeling expert, you have more experience parsing a model. You’re more fluent in the BPM language than the average business user, and a model that makes sense to you may leave them behind.

The first thing you need to understand is that there are several different ways to trigger execution logic in Camunda. You can make a Java API call, subscribe to external events, make restful calls, or asynchronously execute work. In  Camunda, a Job is executed whenever a Timer Event is encountered or when a task, or activity, is explicitly marked as Asynchronous After or Asynchronous Before. Those are checkboxes in the lower bottom part of the general sub-tab when you view your task's properties in the Camunda BPM modeler.

Cloud Data Migration, the body must move broad data into a cloud distribution center. These assignments incorporate source management and planning (mapping), making a data pipeline for each table, and pursue changes over all data sources between others. However, there are various approaches to dispose of failures by utilizing automation. For example: Selecting ETL over ELT: In Extract, Transform, Load, data is extracted from data sources like OLTP database A and B and then deposited into the dimension authority (Staging Area). After that, the data is clean and transformed into a logical data warehouse. In comparison, ETL needs data to pass through a secondary server.

In this Podcast episode, Stuart and Max explore the 5 things that you need to know about Camunda Process History when using the open-source Camunda Platform, an Enterprise Platform for Workflow and Decision Automation.

As an engineer, It's important to get to know your machine. With Camunda, the heart is the job executor. It needs to be repeatedly measured, tested, observed, and refined. It may be beneficial to find an experienced partner and treat them as a resource. The construction and maintenance of this are not as much of a science as it is an art.

APIs, or Application Programming Interfaces, is a mechanism for making remote calls to external services. Every time you make a SOAP or REST call, you’re executing an API. But if you do that often enough, you’re going to need to solve systematic problems, including security, logging, caching, etc. Apigee is a platform managing that.

Every Camunda Application should have it’s own environment, preferably as a Clustered Spring Boot Application. These can be a cluster of one, or bigger cluster. Do not build a single monothetic environment. This is not going to solve your legacy BPM problem. At best, it’s going to move your legacy BPM problem into the cloud, but leave it essentially unchanged. That is the opposite of what you need.

You’re ready to deploy your Camunda application to production, but it’s your first time, and you’re wondering how to archive historical data. So that’s what we’re going to talk about today: the care of feeding Camunda’s archival data. 

What customers need to know once they decide to migrate legacy BPM workflow.

What you should be expecting from your ODM provider and some other alternatives if you're paying too much.

Google stands up a new cutting edge cloud service allowing users to build business process tasks in the cloud. We explore some of the details and the limitations that we feel you should know.