1. © 2002 Oak Grove Systems – www.oakgrovesystems.com Integrating Workflow with J2EE Applications Best Practices from the Field Charles Ames CEO, Oak Grove Systems chuck@oakgrovesystems.com

2. © 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

3. © 2002 Oak Grove Systems – www.oakgrovesystems.com Sample Space

4. © 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”

5. © 2002 Oak Grove Systems – www.oakgrovesystems.com Scenario: Web Services Orchestration StartActivity Stop Location A Service 1 Application Server Location B Service 2 Application Server Location C Service 3 Application Server

6. © 2002 Oak Grove Systems – www.oakgrovesystems.com Scenario: Processes As Web Services Company Buy It StartActivity Stop Customer Supplier Supply It Application Server Web Services Business Process Management “layer” orchestrates complex business services. CIOs will increasingly focus on optimizing core business processes.

7. © 2002 Oak Grove Systems – www.oakgrovesystems.com Scenario: Virtual Data Platform Database Virtual Database/Repository Process Management Presentation

8. © 2002 Oak Grove Systems – www.oakgrovesystems.com Scenario: Composite Applications Multiple Sources Multiple Transports Personalized Applications Central Point of Orchestration Databases Web Services Applications JMS HTTP Managed View

9. © 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”)

10. © 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.

11. © 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