© 2002 Oak Grove Systems – Integrating Workflow with J2EE Applications Best Practices from the...
-
Upload
valentine-adams -
Category
Documents
-
view
212 -
download
0
Transcript of © 2002 Oak Grove Systems – Integrating Workflow with J2EE Applications Best Practices from the...
© 2002 Oak Grove Systems – www.oakgrovesystems.com
Integrating Workflow with J2EE Applications
Best Practices from the Field
Charles AmesCEO, Oak Grove Systems
© 2002 Oak Grove Systems – www.oakgrovesystems.com
Overview• Agenda
– Assumptions – “World View”– Scenarios – Situations– Problems – What are the key issues?– Solutions – How have those been addressed?
• Format– Introduction– Mini-Panel
© 2002 Oak Grove Systems – www.oakgrovesystems.com
Sample Space
© 2002 Oak Grove Systems – www.oakgrovesystems.com
Assumptions
• Objective: Hyper-efficiency
• Mission: Eliminate “friction” resulting from intellectual decay.
• Strategy: Automate “management”.
• Tactics: Web Services + Workflow = Enterprise Orchestration
“Programming the Enterprise”
© 2002 Oak Grove Systems – www.oakgrovesystems.com
Scenario: Web Services Orchestration
Start Activity
Activity Stop
Location A
Service 1
Application Server
Location B
Service 2
Application Server
Location C
Service 3
Application Server
© 2002 Oak Grove Systems – www.oakgrovesystems.com
Scenario: Processes As Web Services
Company
Buy It
Start Activity
Activity StopCustomer
Supplier
Supply It
Application Server
Application Server
Application Server
Web Services
Business Process Management “layer” orchestrates complex business services.
CIOs will increasingly focus on optimizing
core business processes.
© 2002 Oak Grove Systems – www.oakgrovesystems.com
Scenario: Virtual Data Platform
Database Database Database
Virtual Database/Repository
Process Management
Presentation
© 2002 Oak Grove Systems – www.oakgrovesystems.com
Scenario: Composite Applications
Multiple Sources
Multiple Transports
PersonalizedApplications
Central Point of
OrchestrationDatabases
Web Services
Applications
JMS
HTTP
Managed View
© 2002 Oak Grove Systems – www.oakgrovesystems.com
Key Issues
• Common User/Permission Management• Locating intersection of process,
application, & data• Architecture supports recombination at the
logic level (approach to modularity).• Recognize “true” process
– (example: override)
• Modular processes (“Flowlets”)
© 2002 Oak Grove Systems – www.oakgrovesystems.com
Solutions• Use external, multi-source resolver for
user management; encapsulate permissions with each app module.
• Application context.
• Exposed services should be self contained.
• View “workflow” as a logic abstraction layer.
© 2002 Oak Grove Systems – www.oakgrovesystems.com
Panel• David Noble
– Chief Architect, Reactor 5, Oak Grove Systems
• Winston Damarillo– CEO, Gluecode Software
• Charles Ames– CEO, Oak Grove Systems