Paper Purchase Order CERN e Business Web Purchase
Paper Purchase Order CERN e Business –
Web Purchase Request CERN e Business –
Architecture ‘Classical’ 3 -tier ‘Thin’ Web Client Network Intra / Internet 9 i Application Server Oracle Database Workflow CERN e Business –
Common Business Objects - 3 -tier architecture - EJB-like model Java Servlet Person. Home Person find. By. ID Person. Enumeration find. By. Surname Person. Enumeration find. By. String … Person. Service Person. Enumeration find. By. Surname … Object – Relation Mapping Performed by this class CERN e Business – Database
Объекты ввода: пример Text. Input m_General. Descrip String m_General. Descript ion; Person m_Technical. Conta ct; Supplier m_Supplier; Country m_Distrib. Country; Purchase Order CBO Currency m_Currency; CERN e Business – tion; Person. Input ct; Supplier. Input m_Supplier; Country. Input m_Distrib. Country; Purchase Order Servlet. Executor Currency. Input m_Currency;
Объекты ввода: пример Text. Input m_General. Descrip String m_General. Descript ion; Person m_Technical. Conta ct; Supplier m_Supplier; Country m_Distrib. Country; Purchase Order CBO Currency m_Currency; CERN e Business – tion; Person. Input ct; Supplier. Input m_Supplier; Country. Input m_Distrib. Country; Purchase Order Servlet. Executor Currency. Input m_Currency;
Объекты ввода: пример Text. Input m_General. Descrip String m_General. Descript ion; Person m_Technical. Conta ct; Supplier m_Supplier; Country m_Distrib. Country; Purchase Order CBO Currency m_Currency; CERN e Business – tion; Person. Input ct; Supplier. Input m_Supplier; Country. Input m_Distrib. Country; Purchase Order Servlet. Executor Currency. Input m_Currency;
Объекты ввода: пример Text. Input m_General. Descrip String m_General. Descript ion; Person m_Technical. Conta ct; Supplier m_Supplier; Country m_Distrib. Country; Purchase Order CBO Currency m_Currency; CERN e Business – tion; Person. Input ct; Supplier. Input m_Supplier; Country. Input m_Distrib. Country; Purchase Order Servlet. Executor Currency. Input m_Currency;
Example Text. Input m_General. Descrip String m_General. Descript ion; Person m_Technical. Conta ct; Supplier m_Supplier; Country m_Distrib. Country; Purchase Order CBO Currency m_Currency; CERN e Business – tion; Person. Input ct; Supplier. Input m_Supplier; Country. Input m_Distrib. Country; Purchase Order Servlet. Executor Currency. Input m_Currency;
Vi ew Document Executor Document Servlet Stateless CERN e Business – Document Executor Session Business Objects M od el Controller Server Architecture Diagram Business Objects Oracle Database Persistent
Workflow
Skinnable User Interface <aissearchscreen> <head><title>Person Search</title></head> <body> <input type="hidden" name="is. Advanced" value="false"/> <input show="always" type="text" label="Keyword" value="titov"/> <input type="checkbox" label="Fuzzy search" value="No"/> <result> <header> <tablecell>Full Name</tablecell> … </header> <row> <tablecell>Maksym TITOV</tablecell> <tablecell>71169</tablecell> <tablecell>40 -3 -C 08</tablecell> … </row> <tablecell>Oleg TITOV</tablecell> <tablecell>EXT</tablecell> … </row> … <rowcount>4</rowcount> </result> </body> </aissearchscreen> CERN e Business –
Dynamic User Interface Customization CERN Stores Catalog l Data loaded through XML l Data stored in XML l Pure XML-XSLT l 150000 items l +10000 users l Used every second l ~15 -20 K XML for each page l Custom formatting (through XSLT redefinition) CERN e Business –
New Technologies: client side l AJAX (Asynchronous Java. Script and XML) In collaboration with MEPh. I CERN e Business –
Workflow Future: BPEL Business Process Execution Language l XML language for defining behaviour of a process – that provides web-service(s) – that uses web-services – everything it sees is a web-service • no other external interactions CERN e Business – Definition: OASIS
BPEL Process Example CERN e Business –
BPEL Design IDE CERN e Business –
BPEL Deployment Process WSDL Partner WSDL 1 . . . Partner WSDL n CERN e Business – BPEL Scenario <process> <partners> <variables> <sequence> <flow> </sequence> </process> 1. Compile 2. Package 3. Deploy Compiled BPEL Scenario BPEL Runtime Application Server
Core Concepts Long-running interactions (>= 2 parties) l Peer-to-peer synchronous/asynchronous message exchanges l – Request-response – One way (e. g. , notification, reply to ‘callback’ interface) l l l CERN Maintaining state (variables and data access) Data-dependent behavior (conditional and timeout constructs) Exception handling and recovery Compensation (reversal of operations) Cross-partner coordination (message correlation) e Business –
EDH Expansion Documents per Month 220000 18000 16000 14000 12000 10000 Active Users 8000 6000 4000 2000 CERN e Business – 19 93 19 94 19 95 19 96 19 97 19 98 19 99 20 00 20 01 20 02 20 03 20 04 20 05 19 9 2 0
Productivity Gain 70% With EDH 60% 50% 40% 30% Paper (Estimated) 20% 10% 0% 0 CERN e Business – 1 2 3 4 5 6 7 8 Days 9 10 11 12 13 14 >14
For More Information … http: //ais. cern. ch/apps/edh CERN e Business –
- Slides: 30