Oracle SOA suite and Coherence dehydration
4 likes1,177 views
Extreme performance with Oracle SOA Suite 12.2, Coherence and Exalogic can be achieved by configuring the platform to take advantage of the Exalogic infrastructure and optimizing SOA Suite and Coherence settings. Key aspects include using Coherence caching to minimize database transactions, configuring optimal WebLogic and JDBC settings for InfiniBand networking, and tuning SOA Suite dehydration and caching properties. This provides significant performance gains over a traditional architecture.
Oracle SOA suite and Coherence dehydration
- 1. Extreme performance with Oracle SOA Suite 12.2, Coherence and Exalogic Helsinki, Wednesday , May 17, 2017 By Michel Schildmeijer,
- 2. Speaker and Contents ⹠Michel Schildmeijer, Oracle ACE ⹠17 years WebLogic, Middleware, Integration Contents: ⹠Dehydration on SOA, what is it? ⹠How configure Oracle SOA Suite for Exalogic ⹠SOA and Coherence ⥠How can SOA make use of coherence for dehydration? 19-5-2017Ruimte voor voettekst2
- 3. The case âą A credit insurance company âą Lotâs of initiatives to transform to new technology âą Key platform was the âBlue Stackâ âą Current Oracle Fusion Middleware Platform on conventional hardware 19-5-2017Ruimte voor voettekst3
- 4. First: Generic Migration Plan 19-5-20174 Period 1 Period 2 Period 3 Period 4 <nn> weeks <nn> weeks <nn> weeks Inventory & Design Develop, Deploy, Build Rollout & TestRollout & Test Oracle Fusion Middleware 12c Migration Path Operational Ready & LiveOperational Ready & Live <nn> weeks
- 5. Pre-analysis Upgrade SOA 11g to 12c ⹠Pre-analysis for upgrade areas of complexity: ⥠Use custom DB scripts for purge, partitioning ⥠Custom code using SOA locator APIs ⥠Significant performance tuning in 11g? ⥠Long running Instances? 19-5-2017Redesign & Rebuild5
- 6. 19-5-2017Ruimte voor voettekst6 SOA logical landscape Process Services Orchestration System BPM Business Logic Databases Data Services Enterprise Service Bus (ESB) Systems of Record Web Portals Human Business Process Management (BPM) Security RegistryandRepository Manageandmonitor
- 7. Choice: In place upgrade SOA 11g to 12c 19-5-20177
- 8. Chosen: Side by side Upgrade SOA 11g to 12c âą New build domain configuration âą Deploy composites after upgrade âą Not for long-running instances 19-5-2017Redesign & Rebuild8
- 9. 19-5-2017Ruimte voor voettekst9 SOA Infrastructure PlatformSOA Infrastructure Platform WebLogic Server Managed Server(S) Java EE deployed Apps for SOA Webapps EJB/MDB RAR Software & Config files Oracle Linux SOA WebLogic Cluster Operating System Installation & Config Domain Configuration JDBC JMS HTTP(S) JMX
- 10. Side by side Upgrade SOA 11g to 12c 19-5-2017Redesign & Rebuild10
- 11. Dehydration of SOA Suite, what is it? âą Statelessness - Services minimize resource consumption by deferring the management of state information when necessary âą State is maintained and offloaded in a dehydration store âą An instance is created every time a new inbound call arrives âą Every important step is maintained using a dehydration point 19-5-2017Ruimte voor voettekst11
- 12. Why Dehydration? âą Long running instances waiting for response consumes memory and CPU âą While waiting for the response the bpel engine can store the process, thus freeing up server resources. âą Over the life cycle of the BPEL instance, the instance with the current state of execution may be saved in database. 19-5-2017Ruimte voor voettekst12
- 13. Dehydration continued ⹠Storing status of BPEL process(long running process, asynchronous process) into database tables ⹠SOA_INFRA schema is the dehydration store contains tables to hold the meta data of the process. ⹠Synchronous Process ⥠Process gets dehydrated only at the end of the process. ⥠Using Dehydrate activity we can explicitly dehydrate process state if required. ⹠Asynchronous Process ⥠Automatically dehydrated the process based on the activities used. 19-5-2017Ruimte voor voettekst13
- 14. Dehydration store tables âą Cube_Instance: Stores the information about the composite instance that gets created. âą Cube_scope: Stores information about the scopes and variables declared and used. âą DLV_Message: All the incoming payload details are stored. âą Invoke_Message: All the outgoing message payload details are stored. âą Audit_Trail: Used to store information xml rendered in EM console. 19-5-2017Ruimte voor voettekst14
- 16. âą Transaction speeds are constrained by database I/O at dehydration points âą Persisting state and flow data cause substantial database growth âą Purging database at regular intervals is a mandatory operational overhead Oracle Confidential â Internal/Restricted/Highly Restricted16 Challenges
- 17. A possible Solution âą Choice to persist flow and instance data only for faulted transactions âą Coherence cache for running transactions (flow trace, BPEL state, audit trail and payloads) âą Tracks and updates already persisted transactions âą Choice to defer writing to a database - update in batches âą Configurable write behind thread âą Metrics to track and evaluate state of transactions
- 19. But first ⹠Design a SOA Suite infrastructure which makes use of: ⥠Extreme performance features ⥠Stable and solid solution architecture ⥠Exalogic network capabilities 19-5-2017Ruimte voor voettekst19
- 21. Exalogic X5-2 Converged Infrastructure Integrated Network Attached Storage ZFS Clustered for high availability 80 TB SAS disk, 6,4 TB read cache, 800 GB write cache Clones, snapshots, remote replication Integrated Storage 40 Gb/sec internal I/O backplane 10 Gigabit Ethernet connectivity to datacenter Internal I/O Fabric and Data Center Conn. 2 socket, 8-core, 2.9 GHz Intel Xeon processors 7.5 TB of DRAM 1080 cores in a Full Rack; also available in 1/2,1/4,1/8 or multi-rack configurations Redundant SSD, power, cooling, InfiniBand Compute Power
- 22. Different Vendors across the stack Integrated Tuned Optimized Consolidated Application Platform Layer Compute Layer Storage Layer I/O Layer OS Layer HP Blades HP Storage HP Networking 150+ parts Months from start to finish before its ready for production 1 Engineered System Unpack and ready for production âin one dayâ Building Blocks Engineered versus âcommon stackâ
- 23. 5/19/201723 âą The âMagicâ Switch WebLogic boost
- 24. 5/19/201724 âą WebLogic Exalogic Domain Enhancements âą -Dweblogic.ScatteredReadsEnabled & -Dweblogic.GatheredWritesEnabled âą Better I/O in high network volume environments âą Uses Native IO Socket Channels optimized âą -Dweblogic.replication.enableLazyDeserialization âą Clustered session replication WebLogic boost
- 25. 5/19/201725 WebLogic boost âą # Enable Java Exalogic optimizations EXTRA_JAVA_PROPERTIES="${EXTRA_JAVA_PROPERTIES} -Xlargepages:exitOnFailure=false - Doracle.xdkjava.exalogic.optimization=true -Dweblogic.ScatteredReadsEnabled=true -Dweblogic.GatheredWritesEnabled=true - Dweblogic.replication.enableLazyDeserialization=true " export EXTRA_JAVA_PROPERTIES
- 26. More optimizations âą Optimal use of Infiniband âą Clusters and channels âą Oracle Traffic Director âą SOA Suite and Coherence
- 27. Optimal use of Infiniband âą Because of high speed IB network we could âą Store all persistency in database âą JMS TLogs âą JMS FileStores
- 28. Optimal use of Infiniband
- 29. JDBC GridLink over Infiniband âą jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROT OCOL=tcp)(HOST=<IBVIP>)(PORT=1521))(CONNECT_D ATA=(SERVICE_NAME=<DB Service>))) âą JAVA_OPTIONS="${JAVA_OPTIONS} - Djava.net.preferIPv4Stack=true -Doracle.net.SDP=true" setDomainEnvsetDomainEnv JDBCJDBC
- 31. 5/19/201731
- 32. 5/19/201732
- 33. WebLogic Channels Several channels to define âą WebLogic Admin Channel. âą This is the default channel to be used by the AdminServer. âą Internal network channels for HTTP and T3 (Cluster, Coherence, OTD) âą These channels are used for internal traffic: âą Cluster communication âą Application High Availability and Serialization âą Application caching with Coherence âą External network channels for SOA
- 34. JMS Messaging Optimization âą The way message are temporary stored, compressed and decompressed can be set with these optimizations âą JMS Lockless Request Manager. âą A specific WebLogic JMS MBean must be set for using concurrent messaging for JMS queue
- 35. JMS Messaging Optimization âą The way message are temporary stored, compressed and decompressed can be set with these optimizations âą JMS Lockless Request Manager. âą A specific WebLogic JMS MBean must be set for using concurrent messaging for JMS queue ServerMBean.useConcurrentQueueForRequestManager=true
- 36. SOA and Coherence âą Coherence in JVM or separate coherence cluster âą Coherence cluster needs own JVMs âą Coherence WKA addresses use over Infiniband -Dtangosol.coherence.wka1=(IPoIB adress localhost)-Dtangosol.coherence.wka2=(IPoIB adress1)-Dtangosol.coherence.localhost=(IPoIB adress2)
- 37. SOA and Coherence âą Coherence integrate with SOA Suite: âą Activation of Coherence Adapter
- 38. SOA and Coherence âą Coherence Configurations: âą file adapter- soa- config.xml âą New EIS Adapter
- 40. SOA and Coherence âą Test Coherence Adapter: âą WSDL call a different adapter reference for each operation. âą Put (Put item in cache), âą Get (Get item from cache), âą Remove (Remove item from cache) or âą Query (Query item from cache), âą list â retrieve all the objects in the cache. listKeys â retrieve all the keys of the objects in the cache; âą removeAll â remove all the objects from the cache.
- 41. 5/19/201741
- 42. 5/19/201742
- 43. 5/19/201743
- 44. 5/19/201744
- 45. SOA BPEL and Coherence âą Some specific settings set in JVM for Coherence: EXTRA_JAVA_PROPERTIES="${EXTRA_JAVA_PROPERTIES} -Dsoa.archives.dir=${SOA_ORACLE_HOME}/soa -Dsoa.oracle.home=${SOA_ORACLE_HOME} -Dsoa.instance.home=${DOMAIN_HOME} -Dtangosol.coherence.log=jdk âą Transport optimization -Dtangosol.coherence.transport.reliable=imb - Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl âą Take the database role in committing and rollback -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true
- 46. SOA BPEL and Coherence âą Some specific settings for SOA: âą CacheEnabled=true âą -Dbpel.cache.localStorage=true âą -Dbpel.cache.threadCount=<value> âą -Dbpel.cache.cubeInstance.sizeLimit=<value> âą -Dbpel.cache.invokeMessage.sizeLimit=<value> âą -Dbpel.cache.deliveryMessage.sizeLimit=<value> âą -Dbpel.cache.deliverySubscription.sizeLimit=<value> Note that all settings relate to some form of dehydration
- 47. The benefits âą Minimize database traffic by using coherence cache âą Regulate amount of dehydrations to the database âą Use ZFS storage, high speed with Infiniband âą Besides all the Exalogic benefits, also to be used on non Exalogic hardware
- 48. Any Questions? Letâs keep in touch!! The ACE Community mschildmeijer@qualogy.com https://community.oracle.com/blogs/mnemonic https://www.qualogy.com/nl/techblog/author/michel- schildmeijer
- 49. Any Questions? Letâs keep in touch!! @MNEMONIC01 @Qualogy_news nl.linkedin.com/in/mschldmr