IBM E02HRLL-G Administration Guide - Page 130

Configuring 3A4 Connectivity

Page 130 highlights

3. If it is a self-signed certificate, with the console started, the CA certificate should be uploaded as Root and Intermediate certificate. If it is a CA signed certificate, the CA certificate should be uploaded as Root and Intermediate certificate. If the certificate path is to be built till root, then all the CA certificates in the certificate chain should be uploaded. 4. Modify the console configuration to point to the certificate and keystore files. a. Use the console to view the RN PS properties by navigating to System Administration > Console Administration > RN Simulator. b. Click on the Modify icon to place the screen into edit mode. Enter the following with values that are appropriate for your system. You must use der and p8 file formats as shown. bcg.console.certs.vtp.CertificateDir=C://common/security/vtp bcg.certs.vtp.Certificate=testcert.der bcg.certs.vtp.PrivateKey=testkey.p8 bcg.certs.vtp.Passwd=password bcg.certs.vtp.VerifySig=false bcg.vtp.RouterIn=C://common/router_in c. Click the Save button to save the changes that you have made. 5. If the console server is running, restart it. If it is not running, start it now. 6. Check to be sure that the Document Manager configuration is set up correctly. a. Use the console to view the Document Manager security properties by navigating to System Administration > DocMgr Administration > Security. b. Click the Modify icon to place the screen into edit mode. c. Change the value of the bcg.certs.vtp.CertificateDir property to point to the same directory that the console pointed to step 4b. Save the property setting. Note: These directories are named in the context of the server where the components are installed. The document manager and console should map a file system to the same directory. 7. If the Document Manager server is running, restart it. If it is not running, start it now. Configuring 3A4 Connectivity About this task If you are familiar with RosettaNet routing, configure RosettaNet connectivity between an external partner and an internal partner using the following steps. If you are not familiar with RosettaNet routing, see the WebSphere Partner Gateway Hub Configuration Guide for assistance when performing the following tasks: 1. Import the RN and RNSC files that support the 3A4 interactions. Upload the following files in the order shown. The files are located in the /B2Bintegrate/rosettanet directory of the installation CD: v Package_RNIF_V02.00.zip v BCG_Package_RNIFV02.00_3A4V02.02.zip v Package_RNSC_1.0_RNIF_V02.00.zip v BCG_Package_RNSC1.0_RNIFV02.00_3A4V02.02.zip 2. Define the interactions for 3A4 purchase order requests and confirmations to be routed through the hub. 124 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

3.
If it is a self-signed certificate, with the console started, the CA certificate
should be uploaded as Root and Intermediate certificate. If it is a CA signed
certificate, the CA certificate should be uploaded as Root and Intermediate
certificate. If the certificate path is to be built till root, then all the CA
certificates in the certificate chain should be uploaded.
4.
Modify the console configuration to point to the certificate and keystore files.
a.
Use the console to view the RN PS properties by navigating to
System
Administration
>
Console Administration
>
RN Simulator
.
b.
Click on the
Modify
icon to place the screen into edit mode. Enter the
following with values that are appropriate for your system. You must use
der and p8 file formats as shown.
bcg.console.certs.vtp.CertificateDir=C:/<
INSTALL DIR
>/common/security/vtp
bcg.certs.vtp.Certificate=testcert.der
bcg.certs.vtp.PrivateKey=testkey.p8
bcg.certs.vtp.Passwd=password
bcg.certs.vtp.VerifySig=false
bcg.vtp.RouterIn=C:/<
INSTALL DIR
>/common/router_in
c.
Click the
Save
button to save the changes that you have made.
5.
If the console server is running, restart it. If it is not running, start it now.
6.
Check to be sure that the Document Manager configuration is set up correctly.
a.
Use the console to view the Document Manager security properties by
navigating to
System Administration
>
DocMgr Administration
>
Security
.
b.
Click the
Modify
icon to place the screen into edit mode.
c.
Change the value of the
bcg.certs.vtp.CertificateDir
property to point to
the same directory that the console pointed to step 4b. Save the property
setting.
Note:
These directories are named in the context of the server where the
components are installed. The document manager and console should map
a file system to the same directory.
7.
If the Document Manager server is running, restart it. If it is not running, start
it now.
Configuring 3A4 Connectivity
About this task
If you are familiar with RosettaNet routing, configure RosettaNet connectivity
between an external partner and an internal partner using the following steps.
If you are not familiar with RosettaNet routing, see the
WebSphere Partner Gateway
Hub Configuration Guide
for assistance when performing the following tasks:
1.
Import the RN and RNSC files that support the 3A4 interactions.
Upload the following files in the order shown. The files are located in the
/B2Bintegrate/rosettanet
directory of the installation CD:
v
Package_RNIF_V02.00.zip
v
BCG_Package_RNIFV02.00_3A4V02.02.zip
v
Package_RNSC_1.0_RNIF_V02.00.zip
v
BCG_Package_RNSC1.0_RNIFV02.00_3A4V02.02.zip
2.
Define the interactions for 3A4 purchase order requests and confirmations to be
routed through the hub.
124
IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide