2-4 Infrastructure Components and Utilities Users Guide
Figure 2–3 Testing a Synchronous MEP Using a CAVS Simulator Definition
2.3.2 Describing CAVS Process Flows for Testing the Asynchronous Notify Message Exchange Pattern
The following diagrams describe CAVS process flows for testing a provider ABCS using an asynchronous notify MEP.
These sample flows can be used as the basis for testing other artifacts as well, such as the requester ABCS, EBF, or the provider service itself.
Asynchronous Notify MEP Testing Flow Using a Test Definition The requester participating application is replaced by the CAVS test definition. The
test definition points to the URL of the requester ABCS. It uses a composed request message to invoke the ABCS and does not expect a message in response.
Figure 2–4 illustrates testing an asynchronous notify MEP using a CAVS test
definition.
Figure 2–4 Testing an Asynchronous Notify MEP Using a CAVS Test Definition
Asynchronous Notify MEP Testing Flow Using a Test Definition and Simulator Definition
The requester participating application is replaced by the CAVS test definition. The test definition points to the URL of the requester ABCS. It uses a composed request
message to invoke the ABCS and does not expect a message in response.
The provider participating application is replaced by the CAVS simulator definition. The provider ABCS is programmed to route to this simulator instead of the provider
participating application. The simulator definition contains a predefined expected request message.
The simulator definition performs validations on message input from the provider ABCS.
Preparing to Use the Composite Application Validation System 2-5
Figure 2–5 illustrates testing an asynchronous notify MEP using CAVS test and
simulator definitions.
Figure 2–5 Testing an Asynchronous Notify MEP Using a CAVS Test Definition and
Simulator Definition
Asynchronous Notify MEP Testing Flow Using a Simulator Definition The provider participating application is replaced by the CAVS simulator definition.
The requester ABCS is programmed to route to this simulator instead of the provider participating application. The simulator definition contains a predefined expected
request message.
The simulator definition performs validations on message input from the provider ABCS.
Figure 2–6 illustrates testing an asynchronous notify MEP using a CAVS simulator
definition.
Figure 2–6 Testing an Asynchronous Notify MEP Using a CAVS Simulator Definition
2.3.3 Describing Flows for Testing the Asynchronous Two-Way Message Exchange Pattern
