v
Siebel
Sales
Enterprise
v
The
project
for
the
business
objects
that
you
want
to
use
Note:
You
should
check
in
your
locked
projects
only
through
the
query.
14.
Apply
the
physical
schema
to
your
development
database.
You
can
do
this
by
querying
for
the
two
new
tables,
CX_IBM_ARCH_Q
and
CX_IBM_EVENT_Q,
and
select
the
current
query
to
create
a
physical
schema.
Make
sure
that
you
leave
the
table
space
and
index
space
blank.
15.
Activate
the
queried
tables
in
the
development
database.
16.
Move
to
test
and
production
environments
accordingly.
17.
Move
your
newly
compiled
Siebel.srf
file
to
the
server.
Note:
Enable
Enterprise
Application
Integration
by
going
to:
Sitemap
>
Server
Administration
>
Component
Group
and
selecting
Enable.
To
set
Siebel
JAVABean:
1.
Select,
Site
Map->Server
Admin->
Components
(Sales
Object
Manager).
2.
In
the
lower
applet,
go
to
Component
Parameter
and
enter
a
timeout
value.
Note:
The
Request
Timeout
current
value
is
set
to
600.
This
means
that
the
connector
will
die
after
ten
minutes.
Based
on
Siebel,
you
can
change
this
value
to
be
as
large
as
you
want.
Creating
the
event
and
archive
tables
in
Siebel,
versions
below
7.5
This
procedure
uses
the
Siebel
Sales
Enterprise
application
as
an
example.
Substitute
all
references
to
Siebel
Sales
Enterprise
with
the
name
of
the
Siebel
application
in
use.
To
create
the
event
and
archive
tables
and
to
trigger
the
business
objects,
perform
the
following
procedure:
1.
Ensure
that
all
current
projects
have
been
checked
in.
2.
On
your
local
database,
check
out
and
lock
the
following
files:
v
New
Table
Project
v
Siebel
Sales
Enterprise
project
v
Projects
that
include
objects
that
you
want
to
modify,
such
as
the
Account
project
v
Dock
project
Note:
Ensure
that
the
projects
are
locked
on
both
the
local
and
development
servers.
3.
Apply
the
seven
patch
files
in
the
following
order
to
your
local
database:
v
cwtable.sif
v
cwview.sif
v
cwapplet.sif
v
cwbo.sif
v
cwbc.sif
v
cwdo.sif
v
cwscreen.sif
v
schemabo.sif
Chapter
2.
Installing
the
adapter
15