I’m newbie on this. I’m trying to figure out what is the usage of the “Logical Server” that is configurable at the WmDesigner package.
I noticed that the Flow Services defined in a Designer BPM flow gets named (a afterwards created) with this Logical Server name in the service full qualified name. But besides this, is any other purpose for this “Logical Server”?
The steps in a model can each be assigned to a different logical server. A logical server has a configuration that associates it with a physical server. Each different logical server can be associated a different physical server.
This can be used to provide separation of “step ownership” where one group is responsible for the IS services behind steps 1, 2 and 3 while another group and another server handles steps 4, 5 and 6. It is also a way to provide a degree of scalability.
I’ve never seen anyone use logical servers in this way. I’ve only ever seen all steps in a model using one logical, and therefore one physical, server.
As Rob already pointed out The concept looks very nice, as you can target different steos to different IS. However there are (at least) two shortcomings:
- The generated steps are not automatically distributed to the appropriate physical servers. You need to create specific builds in Deployer, which makes the usage quite tedious.
- It is not clear if the concept will be continued by SAG.