IBM E02HRLL-G Administration Guide - Page 46

IBM E02HRLL-G - WebSphere Partner Gateway Express Manual

Page 46 highlights

the flexibility to decide which documents are to be persisted in the message store. You can choose not to store an inbound, outbound or both inbound and outbound WebSphere Partner Gateway documents in message store. For example, to configure the message store option for an AS2 connection between a trading partner and a internal partner, perform the following steps: 1. Create a partner connection between AS > None. 2. List the partner connection between trading partner and internal partner. 3. Edit the attributes for the AS2 package and set the Message Store Required attribute to Yes. 4. Edit the attributes for the none package and set the Message Store Required attribute to No. See the WebSphere Partner Gateway Hub Configuration Guide for more information about setting the message store attributes at the package, protocol, and document type. Prerequisite to setup WebSphere Partner Gateway - WebSphere Transformation Extender Integration Environment Before you begin Here are the prerequisites required to setup the integration environment of WebSphere Partner Gateway and WebSphere Transformation Extender: 1. WebSphere Partner Gateway V6.2 is installed and running. 2. WebSphere Transformation Extender V8.2 is installed and running. 3. WebSphere Transformation Extender server must have access to the WebSphere Partner Gateway common file system. 4. Copy the dtxpi.jar from the WebSphere Transformation Extender installation directory into the directory \router\lib\ userexits. This jar file contains the WebSphere Transformation Extender runtime classes that are required to invoke WebSphere Transformation Extender for performing the transformation. 5. Restart WebSphere Partner Gateway bcgdocmgr server to pick up the new jar files. 6. Add WebSphere Transformation Extender installation directory in the system path even if you are not using the WebSphere Transformation Extender RMI Server, instead running the environment locally. Restart WebSphere Partner Gateway to pick up the new path settings. 7. If using the WebSphere Transformation Extender RMI Server, then start the Server. 8. Open a command prompt and access WebSphere Transformation Extender install directory. Enter the command startRMIServer.bat -verbose. The verbose option will display the port number of the RMI Server that it is listening. 9. In WebSphere Partner Gateway console, provide values for the attributes: v wtx.rmihostname v wtx.rmiport v rmiuseserver v bcg.wtx.mapLocation, which is under system administration tab 40 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

the flexibility to decide which documents are to be persisted in the message store.
You can choose not to store an inbound, outbound or both inbound and outbound
WebSphere Partner Gateway documents in message store.
For example, to configure the message store option for an AS2 connection between
a trading partner and a internal partner, perform the following steps:
1.
Create a partner connection between
AS
>
None
.
2.
List the partner connection between trading partner and internal partner.
3.
Edit the attributes for the AS2 package and set the
Message Store Required
attribute to
Yes
.
4.
Edit the attributes for the none package and set the
Message Store Required
attribute to
No
.
See the
WebSphere Partner Gateway Hub Configuration Guide
for more information
about setting the message store attributes at the package, protocol, and document
type.
Prerequisite to setup WebSphere Partner Gateway - WebSphere
Transformation Extender Integration Environment
Before you begin
Here are the prerequisites required to setup the integration environment of
WebSphere Partner Gateway and WebSphere Transformation Extender:
1.
WebSphere Partner Gateway V6.2 is installed and running.
2.
WebSphere Transformation Extender V8.2 is installed and running.
3.
WebSphere Transformation Extender server must have access to the WebSphere
Partner Gateway common file system.
4.
Copy the
dtxpi.jar
from the WebSphere Transformation Extender installation
directory into the directory
<WebSphere Partner Gateway Install>\router\lib\
userexits
. This jar file contains the WebSphere Transformation Extender
runtime classes that are required to invoke WebSphere Transformation Extender
for performing the transformation.
5.
Restart WebSphere Partner Gateway bcgdocmgr server to pick up the new jar
files.
6.
Add WebSphere Transformation Extender installation directory in the system
path even if you are not using the WebSphere Transformation Extender RMI
Server, instead running the environment locally. Restart WebSphere Partner
Gateway to pick up the new path settings.
7.
If using the WebSphere Transformation Extender RMI Server, then start the
Server.
8.
Open a command prompt and access WebSphere Transformation Extender
install directory. Enter the command
startRMIServer.bat -verbose
. The
verbose option will display the port number of the RMI Server that it is
listening.
9.
In WebSphere Partner Gateway console, provide values for the attributes:
v
wtx.rmihostname
v
wtx.rmiport
v
rmiuseserver
v
bcg.wtx.mapLocation, which is under system administration tab
40
IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide