IBM E027SLL-H Troubleshooting Guide - Page 216

Unresolved variables in custom queries

Page 216 highlights

in Header and Footer expressions set through the view Properties window will only be substituted if the workspace is reached as the target of a link. Verify that the custom workspace for which the expression is being specified is being reached through a link rather than being selected directly from a navigator node or the Workspaces menu. Otherwise, the symbols will evaluate as an empty string. For best results, also ensure that the expression is assigned to the Header or Footer target workspace property through the Link Wizard rather than by editing the Title text field for the Header or Footer region on the Style panel of the Properties Dialog. Whatever expression is assigned to the target workspace property through the Link Wizard will override the Title text entered in the Style panel when the workspace is reached through the link. This problem was reported against Tivoli Management Portal v1.9.6 but also applies to the Tivoli Enterprise Portal v6.1.0, v6.2.0, v6.1.1, and v6.2.2. Unresolved variables in custom queries Whenever you assign a custom query containing $-delimited symbol references to a view through the Properties window, a popup appears asking for values for all symbol references for which a value cannot be found. The values provided through this window are used to parameterize the query issued to fill the Preview pane of the Properties window. The values provided will NOT be saved in the workspace state although they will remain defined from when the Properties window is dismissed until the workspace is refreshed. The reason for the prompt for values is to allow the author of the query/workspace to test whether or not the query returns the expected result set for the provided values. The values are optional and need not be provided in order to complete the assignment of the query to the view. The only impact of not providing values is that the query triggers a syntax error when executed by the Properties window Preview pane and the view is empty. In order for the query to work correctly in the workspace, values must be provided for all the referenced symbols through the execution environment. Typically, this is done by reaching the workspace through a link that either explicitly or implicitly assigns values to the symbols. It can also be done through special controls like the Timespan window, but these must be built into the product. Custom query processing differs from 'standard' query processing in that, for custom queries, a value must be provided for every symbol reference while, for 'standard' queries, the system discards segments of the WHERE clause involving symbols for which a non-null value cannot be found. In order to support historical queries against summarized data, various agent groups distribute product-provided custom queries that reference symbols that are meant to be provided by the Timespan window when the 'Use summarized data' option is selected. These queries are used with the product-provided 'Historical Summarized ...' workspaces available from the Workspaces menu of the Operating System summary workspaces like 'Windows Systems'. In order for the queries to return data, the Warehouse Proxy and Summarization and Pruning agents must be configured and have been running long enough to collect and summarize the data being viewed. The queries reference a number of symbols. Following are some of the commonly referenced symbols and example values: KFW_USER: Name of the summarized database schema owner. Default is ITMUSER but it can be any value assigned by the customer during installation. 198 IBM Tivoli Monitoring: Troubleshooting 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
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310

in Header and Footer expressions set through the view Properties window will
only be substituted if the workspace is reached as the target of a link. Verify that
the custom workspace for which the expression is being specified is being reached
through a link rather than being selected directly from a navigator node or the
Workspaces menu. Otherwise, the symbols will evaluate as an empty string.
For best results, also ensure that the expression is assigned to the Header or Footer
target workspace property through the Link Wizard rather than by editing the Title
text field for the Header or Footer region on the Style panel of the Properties
Dialog. Whatever expression is assigned to the target workspace property through
the Link Wizard will override the Title text entered in the Style panel when the
workspace is reached through the link. This problem was reported against Tivoli
Management Portal v1.9.6 but also applies to the Tivoli Enterprise Portal v6.1.0,
v6.2.0, v6.1.1, and v6.2.2.
Unresolved variables in custom queries
Whenever you assign a custom query containing $-delimited symbol references to
a view through the Properties window, a popup appears asking for values for all
symbol references for which a value cannot be found. The values provided through
this window are used to parameterize the query issued to fill the Preview pane of
the Properties window. The values provided will NOT be saved in the workspace
state although they will remain defined from when the Properties window is
dismissed until the workspace is refreshed.
The reason for the prompt for values is to allow the author of the
query/workspace to test whether or not the query returns the expected result set
for the provided values. The values are optional and need not be provided in order
to complete the assignment of the query to the view. The only impact of not
providing values is that the query triggers a syntax error when executed by the
Properties window Preview pane and the view is empty. In order for the query to
work correctly in the workspace, values must be provided for all the referenced
symbols through the execution environment. Typically, this is done by reaching the
workspace through a link that either explicitly or implicitly assigns values to the
symbols. It can also be done through special controls like the Timespan window,
but these must be built into the product.
Custom query processing differs from 'standard' query processing in that, for
custom queries, a value must be provided for every symbol reference while, for
'standard' queries, the system discards segments of the WHERE clause involving
symbols for which a non-null value cannot be found. In order to support historical
queries against summarized data, various agent groups distribute
product-provided custom queries that reference symbols that are meant to be
provided by the Timespan window when the 'Use summarized data' option is
selected. These queries are used with the product-provided 'Historical Summarized
...' workspaces available from the Workspaces menu of the Operating System
summary workspaces like 'Windows Systems'.
In order for the queries to return data, the Warehouse Proxy and Summarization
and Pruning agents must be configured and have been running long enough to
collect and summarize the data being viewed. The queries reference a number of
symbols. Following are some of the commonly referenced symbols and example
values:
KFW_USER: Name of the summarized database schema owner. Default is
ITMUSER but it can be any value assigned by the customer during installation.
198
IBM Tivoli Monitoring: Troubleshooting Guide