What do I need to know and how can I be prepared to move from IBM Business Automation Workflow (BAW) on-premise to IBM BAW Cloud Pak (Containers)?
If you're running your IBM BAW on-prem at the moment most likely a question of moving to the containerized environment came up in your organization every now and then. In this article, I'd like to focus on what you can do from a DevOps practice perspective to be able to move to a containerized version of BAW successfully.
As a first step, I'd start with a good FAQ that IBM has put together.
And the following articles would be of help as well -
- What artifacts are supported in traditional vs container runtime environment
- Prepare your projects
- Move your DEV projects
After reviewing the above material you should be better prepared now but as we all know the most helpful bit of information is to actually have a practical and not theoretical understanding of what will work and what not when you move your apps\solution code from BAW on-prem to BAW containers.
In the past, I would always recommend our clients to set up POC / DEV type of environment where you can easily do the export/import of your assets and test/verify. But in current circumstances setting up a whole BAW Cloud Pak DEV environment with OpenShift etc would not be an easy task for such a POC.
Luckily, there is a better and easier way to accomplish this task. Thanks to IBM for releasing a service called "Workflow Service".
Workflow Process Service is a new capability with a small footprint and resource usage for authoring and running workflows. It allows you to run a lightweight version of BAW Cloud Pak.
Workflow Process Service offers a fit-for-purpose, single runtime container that lets you split your workflow into separate runtime components.
It only requires PostgreSQL to be installed and pre-configured.
If you need help setting it up feel free to open a ticket with BP3 Labs and we'll be happy to help as we had been using this service in our Labs successfully for some time now.