Überleben im OSB / SOA Dschungel Daniel Joray Trivadis AG Bern

Transcription

1 Überleben im OSB / SOA Dschungel Daniel Jray Trivadis AG Bern Keywrds Weblgic, JMS, Perfrmance, J2EE, Mnitring, SOA, OSB Our SOA&OSB Prject Oracle SOA Suite is a cmprehensive, standards-based sftware suite t build, deply and manage integratin fllwing the cncepts f service-riented architecture (SOA). Oracle Service Bus is an enterprise service bus (ESB) that prvides the key virtualizatin layer required fr any sustainable integratin architecture. In a prductive envirnment a SOA-Suite infrastructure, invlve many cmpnent. This is nt always easy t determine which cmpnent perfrm well and which nt Scpe f this dcument is t give yu sme recmmendatins frm ur experiences, which we gt in a big custmer case where all these cmpnents were invlved. Installatin Use distinct middleware hme fr SOA and fr OSB. (eliminate cnflict in ORACLE_COMMON) Use always the last patch Set Install yur wn JDK, dn t use the system JDK We have in this prject better perfrmance with Oracle JDK as with JRckit Install the last patch set and PSU in cmparisn with the base Versin Patch : OSB Bundle Patch fix 118 bugs Patch : SOA Bundle Patch fix 768 bugs Patch : SU Patch [EJUW]: WLS PATCH SET UPDATE fix mre than 700 bugs Nbdy will spend time fr upgrade in a prject phase, but this is very imprtant t plan updates regularly in yur prject. Use a recent JDK cmpatible with Yur middleware versin After each patch regressin testing must be dne WLS Dmain Cnfiguratin Create Yur Dmain in Prductin Mde mde t maximize perfrmance. Fr perfrmance testing and prductin envirnments, cnsider using the lwest acceptable lgging level, such as "ERROR" r "WARNING" whenever pssible

2 Cnsider turning ff the HTTP access lgging If yu use nn-persistent JMS scenaris, explicitly turn ff persistence at the JMS server level. Fr persistent JMS scenaris yu can use file stre r JDBC stre. If there are multiple JMS servers invlved, create each stre n a separate disk t lwer I/O cntentin. Tune the JVM Memry Cnfiguratin (Heap / Ratin / algrithm) f each Managed Servers As sample the result in this prject fr the OSB part Cnfigure the Cnnectin Pls fr each Data Surce Ensure that the cnnectin pl has enugh free cnnectins. Set Initial Capacity and Minimum Capacity t the same value Disable unnecessary cnnectin testing and prfiling Enabling Data Surce Statement Caching Take care with the Optin Wrap datatypes and DB Adapter Take a lk t the Accept Backlg parameter (tune the number f cnnectin requests that a WebLgic Server instance accepts befre refusing additinal requests) Tune the Default Wrk Manager. It is used by an applicatin when n ther Wrk Managers are specified in the applicatin s deplyment descriptrs. The default wrk-manager belngs t a thread-pl, as initial thread-pl cmes with nly five threads, that's nt much. If yur applicatin has t face a large number f hits, yu may want t start with mre than that.well, that's quite easy. Fr OSB yu can create yur wn Wrk Manager in the WebLgic dmain and assign them t yur services Frce the time zne Set Cnfiguratin Archive Enable auf True and set the Archive Cnfiguratin parameter. This will help yu if yu break yur cnfiguratin If yur system must be permanently available, it is best t define a cluster cnfiguratin type frm the beginning f yur prject SOA and OSB envirnments are extremely slw t start (several minutes) which makes them unusable failver type cnfiguratin A cluster type f cnfiguratin is easily mdified t accept mre lad depending n demand. Fr SOA and OSB cluster cnfiguratins are rbust even under high lad variatin r if sme managed server are nt available If yu use md_wl_hs frm the Oracle HTTP Server r md_wl fr Apache, set the parameter WebLgic plugin Enabled t true

