Deployment Considerations
Some forethought and planning must be applied if you working with Content Service Platform environments in a multiple or clustered installation.
In these situations, exercise caution when deploying environments from the Central Configuration interface. If you deploy a Content Service Platform environment to more than one Integration Server/Process Engine host, you create a situation where it is possible to start multiple (duplicate) business processes when a monitored document type is updated or modified. Take care to avoid this situation.
Consider the following conditions:
Where are my process models running? When you upload a content-enabled process model to an
Integration Server/
Process Engine host, the
webMethods Content Service Platform uses the content type listener specified within the process to monitor a folder location for instances of a specified document type. If you upload the same process model to two or more
Integration Server/
Process Engine hosts that have the same
Content Service Platform environment, a new business process instance will start on each host when the document type listener is triggered.
What document types am I monitoring? When you define a content-enabled process model, you specify a content listener that monitors a specific folder location in the repository. Consider this example:
You create Process1 to monitor a folder in your repository for arrival of DocumentTypeA, and upload Process1 to
Integration Server/
Process Engine host Alpha.
You create Process2 to monitor the same repository folder for arrival of DocumentTypeB (that is, you have specified a different listener), and upload Process2 to
Integration Server/
Process Engine host Beta.
Both hosts monitor the same repository folder, but because the
Process Engine on each host is using a different listener to monitor for a different document type, new process instances will run separately on each host, as expected.
However, if you were to upload Process1 (monitoring for DocumentTypeA) to both hosts, a process instance will start on each host when the DocumentTypeA listener is triggered.
