WebSphere Message Broker V7.0

IBM Software GroupWebSphere Message Broker V7.0© 2012 IBM Corporation

IBM Software GroupWebSphere Message Broker HistoryWebSphere Message Broker V7.0Nov 2009MQSeries Integrator V2.0Mar 2000WebSphere MQ Integrator V2.1Dec 2001WebSphere Message Broker V6.1Nov 2007WebSphere Message Broker V6.0Sep 2005WebSphere Business Integration Message Broker V5.0May 2003IBM MQSeries® Integrator V1Feb 1999© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 2

IBM Software GroupHow to Reduce Complexity with an ESB{Name, Stock, Quantity, Price, Date}Gordon Gekko,ABC Toys,42,1.50,060508WebSphere Message BrokerGordon Gekko#ABC Toys#42#1,05#050608© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 3

IBM Software GroupCharacteristics Of An Effective Enterprise Service BusFailureInput Server Application 1TransformServer Application 2Transformation Multi-ProtocolsContent BasedRoutingDatabaseManagementSystem (DBMS)IntegrationFully TransactionalEffective, PowerfulToolingSimpleExtensibleStandards basedNon-Invasive© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 4

IBM Software GroupWebSphere Message Broker – The Basics● Flexible, High Function, Production Strength ESB Engine● Routes, Transforms, Augments Messages● Excellent, Well Integrated Database Support● Supports Point-To-Point And Event Processing Messaging Styles● Supported On A Wide Variety Of Hardware Platforms● Provides support for multiple protocols, as well as conversion between those protocols, includingWebSphere MQ, HTTP(s), Files, FTP(SFTP), Web Services, Java Message Service (JMS)integrated WebSphere Adapter support for popular enterprise information systems (EIS), TCP/IPSocketsApplicationQueuesApplicationDatabasesRequest in(message, file,TCP sockets,Web service, etc)MessageBrokerRequest out(message, file, TCPsockets, Web service,etc)© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 5

IBM Software GroupThe Big PictureDevelopersRun-timeBrokerExternalRepositoryWorkspaceWorkspaceBrokerAdministratorsBroker© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 6

IBM Software GroupThe WebSphere Message Broker Toolkit● The GUI used for all ESB development tasks● Eclipse based● Provides various “perspectives” for different tasks to beperformedMessage Flow Developer PerspectiveDebug PerspectiveJava Perspectiveetc…● Let’s take a look at it…….© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 7

IBM Software GroupThe WebSphere Message Broker Explorer● The GUI used for ESB administration tasksJava and Command-line administration interfaces also available● Eclipse basedShipped as Plug-in for WebSphere MQ ExplorerEnables unified administration of both WebSphere Message Broker andWebSphere MQ● All local brokers shown automaticallyCan also be used to connect to and manage remote broker instancesBrokers can be grouped into “Sets”● Provides visual status indicators● Supersedes SupportPac IS02● Let’s take a look at it…….© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 8

IBM Software GroupMessage Flows● Sequence of processing steps to transform/route a message as it passes through aBroker● Composed of individual nodes that are “wired” together● Are transactional● Are reusable● Are built in a sophisticated, easy to use GUIWebSphereMessage BrokerDatabasesMessageInMessageOutC 123 BUY IBM 5 X A123_02 PURCHASE 5 IBM© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 9

IBM Software GroupMessage Flow Editor© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 10

IBM Software GroupMessage Processing NodesinputconnectornodefailureterminaloutputconnectorsinputmessageinputterminalActionoutputterminalsoutputmessage© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 11

IBM Software GroupDeployment: The Details● The various artifacts we have developed must be grouped together fordeployment● A Broker Archive (BAR) file is used for this purpose● The .bar file is created, populated and then deployed to the desired Brokerinstance● The WebSphere Message Broker Toolkit (or WebSphere Message BrokerExplorer) passes this deployment request to the targeted Broker instanceMsgFlowProject.barfileDeployBroker© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 12

