IBM E02HRLL-G Administration Guide - Page 182

Loading the native library, Fixing error TCPC0003E and CHFW0029E, Environment, Shared Libraries

Page 182 highlights

Loading the native library When WebSphere Partner Gateway components are started, the logs might show the following message: java.lang.UnsatisfiedLinkError: Can't find library AIXNative (libAIXNative.a or .so) in sun.boot.library.path or java.library.path Depending on which operating system WebSphere Partner Gateway is running, the system uses one of the following libraries: v libWin32Native.dll v libpLinuxNative.so v libAixNative.a v libSolarisNative.so v libHPNative.so This error is returned if the library path is not set correctly, to resolve this error: 1. Log on to the WebSphere Application Server Admin console. 2. Select Environment > Shared Libraries. 3. Edit the following properties: v BCG_NAV_CONSOLE v BCG_NAV_RCVR v BCG_NAV_ROUTER_BPE v BCG_NAV_ROUTER_DOCMGR 4. Note the path shown under ″native library path″. 5. Check the specified library path to verify that the appropriate .dll or .so or .a file is present. 6. If the library is not present, copy it from another location. 7. Verify that the shared libraries are associated with each WebSphere Partner Gateway application. To verify: a. On the WebSphere Application Server Admin console Applications page, click any of the WebSphere Partner Gateway applications containing bcgDocMgr. b. Click Shared Library references. c. Verify that the BCG_NAV_ROUTER_DOCMGR library is associated with the application. If is not associated with the library, assign the application. d. Repeat this check for other applications: v For console shared library, the associated library is BCG_NAV_CONSOLE. v For WebSphere Partner Gateway receiver, the associated shared library is BCG_NAV_RCVR v For WebSphere Partner Gateway BPE application, the associated shared library is BCG_NAV_ROUTER_BPE. Fixing error TCPC0003E and CHFW0029E The WebSphere Partner Gateway Receiver component can fail to start with TCPC0003E and CHFW0029E errors in the SystemOut.log file. The errors can occur because of the following conditions: 1. The configured ports can be used by other applications, check for any port conflicts. 176 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

Loading the native library
When WebSphere Partner Gateway components are started, the logs might show
the following message:
java.lang.UnsatisfiedLinkError: Can't find library AIXNative
(libAIXNative.a or .so) in sun.boot.library.path or java.library.path
Depending on which operating system WebSphere Partner Gateway is running, the
system uses one of the following libraries:
v
libWin32Native.dll
v
libpLinuxNative.so
v
libAixNative.a
v
libSolarisNative.so
v
libHPNative.so
This error is returned if the library path is not set correctly, to resolve this error:
1.
Log on to the WebSphere Application Server Admin console.
2.
Select
Environment
>
Shared Libraries
.
3.
Edit the following properties:
v
BCG_NAV_CONSOLE
v
BCG_NAV_RCVR
v
BCG_NAV_ROUTER_BPE
v
BCG_NAV_ROUTER_DOCMGR
4.
Note the path shown under
native library path
.
5.
Check the specified library path to verify that the appropriate .dll or .so or .a
file is present.
6.
If the library is not present, copy it from another location.
7.
Verify that the shared libraries are associated with each WebSphere Partner
Gateway application. To verify:
a.
On the WebSphere Application Server Admin console Applications page,
click any of the WebSphere Partner Gateway applications containing
bcgDocMgr.
b.
Click
Shared Library references
.
c.
Verify that the BCG_NAV_ROUTER_DOCMGR library is associated with the
application. If is not associated with the library, assign the application.
d.
Repeat this check for other applications:
v
For console shared library, the associated library is
BCG_NAV_CONSOLE.
v
For WebSphere Partner Gateway receiver, the associated shared library is
BCG_NAV_RCVR
v
For WebSphere Partner Gateway BPE application, the associated shared
library is BCG_NAV_ROUTER_BPE.
Fixing error TCPC0003E and CHFW0029E
The WebSphere Partner Gateway Receiver component can fail to start with
TCPC0003E and CHFW0029E errors in the
SystemOut.log
file. The errors can occur
because of the following conditions:
1.
The configured ports can be used by other applications, check for any port
conflicts.
176
IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide