Student SOA Lab Framework for development and testing

Student SOA Lab Framework for development and testing of information systems Peter Leijten TUe

Contents • SOA • Student SOA Lab ▫ Functionality ▫ Realization IBM Websphere • Use Cases • Demonstration • Summary

Service Oriented Architecture (SOA) • Principles for the architecture of information systems • Architecture consists of service consumers, service providers and a service broker • Service providers handle requests from service consumers ▫ A service provider may also be a service consumer • Service contract specifies the accessibility of a service • Service contract is implemented by an interface • Service Broker ▫ Publication of services ▫ Helps service consumers to find service providers • Separating the how from the what ▫ Implementation is separated from the interface

SOA Example Service 5 Service 2 Service 6 Service 1 Service 3 Service 7 Advantage SOA = Loose Coupling Service 4

SOA Example Service 5 Service 2 Service 6 Service 1 Service 3 Service 8 Loose Coupling: • Easy change Service 4 Service 9

SOA Example Service 11 Service 10 Service 12 Service 8 Loose Coupling: • Easy change • Re-use Service 9

Student SOA Lab Functionality • Students are able to build an information system (SOA) ▫ Custom components ▫ Use of Components off-the-shelf (COTS) ▫ Integration with external services • Instructors must be able to offer students realistic exercises ▫ Definition of a context ▫ Logging through context-components • Instructors must be able to test and gain insight in the systems build by students ▫ Manual/Automated testing

Student SOA Lab – Realization Concept Student-Made System Student SOA Lab Exercise Dependent Part: Exercise Independent Part: • Context components • Generator/Collector • Student-System I/O Logger • Execution Trace Logger IBM Web. Sphere

IBM Websphere • Products • WID • Concepts ▫ ▫ ▫ ▫ ▫ SCA Implementation Technologies BPEL Human Task Interface Common Data Model SDO Adapters Modules CEI

IBM Web. Sphere Products Runtime Stack Web. Sphere Business Services Fabric Web. Sphere Process Server Web. Sphere ESB Web. Sphere Application Server ND Web. Sphere Application Server Composite Business Applications Process Choreography Service Connectivity Advanced Clustering Runtime Foundation Image: courtesy IBM

IBM Websphere Integration Developer • Integrated Development Environment • Provides visual editors for the development of components and the assembly of components • Enables deployment of components

IBM Web. Sphere Service Component Architecture (SCA) Interface: How to call this component Component Uniform Representation of encapsulated Implementation Reference: What this components calls Image: courtesy IBM • Component Model ▫ Interface (sell side) ▫ Reference (buy side) ▫ Implementation (independent of technology) • Realizes part of SOA ▫ Component provides a service through its interface ▫ Component consumes services through a reference ▫ Not: Service broker

IBM Web. Sphere Implementation Technologies • BPEL (Business Process Execution Language) ▫ XML-based language ▫ Business Processes ▫ Orchestration/Choreography • Java • Human tasks • Business rules ▫ Contains rules which are deduced from company policy or legal regulation ▫ Information System has to respect these rules

IBM Web. Sphere BPEL(1) • Work-flow like language ▫ Start / End • Activities: assign, invocation, receive, reply • Structures: while, foreach, choice, parallel activities

IBM Web. Sphere BPEL(2) • Long-running/Microflow • Scopes ▫ ▫ ▫ Sub-process isolation Fault handler Compensation handler (long-running) Event handler (long-running) • Correlation (Long-running) ▫ Find the right instance of a process ▫ Field in the input for identification

IBM Web. Sphere Human Task To-do task Invocation task • Three types of tasks ▫ To-do task (service to human) (visual editor) ▫ Invocation task (human to service) (visual editor) ▫ Collaboration task (human to human) (API) • Two types of collaboration tasks ▫ Subtasks, follow-on tasks • Escalations, three kinds of escalation ▫ Ready, claimed and subtask • Task queue available through Java API

IBM Web. Sphere Interface • Web Service Definition Language (WSDL) • One or more operations • Type of operations ▫ One-way One or more input fields ▫ Request/Response One or more input fields One or more output fields Faults

IBM Web. Sphere Common Data Model Image: courtesy IBM • • XML Schema Definition (XSD) in WID: records Nested complex data-types Inheritance

IBM Web. Sphere Service Data Object (SDO) • Technology that allows heterogeneous data to be accessed in a uniform way • Java library • Use of common data model in Java ▫ Data. Object • Example: Assigning value to field firstname in Data. Object DO: ▫ DO. set. String(“Piet”, customer/firstname);

IBM Web. Sphere Adapters SAP Adapter • Adapters enable integration with other systems and technologies ▫ SAP, Siebel, JD Edwards, Peoplesoft, JDBC, ILOG ▫ Email, file system

