70 likes | 186 Views
ebSOA TC Work on Technical Specifications. Co-Chair George Brown, Intel george.w.brown@intel.com. ebSOA TC Membership. Co-chairs Sally St. Amand George Brown Active members Kathryn Breininger Atilla Elci Kamran Ozair David Webber Goran Zugic, principal contributor of specs.
E N D
ebSOA TCWork onTechnical Specifications Co-Chair George Brown, Intel george.w.brown@intel.com
ebSOA TC Membership • Co-chairs • Sally St. Amand • George Brown • Active members • Kathryn Breininger • Atilla Elci • Kamran Ozair • David Webber • Goran Zugic, principal contributor of specs
ebSOA TC Objectives • Define an eBusiness Service Oriented Architecture Technical Specifications and Best Practices Documents • Describe conducting electronic business within a service oriented architecture from a business perspective with the following intent: • Enable business collaboration through a standards solution • Ensures semantic integration at runtime • Drive convergence of current and evolving ebXML specifications, Web Services specifications and other open standards that support the use of Service Oriented Architectures (SOA).
Research Basis Reconciles BPM with SOA • Activities • Inputs/outputs • Flows • Deliverables • Dependencies • Transactions • Decisions • Contracts • Documents • Interfaces • Security • Messages • Registries • Repositories • Content maps • Services • Events • Agents Patterns or use cases of information exchange Reference models SOA standards BPM FERA • Process characteristics determine what capabilities are required • Human interaction determines the need for portal and collaborative services capabilities • Sign-on, authentication, plug-in services (meetings, calendars, chat, visualization, reporting, etc.) • Process administration determines the need for federation server and gateways • Security, protocols, content exchange formats, meta-data mapping, B2B process standards (RosettaNet, CPFR, …) • Process flow determines the need for event management • Alerts, Escalation, Messaging, Queries, Flow controller • Business logic reconciliation determines the need for agent framework • Synchronous vs. asynchronous reconciliation
Functional Architecture for a SOA Solution Portal Federated System Federated System SOA Federation Federation Server Gateway Gateway Federated User Federated User Agent Framework CP Flow Plug-in Services Plug-in Services Collaborative Services
ebSOA Solution Information Models • Federation Information Model (FIM) – Content and Context • FIM is an informational bridge between the public and private world. • Definition of federate profiles, business process specifications, collaboration protocols and agreements, security policies, etc. Information that supports public processes and documents of any type for both public and private processes. • Agent Interface Information Model defines types of agents, invocation rules and status control. • Collaborative Process Information Model (CPIM) • Supports complete CP context including all possible flows, participants and shared context elements like metrics, rules and joint events • The main CPIM entities are: CP Flows, Roles, Rules, Metrics and Clusters of Events • Collaborative Process Flow Information Model (CPFIM) • Supports definition of the possible flows of activities, decisions and events within the CP • The main CPFIM entities are: Activities, I/O-s, Events, Triggers, Decisions, Sequences, References, etc.
Collaboration Semantics • Collaboration semantics in connection with Information Models provides full dynamic collaboration support • Collaboration semantics formally defines all necessary interfaces with methods/functions required for the collaboration data (Information Models) manipulations and interactions between SOA Federation architectural components • SOA Federation is a central block of the SOA architecture solution with the following components which interfaces and methods/functions are already defined as a part of the ebSOA architectural specification: • Gateway • Portal • Plug-in Services • Security • SOA Federation (Federation Server, Agent Framework, CP Flow Controller and Collaborative Services)