IBM E02HRLL-G Administration Guide - Page 229

Appendix C - component-specific system attributes

Page 229 highlights

Appendix C - component-specific system attributes Configuring attributes as WebSphere Application Server ND environment variables On the System Administration page of the WebSphere Partner Gateway Console, there are configuration attributes for specific subcomponents of the WebSphere Partner Gateway runtime. These attributes apply to all instances of their subcomponents. For more information about the attributes, see the tables in "Attribute tables" on page 228. There might be situations in which you want to change the values of an attribute for a specific instance. For example, you might want to increase the number of threads if the computer that the component instance is running on has a greater CPU capacity. To change the value of an attribute for a specific component instance from what is configured in the WebSphere Partner Gateway Console, use the Deployment Manager on the System Administration page to create an environment variable for the node and server where the component is running. The value of the environment variable will take precedence over the value configured in the WebSphere Partner Gateway Console. For detailed information about WebSphere environment variables see the WebSphere Application Server documentation. To create a WebSphere Application Server ND environment variable perform the following steps: 1. Open your WebSphere Application Server Admin Console. 2. Navigate to Environment> WebSphere Variables. 3. From the menu, select the node and server for which you are adding the variable. 4. Click New. 5. Type the name of property as it displays on the WebSphere Partner Gateway System administration page and set its value. 6. Click OK. 7. Save the master configurations. Editing RosettaNet attribute values If XPath queries are not provided for a PIP, the default XPath queries listed in Table 45 are used to extract the corresponding values: Table 45. Default XPath Queries Default XPath queries Extracted value thisDocumentIdentifier[0]/ProprietaryDocumentIdentifier[0] Document ID thisMessageIdentifier[0]/ProprietaryMessageIdentifier[0] thisDocumentGenerationDateTime[0]/DateTimeStamp[0] Document creation date and time stamp theMessageDatetime[0]/DateTimeStamp[0] thisMessageDateTime[0]/DateTimeStamp[0] GlobalDocumentFunctionCode[0] GlobalFunctionCode © Copyright IBM Corp. 2007, 2008 223

  • 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

Appendix C - component-specific system attributes
Configuring attributes as WebSphere Application Server ND
environment variables
On the System Administration page of the WebSphere Partner Gateway Console,
there are configuration attributes for specific subcomponents of the WebSphere
Partner Gateway runtime. These attributes apply to all instances of their
subcomponents. For more information about the attributes, see the tables in
“Attribute tables” on page 228. There might be situations in which you want to
change the values of an attribute for a specific instance. For example, you might
want to increase the number of threads if the computer that the component
instance is running on has a greater CPU capacity. To change the value of an
attribute for a specific component instance from what is configured in the
WebSphere Partner Gateway Console, use the Deployment Manager on the System
Administration page to create an environment variable for the node and server
where the component is running. The value of the environment variable will take
precedence over the value configured in the WebSphere Partner Gateway Console.
For detailed information about WebSphere environment variables see the
WebSphere Application Server documentation.
To create a WebSphere Application Server ND environment variable perform the
following steps:
1.
Open your WebSphere Application Server Admin Console.
2.
Navigate to
Environment
>
WebSphere Variables
.
3.
From the menu, select the node and server for which you are adding the
variable.
4.
Click
New
.
5.
Type the name of property as it displays on the WebSphere Partner Gateway
System administration page and set its value.
6.
Click
OK
.
7.
Save the master configurations.
Editing RosettaNet attribute values
If XPath queries are not provided for a PIP, the default XPath queries listed in
Table 45 are used to extract the corresponding values:
Table 45. Default XPath Queries
Default XPath queries
Extracted value
thisDocumentIdentifier[0]/ProprietaryDocumentIdentifier[0]
thisMessageIdentifier[0]/ProprietaryMessageIdentifier[0]
Document ID
thisDocumentGenerationDateTime[0]/DateTimeStamp[0]
theMessageDatetime[0]/DateTimeStamp[0]
thisMessageDateTime[0]/DateTimeStamp[0]
Document creation date and time stamp
GlobalDocumentFunctionCode[0]
GlobalFunctionCode
© Copyright IBM Corp. 2007, 2008
223