IBM BJ0NJML Integration Guide - Page 296

External Application Preparations, Defining Launch Entries, Launch Entry Properties

Page 296 highlights

External Application Preparations External Application Preparations Most external applications have a Web-based console that you can launch from a URL in a Web browser. The Launch-in-context feature supports the Web application (Servlet or JSP), portal, and Java WebStart console types. To perform a navigation, the external application console must support the landin-context capability. To support context sharing, the land-in-context capability accepts data that is passed by the system to the URL. The external console uses the URL to open a window with the data that was passed to the URL. For example, in the Tivoli Application Dependency Discovery Manager Web console, you can pass the name of a view and the globally unique identifier (GUID) of a configuration item to show in the view. If the external application does not have a land-in-context capability, then the launch-in-context capability can open a standard start page within the console. If your application supports single sign-on, application users are authenticated and directed to the external console. Otherwise, the external console opens a login panel to authenticate the application user. Defining Launch Entries To make a launch entry available to the system applications: 1 Define the properties of the launch entry. 2 Create a user interface control, also known as a launch point, that is tied to the registered launch entry. Available controls include a push button, a select action menu item, and a hyperlink. 3 Assign proper security to the control. Limit access to the control by user and user group. 4 Optional: Assign a condition to the interface control to limit when the launch point is displayed, based on the data you are working with. Launch Entry Properties When you define launch entries, you enter these property values: T The launch entry name. T The launch entry description. T The URL of the console of the external application. The URL value can contain substitution variables that use data from the related business objects that you are viewing in the application. For example, if you have a launch entry that is implemented in your Person application, you can substitute the name value into the URL string by using the attribute name, {attributename}. 282 Integration 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
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330

External Application Preparations
282
Integration Guide
External Application Preparations
Most external applications have a Web-based console that you can launch from a
URL in a Web browser. The Launch-in-context feature supports the Web
application (Servlet or JSP), portal, and Java WebStart console types.
To perform a navigation, the external application console must support the land-
in-context capability. To support context sharing, the land-in-context capability
accepts data that is passed by the system to the URL. The external console uses
the URL to open a window with the data that was passed to the URL.
For example, in the Tivoli Application Dependency Discovery Manager Web
console, you can pass the name of a view and the globally unique identifier
(GUID) of a configuration item to show in the view. If the external application
does not have a land-in-context capability, then the launch-in-context capability
can open a standard start page within the console.
If your application supports single sign-on, application users are authenticated
and directed to the external console. Otherwise, the external console opens a login
panel to authenticate the application user.
Defining Launch Entries
To make a launch entry available to the system applications:
1
Define the properties of the launch entry.
2
Create a user interface control, also known as a launch point, that is tied to the
registered launch entry. Available controls include a push button, a select
action menu item, and a hyperlink.
3
Assign proper security to the control. Limit access to the control by user and
user group.
4
Optional: Assign a condition to the interface control to limit when the launch
point is displayed, based on the data you are working with.
Launch Entry Properties
When you define launch entries, you enter these property values:
The launch entry name.
The launch entry description.
The URL of the console of the external application.
The URL value can contain substitution variables that use data from the
related business objects that you are viewing in the application. For
example, if you have a launch entry that is implemented in your Person
application, you can substitute the name value into the URL string by
using the attribute name,
{attributename}
.