Справочник Пользователя для IBM 4.6.x
Table
4.
Installed
Windows
file
structure
for
the
connector
Subdirectory
of
%ProductDir%
Description
\connectors\Siebel
Contains
the
connector
CWSiebel.jar
and
the
start_Siebel.bat
files.
\connectors\Siebel\dependencies
Contains
the
patch
files
for
event
management
in
the
Siebel
eBusiness
applications.
This
folder
should
also
contain
the
Siebel
.jar
files.
\connectors\messages
Contains
the
relevant
message
file,
SiebelConnector.txt
\connectors\Siebel\Samples\Repository
Contains
the
following
BO
samples:
Siebel_BCAccount
Siebel_BCQuote
Siebel_BCContact
Siebel_BCInternalProduct
Siebel_BCAsset
\repository\Siebel\
Contains
the
CN_Siebel.xsd
file.
\lib
Contains
the
WBIA.
jar
file.
\bin
Contains
the
CWConnEnv.bat
file.
Installer
adds
an
icon
for
the
connector
file
to
the
WebSphere
business
integration
menu.
For
a
fast
way
to
start
the
connector,
create
a
shortcut
to
this
file
on
the
desktop.
Note:
For
more
information
on
WebSphere
business
integration
Installer,
refer
to
the
System
Installation
Guide
for
Windows
or
for
Unix.
Event
and
archive
tables
The
connector
uses
the
event
table
to
queue
events
for
pickup.
If
you
have
set
the
ArchiveProcessed
property
to
true
or
to
no
value,
the
connector
uses
the
archive
table
to
store
events
after
updating
their
status
in
the
event
table.
For
each
event,
the
connector
gets
the
business
object’s
name,
verb,
and
key
from
the
Event
business
component.
The
connector
uses
this
information
to
retrieve
the
entire
entity
from
the
application.
If
the
entity
was
changed
after
the
event
was
first
logged,
the
connector
gets
the
initial
event
and
all
subsequent
changes.
In
other
words,
if
an
entity
is
created
and
updated
before
the
connector
gets
it
from
the
event
table,
the
connector
gets
both
data
changes
in
the
single
retrieval.
The
following
three
outcomes
are
possible
for
each
event
processed
by
a
connector:
v
Event
was
processed
successfully
v
Event
was
not
processed
successfully
v
Event
was
not
subscribed
to
If
events
are
not
deleted
from
the
event
table
after
the
connector
picks
them
up,
they
occupy
unnecessary
space
there.
However,
if
they
are
deleted,
all
events
that
are
not
processed
are
lost
and
you
cannot
audit
the
event
processing.
Therefore,
you
should
also
create
an
archive
table
and
keep
the
ArchiveProcessed
property
set
to
true.
Whenever
an
event
is
deleted
from
the
event
table,
the
connector
inserts
it
into
the
archive
table.
Configuring
event
and
archive
processing
To
configure
event
and
archive
processing,
you
must
use
configuration
properties
to
specify
the
following
information:
v
The
interval
frequency
12
Adapter
for
Siebel
eBusiness
Applications
User
Guide