2-2 Infrastructure Components and Utilities Users Guide
2.3 Which Message Exchange Pattern Is Being Used by the Components Being Tested?
This section includes the following topics:
■
Section 2.3.1, Describing CAVS Process Flows for Testing the Synchronous Message Exchange Pattern
■
Section 2.3.2, Describing CAVS Process Flows for Testing the Asynchronous Notify Message Exchange Pattern
■
Section 2.3.3, Describing Flows for Testing the Asynchronous Two-Way Message Exchange Pattern
Once you have assessed which components you need to test, identify the message exchange pattern MEP being used by the components to help you determine which
types of CAVS test and simulator definitions you need to create. Based on the sequence of service calls and the MEPs employed, you can determine if you need to
use synchronous, notify, or asynchronous two-way test definitions andor simulator definitions.
This section discusses CAVS process flows for testing the following MEPs:
■
Synchronous request-and-response
■
Asynchronous notify
■
Asynchronous two-way
2.3.1 Describing CAVS Process Flows for Testing the Synchronous Message Exchange Pattern
The following diagrams describe CAVS process flows for testing a provider ABCS using a synchronous MEP.
These sample flows can be used as the basis for testing other artifacts as well, such as requester ABCSs, EBFs, or provider services.
Synchronous 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 expects a message in response.
Figure 2–1 illustrates testing a synchronous MEP using a CAVS test definition.
Note: The information in this chapter provides CAVS processing
details that can inform your creation of test and simulator definitions in the CAVS user interface UI. As you prepare to define and run tests
for a particular web service, refer to the section in this chapter that corresponds to the message exchange pattern of the service you want
to test.
Preparing to Use the Composite Application Validation System 2-3
Figure 2–1 Testing a Synchronous MEP Using a CAVS Test Definition
Synchronous 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 expects 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 request and response message pair.
The simulator definition performs validations on message input from the provider ABCS and sends the message back to the provider ABCS. The provider ABCS sends
the message back to the test definition, which validates this actual response against its predefined expected response.
Figure 2–2 illustrates testing a synchronous MEP using CAVS test and simulator
definitions.
Figure 2–2 Testing a Synchronous MEP Using a CAVS Test Definition and Simulator
Definition
Synchronous MEP Testing Flow Using a Simulator Definition 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 request and
response message pair.
The simulator definition performs validations on message input from the provider ABCS and sends the message back to the provider ABCS. The provider ABCS sends
the message back to requester participating application.
Figure 2–3 illustrates testing a synchronous MEP using a CAVS simulator definition.
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
