Welcome. Oracle SOA Suite meets Java The best of both worlds. Guido Schmutz DOAG Konferenz 2013 Nürnberg,

Transcription

1 Welcome Oracle SOA Suite meets Java The best of both worlds Guido Schmutz DOAG Konferenz 2013 Nürnberg, BASEL BERN LAUSANNE ZÜRICH DÜSSELDORF FRANKFURT A.M. FREIBURG I.BR. HAMBURG MÜNCHEN STUTTGART WIEN

2 Unser Unternehmen Trivadis ist führend bei der IT-Beratung, der Systemintegration, dem Solution-Engineering und der Erbringung von IT-Services mit Fokussierung auf und Technologien im D-A-CH-Raum. Unsere Leistungen erbringen wir aus den strategischen Geschäftsfeldern: BETRIEB Trivadis Services übernimmt den korrespondierenden Betrieb Ihrer IT Systeme.

3 Mit über 600 IT- und Fachexperten bei Ihnen vor Ort Hamburg 11 Trivadis Niederlassungen mit über 600 Mitarbeitenden Düsseldorf Frankfurt Stuttgart Freiburg München Basel Bern Zürich Lausanne Wien 200 Service Level Agreements Mehr als 4'000 Trainingsteilnehmer Forschungs- und Entwicklungsbudget: CHF 5.0 / EUR 4 Mio. Finanziell unabhängig und nachhaltig profitabel Erfahrung aus mehr als 1'900 Projekten pro Jahr bei über 800 Kunden 3 3 Stand 12/2012

4 Guido Schmutz Working for Trivadis for more than 16 years Oracle ACE Director for Fusion Middleware and SOA Co-Author of different books Consultant, Trainer Software Architect for Java, Oracle, SOA, EDA, BigData und FastData Member of Trivadis Architecture Board Technology Trivadis More than 20 years of software development experience Contact: guido.schmutz@trivadis.com Blog: Twitter: gschmutz

5 Agenda 1. Introduction 2. How does the Spring component work 3. The use cases 4. Summary

6 SOA Suite 11g Overview BPA Shared BPMN Model BPMN 2.0, BPEL Rich End User Interaction Web based customization Business View Workspace Process Portal (WC spaces) MS Office BPM Studio (with Business and IT views) B2B BPEL BPMN Human Workflow (+AMX, AG, Orgn) Unified Runtime Business Rules Mediator Process Composer Spring BAM Process Analytics Proc Cubes Optimized binding Common JCA-based connectivity infrastructure Oracle Service Bus Policy Manager Repository EM console +BPMN Screens

7 Service Infrastructure SCA Assembly Model Composite - Overarching description of composite service, composed of: Service Entry point to composite Reference Link to services outside of composite Wire Connects references to services Property allow for the configuration of an implementation with externally set data values Component/Implementation Implements business logic or XML processing rules

8 Oracle Mediator for simple service virtualization

9 BPEL / BPMN for implementing (Business) Processes

10 Oracle Business Rules for externalizing business logic

11 Oracle Adapters for accessing external sources DB Adapter (Inbound Mediator Outbound) JMS Adapter (Dequeue Mediator Enqueue)

12 Different strategies for integrating Java in SOA Suite Java Embedding in BPEL Java Callout in Mediator/Oracle Service Bus Custom BPEL/XPATH Functions JAX-WS or JAX-RS Web Services (SOAP / REST services) EJB Services JMS Adapter/Transport and Message Driven Bean (MDB) Custom JCA Adapter or Custom OSB Transport Spring Component When Java meets SOA :

13 Spring SCA Component Spring is a lightweight container using plain old Java objects (POJOs) SCA extends Spring framework capabilities Publish spring beans as SCA component services Provide references to Spring beans wired to services of other components Following types of component integrations are supported Java components to WSDL components WSDL components to Java components Java components to Java components

14 Agenda 1. Introduction 2. How does the Spring component work 3. The use cases 4. Summary

15 Hello World The HelloWorldImpl POJO used inside a Spring component Lessons learnt: Make sure to compile classes before wiring!

16 <sca:service> Element Declares a Spring bean that SCA exposes as a service Takes the following attributes: Name the name of the service (required) Type The fully qualified Java type of the Java class to be exposed as an SCA service (required) Target The bean to be exposed as a service (required)

17 <sca:reference> Element Declares a Spring bean representing an SCA service external to the Spring application context Takes the following attributes: Name The name of the reference (required) Type The fully-qualified Java type of the interface or class representing the remote service (required) Default The target bean for the reference if none is specified (optional)

18 Using the Predefined Beans The following spring beans are predefined in SOA Suite: headerhelperbean for getting an setting header properties instancehelperbean for getting Instance ID of composite and component, name of the Spring service component loggerbean for providing context-aware logging message You can also define your own Spring beans globally => see use case 3

