Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
SCA Composite new Features and Updates
Robert van Mölken, 17-07-2014
SOA Suite 12c Deep-Dive
Composite Updates
2
3
Changed project structure
The structure of the project has changes drastically.
All components are now placed in there o...
4
New designed
Components view
Components and adapters are now logically separated.
It is also possible to display the ite...
5
New designed
Properties view
It displays as it were, all the steps in the wizard or tabs of the dialog
window of a compo...
6
Share artifacts across apps
• Possible to transfer (local) artifacts from a SOA application to the Design-
Time MDS
• Wi...
Kick-start a SOA project
using templates
7
8
SOA Templates
• Using the build-in template support you can kick-start a SCA Composite
or add reusable components
• Ther...
9
SOA Templates
• Project Templates
– Create/load an entire project.
– Accessible at creation of new project, or when it i...
10
SOA Templates
Available Templates
Consume
Templates
Re-use of BPEL code
using Sub-processes
11
12
BPEL Sub-processes
• Sub-processes allow certain business logic to be made reusable
• There are two types; standalone a...
13
BPEL Sub-processes
Details about inline sub-process:
– Group activities that can be re-used in the same BPEL process
– ...
14
BPEL Sub-processes
Details about standalone sub-process:
– It is a fragment of a BPEL process, which includes a set of ...
Updated Mediator Component
15
16
Translate from Native action
• With this action you can transform a CSV/JSON/String element of the
request to XML using...
17
Override Using action
• Override routing rule options using a DVM or Business Rules
• Change the routing rule option dy...
18
New graphical Assign editor
12c Mediator: Assign Values Editor
Other Component Updates
19
20
BPEL 2.0 default specification
In 12c BPEL uses 2.0 specification by default
XQuery support & mapper
• 100% XQuery 1.0 support in SOA Suite Composites
• Dedicated activity to use XQuery for transform...
22
XQuery mapper
XQuery Mapper in JDeveloper
23
Enhanced XSLT Mapper
• Better support for very large and
complex stylesheets
• Multi-template support
(also recursive f...
24
Fault Policy Editor
• Graphical editor for creating Fault policies, Alerts, Actions & Property Sets
• New Default actio...
25
Fault Policy Editor
12c Composite: Fault Policy Editor
26
SOA Composite Testing
More user friendly
Wizard for creating
Testsuites
27
SOA Composite Testing
Define the input message
directly in the wizard ...
... and also define the
expected result
28
Encrypt/Decrypt Personal info
• Protect sensitive data from appearing as clear text in admin consoles
– For example a S...
29
Sensors DT@RT
• Possible the define or change Sensors at runtime: Design Time at Run
Time (DT@RT)
• Functionality is ad...
Enterprise Manager
(SOA-Infra Dashboard)
30
31
EM Startpage
32
Search instances using SOA-
Infra dashboard
33
Deployed Composites
34
Search Instances
35
Sensor Values
36
Search on Sensors
Enterprise Manager
(Composite Dashboard)
37
Composite Dashboard
39
Graphical Composite Definition
40
Shows no instances by default
41
Instance Details
42
Instance Sensor Values
43
Instance Dependencies
44
Instance Flow Trace
SOA Composer
45
SOA Composer Dashboard
47
Composite Diagram
SOA Error Hospital
48
Error Dashboard
50
Recoverable Faults
51
Error Hospital Bulk Recover
52
During attempt count decreases
53
Recovered Faults are green
54
Upcoming SlideShare
Loading in …5
×

SOA_BPM_12c_launch_event_SOA_track_deepdive_scacompositeupdatesandnewfeatures_robertvanmolken

853 views

Published on

Deep dive SCA Composite updates and new features. Presentation during the SOA track of the AMIS SOA and BPM Suite 12c launch event on July 17, 2014

Published in: Engineering
  • Be the first to comment

  • Be the first to like this

SOA_BPM_12c_launch_event_SOA_track_deepdive_scacompositeupdatesandnewfeatures_robertvanmolken

  1. 1. SCA Composite new Features and Updates Robert van Mölken, 17-07-2014 SOA Suite 12c Deep-Dive
  2. 2. Composite Updates 2
  3. 3. 3 Changed project structure The structure of the project has changes drastically. All components are now placed in there own sub folder. • Adapters - Collection of JCA adapter resources • BPEL - Collection of BPEL en SBPEL components • Events - Collection of Event definitions • DVM - Collection of Domain Value Maps • Mediators - Collection of Mediator components • Schemas - Collection of XML Schemas (XSD) • Testsuites - Collection of Composite tests • Transformations - Collection of XSLT transformations • WSDLS - Collection of service contracts The composite.xml carries the name of the SOA project.
  4. 4. 4 New designed Components view Components and adapters are now logically separated. It is also possible to display the items in a list view
  5. 5. 5 New designed Properties view It displays as it were, all the steps in the wizard or tabs of the dialog window of a component activity and possibility to make changes
  6. 6. 6 Share artifacts across apps • Possible to transfer (local) artifacts from a SOA application to the Design- Time MDS • Wizard to share design time artifacts such as WSDLs and Schemas across applications • Updates all the references to the transferred artifacts with MDS URLs on transfer
  7. 7. Kick-start a SOA project using templates 7
  8. 8. 8 SOA Templates • Using the build-in template support you can kick-start a SCA Composite or add reusable components • There are three types of templates – SOA Project, Component and Custom Activity template. • Templates are fully editable – Once you apply them to you SCA Composite or BPEL component it is part of that composite or component • All dependencies (e.g. partnerlinks) are part of the template • Templates are visible if available in the template path – But there is also an import wizard available
  9. 9. 9 SOA Templates • Project Templates – Create/load an entire project. – Accessible at creation of new project, or when it is part of new application. – Example: skeleton project with default adapters and mediators (without wires). • Component Templates – Create/load a component with all his dependencies (resources and components). – Automatically discovered in the Components window (Composite editor) – Example: BPEL process with default invocations to common services. • Custom Activity Templates – Contain variables and activities (assign, invoke, transformation, etc). – Automatically discovered in the Components windows (BPEL Process editor). – Example: Default Fault handling scope
  10. 10. 10 SOA Templates Available Templates Consume Templates
  11. 11. Re-use of BPEL code using Sub-processes 11
  12. 12. 12 BPEL Sub-processes • Sub-processes allow certain business logic to be made reusable • There are two types; standalone and inline – Inline Sub-processes permits access to data (variables) of the parent process – With a standalone Sub-process the data needs to be assigned • Improve performance (faster rendering of only entity in question) and Manageability (modular approach) of BPEL processes 12c Composite: BPEL Standalone Sub-Process
  13. 13. 13 BPEL Sub-processes Details about inline sub-process: – Group activities that can be re-used in the same BPEL process – It is part of the parent BPEL process code and not visible in composite view. – There is a new ‘call’ activity in BPEL to call a sub-process – You can define parameters or use the parent process parameters. – The inline sub-process is visible in the Activities (component) view. – Activities should be part of a scope to be converted to a sub-process. – At run-time, the code of the sub-process is reusable and can be parallel used. Only one copy is stored in the memory, even when it is invoked 20 times.
  14. 14. 14 BPEL Sub-processes Details about standalone sub-process: – It is a fragment of a BPEL process, which includes a set of activities that can be reused by other BPEL processes. – A standalone sub-process has no interface, and can only be called by another BPEL process, but may have partnerlinks. – In the composite view, the wire to a sub-process is shown as a dotted line, in order to indicate that there is no interface. – The ‘call’ activity is used to call standalone sub-processes. – In the first release of 12c, sub-process can not be called from outside its own Composite, but it may change in the future. – Sub-processes are visible in the component view to make them easy to drag into a BPEL process.
  15. 15. Updated Mediator Component 15
  16. 16. 16 Translate from Native action • With this action you can transform a CSV/JSON/String element of the request to XML using a NXSD transformation. • Transformed output can be used in the routing rules of the Mediator • Action can be done on operation level and on a specific routing rule
  17. 17. 17 Override Using action • Override routing rule options using a DVM or Business Rules • Change the routing rule option dynamically based on a request element • With the key value you have the possibility to override: – XSLT transformation file – Filter expression – Execution Type – Syntax Validation – Semantic Validation • Reduces the creation a bunch of static routing rules
  18. 18. 18 New graphical Assign editor 12c Mediator: Assign Values Editor
  19. 19. Other Component Updates 19
  20. 20. 20 BPEL 2.0 default specification In 12c BPEL uses 2.0 specification by default
  21. 21. XQuery support & mapper • 100% XQuery 1.0 support in SOA Suite Composites • Dedicated activity to use XQuery for transformations (BPEL) • XQuery mapper with support for XPath 2.0 and user defined functions • User friendly and made consistent with the XSLT mapper interface • Integrated Test framework (Run Xquery) • Build for reuse in both SOA & Service Bus
  22. 22. 22 XQuery mapper XQuery Mapper in JDeveloper
  23. 23. 23 Enhanced XSLT Mapper • Better support for very large and complex stylesheets • Multi-template support (also recursive functions) • Source & target structures from sample XML • XSLT execution sequence • Testing capabilities
  24. 24. 24 Fault Policy Editor • Graphical editor for creating Fault policies, Alerts, Actions & Property Sets • New Default actions for invoking a WS and enqueue data (JMS). • Alerts can be defined to send fault to JMS, Email or Log file. • Alerts can be assigned to actions if type of Alert is desired to be triggered. • Fault Policies can be coupled, using the Composite Binding dialog, to different levels: – Composite – Component – Reference binding – Service binding
  25. 25. 25 Fault Policy Editor 12c Composite: Fault Policy Editor
  26. 26. 26 SOA Composite Testing More user friendly Wizard for creating Testsuites
  27. 27. 27 SOA Composite Testing Define the input message directly in the wizard ... ... and also define the expected result
  28. 28. 28 Encrypt/Decrypt Personal info • Protect sensitive data from appearing as clear text in admin consoles – For example a Social Security Number or Credit card Number • Encrypt/Decrypt specific fields in messages • Available in SOA and Service Bus
  29. 29. 29 Sensors DT@RT • Possible the define or change Sensors at runtime: Design Time at Run Time (DT@RT) • Functionality is added to the existing ‘SOA Composer’ application SOA Composer 12c: Sensor Values
  30. 30. Enterprise Manager (SOA-Infra Dashboard) 30
  31. 31. 31 EM Startpage
  32. 32. 32 Search instances using SOA- Infra dashboard
  33. 33. 33 Deployed Composites
  34. 34. 34 Search Instances
  35. 35. 35 Sensor Values
  36. 36. 36 Search on Sensors
  37. 37. Enterprise Manager (Composite Dashboard) 37
  38. 38. Composite Dashboard
  39. 39. 39 Graphical Composite Definition
  40. 40. 40 Shows no instances by default
  41. 41. 41 Instance Details
  42. 42. 42 Instance Sensor Values
  43. 43. 43 Instance Dependencies
  44. 44. 44 Instance Flow Trace
  45. 45. SOA Composer 45
  46. 46. SOA Composer Dashboard
  47. 47. 47 Composite Diagram
  48. 48. SOA Error Hospital 48
  49. 49. Error Dashboard
  50. 50. 50 Recoverable Faults
  51. 51. 51 Error Hospital Bulk Recover
  52. 52. 52 During attempt count decreases
  53. 53. 53 Recovered Faults are green
  54. 54. 54

×