IBM BJ0NJML Integration Guide - Page 29

Operational Management Products, Integration Framework for User Interface Integration, Launch Entries

Page 29 highlights

Integration Framework for User Interface Integration When invoked by a process management product, the integration module uses data that is passed by the process management product to assist in the invocation of the operational management product service. The integration module may also return the operational management product response data to the process management product. When installed, integration modules include the logical management operations that they support for an operational management product. Depending upon the level of complexity, you can implement an integration module as a Java class or an invocation channel. Operational Management Products Operational management products are external products that you can use to perform information technology services. IBM® Tivoli® Application Dependency Discovery Manager (TADDM), Tivoli Provisioning Manager (TPM), and IBM® Tivoli® Configuration Manager (TCM) are examples of operational management products. Operational management products provide services that external applications (integration modules) can invoke to initiate operational management product actions. Operational management product definitions are registered in the system and can be loaded from the discovery engine using the Integration Composer. You can also load operational management product definitions by using the features of the integration framework, such as object structure services. The operational management product definitions include properties of the operational management product, such as a host name. The definitions also include configuration item relationships for those configuration items that are managed by the operational management product. Integration Framework for User Interface Integration Launch Entries The integration framework provides components and features that support user interface-based integration between the system applications and the external applications. You create a launch entry record in the Launch in Context application. A launch entry defines the URL of an external application that you use to open an external application. Launch entries can have the following properties: T Specific business objects or multiple objects to identify the objects that can restrict the use of a launch entry to certain applications T Context by substituting object field values into the URL string T An object classification value that controls the launch entry visibility in a user interface (only show the launch entry on the user interface based on Integration Framework Architecture 15

  • 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
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330

Integration Framework for User Interface Integration
Integration Framework Architecture
15
When invoked by a process management product, the integration module uses
data that is passed by the process management product to assist in the invocation
of the operational management product service. The integration module may also
return the operational management product response data to the process
management product.
When installed, integration modules include the logical management operations
that they support for an operational management product. Depending upon the
level of complexity, you can implement an integration module as a Java class or an
invocation channel.
Operational Management Products
Operational management products are external products that you can use to
perform information technology services. IBM
®
Tivoli
®
Application Dependency
Discovery Manager (TADDM), Tivoli Provisioning Manager (TPM), and IBM
®
Tivoli
®
Configuration Manager (TCM) are examples of operational management
products. Operational management products provide services that external
applications (integration modules) can invoke to initiate operational management
product actions.
Operational management product definitions are registered in the system and can
be loaded from the discovery engine using the Integration Composer. You can
also load operational management product definitions by using the features of
the integration framework, such as object structure services.
The operational management product definitions include properties of the
operational management product, such as a host name. The definitions also
include configuration item relationships for those configuration items that are
managed by the operational management product.
Integration Framework for User Interface Integration
The integration framework provides components and features that support user
interface-based integration between the system applications and the external
applications.
Launch Entries
You create a launch entry record in the Launch in Context application. A launch
entry defines the URL of an external application that you use to open an external
application.
Launch entries can have the following properties:
Specific business objects or multiple objects to identify the objects that can
restrict the use of a launch entry to certain applications
Context by substituting object field values into the URL string
An object classification value that controls the launch entry visibility in a
user interface (only show the launch entry on the user interface based on