Business Process Modelling ISD3 Lecture 17

Topics The case for long-running processes Application Integration Technology overview Web Services Collaxa BPEL4WS presentation

Purchase Order Processing (1) Ordering a site licence for a Requirements Management package called DOORS from Telelogic DOORS mandated for MOD contracts and the market leader (against Rational’s Requisite Pro) Almost there after 8 weeks of negotiation – who is going to pay, which version, which add-ons, what are the technical requirements, who is responsible for support?

Purchase Order Processing (2) Actors – –Project Leader, Orginator (CW), CEMS IT manager, Budget holder(Dean), CEMS PO, UWE PO, Telelogic Accounts, Telelogic technial Support, CEMS IT Unix Manager, CEMS IT Windows Manager. ~50 interactions. –face-to-face, phone, and paper– no system-to-system communication

Purchase Order Processing (3) Main flow: –CEMS: Complete Official PO form –CEMS: To budget holder for signature –CEMS: To IT manager for technical approval –CEMS: To CEMS PO –CEMS: To UWE PO –UWE: New supplier, so account needs to be created, suppler credentials confirmed To UWE IT manager if above threshold –UWE: PO to supplier –Telelogic: Fulfilment request to Originator for technical details –CEMS: Server details to Telelogic –Telelogic: Account setup and password to CEMS –CEMS: Download and install Informal communications: –Investigate suitability, negotiate to find budget, negotiate price and options, decide on installation configuration, plan training programme

Process issues Long elapsed time High cost of staff time Problems due to transcription errors, misunderstandings Many points of human interaction Complex, long-running process Need to set-up and adapt very quickly – how to interact with Telelogic’s order processing

Application Interaction Single Integrated internal solution – e.g SAP BPM systems such as E-Work B2B integration - Biztalk Loosely integrated Web Services

CompanyProductPurpose Metastorme-workBusiness Process Management tool MicrosoftBiztalkapplication integration via XML ExcelSpreadsheet / graphics MapPointMapping and location web service Outlook FrontPageHTML editor Sharepointenterprise portal server Word 2003XML-based Document editor ExchangeCollaboration tool Business ObjectsCrystal ReportsReport generator SAP business application suite NovellGroupwiseCollaboration tool Visual ScriptVisual XML schema editor MacromediaDreamweaverHTML editor AdobeAcrobat (PDF)Document creation and printing Collaxaapplication integration via XML

Web Services Application provides an interface, e.g. to place an Order, request a Loan XML format messages exchanged between client and application SOAP (Simple Object Access Protocol) standard defines a common message protocol WSDL (Web Service Description Language) – defines the service so that a client can set up a link without programming – what to send, what to expect in return

The SOAP request: POST /InStock HTTP/1.1 Host: Content-Type: application/soap+xml; charset=utf-8 Content-Length: nnn <soap:Envelope xmlns:soap=" soap:encodingStyle=" IBM

SOAP reply HTTP/ OK Content-Type: application/soap; charset=utf-8 Content-Length: nnn <soap:Envelope xmlns:soap=" soap:encodingStyle=" 34.5

Web service orchestration A business process requires the integration of multiple services interacting with multiple partners Business processes described by a process modelling language such as BPEL4WS (Business Process Execution Language for Web Services) enables processes to be enacted by a suitable platform e.g. Collaxa