IBM E02HMLL-I Implementation Guide - Page 66

Naming, component, guidelines, Launching, designer, tools

Page 66 highlights

For information on working with components that you have developed and deployed to an InterChange Server Express instance, see "Working with components in an InterChange Server Express repository" on page 83. Naming component guidelines When you create components, keep in mind the following general guidelines and requirements v In general, limit component names to combinations of alphanumeric characters and underscores because most punctuation and special characters are not used in an ICS system. Do not use spaces in component names. v Begin all component names with a letter (not a digit or an underscore). See specific sections for exceptions. v In property names, do not use apostrophes (') or double quotation marks (″). v Many component names have a maximum length limit: - Map names: Maximum 76 characters - Collaboration templates: Maximum 80 characters - Collaboration object: Maximum 80 characters v The following components must be composed only of characters in the code set associated with the U.S. English locale, en_US: connectors and connector configuration properties, collaboration templates, collaboration objects, collaboration properties, collaboration ports, maps, business object definitions, attributes, attribute types, and verbs. In the interest of backward compatibility, IBM enforces only a few naming requirements. However, because naming is subject to restrictions from underlying system components, follow the conventions in this guide. For example, Java imposes restrictions on Java class names, and your operating system and database likely have restrictions on the length of and characters used in file names. Launching designer tools This section describes the different ways you can launch each of the designer tools. You can use the designer tools to create new components or to open and modify existing components. Note: If you attempt to launch one of the designer tools and experience an error about a class not being found, you must launch System Manager and then try to launch the designer tool again. System Manager does not have to remain running after the tool is initially launched, however. Business Object Designer Express To launch Business Object Designer Express, do one of the following: v Right-click the Business Objects folder in the WebSphere Business Integration System view and choose Create New Business Object from the context menu v Select any folder in the WebSphere Business Integration System Manager view and do one of the following: - Select Tools > Business Object Designer Express from the menu bar - Click the Business Object Designer Express toolbar button - Use the keyboard shortcut Ctrl+4 v Select Start > Programs > WebSphere Business Integration Express > Toolset Express> Development > Business Object Designer Express 54 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

For
information
on
working
with
components
that
you
have
developed
and
deployed
to
an
InterChange
Server
Express
instance,
see
“Working
with
components
in
an
InterChange
Server
Express
repository”
on
page
83.
Naming
component
guidelines
When
you
create
components,
keep
in
mind
the
following
general
guidelines
and
requirements
v
In
general,
limit
component
names
to
combinations
of
alphanumeric
characters
and
underscores
because
most
punctuation
and
special
characters
are
not
used
in
an
ICS
system.
Do
not
use
spaces
in
component
names.
v
Begin
all
component
names
with
a
letter
(not
a
digit
or
an
underscore).
See
specific
sections
for
exceptions.
v
In
property
names,
do
not
use
apostrophes
(’)
or
double
quotation
marks
(
).
v
Many
component
names
have
a
maximum
length
limit:
Map
names:
Maximum
76
characters
Collaboration
templates:
Maximum
80
characters
Collaboration
object:
Maximum
80
characters
v
The
following
components
must
be
composed
only
of
characters
in
the
code
set
associated
with
the
U.S.
English
locale,
en_US:
connectors
and
connector
configuration
properties,
collaboration
templates,
collaboration
objects,
collaboration
properties,
collaboration
ports,
maps,
business
object
definitions,
attributes,
attribute
types,
and
verbs.
In
the
interest
of
backward
compatibility,
IBM
enforces
only
a
few
naming
requirements.
However,
because
naming
is
subject
to
restrictions
from
underlying
system
components,
follow
the
conventions
in
this
guide.
For
example,
Java
imposes
restrictions
on
Java
class
names,
and
your
operating
system
and
database
likely
have
restrictions
on
the
length
of
and
characters
used
in
file
names.
Launching
designer
tools
This
section
describes
the
different
ways
you
can
launch
each
of
the
designer
tools.
You
can
use
the
designer
tools
to
create
new
components
or
to
open
and
modify
existing
components.
Note:
If
you
attempt
to
launch
one
of
the
designer
tools
and
experience
an
error
about
a
class
not
being
found,
you
must
launch
System
Manager
and
then
try
to
launch
the
designer
tool
again.
System
Manager
does
not
have
to
remain
running
after
the
tool
is
initially
launched,
however.
Business
Object
Designer
Express
To
launch
Business
Object
Designer
Express,
do
one
of
the
following:
v
Right-click
the
Business
Objects
folder
in
the
WebSphere
Business
Integration
System
view
and
choose
Create
New
Business
Object
from
the
context
menu
v
Select
any
folder
in
the
WebSphere
Business
Integration
System
Manager
view
and
do
one
of
the
following:
Select
Tools
>
Business
Object
Designer
Express
from
the
menu
bar
Click
the
Business
Object
Designer
Express
toolbar
button
Use
the
keyboard
shortcut
Ctrl+4
v
Select
Start
>
Programs
>
WebSphere
Business
Integration
Express
>
Toolset
Express>
Development
>
Business
Object
Designer
Express
54
IBM
WebSphere
Business
Integration
Server
Express
and
Express
Plus:
System
Implementation
Guide