IBM Software GroupDefining Messages To WebSphere Message Broker01 ACCOUNT.05 PROGNAME PIC X(8) VALUE 'ESBBRID'.05 ACCOUNT-NUMBER PIC X(10).05 CUSTOMER-NAME PIC X(10).05 CUSTOMER-APPLICATION.10 APPLICATION-DATE PIC X(10).10 CONTACT-NAME PIC X(30).10 STREET PIC X(30) OCCURS 2 TIMES.10 CITY PIC X(20).10 ST-CODE PIC X(20).10 COUNTRY PIC X(20).10 POSTALCODE PIC X(10).10 CONTACT-PHONE PIC X(18).10 AMOUNT PIC S9(9) USAGE COMP.10 COMMENTS PIC X(50) VALUE ' '.10 DECISION PIC X VALUE 'Y'.88 APPROVED VALUE 'Y'.88 REJECTED VALUE 'N'.Dictionary© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 13

IBM Software GroupExample data representationsclass Address{public String street;public String city;public String state;public int zip;}01 ADDRESS.02 STREET PIC X(40).02 CITY PIC X(40).02 STATE PIC X(20).02 ZIP PIC 9(5).struct Address{char street[40];char city[40];char state[20];int zip;}© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 14

IBM Software GroupExample data representationsAddressclass Address{public String street;public String city;public String state;public int zip;}01 ADDRESS.02 STREET PIC X(40).02 CITY PIC X(40).02 STATE PIC X(20).02 ZIP PIC 9(5).struct Address{char street[40];char city[40];char state[20];int zip;}Street City State Zip© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 15

IBM Software GroupThe Logical Message ModelPhysicalJohnSmithGraphics Card3220007/11/08LogicalOrderName Item Qty Price DateString Integer Integer DateJohn,Smith,Graphics Card,32,200,07/11/08John Smith............Graphics Card.........3220020071108.........FirstStringLastString© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 16

IBM Software GroupThe Logical Message Tree - ExampleRootPathsRoot.XMLNSC.Money.CurrencyRoot.XMLNSC.Money.AmountProperties MQMD XMLNSCXML MessageUSD5000.00MoneyCurrencyAmountUSD ‘5000.00’© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 18

IBM Software GroupWebSphere Message Broker Overview – flows, nodes,message treeParserassociated withbit-streamParser invoked(on demand)bit-stream treeParser invoked(in reverse)tree bit-streamInput node readsbit-streamNode accesses logicalmessage treeOutput node writesbit-streamInput Java Compute Output© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 19

IBM Software GroupCreating Message ModelsC HeaderCOBOLCopybook WSDLPre-builtXMLSchemaDTDEnterpriseInformationSystem(SAP, Siebel,PeopleSoft)SOAP, MIME,CSV, IDOC,SWIFT,EDIFACT, X12,FIX, HL7,etcDefineyour ownusing theEclipse-basedToolingWebSphereTransformationExtenderFile ImportDiscoveryMessage SetType treeParsersWebSphere Message Broker© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 20

IBM Software GroupRelationship of Message Set Projects/ SetsA Message Set Project contains one Message SetA Message Set can contain multiple Message Definition FilesA Message Definition File contains the information required to parse a particular message© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 21

IBM Software GroupWeb Services© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 22

IBM Software GroupSOAP, WSDL and Web Services – A Quick Review● A Web service is a remotely accessible piece of softwareTypically implies a SOAP message format and HTTP transportWebSphere Message Broker also supports WebSphere MQ & JMS as a transport● SOAP defines a common envelope to wrap payload dataA top-level with and optional sections● WSDL (Web Services Description Language) defines a Web serviceWSDL defines the message format, transport/binding and service endpoint(s)A Web services provider advertises a Web service using WSDL● SOAP and WSDL standards are published by the W3CSOAP and WSDL are further qualified by the WS-I Basic Profile© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOA Intro 23

