ActiveVOS Server Architecture. March 2009

Transcription

1 ActiveVOS Server Architecture March 2009

2 Topics ActiveVOS Server Architecture Core Engine, Managers, Expression Languages BPEL4People People Activity WS HT Human Tasks Other Services JMS, REST, POJO,... Web Services Receive and Invoke Admin and Event Handlers Handling MUWS Policy Partner Addressing ActiveVOS BPEL Engine Creation & Task Expression ing Common Utilities: Timer, Work, URN Mapping Queues and Alerts, Exception Activity Managers Directory Services Deployment Plans State Queues Deployment Inbox Web/Application Server Services Administration 2

3 ActiveVOS Architecture Overview Core ActiveVOS Engine 3 Definition, validation and execution WS BPEL 2.0 and BPEL4WS 1.1 compliant BPEL4People Extensible Expression Execution XPath 1.0, XQuery (XPath 2.0), JavaScript,... Server Engine Managers Alarm Manager Cluster Manager Deployment Manager Manager Queue Manager Storage Manager Task Manager Complex Event ing Service framework Policy driven Publishes endpoints which Receive and Reply to callers in conjunction with engine Invokes of endpoints Publishes administrative, WS HT APIs Robust interface allows wide variety of service types. WS, JMS, POJO, REST... Utilities and Other Services Work and Timer Managers URN Mapping Identity Services Services Deployment Handling Administration

4 ActiveVOS Server Other Services JMS, REST, POJO,... Web Services Receive and Invoke Handlers Admin and Event Handling MUWS Policy Partner Addressing ActiveVOS BPEL Engine Creation & Task Expression ing Common Utilities: Timer, Work, URN Mapping Queues and Alerts, Exception Activity Managers Directory Services Deployment Plans State Queues Inbox Web/Application Server 4

5 ActiveVOS Server Other Services JMS, REST, POJO,... Web Services Receive and Invoke Handlers Admin and Event Handling MUWS Policy Partner Addressing ActiveVOS BPEL Engine Creation & Task Expression ing Common Utilities: Timer, Work, URN Mapping Queues and Alerts, Exception Activity Managers Directory Services Deployment Plans State Queues Inbox Web/Application Server 5

6 Core ActiveVOS BPEL Engine Factory creates engine with appropriate configuration Engine Configuration points to managers, expression languages, function extensions and specific processing directives Configuration loaded from an XML file called aeengineconfig.xml by default or can be passed to factory Managers perform operations on behalf of engine Manager Queue Manager Alarm Manager Cluster Manager Storage Manager Task Manager Creates and Manages State saving and restoration Manages Receive Queues and correlations Manages timers for on alarms and waits Manages failover and inter engine facilities Manages interaction with persistent storage Manages human tasks 6

7 BPEL Definitions Installed into the engine via a standardized deployment format (or directly through API) Utilize a visitor pattern on the definition objects for creation of implementation classes Cached as part of overall deployment plan for process Implementations Handle activity execution scheduling and event notifications Are themselves derived from the scope activity Visitors and definitions can be extended for custom activities BPEL4People implementation is an example of a extension 7

8 Activities Activity Implementations are associated with definition objects at construction All activities have a state, and transition through one or more standard states Inactive, Ready to Execute, Executing, Finished, Faulted and Dead Path State changes trigger events which can have registered listeners Activity state is key to depicting proper visualizations of process ActiveVOS consoles and debuggers depict state visually Each activity has an execute method to do the actual execution Activities set object completed state when their work is done, not always when execute is complete (some work can be asynchronous from actual execute e.g. Receive) 8

9 ActiveVOS Server Expression ing Other Services JMS, REST, POJO,... Web Services Receive and Invoke Handlers Admin and Event Handling MUWS Policy Partner Addressing ActiveVOS BPEL Engine Creation & Task Expression ing Common Utilities: Timer, Work, URN Mapping Queues and Alerts, Exception Activity Managers Directory Services Deployment Plans State Queues Inbox Web/Application Server 9

