How to Test Using CAVS How to Test Using Dummy Trading Partner Endpoints

Developing and Implementing Outbound B2B Integration Flows 17-33 The next step, as shown in Figure 17–37 , is to test your newly developed or deployed AIA services that make up the B2B integration flow. Figure 17–37 Step 7: Testing and Verifying Before you go live with your B2B integration flows with your trading partners, we recommend that you complete the following sequence of tests.

17.8.1 How to Test Using CAVS

If your AIA services are Composite Application Validation System CAVS-enabled, you can test your AIA services using a test simulator. Using a CAVS simulator, you can simulate the behavior of your trading partners by sending messages to and receiving messages from a test harness, instead of your actual trading partners. This testing can take place without any knowledge of your trading partners. The objective of this testing, as shown in Figure 17–38 , is to verify that the AIA services are properly developed, deployed, and configured. Figure 17–38 B2B Integration Flow Test Using CAVS

17.8.2 How to Test Using Dummy Trading Partner Endpoints

This section includes the following topics: 17-34 Developers Guide for Oracle Application Integration Architecture Foundation Pack ■ Section 17.8.2.1, How to Test Using the Production Code Value Set to Test ■ Section 17.8.2.2, How to Test Using Dummy Business Data Another common approach to testing is to create dummy delivery channels in your trading partner setup, as shown in Figure 17–39 . For example, instead of configuring your trading partner agreement to send outbound documents to the remote trading partners server, you can configure the agreement to create the outbound B2B files in a temporary B2B file location on the server. Figure 17–39 B2B Integration Flow Test Using Dummy Trading Partner Endpoints In this case, if you test an outbound B2B flow, all of the components involved in the flow are invoked, but the generated B2B document is copied to a temporary file directory. You can review the B2B document for completeness and correctness and also share it for review with your trading partners. ■ The objective of this testing is to verify the integration between AIA services, the application, and B2B and to verify that the configuration across these layers is consistent. ■ This testing can also take place without any knowledge of your trading partners.

17.8.2.1 How to Test Using the Production Code Value Set to Test

Certain B2B document protocols support a protocol envelope-level flag that can be used to specify whether the B2B document is being sent in test or production mode. The trading partner agreements in Oracle B2B can be configured to set this indicator to Test mode. Now when you trigger an outbound B2B flow, the document is sent across to your trading partners, but the trading partner system recognizes the inbound document as a test instance and does not pass it on to the backend application, as shown in Figure 17–40 . Developing and Implementing Outbound B2B Integration Flows 17-35 Figure 17–40 B2B Integration Flow Test Using the Product code Value Set to Test The objective of this testing is to verify the handshake between your B2B server and the trading partners B2B server. Setup of transport and messaging features such as acknowledgement, encryption, packaging, partner and document identification, and so forth are verified. This approach requires that this test mechanism be discussed and agreed upon with each of your trading partners.

17.8.2.2 How to Test Using Dummy Business Data

Finally, you can test integration from your production systems to your remote trading partners production systems by using dummy business data in the B2B documents being exchanged. For example, if you need to test end-to-end outbound Purchase Order integration from your buyer system to your trading partners vendor system, which are integrated by an outbound EDI X12 850 B2B flow, you can place orders either using an EDI test item created for the trading partner or using a price of one cent for the items being ordered. The order request is received and processed successfully by the trading partners business application, as shown in Figure 17–41 , however, the trading partners business users or rules discard the order request. Figure 17–41 B2B Integration Flow Test Using Dummy Business Data This approach also requires that the test mechanism be discussed and agreed upon with each of your trading partners.

17.9 Step 8: Going Live and Monitoring