IBM Software GroupExample SOAP Message…HeaderEnvelope…Body© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOA Intro 24

IBM Software GroupWebSphere Message Broker Web Services Overview● Message Flows can be exposed as Web Services● Message Flows can invoke Web Services● WSDL can be generated from a Message Set with NameSpaces● WSDL can be imported to create any required Message Sets● WSDL can be used with a wizardWill automatically generate many artifacts that will be used in a messageflow that supports Web Services© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOA Intro 25

IBM Software GroupWeb Services: Putting it all togetherInput Message Format(Web Service request)WS ClientReply Message Format(Web Service reply)SOAPInputNodeSOAPRequestNodeSOAPReplyNodeRequest Message Format(Web Service request)Response Message Format(Web Service reply)HTTP)Web ServiceProvider© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOA Intro 26

IBM Software GroupSOAPExtract and SOAPEnvelope nodes● The SOAPExtract node allows the user to conveniently work on the payload ofthe SOAP body.The context, headers and any attachments are removed and stored in theLocalEnvironment for possible later useThese are automatically picked up and restored when a SOAPReply node isencountered in the flowEnvelopeLocalEnvironmentBodyXMLNSCNodes● The SOAPEnvelope node can be used to insert SOAP headers into a non-SOAP message© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOA Intro 27

IBM Software GroupAdapters© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 28

IBM Software GroupWebSphere Message Broker EIS Adapter Support● WebSphere Message Broker supports native, bi-directional interaction with majorEIS systems: SAP Siebel PeopleSoft● Based on WebSphere Adapters technology© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOA Intro 29

IBM Software GroupImplementation● A set of input and request nodes PeopleSoftInput, PeopleSoftRequest SAPInput, SAPRequest, SAPReply SiebelInput, SiebelRequest TwineBallInput, TwineBallRequest● A wizard to discover business objectinformation from these systems and generateconnection definitions© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOA Intro 30

IBM Software GroupRouting© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 31

IBM Software GroupMessage Routing● One of the core strengths of WebSphere Message Broker is content based routing –the ability to dynamically make a routing decision based on the actual data in aparticular message passing through the Flow at that instant● There are many ways to do Routing in a FlowRoute nodeDatabaseRoute nodeFilter nodeCompute nodeJavaCompute nodePHPCompute nodeDestination ListPublication nodeRoute To Label© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOA Intro 32

IBM Software GroupXPath AddressingRootCustomerInfocustomerAccountNumbercustomerNamecustomerApplicationapplicationDatecontactFirstNamecontactLastNamecustomerAddress1customerAddress2customerCitycustomerStatecustomerCountrycustomerPostalCodecontactPhoneNumberrequestAccountAmountapplicationDecisioncomment●●●●Given an XML tree structure: Path separator is a forward slash (/) Absolute path from the root starts with a / Double period (..) means the parent of the current node Single period (.) means the current node @ means an attributeWildcards * Matches any element node (not attributes or text) node() Matches any node of any kind @* Matches any attribute nodeExtended Addressing // Allows match at multiple levelsExamples /CustomerInfo/customerApplication ./contactFirstName /CustomerInfo//comment© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOA Intro 33

IBM Software GroupTransport Headers© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 34

IBM Software GroupThe Transport Header Nodes●●●●A set of nodes that can be used to manipulate the headers in a messageNodes supplied for three protocols WebSphere MQ – MQHeader Processes MQMD, MQDLH JMS – JMSHeader Processes Header properties and User (application) properties HTTP - HTTPHeader Processes HTTPInput, HTTPReply, HTTPRequest, HTTPResponseEach node can perform the following functions Insert a header Remove a header Modify an existing header Pass a header through unmodifiedThis work is done without the need to write code By selecting options via check boxes References to elements in a message tree done via XPath expressions© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOA Intro 35

