Need suggestions on using BPM MSR with the required packages to have BPM working as standalone microservice.

,
1

Hi All

I need some suggestions. Is it advisable to use BPM to run as a MSR. If yes why and if no why.

If anyone has implemented this can you please share the steps.

Thanks
Abhijith

2

I don’t have any recommendation on whether using BPM as containers or not (the question is ambiguous, it is not clear whether you are asking this info for containers or on-prem standalone MSR) since it mostly depends on your implementation/configuration.

There could be some complications when resubmitting the processes since it was using hostname instead of load balancer DNS name in the past. It is not directly related to containers or MSR though. MSR is pretty much the same product as IS so from the IS point of view, there is no difference. But if they haven’t fixed hostname usage on process resubmit, and if the node you are trying to resubmit to is offline/unavailable at the time of resubmit, it could make you do extra work to work around this. It has been a long time since the last time I worked with BPM, so this issue might have long gone. It was version 9.6 when I had this issue.

3

Hi Engin.

Thanks for the reply. My usecase is at present i have an onprem instance with BPM. Now we want to check if the same can be relicated as MSR.

The MSR doesnt have all packages so we are planning to create a custom image like copy the related configuration and packages like WmPRT,WmTaskEngine,WmTaskAssets,WmMonitor etc and deploy as MSR.

So i wanted to know if this is feasible and how to connect this MSR to MWS if we have tasks and other activities.

4

Hi,

Don’t forget the BPM engine relies heavily on the database, and messaging through the UM.

Also, I’m not too sure of the license you have to apply in this case.

Best regards,

5

You can download those packages on runtime from https://packages.webmethods.io/
No need to create your own container but you can of course. You can just use the instance you already have to create the container. The script to create container comes with the installer. Using the containers published have a very good advantage though. You can update your environment very quickly. Database connections can be established in yaml files or configuration variables. But you need to create the container for MWS yourself since it doesn’t have a prod ready image.