Preparing To Test; Setting Up Test Scenarios - IBM E02HRLL-G - WebSphere Partner Gateway Express Administration Manual

Preparing to test

About this task
Before you start the test, you must perform the following tasks, which may vary
by the role that you are simulating, either a request or response from the internal
partner, or a request or response from a partner:
1. Review the connections that you have configured to confirm that the test
2. Verify that your receivers are enabled and configured with the appropriate URL
3. Verify the Business IDs in the header of your test document. The Business IDs
The following is an example of the "from" and "to" Business IDs in a test
document (lines that are not relevant have been removed):
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Preamble SYSTEM "3A4_MS_V02_02_PurchaseOrderRequest.dtd">
<Pip3A4PurchaseOrderRequest>

Setting up test scenarios

You can use the RN PS to test the scenarios shown in Table 35 between you and
your partners.
122
IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide
scenario appears to be configured correctly. In particular, make sure that the
destinations that are configured in the connection are active.
for incoming messages. Different traffic occurs on different receivers.
This requirement only applies when you are testing a document that requires a
response. For more information about receivers, see the WebSphere Partner
Gateway Hub Configuration Guide.
drive the routing process and control where the document is sent.
For example, if you are sending your document to yourself, the internal
partner, the "to" Business ID in the document header must be your own
Business ID. The system uses the "to" Business ID to find the correct
connection.
<fromRole>
<GlobalBusinessIdentifier>987654321</GlobalBusinessIdentifier>
<toRole>
<GlobalBusinessIdentifier>567890123</GlobalBusinessIdentifier>
Table 35. Test scenarios
Scenario
One-way outbound from an internal partner to an
external partner.
Simulating internal partner.
One-way inbound from an external partner to an
internal partner.
Simulating external partner.
Two-way outbound from an internal partner to an
external partner (Upload Request).
Simulating internal partner.
Two-way inbound from an external partner to an
internal partner (Upload Request).
Simulating external partner.
Destination for
Connection URL
VTP_Owner VTP_OWNER
VTP_TP Not applicable
in this scenario.
VTP_Owner VTP_OWNER
VTP_TP VTP_TP