IBM Software GroupMessage Transformation© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 36

IBM Software GroupNow We Have A Message – Let’s Transform ItMessage InMessage Out© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOA Intro 37

IBM Software GroupWebSphere Message Broker Message Transformation Tools● How you can convert from one messageformat to another●●Graphical, easy touseDrag and Dropfields, applyfunctions●●Convert XML toanythingUses standard XSLStyle sheets●●Describe powerfultransformationsquicklyUses SQL-basedlanguage (ESQL)●●Uses JavaprogramminglanguageAbility to use XPath●●Uses PHP dynamicscripting languageWindows only today●Run a WebSphereTransformationExtender map© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOA Intro 38

IBM Software GroupMappings – A Simplified ViewBuilding an output message from an input messageInput Message (Source)CustomerFirst_NameLast_NameAddressStreetCityStateZIP_CodeTran_DateCostCC_NoOutput Message (Target)CustomerNameStreetCitySt_CodeZIPDatePriceCreditCard© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOA Intro 39

IBM Software GroupMapping NodeSourceTargetGeneratedMappings© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOA Intro 40

IBM Software GroupFile support© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 41

IBM Software GroupFile Support - Overview● WebSphere Message Broker provides a native, function richset of options for processing filesWell thought out, flexible, easily configured● FileInput node reads files from the local file system or anFTP server● FileOutput node writes files to the local file system or anFTP server● SFTP is supported for secure file transfer● Focus on message processing rather than message deliveryUse WebSphere MQ File Transfer Edition for bulk movement offiles● Supported on all broker platforms© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOA Intro 42

IBM Software GroupFileInput node – Basic algorithm [1]● Scans a pre-configured directory forfiles that match a given specification● Locked files are ignored until theybecome unlocked/homemattmessagesF1.txt F2.xml F3.txtFor example:Input directory: /home/matt/messagesFile name or pattern: *.txt© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOA Intro 43

IBM Software GroupFileInput node – Basic algorithm [2]● Upon successful processing, file iseither deleted or moved to anmqsiarchive subdirectory● Dealing with files with duplicatenames:Option to include timestamp in archivedfilenameOption to replace any existing file/homemattmessagesmqsiarchiveF2.xmlF1.txtF3.txt© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOA Intro 44

IBM Software GroupFileInput node – Basic algorithm [3]● Once the directory is parsed, the algorithm repeats● If no files are found during the directory scan, the node waits for aconfigurable amount of time before trying again© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOA Intro 45

IBM Software GroupRecord detection● The FileInput node can split each file up into separate records, whichcauses the message flow to be invoked multiple times● Handling options (on the Records and Elements tab):Whole fileFixed LengthDelimitedParsed Record Sequence● Only requires one record to be in memory at any one timeAllows very large files to be streamed efficientlyStreaming possible with MRM (CWF and TDS) and XMLNSC parsers only© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOA Intro 46

IBM Software GroupFileInput node – using FTP● When active, FTP settings cause the node to periodically transfer files on aremote server to the local directory for input.● Security Identity ‘UserMapping’ set using runtime command:mqsisetdbparms BROKER –n UserMapping –u ftp:USER –p PASS© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOA Intro 47

IBM Software GroupFileOutput – Basic Algorithm● In the simplest scenario, the received message body is written to thepre-configured file● The destination directory and file name can be set dynamically in theflow© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOA Intro 48

IBM Software GroupFileOutput - FTP Support● If enabled, whenever a complete file is closed an FTP transfer of the file isattempted to the supplied FTP server● File is optionally deleted from the local file system when the transfercompletes● Transfer is synchronousUse additional instances if throughput rate is an issue© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOA Intro 49

IBM Software GroupMonitoring© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 50