IBM Web. Sphere Modules • Modules are used in Web. Sphere to group components and make components available • Consists of one or more components • Components within a module can interact • Components within a module can be made available to systems outside of the module by using export components

IBM Websphere Modules Module A Comp P Module B Import • Protocols available for export Export Comp Q ▫ SCA ▫ Web Service (SOAP/HTTP, SOAP/JMS) ▫ MQ, JMS

IBM Web. Sphere Modules Java Application Human Task BPEL Business Process Business State Machine Business Rules Image: courtesy IBM • All components (e. g. , services, rules, human interactions) are represented consistently and invoked in the same way (SCA) • Best practice for SOA development ▫ Define services ▫ Orchestration of services using BPEL

IBM Web. Sphere Common Event Infrastructure (CEI) • Enables the emitting, storing and retrieving of events • Events can be emitted from different levels ▫ Component ▫ BPEL • Events are stored in a Apache Derby Database • Retrieving of events using a Java API

Student SOA Lab Exercise Independent Part • Generator/Collector ▫ Enables instructor to test a system Automated generation of test-cases Manual input of test-cases Collection of system output • Student-System I/O Logger ▫ Enables logging of input, output and intermediate output • Execution Trace Logger ▫ Retrieves and parses CEI-events

Student SOA Lab Exercise Independent Part Student System Export Import Generator/ Collector Student SOA Lab Execution Trace Logger Student. System I/O Logger JDBC Adapter

Student SOA Lab Exercise Independent Part

Student SOA Lab Exercise dependent part • Context-components (external services) are predefined • Students are required to integrate contextcomponents in their system • Context-components can be used to gain insight in systems ▫ Logging

Student SOA Lab Exercise Dedependent Part Student System Export Student SOA Lab Import Generator/ Collector Context Export Student. System I/O Logger Import Execution Trace Logger JDBC Adapter

Student SOA Lab concept Component A Component B Student-Made System Student-System Init Student SOA Lab Context Component 1 Exercise Dependent Part Stud-Sys I/O Logger Context Component 2 Execution Trace Logger CEI IBM Web. Sphere Apache Derby Generator/ Collector Exercise Independent Part

Use Cases Supply Chain Management System • Customers, Factories, Warehouses, Service Broker • Factories fabricate a certain set of products ▫ The fabrication process might need parts to complete. • Warehouses have inventories which hold products ▫ Warehouses keep their inventories replenished • Service broker provides list of suppliers for a given product

Supply Chain Management System Context Components • Log. Internal. Orders ▫ Log orders between suppliers • Log. Inventory. Changes ▫ Log changes in the inventory of warehouses

Supply Chain Management System Architecture Warehouse Service Router Factory Service Broker

SCM Module

Use Cases Open University System • Student ▫ Must be able to follow courses of his/her choice on the university of his/her choice • University ▫ Must allow students to follow courses (administration) • Bank ▫ Enables payments for external registrations • Teacher ▫ Evaluates examinations for courses from students • Examinations Committee ▫ Evaluates external registrations of students • Course Register ▫ Offers information to students

Open University System Context Components • Central Register ▫ ▫ ▫ ▫ Retrieve students Retrieve universities Retrieve courses Retrieve prior knowledge Retrieve courses offered by a given university Log external registration Log fulfilled payment • Retrieval interactions are logged

Open University System Architecture Course Register Central Register Student Bank University Teacher

OUS Module

Demonstration Testing OUS using Student SOA Lab • Manual testing ▫ Student 1 wants to follow course 10 at university 3 ▫ Student 8 wants to follow course 16 at university 3 • Automatic test generation ▫ ▫ Generate 3 test cases: Student can be student 1 to 10 Course can be course 1 to 20 University can be university 1 to 5

OUS Testing Manual: Student. Group. Name (string) : OUS Student. System. Partner (string) : Student. Partner Operation. Name (string) : student Test. Cases. List. Name (string) : Course. Registration. Data. List Output. Name (string) : output Test. Cases (any. Type) : Course. Registration. Data. List (Course. Registration. Data[]) : Course. Registration. Data. List[0] (Course. Registration. Data) : Student. Id (integer) : 1 Course. Id (integer) : 10 University. Id(Integer) : 3 Course. Registration. Data. List[1] (Course. Registration. Data) : Student. Id (integer) : 8 Course. Id (integer) : 16 University. Id(Integer) : 3

OUS testing Test-case generation: Student. Group. Name (string) Student. System. Partner (string) Operation. Name (string) Name. Type (string) Namespace. Type (string) Test. Case. Amount (integer) Output. Name (string) Test. Case. Data (Field. Data. List) : OUS : Student. Partner : student : Course. Registration. Data : http: //OUSLib : 3 : output :

Questions?