10 Expression ing Engine Configuration allows installation of multiple Expression Languages Expression languages are registered with a namespace, which is used in the BPEL process to designate the language to use Expression languages support both analysis and runtime execution All expression languages can support custom function contexts Registration is by namespace and associates those entries with a function context Once a context is registered it can be used in any BPEL process Built in support for XPath, XQuery and JavaScript XPath is supported via JAXEN XQuery is supported through SAXEN JavaScript is supported through Rhino Also has support for BSF An example is provided for Python 10

11 Example: Custom function integration ActiveVOS BPEL Engine BPEL User defined Custom Functions Evaluate XPATH Expression with Custom Function Expression Language Factory XPATH Language Environment XQUERY Language Environment JAVA SCRIPT Language Environment Expression Evaluation Evaluate Custom Function Custom Function Context BPEL Function Context Function Evaluation Function Context Factory ActiveVOS Engine Runtime Environment Custom Function Evaluation Flow Entity Instantiation 11

12 ActiveVOS Server BPEL4People Other Services JMS, REST, POJO,... Web Services Receive and Invoke Handlers Admin and Event Handling MUWS Policy Partner Addressing ActiveVOS BPEL Engine Creation & Task Expression ing Common Utilities: Timer, Work, URN Mapping Queues and Alerts, Exception Activity Managers Directory Services Deployment Plans State Queues Inbox Web/Application Server 12

13 BPEL4People BPEL4People (B4P) WS BPEL Extension for People Integrates human tasks into BPEL processes Defines a new activity (People Activity) which invokes a WS HT task service Tasks can be defined Locally in the BPEL process Outside of the BPEL process, allowing them to be shared by more than one process Web Services Human Task (WS HT) Integrates human tasks into service oriented applications Human tasks are services implemented by people Specifies a human task schema definition Defines an API for manipulating tasks (task inbox) 13

14 BPEL4People Task Task Environment Performs task state and lifecycle processing (deadlines, escalation) Handles notifications triggered by escalations Lifecycle handling built as BPEL processes Enforces role operations, who can do what and when Uses integrated identity services Providers supplied for LDAP, LDIF and XML Easy addition of custom providers Exposes services layer for interacting with tasks Standard Robust WS HT API Task information contains rendering information provided by developer for generalizing integrations ActiveVOS Inbox uses WS HT API (task list client) 14

15 Built in in Task Inbox Application Inbox Application Web application which uses WS HT for presenting tasks to users Task lists Filters (claimed, started, ) Custom sorting Actions to claim, and start work in list Task Detail Built in complete task detail handling Owners and administrators can claim, start, revoke, forward, complete and fault tasks Attachment and comment support Customizable either whole page or work item via XSL Can be used as a starting point for more complex task inbox WS HT allows for a rich set of rendering capabilities 15

16 ActiveVOS Server Deployment Other Services JMS, REST, POJO,... Web Services Receive and Invoke Handlers Admin and Event Handling MUWS Policy Partner Addressing ActiveVOS BPEL Engine Creation & Task Expression ing Common Utilities: Timer, Work, URN Mapping Queues and Alerts, Exception Activity Managers Directory Services Deployment Plans State Queues Inbox Web/Application Server 16

17 Deployment Business Archive (*.BPR file) Contains processes and process deployment descriptors as well as resources like WSDL, Schema and Style Sheets Deployment Descriptor Describes Partner Role Link Endpoint associations References and policies Static Defined in deployment descriptor Dynamic Invoke Mapped in (i.e. assign to partnerrole) Transmitted in SOAP headers of Partner (WS Addressing) Principal Lookup from Partner Definition based on Authenticated Principal 17 My Role Service information for installing process endpoints Service Name, Allowable Roles, Binding and Policies BPEL4People Logical People Group Assignment Maps logical people groups to users or groups Specific directives Persistence (None, Full, ),suspend on uncaught fault, data indexes,

