SOA Interest Group
EclipseCon Europe
Ludwigsburg, Germany
29.10.2013
Robert Sauer, Marc Gille
SunGard Infinity
Agenda














Stardust Overview (Marc)
End-to-end Example mit RAD (Marc)
Break
Browser Modeler (Marc)
...
Paradigm

3
Workflow Participants
 Business Aspects

Data Access
 System Integration
Process Activities
 Business Aspects

Service ...
End User Portal
Origin and Approach

6
Origin
 12-year-old, comprehensive BPMS
 CARNOT AG
 Founded in 2000 („Workflow and EAI for J2EE“)
 Acquired by SunGard...
Approach and Status
 SunGard has contributed virtually the entire IPP codebase into
Stardust under EPL.
 Exceptions caus...
Ecosystem

Eclipse Community

SunGard

Contribution

Resources

Contribution
Consumption via
Eclipse Public License (EPL)
...
Access






Homepage: www.eclipse.org/stardust
Wiki: http://wiki.eclipse.org/STP/Stardust
Update Site: http://downlo...
Use Cases

11
Interactive Workflow
Requirements
• Simple configuration of organizational hierarchy including
departments
• Flexible inte...
Document Processing
Requirements
• Document management and retrieval
• Document viewing and editing (TIFF, PDF, HTML)
• Pr...
Data Extraction and Transformation
Requirements
• Receive request for data gathering from multiple systems
• Data retrieva...
Message Processing and Service Orchestration
Integration Requirements
• Connectivity to financial networks
and protocols (...
Event Processing and Client Push

Integration Requirements
• Different incoming market data streams
(e.g. Market Map, Bloo...
Architecture

17
Overall Architecture
Process Modeling
Stardust
Process Portal

Mobile
Client

Business Event

Stardust
Process Engine

Dep...
Orion Integration – Ubiquitous Development
Orion Shell

Stardust Browser Modeler

BPMN/XPDL/Rules
Marshaller/
Unmarshaller...
Contact
 Feel free to contact us at robert.sauer@sungard.com and
marc.gille@sungard.com

20
Upcoming SlideShare
Loading in …5
×

Stardust Overview - Eclipse Con Europe, Ludwigsburg, 10/29/2013

1,508 views

Published on

Presentation of the SOA Interest Group.

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

  • Be the first to like this

No Downloads
Views
Total views
1,508
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
13
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Stardust Overview - Eclipse Con Europe, Ludwigsburg, 10/29/2013

  1. 1. SOA Interest Group EclipseCon Europe Ludwigsburg, Germany 29.10.2013 Robert Sauer, Marc Gille SunGard Infinity
  2. 2. Agenda              Stardust Overview (Marc) End-to-end Example mit RAD (Marc) Break Browser Modeler (Marc) Browser Modeler Plugins (Robert) BPMN/XPDL (Robert) Modeling Concurrency (Robert) Break Stardust on Amazon Web Services (Marc) Reporting (Marc) Rules Processing (Marc) High Throughput/Low Latency Processing (Robert) Mobile Workflow (Marc) 2
  3. 3. Paradigm 3
  4. 4. Workflow Participants  Business Aspects Data Access  System Integration Process Activities  Business Aspects Service Invocation  System Integration 4
  5. 5. End User Portal
  6. 6. Origin and Approach 6
  7. 7. Origin  12-year-old, comprehensive BPMS  CARNOT AG  Founded in 2000 („Workflow and EAI for J2EE“)  Acquired by SunGard in November 2006  All key players still on board – and are Stardust committers  Rebranded CARNOT Process Engine as Infinity Process Platform (IPP).  Used in > 60 (= 75%) of SunGard products.  Production deployments e.g. with  > 10,000 users (Commerzbank, former Dresdner Bank)  > 1,000,000 processes/day (CSS Insurance, Arkelis)  > 300,000 documents/day (VAR Japan)  Ranked #2 in Vision in Gartner MQ for BPMS. 7
  8. 8. Approach and Status  SunGard has contributed virtually the entire IPP codebase into Stardust under EPL.  Exceptions caused by mismatching licenses (e.g. LGPL for Hibernate)  2,3 Mill. lines of code …  Process of IP review and 3rd party approval took Eclipse Legal and us more than a year …  Stardust 1.0 released with Kepler June 2013  Stardust 1.1 to be released shortly  Stardust 1.1.1 to be released with Kepler SR2 (January) 8
  9. 9. Ecosystem Eclipse Community SunGard Contribution Resources Contribution Consumption via Eclipse Public License (EPL) Update on important fixes or enhancements Maintenance Infinity Process Platform Stardust Periodic update e.g. on Eclipse Releases Consumption via SunGard-proprietary commercial license SunGard Customers
  10. 10. Access      Homepage: www.eclipse.org/stardust Wiki: http://wiki.eclipse.org/STP/Stardust Update Site: http://download.eclipse.org/stardust/nightly Git: http://git.eclipse.org/c/?q=stardust Forum: http://www.eclipse.org/forums/index.php?t=thread&frm_id=225  Videos: http://www.eclipse.org/stardust/documentation/training-videos.php  Facebook: https://www.facebook.com/eclipsestardust 10
  11. 11. Use Cases 11
  12. 12. Interactive Workflow Requirements • Simple configuration of organizational hierarchy including departments • Flexible integration user management/SSO • Configurable Portal UI • Large number of parallel users Stardust Stardust Solution • Department concept • LDAP/SAML integration • Flexible Portal mashups • Multiple Portal views • Reporting • Simulation
  13. 13. Document Processing Requirements • Document management and retrieval • Document viewing and editing (TIFF, PDF, HTML) • Process and document binding Stardust Solution • Document Repository • TIFF Viewer and Editor • Servers-side PDF-Viewer • Scan client (WS communication to server) • Document Metadata Modeling • Document security (document, folder, type) Stardust
  14. 14. Data Extraction and Transformation Requirements • Receive request for data gathering from multiple systems • Data retrieval from these systems • Data transformation, normalization and merge • Return data • Possibly high record volume (~ 100.000) Stardust Stardust Solution • Simple message transformations via drag & drop • Complex message transformation with JavaScript • Out-of-the-box connectivity to RDBMS, Files etc. • Well-defined Connector structure to be used for custom connectors • Parallel data gathering via process topology Relational Database
  15. 15. Message Processing and Service Orchestration Integration Requirements • Connectivity to financial networks and protocols (FIX, SWIFT, XML) • Grouping of messages • Correlation of messages (e.g. for cancellation) • Content-based routing • Message multicast • Low(er) latency Stardust e.g. Financial Networks Stardust Solution • FIX and SWIFT connectivity • Message transformation to normalized format • Caching and JMS channeling for sequencing • Routing via transition conditions • Transient processing/write-behind for highest throughput/lowest latency
  16. 16. Event Processing and Client Push Integration Requirements • Different incoming market data streams (e.g. Market Map, Bloomberg, Reuters) • Normalization of content • Client push Stardust e.g. Market Data Streams Stardust Solution • FIX and SWIFT connectivity e.g. market data streams • Correlation of messages arriving in time window via caching • Message transformation to normalized format • Rules for golden copy creation • Client push via publish/subscribe via REST Push and • HTML messaging
  17. 17. Architecture 17
  18. 18. Overall Architecture Process Modeling Stardust Process Portal Mobile Client Business Event Stardust Process Engine Deployment Business Logic 1 (EJB) Business Logic 2 (Spring) Model Repository JDBC JMS HTTP Messaging Audit Trail Database Apache Camel J2EE (Web) Application Server (e.g.Tomcat) Web Service/REST
  19. 19. Orion Integration – Ubiquitous Development Orion Shell Stardust Browser Modeler BPMN/XPDL/Rules Marshaller/ Unmarshaller Document Adapter BPMN/XPDL Rules Software Artefacts Orion File Store BPMN/XPDL Rules Document Repositiory Stardust (Cloud) Runtime
  20. 20. Contact  Feel free to contact us at robert.sauer@sungard.com and marc.gille@sungard.com 20

×