IBM E02HMLL-I Implementation Guide - Page 168

Creating, collaboration, object

Page 168 highlights

another collaboration object, the combination of collaboration objects is a collaboration-object group. Any number of collaboration objects can be bound into a group. The behavior of collaboration objects that are members of a collaboration-object group is different from the behavior of those that are not members of a group. When you apply a command such as start, pause, or stop to a collaboration object that is a member of a group, the command affects all members of the group. All members of a collaboration-object group must support the same transaction level in order for one member of the group to execute transactionally. If you bind a collaboration object that has transactional level None to a collaboration object that has transaction level Best Effort, both run at level None. Creating a collaboration object This section describes how to create a new collaboration object using the System Manager wizard. It describes the general flow of the wizard and references other sections in this chapter to address the specifics of collaboration object configuration. Do the following to create a collaboration object using the wizard: 1. In System Manager, right-click on the Collaboration Objects folder in an integration component library and choose Create New Collaboration Object from the context menu. The "Create New Collaboration" wizard appears, listing the installed templates in the Template Name column and a description (if available) in the Description column. The dialog is the first screen in a wizard that steps you through the initial creation and configuration of a collaboration object. You can later modify the configuration values. 2. Select the collaboration template upon which the object should be based from the list of templates. The name you select is displayed in the Selected Collaboration template field below the list. You can also type text in the Find field and the dialog will select a collaboration template whose name begins with the characters you type in the field. You can then use the up and down arrows to navigate among templates that share the pattern of characters, if there are several that match. 3. Type a name for the collaboration object in the Collaboration object name field. Note: Do not give the collaboration object exactly the same name as the collaboration template from which it is derived. That is, if the collaboration template name is SalesOrderProcessing, the name of the collaboration object cannot be simply SalesOrderProcessing. If the names are completely identical, you will not be able to access the collaboration object using repos_copy with the -e (Entity) option because repos_copy searches for the collaboration template before searching for a collaboration object. A typical approach to naming the collaboration object is to include the name of the template along with the names of the source and destination applications that the collaboration object integrates, as in the following syntax: CollabTemplateName_SourceAppName_to_DestAppName The name cannot exceed 80 characters in length. 4. Click Next to advance the wizard to the Bind ports screen. 156 IBM WebSphere Business Integration Server Express and Express Plus: System Implementation 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

another
collaboration
object,
the
combination
of
collaboration
objects
is
a
collaboration-object
group.
Any
number
of
collaboration
objects
can
be
bound
into
a
group.
The
behavior
of
collaboration
objects
that
are
members
of
a
collaboration-object
group
is
different
from
the
behavior
of
those
that
are
not
members
of
a
group.
When
you
apply
a
command
such
as
start,
pause,
or
stop
to
a
collaboration
object
that
is
a
member
of
a
group,
the
command
affects
all
members
of
the
group.
All
members
of
a
collaboration-object
group
must
support
the
same
transaction
level
in
order
for
one
member
of
the
group
to
execute
transactionally.
If
you
bind
a
collaboration
object
that
has
transactional
level
None
to
a
collaboration
object
that
has
transaction
level
Best
Effort
,
both
run
at
level
None
.
Creating
a
collaboration
object
This
section
describes
how
to
create
a
new
collaboration
object
using
the
System
Manager
wizard.
It
describes
the
general
flow
of
the
wizard
and
references
other
sections
in
this
chapter
to
address
the
specifics
of
collaboration
object
configuration.
Do
the
following
to
create
a
collaboration
object
using
the
wizard:
1.
In
System
Manager,
right-click
on
the
Collaboration
Objects
folder
in
an
integration
component
library
and
choose
Create
New
Collaboration
Object
from
the
context
menu.
The
“Create
New
Collaboration”
wizard
appears,
listing
the
installed
templates
in
the
Template
Name
column
and
a
description
(if
available)
in
the
Description
column.
The
dialog
is
the
first
screen
in
a
wizard
that
steps
you
through
the
initial
creation
and
configuration
of
a
collaboration
object.
You
can
later
modify
the
configuration
values.
2.
Select
the
collaboration
template
upon
which
the
object
should
be
based
from
the
list
of
templates.
The
name
you
select
is
displayed
in
the
Selected
Collaboration
template
field
below
the
list.
You
can
also
type
text
in
the
Find
field
and
the
dialog
will
select
a
collaboration
template
whose
name
begins
with
the
characters
you
type
in
the
field.
You
can
then
use
the
up
and
down
arrows
to
navigate
among
templates
that
share
the
pattern
of
characters,
if
there
are
several
that
match.
3.
Type
a
name
for
the
collaboration
object
in
the
Collaboration
object
name
field.
Note:
Do
not
give
the
collaboration
object
exactly
the
same
name
as
the
collaboration
template
from
which
it
is
derived.
That
is,
if
the
collaboration
template
name
is
SalesOrderProcessing
,
the
name
of
the
collaboration
object
cannot
be
simply
SalesOrderProcessing
.
If
the
names
are
completely
identical,
you
will
not
be
able
to
access
the
collaboration
object
using
repos_copy
with
the
-e
(Entity)
option
because
repos_copy
searches
for
the
collaboration
template
before
searching
for
a
collaboration
object.
A
typical
approach
to
naming
the
collaboration
object
is
to
include
the
name
of
the
template
along
with
the
names
of
the
source
and
destination
applications
that
the
collaboration
object
integrates,
as
in
the
following
syntax:
CollabTemplateName_SourceAppName_to_DestAppName
The
name
cannot
exceed
80
characters
in
length.
4.
Click
Next
to
advance
the
wizard
to
the
Bind
ports
screen.
156
IBM
WebSphere
Business
Integration
Server
Express
and
Express
Plus:
System
Implementation
Guide