SOA at Dutch Railways

1. Dutch Railways and SOA Jack van Hoof JvH-Y2K+7 v1.0

7. Our Vision

14. Implementation technologies Business logic services ERP Access services Exchange Area Data storage services COTS Home made Legacy Business Process Management Business Activity Monitoring (Complex) Event Processing Web 2.0 clients (web browsers) AJAX mashups Portal with portlets Databases SOA and EDA ESB

17. We go for Web services and ESB By using standard Web services technology everything can be connected with everything Enterprise Service Bus (ESB) is our deployment platform for Web services technology Application level Infrastructure level

18. The application level

20. SBI: focus on monolithic application New Connect monolithic applications (legacy, COTS, ERP) using Web services technology to harmonize different technologies Keywords: Legacy, stove-pipes, packaged software (COTS, ERP) Old Looking for common technologies to communicate e.g: B with C via fileshare on server of A Application B Application C Application A Web Services Application B Application C Application A

22. EDA: focus on event messaging Events Web Services (SOAP) Applications (legacy, SOA’s, workflows, transactions, processes, UI’s, portals, databases, gateways, devices) Keywords: Loose coupling, linking autonomous processes, workflow Publish and consume messages using Web services technology

23. Simple example of EDA (illustrative) ESB Passenger x Train Routing table Gates at stations a, b, c, d Back-end systems SOAP SOAP SOAP SOAP SOAP … buys ticket from A to B via Internet (business event) … Determines stations on route A-D (enrichment) … allow access to passenger x on date y … register transaction Passenger: x Date: y Stations: a, b, c and d Passenger: x Date: y Route: A-D Data- warehouse SOAP … logs data ibo analyses and rapporting 1 2 3 4 5 Concurrent with: Concurrent with:

24. Holistic approach at Dutch Railways Access to old and packaged systems: Service based integration Development of new systems (processes): Service oriented architecture Connecting systems (processes) into chains: Event-driven architecture Not subsequently, but all three concurrently! And all with the same common technology: Web services

26. The infrastructure level - distributed web services platform -

29. Reach of our ESB (future) ESB Stations Trains PDA’s Data Centers Railpockets Gates … Partners Gateway All places where applications are running

30. Appearance of our ESB ESB SAP-FIN Netweaver XI SAP-CRM Netweaver XI SAP-HR Netweaver XI IBM WebSphere (Corporate) BEA WebLogic ESB Partner Gateway Etcetera (future) BizTalk Ddatagateway (MQ-Series) Remaining applications External environment (business partners)

31. ESB: Intelligent layer on the network Messages flowing through ESB safely cross firewalls over HTTP port 80: No connectivity issues anymore! Connectivity Enterprise Service Bus Network Security Reliability Transactions … User-defined Host-config: DHCP Name: DNS Time: SNTP Netwerkmngt: SNMP … Technical infrastructure oriented services Business oriented services

35. Innovation roadmap

38. SOA SOA SOA SOA Event- msg Event- msg Event- msg ERP COTS Legacy Event- msg External Gateway External Systems Event- msg Event- msg SOA, COTS, ERP, legacy and external systems = heterogenous and flexible application landscape with EDA = Heterogenous systems are loosely (asynchronously) coupled via triggering event messages

39. Competence Center of Integration

40. Competence Center of Integration to help Integration process Define message flows (data analyses) Build message flows through ESB Buy/build/deploy adapters/wrappers Buy/build/adapt/decompose business applications Operate/manage message flows through ESB Test and user acceptance CCI CCI advises development teams and delivers specialists (designers/developers) CCI does the work Focus is on message flows

42. FIN

43. Questions?

44. Hidden sheets

46. Loose coupling required Autonomous business function 1 Sub-function 1a Sub-function 1b Sub-function 1e Sub-function 1c Sub-function 1d Autonomous business function 2 Basic principles illustrated Supporting software component 1 (service) Supporting software component 2 (service) Reusable components One-to-one mapping Autonomy Strong cohesion allowed Sub-function 2a Sub-function 2b Sub-function 2e Sub-function 2c Sub-function 2d

47. Event- msg Event- msg Event- msg Business process chain: EDA pub pub pub sub sub sub Command and Control: SOA Data and services reuse domain Data and services reuse domain Data and services reuse domain Data and services reuse domain Final pattern Decoupling borders Loose coupling Asynchronous communication (publish-subscribe) Strong cohesion Synchronous communication (request-reply) Specific per situation “ craftsmanship” of the architect