IBM E02HRLL-G Administration Guide - Page 128

Preparing to test, Setting up test scenarios

Page 128 highlights

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 scenario appears to be configured correctly. In particular, make sure that the destinations that are configured in the connection are active. 2. Verify that your receivers are enabled and configured with the appropriate URL 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. 3. Verify the Business IDs in the header of your test document. The Business IDs 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. The following is an example of the "from" and "to" Business IDs in a test document (lines that are not relevant have been removed): 987654321 567890123 Setting up test scenarios You can use the RN PS to test the scenarios shown in Table 35 between you and your partners. Table 35. Test scenarios Scenario Destination for Connection URL One-way outbound from an internal partner to an external partner. VTP_Owner VTP_OWNER Simulating internal partner. One-way inbound from an external partner to an internal partner. VTP_TP Not applicable in this scenario. Simulating external partner. Two-way outbound from an internal partner to an external partner (Upload Request). VTP_Owner VTP_OWNER Simulating internal partner. Two-way inbound from an external partner to an internal partner (Upload Request). VTP_TP VTP_TP Simulating external partner. 122 IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268

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
scenario appears to be configured correctly. In particular, make sure that the
destinations that are configured in the connection are active.
2.
Verify that your receivers are enabled and configured with the appropriate URL
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
.
3.
Verify the Business IDs in the header of your test document. The Business IDs
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.
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>
<fromRole>
<GlobalBusinessIdentifier>987654321</GlobalBusinessIdentifier>
<toRole>
<GlobalBusinessIdentifier>567890123</GlobalBusinessIdentifier>
Setting up test scenarios
You can use the RN PS to test the scenarios shown in Table35 between you and
your partners.
Table 35. Test scenarios
Scenario
Destination for
Connection
URL
One-way outbound from an internal partner to an
external partner.
Simulating internal partner.
VTP_Owner
VTP_OWNER
One-way inbound from an external partner to an
internal partner.
Simulating external partner.
VTP_TP
Not applicable
in this scenario.
Two-way outbound from an internal partner to an
external partner (Upload Request).
Simulating internal partner.
VTP_Owner
VTP_OWNER
Two-way inbound from an external partner to an
internal partner (Upload Request).
Simulating external partner.
VTP_TP
VTP_TP
122
IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide