Several failed attempts to split the BPMN application into multiple applications with separate camunda process engines have left a mess of confusing classes and process engine definitions.

In the Amsterdam release, there should be only one BPMN application war.  This is MSOInfrastructureBPMN.  MSOCommonBPMN should not be deployed as a separate application.  Its classes are compiled into a jar and this is included inside MSOInfrastructureBPMN.

The MSOInfrastructureBPMN application should use the "default" process engine.

WorkflowAsyncInfrastructureResource and MSOCommonApplication classes are not needed.