IBM Software GroupWebSphere Message Broker Monitoring● A message flow can be configured to emit events through Monitor Properties on each node Events are available for transaction start, transaction end, transaction rollback for Input nodes Events are available for a message passing into or out of any terminal on any node Each event must be manually added – then they can be enabled or disabled. The entire message or selected fields can be included in the event Even though events are defined and enabled they will not be produced unless monitoring has beenactivated for the message flow Events are published to a WebSphere MQ topic Any subscribed application will receive the events© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOA Intro 51

IBM Software GroupSystem Architecture & Scalability© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 52

WorkspaceClientAppl ApplMessageAdminBrokersApplToolkitExternal RepositorySourceIBM Software GroupMessagesBrokerSystem ArchitectureMessage FlowsMessage DictionariesManagement MessagesMonitoring ProfilesXML SchemasPolicy SetsController Message Flow HTTP ListenerInputFilterExecution Node Group(s)NodeMsg Filter NodeSOAPFlow ListenerWarehousing NodeAdministrativeNeon AgentRulesRuntimeOutputNodeSecurity MgrBrokerExplorerMessagesClientAppl ApplTargetRuntimePlatformsIBM AIX®Sun Solaris SPARCSun Solaris x86-64HP-UX ItaniumIBM z/OS®IBM System i ®Windows® XPWindows 2003Windows 2008Windows VistaLinux® (Intel)Linux on POWER®Linux on System z ®RDBMSInputNodeFilterNodeFilter NodeWarehousing NodeComputeNodeOutputNode© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOA Intro 53

IBM Software GroupWSRR© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 54

IBM Software GroupWebSphere Message Broker Client for WebSphere ServiceRegistry and Repository● EndpointLookup NodeFocussed on the retrieval of endpoints defined within WSDLRetrieves End Point Reference and Metadata, not whole artifactAble to search port type names within WSDL imported into WebSphere Service Registryand RepositoryInsert WSDL endpoint into WebSphere Message Broker flowUse endpoint for dynamic routing at runtime● RegistryLookup NodeGeneric Node for retrieval of any WebSphere Service Registry and Repository entityAble to search entity namesRetrieve entire contents of entity into the brokerUse entity information at runtime© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOAWSRRIntro 55

IBM Software GroupUsing WebSphere Service Registry and Repository To AddMetadata To Ports (Endpoints)Note – This is done from the WebSphere Service Registry and Repository console not the WebSphereMessage Broker Toolkit© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOAWSRRIntro 56

IBM Software GroupDebugging© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 57

IBM Software GroupFlow Debugger Overview● Provides a convenient, easy to use graphical interface for flow testing● Breakpoints can be established between nodes to allow interruption of flowexecution● When a breakpoint is encountered control is returned to you● Current content of message trees can be examined and modified● If next node to be executed supports source you can step into that node anddebug at the source levelMapping node, Compute node (ESQL), JavaCompute node© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOADebugIntro 58

IBM Software GroupCollector Node© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 59

IBM Software GroupCollector Node● Groups incoming messages or events together from multiple sources andplaces them into “Message Collections”.● The messages can be correlated based on message content● When a correlated set of messages arrives, the Message Collection ispropagated to the output terminal where is can be processed by a Computeor JavaCompute node● An expiry time can be specified for incomplete collectionsThese are propagated through the Expire terminal of the node© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOACollectoIntror 60

IBM Software GroupCollector Node – Terminal Properties● Terminal Name Also used as the folder name in the collection tree● Quantity Number of required messages that makes up a set If another message arrives, a new collection is created for it● Timeout When quantity > 1, this is the maximum time (in seconds) to wait for subsequent messages inthe set● Correlation Path Location in that message’s tree that contains the correlation identifier● Correlation Pattern Substring of the value in the correlation path that contains the correlation identifier Properties.WildcardMatch used to store the correlation string© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOACollectoIntror 61

IBM Software GroupConfiguring the Collector Node© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOACollectoIntror 62

IBM Software GroupPublish / Suscribe© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 63

