Embed Size (px)
Citation preview
<In
sert
Pic
ture
Here
>
SO
A S
uit
e S
up
po
rt 1
0g
R3 (
10.1
.3.x
):
Patc
hin
g s
trate
gy a
nd
mo
st
co
mm
on
desig
n c
hall
en
ges
Natascha Schönfeld & Thorsten W
esselborg
Principal Support Engineers -BDE Integration Products
<In
sert
Pic
ture
Here
>
Ag
en
da
•Introduction -Motivation
•10.1.3.x Patching Strategy and C
ertification
(Thorsten)
•10.1.3.x Common BPEL design problems
(Natascha)
•Q&A
DOAG SIG
SOA Köln, 11.05.2009
•Q&A
Mo
tivati
on
•Increase t
ran
sp
are
ncyregarding the current
patching strategy for 10.1.3.x for customers and
partners
•P
rovid
e in
form
ati
onabout useful sources r
eg
ard
ing
cert
ific
ati
on
s a
nd
err
or
co
rrecti
on
po
licie
scert
ific
ati
on
s a
nd
err
or
co
rrecti
on
po
licie
s
•Address the m
ost
co
mm
on
desig
n a
nd
co
nfi
gu
rati
on
pit
fall
s, that lead to escalations and
extend resolution tim
es in late phases of customer
projects .
DOAG SIG
SOA Köln, 11.05.2009
So
meti
mes it
feels
lik
e t
his
...
(… o
f c
ou
rse
th
is is
Dilb
ert
.co
m o
nly
)
Cu
sto
me
rC
us
tom
er
•Global Product Support / FL
•BDE (Bug Diagnosticsand Escalations) / BL
Glo
ba
l C
us
tom
er
Su
pp
ort
De
live
ryG
lob
al C
us
tom
er
Su
pp
ort
De
live
ry
Bu
g D
iag
no
sti
cs a
nd
Escala
tio
ns
Ou
r ro
le in
th
e r
es
olu
tio
n p
roc
es
s
•SE (Sustaining Engineering)
•Base Development
•Product Management
•Patching Team
•A-Team
Pro
du
ct
De
ve
lop
me
nt
Pro
du
ct
De
ve
lop
me
nt
“Global BDE (Bug, Diagnosis and Escalations) acts as the
primary Support interface to Development for Bug
handling.
BDE focuses on managing the Customer Bug backlog
and Bug escalations through technical analysis, training,
process improvement and by sustaining a cooperative
relationship with the respective Product Development and
Support teams.”
Bu
g D
iag
no
sti
cs a
nd
Escala
tio
ns
Ou
r ro
le in
th
e r
es
olu
tio
n p
roc
es
s
Support teams.”
�BUG Lifecycle Coordination
�BUG Triage/Screening Function
�BUG Prioritization and Escalation Support
�Fix Backport and Patch Delivery Coordination
�External OEM vendor Support coordination
Bu
g D
iag
no
sti
cs a
nd
Escala
tio
ns
Ou
r ro
le in
th
e r
es
olu
tio
n p
roc
es
s
•O
ur
Mis
sio
n is, to proactively i
mp
rove B
ug
reso
luti
on
tim
esand reduce the number of Bugs and
Escalations.
•Additionally, Global BDE's aim
is to engage
proactively in the Bug process to ensure the t
imely
proactively in the Bug process to ensure the t
imely
an
d s
uccessfu
l re
so
luti
onof all escalated and
critical issues.
DOAG SIG
SOA Köln, 11.05.2009
jdb
c BP
EL
oc4j
OE
M
Da
ta G
ath
eri
ng
a
nd
An
aly
sis
/ B
DE
Bu
g
Sc
ree
nin
g
Re
so
luti
on
, C
oll
ab
ora
tio
n
wit
h B
ug
ow
ne
r (D
EV
)
Fix
Ba
ck
po
rt
Pro
ble
m
Bu
g D
iag
no
sti
cs a
nd
Escala
tio
ns
Bu
gg
ed
Ca
se
Lif
ec
yc
le
Sc
ree
nin
g(D
EV
)
So
luti
on
/Pa
tch
Th
ing
s t
o a
vo
id…
DOAG SIG
SOA Köln, 11.05.2009
htt
p:/
/ww
w.s
t.cs.u
ni-
saarl
an
d.d
e/e
du
/ad
eb
ug
/2008/s
lid
es/T
rackin
gP
rob
lem
s.p
df
Bu
g D
iag
no
sti
cs a
nd
Escala
tio
ns
Wh
at
is a
bu
g?
•… a description of a
po
ssib
le p
rod
uct
malf
un
cti
on
or
do
cu
men
tati
on
defe
ct
•It m
ight turn out to be
Pu
blic
SR
en
trie
s:
•It m
ight turn out to be
“wo
rks a
s d
esig
ned” or
a d
esig
n / c
on
fig
ura
tio
n
issu
e
DOAG SIG
SOA Köln, 11.05.2009
Bu
g D
iag
no
sti
cs a
nd
Escala
tio
ns
Wh
at
is a
wo
rka
rou
nd
?
•… a v
ali
d a
nd
su
pp
ort
ed
wayto avoid
the impacts of a r
ealbug
(until the bug is fixed)
•… the only solution to
•… the only solution to
solve a problem, if the
behavior is confirm
ed as
expected
DOAG SIG
SOA Köln, 11.05.2009
Wo
rks
as
d
es
ign
ed
!
Bu
g D
iag
no
sti
cs a
nd
Escala
tio
ns
OE
M c
ha
lle
ng
es
•Third party Support organizations
–Lim
ited O
racle Know-H
ow
–Different patching process
–No direct, automatic data exchange between support systems
•Communication boundaries betw
een project
•Communication boundaries betw
een project
stakeholders
DO
AG
SIG
SO
A K
öln
, 1
1.0
5.2
00
9
Bu
g D
iag
no
sti
cs
an
d E
scala
tio
ns
OE
M c
ha
lle
ng
es
–W
ha
t yo
u c
an
do
in
ste
ad
... in
ca
se
of
a
pro
ble
m
•Sim
plify the use case
−Reproduce the problem with standard functions
•Try to identify and isolate the component
•Try to elim
inate the SOA component(s)
−Standalone test case (e
. g. http://host:port/iwafjca/, Application Explorer)
DO
AG
SIG
SO
A K
öln
, 1
1.0
5.2
00
9
−Standalone test case (e
. g. http://host:port/iwafjca/, Application Explorer)
•Involve the component owners into the resolution
process
•Describe system landscape
•Adapter release N
otes / Debugging + Patching N
ote
−736005.1 Common Adapter issues and How To's (still to be
extended)
<In
sert
Pic
ture
Here
>
SO
A S
uit
e 1
0.1
.3.x
Patc
hin
g S
trate
gy
DOAG SIG
SOA Köln, 11.05.2009
•Fixes are usually done on the l
ate
st
co
de l
ine b
ran
ch
and then back ported.
•P
atc
h s
ets
are the preferred vehicles for delivering
bug fixes to the customers
•Due to number of fixes, additional regular
SO
A 1
0.1
.3.x
Patc
hin
g S
trate
gy
Mo
tiva
tio
n a
nd
His
tory
•Due to number of fixes, additional regular
Bundle Patches (“SOA M
LRs”) are
released for SOA Server Infrastructure
(BPEL/ESB/Adapters) since 10.1.3.3
•The latest SOA M
LRs can be found on
Metalink via the following tracking bugs:
–Bug 6814276 -10.1.3.3.1 cumulative m
lr placeholder
–Bug 7380737 -10.1.3.4.0 cumulative m
lr placeholder
•Please check the Readme.txt delivered w
ith the M
LR
SO
A 1
0.1
.3.x
Patc
hin
g S
trate
gy
SO
A M
LR
De
tails
•Please check the Readme.txt delivered w
ith the M
LR
•Please review the following M
etalink N
otes for any
updates to the README:
–Note 741499.1 "Supplement to 10.1.3.4 M
LR README.txt
–Note 554100.1 "Supplement to 10.1.3.3.1 M
LR README.txt"
•N
o s
ing
le p
atc
hes (“one-off patches”)
can be installed on top of SOA M
LRs
(Merge Label Requests) due to current
limitation in O
patch.
•W
ait
ing
peri
od
until fix inclusion into
SO
A 1
0.1
.3.x
Patc
hin
g S
trate
gy
Cu
rre
nt
Ch
alle
ng
es
“next” M
LR
•Q
uali
ty a
nd
reg
ressio
n t
esti
ngof
MLRs vs. on-schedule delivery
•Third party container (W
LS, etc.)
certification of SOA M
LRs
•New feature in O
patch is currently being tested, which
enables “
overl
ayin
g” of patches. This w
ill enable:
–In-tim
e single (one-off) patch delivery for time critical issues on
top of SOA M
LRs
–Less frequent, but fully integration tested and certified SOA
MLRs
SO
A 1
0.1
.3.x
Patc
hin
g S
trate
gy
Ou
tlo
ok
MLRs
•SOA Patches will be enabled to use p
atc
h
cla
ssif
icati
on
s. This will allow to identify
“recommended” patches via M
etalink
•Opatch “standalone” will enable applying patches to
Jdeveloper 11g
Patc
hin
g a
nd
Err
or
Co
rrecti
on
Po
licy
Info
rma
tio
n a
nd
us
efu
l lin
ks
•S
up
po
rt P
oli
cie
s:
http://www.oracle.com/support/policies.htm
l
•C
ert
ific
ati
on
s
•http://www.oracle.com/technology/software/products/i
as/files/oracle_soa_certification_101310.htm
las/files/oracle_soa_certification_101310.htm
l
•S
up
po
rt S
tatu
s a
nd
Ale
rts (
No
te 3
97022.1
)
https://m
etalink2.oracle.com/m
etalink/plsql/ml2_docu
ments.showFrameDocument?p_database_id=NOT&p
_id=397022.1
DOAG SIG
SOA Köln, 11.05.2009
<In
sert
Pic
ture
Here
>
SO
A S
uit
e 1
0.1
.3.x
Co
mm
on
BP
EL
Desig
n
Pit
falls
DOAG SIG
SOA Köln, 11.05.2009
Pit
falls
Co
mm
on
BP
EL
Desig
n P
itfa
lls
Mo
tiva
tio
n
•E
scala
ted
bu
gs being closed w
ith the statuses below
•Occur in l
ate
pro
ject
ph
ases
•Resolution tim
e m
ay be long, as a lot of components are
involved.
•Symptoms: p
erf
orm
an
ce d
eg
rad
ati
on
an
d r
eso
urc
e
DOAG SIG
SOA Köln, 11.05.2009
•Symptoms: p
erf
orm
an
ce d
eg
rad
ati
on
an
d r
eso
urc
e
lim
its (OOM)
Co
mm
on
BP
EL
Desig
n P
itfa
lls
Re
as
on
s
•Often due to m
issing c
on
fig
ura
tio
n s
tep
s, the docs
are not very detailed…
•Often due to d
esig
n p
att
ern
s chosen, which impact
dehydration and threading..
DOAG SIG
SOA Köln, 11.05.2009
Co
mm
on
BP
EL
Desig
n P
itfa
lls
Serv
ice i
nte
rfaces a
nd
tra
nsacti
on
s
Receiv
e
Rep
ly
Clie
nt
•Typical "synchronous" process
•Request-response invocation
Req
uest
Resp
on
se
Receiv
e
Invo
ke
Clie
nt
On
e-w
ay
On
e-w
ay (
Call
back)
•Typical "asynchronous" process
•One-w
ay with callback
DOAG SIG
SOA Köln, 11.05.2009
Co
mm
on
BP
EL
Desig
n P
itfa
lls
Serv
ice i
nte
rfaces a
nd
tra
nsacti
on
s
•Transient
•Durable
Receiv
e
Rep
ly
Clie
nt
Re
qu
es
t
Re
sp
on
se
Receiv
e
Rep
ly
Clie
nt
On
e-w
ay
Req
uest
DOAG SIG
SOA Köln, 11.05.2009
Rep
ly
Invo
ke
Invo
ke
Serv
ice
Re
qu
es
t-R
es
po
ns
e
On
e-w
ay (
Ca
llb
ac
k)
Invo
ke
Receiv
e
Serv
ice
Invo
ke
On
e-w
ay (
Call
back)
Req
uest
Resp
on
se
Co
mm
on
BP
EL
Desig
n P
itfa
lls
BP
EL
Pro
ce
ss
De
sig
n C
on
sid
era
tio
ns
•The following i
mp
lem
en
tati
on
patt
ern
s o
f B
PE
L
pro
cess d
esig
neither incur
larg
e p
erf
orm
an
ce c
ost,
or are m
eant to boost perform
ance, but come with
neg
ati
ve im
pli
cati
on
s to other areas:
–Large while loop
–Large while loop
–Batch processing
–Synchronous durable process
–Flow/FlowN with non-blocking invoke
–Non-idempotent invoke
–Inbound adapter with asynchronous process
DOAG SIG
SOA Köln, 11.05.2009
Co
mm
on
BP
EL
Desig
n P
itfa
lls
Big
<w
hile
> lo
op
s
An
ti-p
att
ern
s
•Using <
wh
ile>
for im
plementing r
etr
y l
og
ic
•Using <
wh
ile>
together with b
reakp
oin
t acti
vit
ies
without the need for content aggregation.
•Using <
wh
ile>
with the expectation of callback
•Using <
wh
ile>
with the expectation of callback
message ordering
•Singleton process without externalization of sub-steps
–level of granularity
DOAG SIG
SOA Köln, 11.05.2009
Co
mm
on
BP
EL
Desig
n P
itfa
lls
Big
<w
hile
> lo
op
s
Rem
em
ber.
..
•Each loop iteration creates a new scope object. This
object takes m
em
ory, (not much) but with each iteration
the t
ota
l all
ocate
d s
pace g
row
s.
•If a large w
hile loop contains a breakpoint activity such
•If a large w
hile loop contains a breakpoint activity such
as W
ait, the entire scope tree will n
eed
to
be p
ers
iste
d
as well as any w
ork items created since the last
dehydration.
DOAG SIG
SOA Köln, 11.05.2009
Co
mm
on
BP
EL
Desig
n P
itfa
lls
Big
<w
hile
> lo
op
s..
•S
ho
uld
I Im
ple
men
t a D
aem
on
usin
g O
racle
BP
EL
Pro
cess M
an
ag
er?
•The short answer is no…
•http://download.oracle.com/technology/tech/soa/soa_
best_practices_1013x_drop3.pdfSOA Best Practices
DOAG SIG
SOA Köln, 11.05.2009
best_practices_1013x_drop3.pdfSOA Best Practices
Co
mm
on
BP
EL
Desig
n P
itfa
lls
Big
<w
hile
> lo
op
s
Wh
at
yo
u c
an
do
in
ste
ad
...
•Create your own activation agent as daemon process
•Use BPEL as a glue to orchestrate service endpoints,
do
no
t u
se i
t as a
pro
gra
mm
ing
lan
gu
ag
e
DOAG SIG
SOA Köln, 11.05.2009
Co
mm
on
BP
EL
Desig
n P
itfa
lls
Ba
tch
pro
ce
ss
ing
An
ti-p
att
ern
s
•File / FTP adapters pick-up large files once a day
•XML Files /opaque payload
•Using BPEL as “
Batc
h P
rocess E
xecu
tio
n L
an
gu
ag
e”
is not what BPEL is intended for. It causes excessive
CPU and m
emory consumption on the large size
payload
DOAG SIG
SOA Köln, 11.05.2009
Co
mm
on
BP
EL
Desig
n P
itfa
lls
Ba
tch
pro
ce
ss
ing
Wh
at
yo
u c
an
do
in
ste
ad
...
•Consider if O
racle Data Integrator (O
DI) is better fit
for the job
DOAG SIG
SOA Köln, 11.05.2009
Co
mm
on
BP
EL
Desig
n P
itfa
lls
Th
e t
ruth
ab
ou
t <
flo
w>
/<fl
ow
N>
Wh
at
the s
tan
dard
says…
•The <
flo
w>
construct allows you to specify o
ne o
r
mo
re a
cti
vit
ies t
o b
e p
erf
orm
ed
co
ncu
rren
tly.
Lin
kscan be used w
ithin concurrent activities to
define arbitrary control…
DOAG SIG
SOA Köln, 11.05.2009
define arbitrary control…
•The m
ost fundamental semantic effect of grouping a
set of activities in a flow is to enable c
on
cu
rren
cy
htt
p:/
/do
wn
load
.bo
uld
er.
ibm
.co
m/i
bm
dl/
pu
b/s
oft
ware
/dw
/sp
ecs/w
s-
bp
el/w
s-b
pel.
pd
fB
PE
L4W
S 1
.1 B
PE
Lv11-M
ay0
520
03F
inal.
pd
f 1
2.5
Flo
w
Co
mm
on
BP
EL
Desig
n P
itfa
lls
Th
e t
ruth
ab
ou
t <
flo
w>
/<fl
ow
N>
An
ti-p
att
ern
s
•Using <
flo
w>
to increase parallelism by setting
No
nB
lockin
gIn
vo
kein the Partnerlink properties
•Calling the same partnerlink w
ithin <
flo
w>
in order to
•Calling the same partnerlink w
ithin <
flo
w>
in order to
increase reusability
•Calling the same Apps concurrent program within
<fl
ow
N>
DOAG SIG
SOA Köln, 11.05.2009
Co
mm
on
BP
EL
Desig
n P
itfa
lls
Th
e t
ruth
ab
ou
t <
flo
w>
/<fl
ow
N>
Rem
em
ber.
..
•Partner link property NonBlockingInvokeindicates
whether BPEL would u
se m
ult
iple
th
read
s to execute
invocation to this partner in Flow/Flown branches
•T
rue: Engine w
ill spawn a n
ew
th
readto execute each
•T
rue: Engine w
ill spawn a n
ew
th
readto execute each
invocation in the flow/flowN
branch. It will go into the
same dispatching m
echanism as the delivery service.
•F
als
e (
defa
ult
): Engine w
ill N
OT
sp
aw
n a
new
th
read
to execute each invocation in the flow/flowN
branch
DOAG SIG
SOA Köln, 11.05.2009
Co
mm
on
BP
EL
Desig
n P
itfa
lls
Th
e t
ruth
ab
ou
t <
flo
w>
/<fl
ow
N>
Wh
at
yo
u c
an
do
in
ste
ad
...
•Be aware of the implications of non-blocking invoke if
used to increase parallelism
•Use <
flo
w>
for im
plementing concurrency.
•Use <
flo
w>
for im
plementing concurrency.
•You should w
eight between the p
erf
orm
an
ce g
ain
of
mu
lti-
thre
ad
ingand the p
erf
orm
an
ce c
ost
of
deh
yd
rati
on
DOAG SIG
SOA Köln, 11.05.2009
Co
mm
on
BP
EL
Desig
n P
itfa
lls
Syn
ch
ron
ou
s d
ura
ble
pro
ce
ss
as
a s
erv
ice
pro
vid
er
Receiv
e
Invo
ke
EJ
BT
ran
sacti
on
Part
icip
ate
Le
ga
cy
Co
mm
itC
om
mit
Se
rvic
es
Clie
nt
DOAG SIG
SOA Köln, 11.05.2009
Invo
ke
Rep
ly
Le
ga
cy
No
Tra
nsacti
on
SO
AP
No
Tra
nsacti
on
Co
mm
itC
om
mit
Ad
din
g a
bre
ak
po
int
ac
tivit
y t
o a
syn
ch
ron
ou
s p
roc
es
s m
ak
es
th
e p
roc
es
s
du
rab
le.
Co
mm
on
BP
EL
Desig
n P
itfa
lls
Syn
ch
ron
ou
s d
ura
ble
pro
ce
ss
as
a s
erv
ice
pro
vid
er
An
ti-p
att
ern
s
•Usage of ch
eckp
oin
ts, overdesigned reliability.
•Calling external programs with long execution tim
es
and i
gn
ori
ng
tim
eo
uts
in the design (PL/SQL
procedures , SAP BAPI’s)
procedures , SAP BAPI’s)
DOAG SIG
SOA Köln, 11.05.2009
Co
mm
on
BP
EL
Desig
n P
itfa
lls
Syn
ch
ron
ou
s d
ura
ble
pro
ce
ss
as
a s
erv
ice
pro
vid
er
Rem
em
ber.
..
•The consumer BPEL process expects a synchronous
reply within the s
yn
cM
axW
ait
Tim
e
•Depending upon the server load, the reply m
ay not be
scheduled for some tim
e, which m
eans the c
all
er
thre
ad
scheduled for some tim
e, which m
eans the c
all
er
thre
ad
will ti
me o
ut after syncMaxWaitTim
e seconds.
•If the caller is an asynchronous BPEL process, both the
caller and called process are c
on
su
min
g M
DB
receiv
er
thre
ad
s. We m
ay have a thread starvation scenario
(specific to 10.1.3.3.x).
DOAG SIG
SOA Köln, 11.05.2009
Co
mm
on
BP
EL
Desig
n P
itfa
lls
Syn
ch
ron
ou
s d
ura
ble
pro
ce
ss
as
a s
erv
ice
pro
vid
er
Wh
at
yo
u c
an
do
in
ste
ad
...
•Consider using ‚p
art
ial p
rocessin
g p
att
ern‘ , when
designing BPEL service providers
•Use checkpoint() for explicitely influencing BPEL PM
transactions.
transactions.
•Consider the p
rocess p
ers
iste
nce t
yp
es w
hen
designing transactions.
DOAG SIG
SOA Köln, 11.05.2009
Receiv
e
Rep
ly
Invo
ke
Invo
ke
Clie
nt
Serv
ice
Co
mm
on
BP
EL
Desig
n P
itfa
lls
Syn
ch
ron
ou
s p
roc
es
se
s…
Wh
at
yo
u c
an
do
in
ste
ad
...
•Carefully design e
rro
r h
an
dli
ngand actions required for
the tim
eouts depending on the SLA’s.
•Adjusting t
ran
sacti
on
tim
eo
ut
sett
ing
s m
ight
help in some cases, but it is not solving
help in some cases, but it is not solving
the problem.
DOAG SIG
SOA Köln, 11.05.2009
Receiv
e
Rep
ly
Invo
ke
Invo
ke
Clie
nt
Serv
ice
Co
mm
on
BP
EL
Desig
n P
itfa
lls
Lo
ng
Ru
nn
ing
tra
ns
ac
tio
ns
An
ti-p
att
ern
s
•Designing XA transactions for asynchronous long
running processes.O
r in other words, im
plementing
all
-or-
no
thin
gbehavior with BPEL..
all
-or-
no
thin
gbehavior with BPEL..
•Mostly a d
esig
n d
ecis
ion
whenever the partner
applications cannot be m
odified to support logical
rollback.
•Im
plement mechanisms for distributing transactions
hoping that g
uara
nte
es d
ata
co
nsis
ten
cy
DOAG SIG
SOA Köln, 11.05.2009
Co
mm
on
BP
EL
Desig
n P
itfa
lls
Lo
ng
Ru
nn
ing
tra
ns
ac
tio
ns
Wh
at
yo
u c
an
do
in
ste
ad
...
•Consider designing c
om
pen
sati
ng
op
era
tio
ns (part
of BPEL spec and implemented in BPEL PM) to run
operations that lo
gic
all
y u
nd
o the effects of partial
work
work
•Async, lo
ng
-ru
nn
ing
BP
EL
Pro
cesses ≠
lo
ng
-
run
nin
g J
TA
tra
nsacti
on
s...
•Leverage other
imp
lem
en
tati
on
po
ssib
ilit
ies for
patterns requiring distributed transactions
•D
e-c
ou
pli
ng
is a
pro
cess,
no
t a b
ug
–governance
aspects
DOAG SIG
SOA Köln, 11.05.2009
Co
mm
on
BP
EL
Desig
n P
itfa
lls
Ru
les
of
thu
mb
fo
r d
es
ign
ing
tra
ns
ac
tio
ns
wit
h B
PE
L P
M
htt
p:/
/ww
w.o
racle
.co
m/t
ech
no
log
y/a
rch
itect/
so
a-s
uit
e-s
eri
es/w
li-b
pel-
tran
sacti
on
s.h
tml
DOAG SIG
SOA Köln, 11.05.2009
Co
mm
on
BP
EL
Desig
n P
itfa
lls
No
n Id
em
po
ten
t in
vo
ke
An
ti-p
att
ern
s
•Calling i
dem
po
ten
tapplications w
ith n
on
-
idem
po
ten
t sett
ing
s
DOAG SIG
SOA Köln, 11.05.2009
Co
mm
on
BP
EL
Desig
n P
itfa
lls
No
n Id
em
po
ten
t in
vo
ke
Rem
em
ber.
..
•On one hand, an non-idempotent invoke i
ncu
rs
deh
yd
rati
on
an
d p
erf
orm
an
ce s
acri
fices
•On the other hand, non-idempotent invoke can only
reduce but n
ot
tota
lly e
lim
inate
the probability of the
reduce but n
ot
tota
lly e
lim
inate
the probability of the
endpoint being called m
ore than once, if the protocol to
the endpoint is not transactional (such as file, FTP or
SOAP)
DOAG SIG
SOA Köln, 11.05.2009
Co
mm
on
BP
EL
Desig
n P
itfa
lls
No
n Id
em
po
ten
t in
vo
ke
Wh
at
yo
u c
an
do
in
ste
ad
...
•You m
ust weight between the l
ow
er
pro
bab
ilit
y of
endpoint being called m
ore than once, and the
perf
orm
an
ce c
ost
of
deh
yd
rati
on
perf
orm
an
ce c
ost
of
deh
yd
rati
on
•Know the n
atu
re o
f yo
ur
part
ner
ap
pli
cati
on
s and their
role in the end2end Flow.
DOAG SIG
SOA Köln, 11.05.2009
Co
mm
on
BP
EL
Desig
n P
itfa
lls
Inb
ou
nd
ad
ap
ter
wit
h a
syn
c p
roc
es
s
An
ti-p
att
ern
s
•Although the inbound backend system is a natural
persistence of the m
essage, BPEL’s invoke_message
table also persisting the m
essage.
DOAG SIG
SOA Köln, 11.05.2009
Co
mm
on
BP
EL
Desig
n P
itfa
lls
Lo
ng
Ru
nn
ing
tra
ns
ac
tio
ns
Definingtheorganizationalprocessesaround
BPEL,i.e.,
whousesBPELandhow,is
of
paramountimportanceto
theroleandsuccess
ofserviceorientedarchitecture.
DOAG SIG
SOA Köln, 11.05.2009
ofserviceorientedarchitecture.
Paul Brown 2003-12-16
http://www.bptrends.com/publicationfiles/BPEL4ProgArchies.pdf
Ou
r 2 c
en
ts..
.
•Consult the R
ele
ase N
ote
s /
RE
AD
ME
s about the
restrictions before you start implementation.
•Let us know about your
bu
sin
ess u
se c
ase. This
greatly helps to m
ove the r
eso
luti
on
pro
cess
forw
ard and find viable solutions.
•Try to remove / break down t
est
case c
om
ple
xit
y.
DOAG SIG
SOA Köln, 11.05.2009
•Try to remove / break down t
est
case c
om
ple
xit
y.
This greatly helps to iso
late
components, which are
causing the problem, and route the bug to the correct
group e
arl
y i
n t
he r
eso
luti
on
pro
cess.
•Im
plementation design decisions highly influence
BPEL PM’s dehydration and threading behavior.
Usefu
l li
nks
•Tim
eout settings
http://download-
west.oracle.com/docs/cd/B31017_01/integrate.1013/b28981/app
_trblshoot.htm
#sthref3957
•AIA Foundation Packs G
uides
http://edelivery.oracle.com/EPD/Download/get_form
?egroup_aru
_number=10522402(needs authentication)
DOAG SIG
SOA Köln, 11.05.2009
_number=10522402(needs authentication)
•Transactions
http://www.oracle.com/technology/architect/soa-suite-series/wli-
bpel-transactions.htm
l
•http://download.oracle.com/technology/tech/soa/soa_best_practi
ces_1013x_drop3.pdf
Q U
E S
T I O
N S
Q U
E S
T I O
N S
Q U
E S
T I O
N S
Q U
E S
T I O
N S
A N
S W
E R
SA
N S
W E
R S
DOAG SIG
SOA Köln, 11.05.2009
