A Beginners Guide to Building a RAG App Using Open Source Milvus
WebLogic Developer Webcast 3 : Spring and JAX Message Driven and Web Services
1.
2. JMS + Web Services w/ JAX and Spring Jeffrey West, Pyounguk Cho, Dave Cabelus WebLogic Product Management
3. <Insert Picture Here> Program Agenda Web Services WebLogic Web Services Overview Spring WS Build (Code walkthrough, Demo) Spring WS Limitations JAX-WS Build (Code walkthrough, Demo) JAX-WS Benefits JMS WebLogic JMS Overview and New Features Spring MDP Build (Code Walkthrough, demo) Spring MDP Limitations vs. MDB Benefits Java MDB Build (Code Walkthrough)
122. JMS Event-Driven SOA EnhancementsWebLogic 10.3.4 – Partitioned Distributed Topics, Shared Subscriptions, APIs, MDB Enhancements Messages published to Distributed Topic load-balanced among members 3 2 1 Enables architectural flexibility Scale the messaging infrastructure to adapt to growing traffic needs Send/pub side has no knowledge/dependency on the receive/subscribe side Messages load balanced, not duplicated MDB enhancements to handle subscriptions Subscribe to the Distributed Topic, not the individual member Improved performance and scalability Aligned MDB and Topic clustered deployment Cluster Server 1 Server 2 Server 3 Distributed Topic DT Member 1 DT Member 2 DT Member 3 Subscription Subscription Subscription MDB MDB MDB
123. JMS Event-Driven SOA EnhancementsWebLogic 10.3.4 – Partitioned Distributed TopicsRemote Cluster Case Publish Cluster 1 Distributed Topic Parallelism for performance and scalability Architectural flexibility Adaptability No dependency on architecture from either publish or subscribe side Simplified configuration DT Member 1 DT Member 2 DT Member 3 1 2 3 5 4 7 1 2 3 4 5 6 7 8 9 9 6 8 Shared Sub Shared Sub Shared Sub Cluster 2 Server 1 Server 2 Server 3 MDB MDB MDB
124. Limitations of MDPs Primary concern – MDPs are not cluster-aware No support for automatic subscription handling No support for HA/migration No real automatic handling of cluster topology changes, esp remote Other limitations: Security model differences Foreign TX management limitations No automatic resource pooling Distributed topic subscription work-around: Use foreign JMS to map a common local JNDI name to the DT member name Additional benefits: automatic resource pooling
125. MDB Benefits Easier to write – use annotations instead of descriptors and resource wiring through beans in applicationContext.xml Container handles the details: MDB manager created wherever destination resides Simplified subscription handling – container creates necessary subscriptions Adapts to cluster topology changes Shared security model, common transaction manager, automatic resource pooling
Architectural flexibilityBreak the architectural tight couplingAdd “message generators” at willAdd “message receivers”/integrated systems at willScale the messaging infrastructure to adapt to growing traffic needsEvent-driven SOAPublish events, subscribers listen for eventsSend/publish side has no knowledge or dependency on the receive/subscribe sideFire and forgetNew policy to turn off message forwardingMessages load balanced, not duplicatedMDB subscribes to the Distributed Topic, not the individual member Improved performance and scalabilityAligned with Distributed QueuesAlign MDB and Topic clustered deployment
Parallelism for performance and scalabilityArchitectural flexibilityAdaptability, no dependency on architectureSimplified configuration