18 Deployment Multiple deployment interfaces Administrative console page for uploading a BPR Web service for accepting a BPR Directory scanner for looking for new, modified or removed deployments Direct Administrative API call can be used for custom deployment High availability and clustering Application Servers: Red Hat JBoss Enterprise Application Platform 4.3 Red Hat JBoss Enterprise SOA Platform 4.3 Apache Tomcat 5.x BEA WebLogic Server 9.2 Oracle WebLogic 10.3 IBM WebSphere Server 6.1 Database Servers: MySQL 5.x, Oracle Database 10g, Microsoft SQL Server 2005, IBM DB2 8.x, 9.x 18

19 ActiveVOS Server Services and Administration Other Services JMS, REST, POJO,... Web Services Receive and Invoke Handlers Admin and Event Handling MUWS Policy Partner Addressing ActiveVOS BPEL Engine Creation & Task Expression ing Common Utilities: Timer, Work, URN Mapping Queues and Alerts, Exception Activity Managers Directory Services Deployment Plans State Queues Inbox Web/Application Server 19

20 Service Layer Exposes key runtime interfaces ( deployments endpoints ( My Role Administrative API: Engine Admin, MUWS, Event Listeners WS HT API Receive and Invoke Handlers are pluggable Web service support implemented using Axis WS Addressing WS Security WS Reliable Messaging POJO plain old java objects JMS Support REST Support EJB Other Services JMS, REST, POJO,... Policy driven transports and capabilities are driven by policy attachments Web Services ( principal Partner Addressing supports partner lookups (e.g. By Receive and Invoke Handlers Admin and Event Handling MUWS Policy Partner Addressing 20

21 Service Handler Factories ActiveVOS Service Engine Architecture WS Receive Handler JMS Receive Handler REST Receive Handler... Receive Handler ActiveVOS BPEL Engine Inbound Service Request Flow Receive Handler Factory Receive Handler BPEL Outbound Service Invoke Flow Receive and invoke handler factory architecture allows for extensible service framework WS Invoke Handler Invoke Handler POJO Invoke Handler JMS Invoke Handler REST Invoke Handler... Invoke Handler Entity Instantiation Invoke Handler Factory Invocation Handler 21

22 Simplified Request Dispatch Flow Web Service Request Receive Handler Deployment Plan Partner Addressing Fault Lookup Correlated Receive Not Found Create? No Queue Manager Yes New Found Queued Receives Queued Reply Dispatch Receive To And Queue Reply Receive Activity Reply Activity 22

23 Administrative API Allows process maintenance interactions Suspend, Resume, Terminate, State Request, List, etc. Registers process and engine event listeners Interfaces Can also dispatch events to Web services Available directly through engine factory for in process usage Most methods are also exposed via a Web service, which will be the recommended interface OASIS WSDM/MUWS API usage examples Consoling, debugging, external management,... 23

24 Administration Exception Exception Some critical processes can t be allowed to fail because of programming or environmental errors Developers and Administrators need to be able to take corrective action to ensure process success ActiveVOS Exception Allows suspending processes on uncaught faults Configurable at per process level with an engine default Integrates an alerting service so that appropriate actions can be taken Set of robust API for fixing a problem (changing data, retrying activities and scopes, coercing an activity into completing normally) Administrative Consoling for manually fixing a problem Easy filtering of processes in a suspended/faulting state 24

25 Conclusion ActiveVOS is built on a world class architecture and components Robust BPEL engine Utilizes Managers for flexible implementation of surrounding functionality Extensible expression language integration with custom functions BPEL4People extension for standardized workflow Deployment considers many scenarios for binding and process directives Service handling delivers ease of service creation and interfacing Policy driven architecture for proper process governance Rich administrative functionality exception management handles unexpected faults Alerting and monitoring facilitates enterprise management 25