19 Agenda 1. Introduction 2. How does the Spring component work 3. The use cases Case 1 - Configuration 4. Summary

20 Case 1 Configuration: Within SOA Suite Use Case: Need configuration properties which are changeable at runtime Within a SCA Composite preferences can be declared Has to start with bpel.preference Use ora:getpreference('greetingmessage')from within BPEL Restriction: Only scalar values are supported! Can only be accessed from a BPEL component.

21 Case 1 Configuration: Within SOA Suite Values can be changed through System MBean Browser in EM oracle.soa.config > Server : soa_server1 > SCAComposite > your_project > SCAComposite.SCAComponent > your bpel_process

22 Case 1 Configuration: using Spring and JMX

23 Case 1 Configuration: using Spring and JMX

24 Case 1 Configuration: using Spring and JMX

25 Agenda 1. Introduction 2. How does the Spring component work 3. The use cases Case 2 Dynamic Routing 4. Summary

26 Case 2 Dynamic Routing: Using Spring bean for subscription

27 Case 2 Dynamic Routing: Using Spring bean for subscription

28 Case 2 Dynamic Routing: Using Spring bean for subscription

29 Case 2a Dynamic Routing: Using Spring bean for subscription

30 Case 2a Dynamic Routing: Using Spring bean for subscription

31 Agenda 1. Introduction 2. How does the Spring component work 3. The use cases Case 3 Generic Message Handling through JMS 4. Summary

32 Case 3 Generic Message Handling through JMS

33 Case 3 Generic Message Handling through JMS

34 Agenda 1. Introduction 2. How does the Spring component work 3. The use cases Case 4 NoSQL 4. Summary

35 Case 4 NoSQL: What is NoSQL? NoSQL is a new class of databases They don t use the relational data model and thus don t use SQL Tend to be designed to run on cluster Schema-Less - Don t have a fixed schema, allowing to store any data in any record Different types of NoSQL databases Key/value Column Family Document Graph

36 Case 4 NoSQL: MongoDB Integration through Spring

37 Case 4 NoSQL: MongoDB Integration through Spring

38 Case 4 NoSQL: MongoDB Integration through Spring

39 Case 4a NoSQL: MongoDB Logging Bean

40 Case 4a NoSQL: MongoDB Logging Bean Define bean in the global spring context (custom predefined bean) so that logging is globally available 1. Add the bean definition here SOA_HOME/soa/modules/oracle.soa.ext_11.1.1/classes/ springseextension-global-beans.xml 2. Add the corresponding classes in either the lib or classes directory 3. Run the ant script and restart server (more information in readme.txt) The image cannot be displayed. Your computer may not have enough memory to open the image, or the image may have been corrupted. Restart your computer, and then open the file again. If the red x still appears, you may have to delete the image and then insert it again. The image cannot be displayed. Your computer may not have enough memory to open the image, or the image may have been corrupted. Restart your computer, and then open the file again. If the red x still appears, you may have to delete the image and then insert it again.

41 Case 4a NoSQL: MongoDB Logging Bean Usage of the custom bean in the global spring context

42 Agenda 1. Introduction 2. How does the Spring component work 3. The use cases Case 5 Twitter 4. Summary Please follow me on twitter to get the full experience J Twitter User: gschmutz

43 Case 5 Twitter: Send an Update Message

44 Case 5 Twitter: Send an Update Message

45 Case 5 Twitter: Send an Update Message

46 Case 5a - Send a Twitter message with hash tags #doag #springtalk to get the link to the #aoug #springtalk Oracle SOA Suite und Spring ist #doag #doag #springtalk Slides #doag #springtalk das ist wirklich #doag #springtalk a piece of Cool stuff! Das will ich gleich austesten! #doag #springtalk

47 Case 5a Twitter: Process Mentioned Messages and send message with link to slides J

48 Case 5a Twitter: Process Mentioned Messages and send message with link to slides J

49 Agenda 1. Introduction 2. How does the Spring component work 3. The use cases Case 6 4. Summary

50 Case 6: so many more ideas. And not enough time Invoking Spring Batch Invoking Hadoop Processing Groovy Script integration (i.e. XML ó JSON) Read/Write Excel Create PDF Submit to Evernote Message Enrichment (Mediator cannot do that)

51 Agenda 1. Introduction 2. How does the Spring component work 3. The use cases 4. Summary

52 Summary The Spring component is a nice way to extend the functionality of the SOA Suite and the other service engines Use cases for it are endless. Only use the Spring component if no out-of-the-box feature in the SOA Suite exists! Bring your Java people on board.. Make sure to first test the Java and Spring stuff externally!

53 THANK YOU. Trivadis Guido Schmutz BASEL BERN LAUSANNE ZÜRICH DÜSSELDORF FRANKFURT A.M. FREIBURG I.BR. HAMBURG MÜNCHEN STUTTGART WIEN