IBM E02HRLL-G Administration Guide - Page 129

Sample scenarios, Internal partner, RosettaNet PIP XML files

Page 129 highlights

Table 35. Test scenarios (continued) Scenario Two-way outbound from an internal partner to an external partner (Upload Response). Simulating external partner. Two-way inbound from an external partner to an internal partner (Upload Response). Destination for Connection VTP_TP URL VTP_TP VTP_Owner VTP_Owner Sample scenarios This section describes the steps involved in configuring the RN PS to simulate two one-way RosettaNet (RN) interactions. The steps for setting up RN interactions are described here in the context of setting up the RN PS. For more information about configuring RN in general, see the WebSphere Partner Gateway Hub Configuration Guide. You will see the directories and hub configuration settings that are used by the RN PS, and you will have a better understanding of how the RN PS can be helpful in debugging routing between partners. Internal partner Set up an HTTP sink destination for the internal partner. This is an HTTP destination that sends to URL http://:/console/sink. The sink destination should be specified as the default RN PS partner and RN PS Manager destination for the internal partner. External partner Set up an HTTP sink destination for the partner just as you did for the internal partner. RosettaNet PIP XML files The 3A4 interaction is the scenario described here. The external partner to internal partner simulation uses XML that contains the 3A4 Purchase Order Request content. The internal partner to external partner simulation uses XML that complies with the 3A4 Purchase Order Confirmation RNSC content. These XML files reside on your local file system. See the WebSphere Partner Gateway Hub Configuration Guide for related information. When you create the files, remember that the to and from Ids must match those of the internal partner and the external partner in the appropriate places in these files. Configuring the Console and Router Servers About this task If you plan to use encryption or signing in your simulation, you must have a pair of public-key and private-key certificates. Use p8 format for the private keystore and der format for the public certificate. 1. Copy your PKCS#8 and DER files to the common/security/vtp directory. 2. Copy the DER file to the common/security/ca directory. Chapter 12. Simulating production traffic 123

  • 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

Table 35. Test scenarios (continued)
Scenario
Destination for
Connection
URL
Two-way outbound from an internal partner to an
external partner (Upload Response).
Simulating external partner.
VTP_TP
VTP_TP
Two-way inbound from an external partner to an
internal partner (Upload Response).
VTP_Owner
VTP_Owner
Sample scenarios
This section describes the steps involved in configuring the RN PS to simulate two
one-way RosettaNet (RN) interactions. The steps for setting up RN interactions are
described here in the context of setting up the RN PS. For more information about
configuring RN in general, see the
WebSphere Partner Gateway Hub Configuration
Guide
.
You will see the directories and hub configuration settings that are used by the RN
PS, and you will have a better understanding of how the RN PS can be helpful in
debugging routing between partners.
Internal partner
Set up an HTTP sink destination for the internal partner. This is an HTTP
destination that sends to URL
http://<
console-ip
>:<
console-port
>/console/sink
.
The sink destination should be specified as the default RN PS partner and RN PS
Manager destination for the internal partner.
External partner
Set up an HTTP sink destination for the partner just as you did for the internal
partner.
RosettaNet PIP XML files
The 3A4 interaction is the scenario described here. The external partner to internal
partner simulation uses XML that contains the 3A4 Purchase Order Request
content.
The internal partner to external partner simulation uses XML that complies with
the 3A4 Purchase Order Confirmation RNSC content. These XML files reside on
your local file system.
See the
WebSphere Partner Gateway Hub Configuration Guide
for related information.
When you create the files, remember that the to and from Ids must match those of
the internal partner and the external partner in the appropriate places in these
files.
Configuring the Console and Router Servers
About this task
If you plan to use encryption or signing in your simulation, you must have a pair
of public-key and private-key certificates. Use p8 format for the private keystore
and der format for the public certificate.
1.
Copy your PKCS#8 and DER files to the
common/security/vtp
directory.
2.
Copy the DER file to the
common/security/ca
directory.
Chapter 12. Simulating production traffic
123