3 OSB Cluster If yu deply a large numbers f services in yur OSB yu can increase the size f the built-in cache fr prxy services Yu can cnfigure External Cherence Server and change the lcal-strage frm each cache, if yu want n spend OSB JVM Memry fr the cache. Check File sb-cherence-cache-cnfig.xml and sb-cherence-verride.xml lcated in $DOMAIN_HOME/cnfig/sb/cherence/ Yu can enable result caching fr the OSB Dmain Chse witch methd yu will use fr lad balancing SOA Cluster Oracle SOA Suite 11g use an embedded Cherence cache t crdinate several cluster-wide activities including cmpsite deplyment. T allw the cmmunicatin between the cherence cache membre yu shuld add in the setdmain.sh/cmd thse Prperties In setdmain frm Managed Server 1 In setdmain frm Managed Server 2 Dn t frget t cnfigure the Java Object Cache (JOC) and the pst JMS cnfiguratin and the pst JMS cnfiguratin In Enterprise cnsle set The Audit Level prperty enables t Prductin

4 Dn t frget t turn ff the Paylad Validatin at SOA Infra Prperties, if yu dn t need validatin at this level Fr the BPEL/BPMN Engine check the prperties dspsystemthreads dspinvkethreads dspenginethreads largedcumentthreshld Mediatr Engine check the prperties metricslevel Parallel Wrker Threads (DeferredWrkerThreadCunt) Parellel Maximum Rws Retrieved (DeferredMaxRwsRetrieved) Parallel Lcker Thread Sleep (DeferredLckerThreadSleep) SOA Schema Dn t let yur SOA Cmpsite instance grw expnentially Has ne f the biggest impacts n a SOA business applicatin Impacts perfrmance f runtime SQL queries Impacts asynchrnus ruting rules and asynchrnus BPEL prcesses Slws dwn cnsle access when querying fr auditing data Define rules t keep the huse clean, purge the instances at regular interval t btain better perfrmance frm BPEL engine and Enterprise Manager Oracle prvides a purge Script t delete instances that are n lnger required using stred prcedures that are prvided with Oracle SOA Suite ut f the bx. (sa.delete_instance) Testing Perfrmance ptimizatin n SOA Suite applicatins is a challenge! A large number f cmpnents are invlved in each Request Each cmpnent (JVM, DB, OSB, SOA, Netwrk) must be initially ptimized separately T ensure that parameter changes have the desired effect it is necessary t repeat the same test under the same cnditins several times (this change may have negative effects n the ther part f the applicatin) T be representative test cases must represent reality End scenaris must be a representative mixture f all applicatin services Fr each service it is necessary t develp autmatic test scenari that can be repeated several times. Fr each scenari it is necessary t define The expected respnse time The number f times that this service can be called per secnd The expected respnse In reality, sme query will be wrng, it is imprtant that this type f queries is integrated int yur test scenaris. Many tl will test autmatin SapUI, LadUI, Jmeter, ect, the key is t master the ne we chse!

5 Tls Fr each cmpnent type there are many specific tls t perfrm these measurements JVM -> jcnsle, jvisualvm, jmc (Java Missin Cntrl), DmainHealth WLST, Enterprise Culd Cntrl, Dmain -> DmainHealth, WLST, Enterprise Culd Cntrl, SOA -> DMS Spy, WLST, But nly few tls give yu the pssibility t see yur cmplete envirnment in the same a applicatin (Enterprise Culd Cntrl, Dynatrace, AppDynamics) Summary Each cmpnents frm a SOA Suite shuld be tuned separately. D t this, yu need autmated test scenaris T tune an applicatin, yu must understand hw it wrks, speak with develpers T ptimize the right parameters yu need t understand what represents the measured value The ptimizatin applicatin is a permanent jb. it must be started frm the start f develpment Cntact: Daniel Jray Principal Cnsultant Infrastructure Managed Services trivadis ag Weltpststrasse 5 CH-3015 Bern Mbile daniel.jray@trivadis.cm