IBM Software GroupComparison Of Messaging Styles – Point-to-Point● Point-to-PointLimited and well defined set of senders and receiversSenders and receivers normally aware of each other● Point-to-Point is not always suitableIf there are a large number of senders or receiversIf the senders and/or receivers frequently change If senders need to know exactly who to send messages to When a change occurs, clients need to be updated Can become unmanageable64© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOAPub/SuIntrob 64

IBM Software GroupWhat Is A Publisher?● Application that owns data to be made available to otherapplications (subscribers)● Does not know which or how many subscribers are interestedin the data● Does not know how to deliver the data to subscribers● Associates the data with a “topic”● Example: stock tradingNew stock price© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOAPub/SuIntrob 65

IBM Software GroupWhat Is A Subscriber?● An application that is interested in receiving data of a certaintype or category● Does not know where the data comes from● Identifies the topic(s) on which it is interested in receivingassociated dataExample: Interested in price of IBM stock● Optionally specifies a filter to further qualify the publicationsof interestExample: Only interested when price of IBM stock is > $100© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOAPub/SuIntrob 66

67IBM Software GroupTerminals provided on Publication node● There are two output terminals on the Publication node● Drives flow depending on subscribers matching publicationNo-match terminal If there are no matching subscribersOut terminal If one or more subscribers match© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOAPub/SuIntrob 67

IBM Software GroupDatabase access© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 68

IBM Software GroupDatabase Access In WebSphere Message Broker● WebSphere Message Broker provides convenient and easy access todatabases from a message flow● You can read, update, delete database content if you have the authority todo so● Databases can be accessed from flows as follows:Codelessly Mapping node, DatabaseRoute Node, DatabaseRetrieve node, DatabaseInsertnode, DatabaseDelete nodeVia coded statements Compute node, JavaCompute node, Database node, Filter node● The following databases are supportedIBM DB2®, Oracle, Sybase, SQL Server, IBM Informix®© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOADatabasIntro e 69

IBM Software GroupDatabaseRoute Node● Similar to Route, but matches on contents of a database rather than theinput messageIf last nameis JonesLook upemployee00002If salarybetween20000 and26000EmpNo LastName FirstName Salary00001 Smith John 2000000002 Jones Harry 2600000003 Colins Roger 31000© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOADatabasIntro e 70

IBM Software GroupConfiguring the DatabaseRoute Node [1]For example, if the incoming message has $Body/EmpRecord/EmpNumber = “00001”do the SQL querySELECT EMPLOYEE.SALARY, EMPLOYEE.LASTNAME FROM EMPLOYEEWHERE EMPLOYEE.EMPNO = “00001”© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOADatabasIntro e 71

IBM Software GroupConfiguring the DatabaseRoute Node [2]●●●●●If the retrieved value of the LASTNAME column has a last name of Jones, route to out_exp1If the retrieved value of the SALARY column has a value of between 20000 and 26000, route to out_exp2If both are true and Distribution Mode is set to ‘all’, route to out_exp1 then out_exp2.If both are true and Distribution Mode is set to ‘first’, route to the first match only (out_exp1)If neither are true, route to the default terminal© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOADatabasIntro e 72

IBM Software GroupDatabaseRetrieve Node● Allows data to be retrieved from one or more database tables● The retrieved data is stored as elements within this node’s output message● Queries can span multiple tables and select multiple predicates● Configuration is similar to that of the DatabaseRoute nodeLook upemployee00002Outputmessage(Key notfound)Set $Body/EmpRecord/Surname to value of EMPLOYEE.LASTNAMESet $Body/EmpRecord/Wage to value of EMPLOYEE.SALARY© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOADatabasIntro e 73

IBM Software GroupConfiguring the DatabaseRetrieve Node© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7.0 for your ESB and SOADatabasIntro e 74

IBM Software GroupThank you!© 2012 IBM CorporationDiscovering the value of WebSphere Message Broker V7 for your ESB and SOA Intro 75