IBM E02HRLL-G Administration Guide - Page 172

FTPScripting Receiver receives StringIndexOutofBoundsException, Error scenario, Working scenario

Page 172 highlights

FTPScripting Receiver receives StringIndexOutofBoundsException If you receive a StringIndexOutOfBoundsException while connecting to a Pro FTP server, request the partner to remove all blank lines from the Welcome Message for the FTP server. This FTP server send this message whenever a client connects to the FTP server. Error scenario The following example shows blank lines in the Welcome Message. ftp myftp.mycompany.com Connected to myftp.mycompany.com 220 You have connected to myftp.mycompany.com FTP Server. Please enter userid and password to login 220 MYCOMPANY FTP Server ready. User (myftp.mycompany.com:(none)): Working scenario The following example shows the Welcome Message with the blank lines removed. ftp myftp.mycompany.com Connected to ftp myftp.mycompany.com 220-You have connected to myftp.mycompany.com FTP Server. Please enter userid and password to login 220 MYCOMPANY FTP Server ready. User (myftp.mycompany.com:(none)): Receiver Failure to read Configuration File If the Receiver failed to read the configuration file, the following error message is displayed: Unable to update the Receiver Config file java.io.IOException: A file or directory in the path name does not exist. This error occurs when the WebSphere Partner Gateway Receiver is starting and it does not have a connection to the database and it is attempting to read the configuration information from the BCGReceiverConfiguration.xml file. The BCGReceiverConfiguration.xml file is located in a folder specified by the attribute bcg.receiver.configpath on the System Administration Page of the console. Ensure that the path specified by bcg.receiver.configpath is correct. Configuring Users to receiving Alerts Notification If the SMTP configuration has not been provided in the System Administration page of the WebSphere Partner Gateway console, the configured alerts are not sent to the Users because document manager fails to locate the necessary SMTP configuration. To configure the alerts, update the values of the following two attributes: v On the System Administration > DocMgr Administration > Alert Engine page, update the bcg.alertNotifications.mailHost attribute v On the System Administration > DocMgr Administration > Delivery Manager page, update the bcg.delivery.smtpHost attribute 166 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

FTPScripting Receiver receives StringIndexOutofBoundsException
If you receive a StringIndexOutOfBoundsException while connecting to a Pro FTP
server, request the partner to remove all blank lines from the Welcome Message for
the FTP server. This FTP server send this message whenever a client connects to
the FTP server.
Error scenario
The following example shows blank lines in the Welcome Message.
ftp myftp.mycompany.com
Connected to myftp.mycompany.com
220-
<blank line>
You have connected to myftp.mycompany.com FTP Server.
<blank line>
Please enter userid and password to login
<blank line>
220 MYCOMPANY FTP Server ready.
User (myftp.mycompany.com:(none)):
Working scenario
The following example shows the Welcome Message with the blank lines removed.
ftp myftp.mycompany.com
Connected to ftp myftp.mycompany.com
220-You have connected to myftp.mycompany.com FTP Server.
Please enter userid and password to login
220 MYCOMPANY FTP Server ready.
User (myftp.mycompany.com:(none)):
Receiver Failure to read Configuration File
If the Receiver failed to read the configuration file, the following error message is
displayed:
Unable to update the Receiver Config file java.io.IOException: A file
or directory in the path name does not exist.
This error occurs when the WebSphere Partner Gateway Receiver is starting and it
does not have a connection to the database and it is attempting to read the
configuration information from the
BCGReceiverConfiguration.xml
file. The
BCGReceiverConfiguration.xml
file is located in a folder specified by the attribute
bcg.receiver.configpath
on the System Administration Page of the console.
Ensure that the path specified by
bcg.receiver.configpath
is correct.
Configuring Users to receiving Alerts Notification
If the SMTP configuration has not been provided in the System Administration
page of the WebSphere Partner Gateway console, the configured alerts are not sent
to the Users because document manager fails to locate the necessary SMTP
configuration.
To configure the alerts, update the values of the following two attributes:
v
On the
System Administration
>
DocMgr Administration
>
Alert Engine page
,
update the
bcg.alertNotifications.mailHost
attribute
v
On the
System Administration
>
DocMgr Administration
>
Delivery Manager
page, update the
bcg.delivery.smtpHost
attribute
166
IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide