Instance Matching
A matching algorithm dynamically determines a set of process instances.
The matching algorithm compares attribute values of a process instance against the match parameter values in the named instance definitions. A process instance matches a named instance definition when every match parameter you configure in the named instance definition is identical to the corresponding attribute value in the process instance. A match parameter without any value acts like a wildcard: that is, it matches any attribute value in every process instance.
The order of the named instance definitions within the application definition determines the order in which the matching algorithm attempts to match them. The first named instance definition that matches the process instance determines the endpoint implementation for the process.
If none of the named instances matches the process instance, then the default instance determines the endpoint implementation for the process. (If you have not defined any named instances, then the default instance always determines implementation for all process instances, without matching.)
To configure match parameters, set the Identifier and Host columns of the applications grid (see Instance Level).
Instance Matching and Persistence
You can also use instance matching with persistence stores, to map from subscriber names to static durables. Define an instance that matches on an identifier, and configure the subscriber mapping on its endpoints. See also Instance Matching for Subscriber Name Mapping.