SOA_BPM_12c_launch_event_SOA_track_Servicebus12c_newfeatures_lucas_jellema

870 views

Published on

Servicebus 12c new feature summary. Presentation by Lucas Jellema during the SOA track of the AMIS SOA and BPM Suite 12c launch event on July 17, 2014

Published in: Engineering
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
870
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
18
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

SOA_BPM_12c_launch_event_SOA_track_Servicebus12c_newfeatures_lucas_jellema

  1. 1. Service Bus new Features and Updates Lucas Jellema, 17-07-2014 SOA Suite 12c Deep-Dive
  2. 2. Overview • Service Bus integration into ‘the rest of SOA Suite’ • Demonstration of – Design Time MDS – JCA (File) Adapter in JDeveloper/SB – Pipeline – Disable/Enable Activities – Run (&Debug) Pipeline from IDE – XSLT Mapper in SB development – Native Format Translation (JSON => XML) – Proxy Service (new style) fronting the Pipeline – Enterprise Manager FMW Control – Pipeline Alerts & Message Reports – Pipeline Template – Chained Pipeline – Service Bus Console – configuration, test, development – Second Proxy on top of same Pipeline Chain – REST-ful interface (JSON speaking)
  3. 3. OSB => SB • OSB rest in peace • Service Bus integrated into – JDeveloper (design time) – Enterprise Manager FMW Control (run time) – Also: run time Service Bus Console for configuration & development • Service Bus not [yet] integrated in many areas – Does not support SCA, Fault Policies, EDN, Composite Sensors, (detailed) Flow Trace, run time MDS, SCA Composite deployment plan • Full support for XSLT (Mapper), JCA Adapters, Domain Value Maps, Xref functions • Use EM FMW Control for monitoring Message Reports & SLA/Pipeline Alerts • Share custom XPath functions • Note: calling SB from SCA and vice versa: – Preferred is HTTP; use SOA-DIRECT [only] to propagate transaction or security
  4. 4. Objective • Implement a Service that returns the allowable values in a domain – Through both a SOAP/XML and a REST/JSON interface • The source is a document (domains_repositories.txt):
  5. 5. 5 DomainValuesPipeline
  6. 6. 6

×