Agenda 1.Implementation of CustomerService

CustomerService wrapper SOAP → ESB internal format Abstract → Concrete XML syntax ESB internal format → HTTP (external service processes the message) HTTP → ESB internal format Concrete → Abstract XML syntax ESB internal format → SOAP Internal representation: XQMessage and JMS message

Progress Sonic ESB Product Family (a part of) Orchestration ESB Messaging queues topics services service types endpoints ESB processes ESB containers BPEL processes Sonic MQ Sonic ESB Sonic BPEL Server

ESB Key Concepts Service Message Endpoint Container Process

ESB Key Concepts Service (“internal service”) deployed piece of code providing business or mediation functionality identified by name, e.g. MyService (or MyApp.MyService) instance of specific service type, e.g. MyServiceType (Service ≈ object, ServiceType ≈ class) custom-built or provided with Sonic ESB: –content-based routing service –XSLT transformation service –file handling services (pickup, drop, split) –split-and-join services

ESB Key Concepts Service (cont’d) A service has following endpoints defined: entry endpoint: for getting input messages exit endpoints: for sending output messages fault endpoint: for sending (recoverable) faults rejected messages endpoint (RME): for sending unprocessable messages (e.g. when service throws an exception) These are set administratively, not hard-coded into service code (although service can send message to any endpoint it wishes to).

ESB Key Concepts Endpoint an abstraction of JMS queue or topic accessible on specific JMS connection identified by name, e.g. Test.MyEndPoint Connection Parameters: URL (e.g. tcp://broker:2507) username & password parameters concerning session pooling Endpoint Parameters: connection QoS (best effort, at least once, exactly once) JMS destination (queue or topic) message priority & time to live...

ESB Key Concepts Message (an in-memory) equivalent of JMS message quite simplified: –contains header and 0 or more parts –header: application-defined and transport (i.e. JMS-) specific data: just like JMS properties and JMS header mixed together –parts: each has its own header and data (arbitrary java object) when receiving/sending through JMS, JMS message is mapped to ESB message and vice versa

ESB Key Concepts ESB Container a place where services live provides all the necessary infrastructure for –loading, starting and stopping services –communicating with JMS broker(s) and external web services –loading necessary resources from Directory Service and caching them –executing ESB processes –ensuring fault tolerance (via backup containers) –logging and auditing services in a container can communicate locally, bypassing the broker default: dev_ESBCore + dev_ESBTest

ESB Key Concepts ESB Process sequence of service invocations defined in an itinerary

Our solution

XSLT & call http service WSDL: published at – ?wsdl –(implemented by assigning a WSDL file to a process) example: InfoPath tracking example: Java example: SOAP client