Neuron ESB 3.0 Feature Summary

Transcription

1 Neurn ESB 3.0 Features Neurn ESB 3.0 Feature Summary Neurn ESB is built n tp f the.net Framewrk and fully leverages WCF, WF, and ther framewrk cmpnents, using an pen architecture that embraces extensibility. Users can develp custm adapters, messaging prcessing, business prcesses (stateless wrkflw), and system level services t extend the ut- f- the bx functinality while maintaining cnsistent tling and peratinal characteristics. While supprt f the Micrsft stack is very strng, interperability with ther vendr platfrms is brad and far reaching due t Neurn s adptin f the mst cmmn messaging standards and specificatins. Sme f the features that Neurn ESB prvides are: Sample Launcher Messaging Hierarchical Tpic based Pub/Sub Messaging Deplyment Cnnectivity Real time, in memry Messaging Guaranteed/Durable Messaging Event- based distributable.net client API Multiple Instances f Runtime Cnfiguratin Stre/XCpy Multi Develper Supprt Incremental Deplyment Cmmand Line Deplyment Adapters and Adapter Framewrk Adapter Plicies Event based Adapters Service Brker (SOAP/REST) Micrsft Dynamics CRM 4/2011 Micrsft SharePint 2007/2010 Service Intermediary

2 Neurn ESB 3.0 Features Service Ruter Service Versining Service Prvider Service Patterns Service Plicies Management Real Time Activity Mnitring Auditing/Tracking/Edit and Resubmit Failed Message supprt WMI perfrmance Cunters and Events SCOM management Pack Mnitring/Dashbard/Perfrmance Cunters Micrsft Azure Supprt Azure Service Bus Adapter Azure Service Bus Service Bindings Sql Azure supprt fr Neurn Audit database Real Time Business Prcessing Business Prcess Designer Ability t create custm Prcess steps Distributed Executin 34 Prcess Steps Business Prcess Testing Sample Launcher Neurn ESB ships with a Samples launcher accessibly thrugh the Neurn ESB Explrer. There are 50 samples that demnstrate varius capabilities. Fr example, users will find samples n hw t write custm adapters and Business Prcess Steps. Samples exist

3 Neurn ESB 3.0 Features that demnstrate a variety f service brker and Neurn ESB Tpic- based publish and subscribe messaging patterns. There are als samples fr develping custm Business Prcesses fr mediatin and general applicatin integratin (EAI). Messaging Neurn ESB prvides a middleware messaging layer that islates and decuples cmmunicating parties (services r applicatins), allwing them t effectively exchange messages. When using Neurn ESB, applicatins and/r services simply publish messages nt the bus, withut regard t the type r number f cnsumers; similarly, they may subscribe t specific messages r grups f messages, withut regard t the surce f the messages. This frees the develpers frm spending time n messaging business lgic and allws them t cncentrate n the specific business lgic assciated with manipulating the message data. Neurn ESB is an extrardinarily lightweight slutin with little t n ftprint required n external systems. The Neurn ESB Server frms the heart f the prduct and cnsists f a single Windws service that hsts a number f applicatin dmains fr cre services as well as services required t supprt a specific cnfiguratin (e.g. adapter endpints, service cnnectrs, client cnnectrs, etc.) The fllwing picture illustrates the majr Neurn ESB cmpnents and their relatinship t specific servers.

4 Neurn ESB 3.0 Features Installing Neurn ESB is simple and straightfrward, requiring less than 15 minutes t bring a server nline. Installatin n client machines is nly required if the client sftware uses the Neurn Client API. Neurn ESB cmpnents are nt required fr Web services, r mst LOB applicatins. The exceptin t this are LOB applicatins that utilize Neurn ESB adapters t generate and publish events t the ESB, these cmpnents generally require installatin n the LOB server. Neurn ESB is self- hsted and des nt require WAS r IIS. Tpics Neurn ESB prvides a pwerful, hierarchical Tpic based publish and subscribe messaging system where publishers can label each message with the name f a Tpic, rather than addressing it t specific recipients. Tpic based messaging systems tend t be mre intuitive as they can be clsely mdeled after the specific business requirements and/r the existing rganizatinal hierarchy. Neurn ESB manages sending the message t all eligible recipients that have expressed interest in receiving messages n that Tpic. This frm f asynchrnus messaging is a far mre scalable architecture than pint- t- pint alternatives, since message senders (publishers) need nly cncern themselves with creating the riginal message, and can leave the task f servicing recipients (subscribers) t the messaging infrastructure. Tpic- based publish and subscribe messaging systems share several cmmn attributes sme f which are: Subscribers subscribe t ne r mre tpics and nly receive messages that are f interest The publishers have n knwledge abut the subscribers, including hw many there are r where they live The subscribers have n knwledge abut the publishers, including hw many there are r where they live New systems (publishers r subscribers) can easily be added r remved frm the flw f infrmatin, withut cde changes. This type f messaging architecture sends messages nly t the applicatins that are interested in receiving the messages withut knwing the identities f the receivers. There are many ther reasns t adpt a hierarchical Tpic taxnmy. It allws fr mre meaningful self- describing subscriptins which can mdel events, systems, categries r functins. They mre intuitive as they can be mdeled t represent specific resurces, peple r systems t rute messages t. Subtpics can be used t describe different versins f existing services that messages may be ruted t. When a hierarchical (sub tpics) Tpics are created, they can be lgically mapped t recipients like Service and Adapter Endpints r even t different versins f services that thse endpints represent.

5 Neurn ESB 3.0 Features Transprts and QOS Neurn ESB Tpics cntrl nt nly the path/rute f the messages in Neurn ESB but als the Quality f Service (QOS) which is cnfigured by chsing a specific Transprt fr the Tpic. QOS attributes are always cnfigured at the rt Tpic level and affect all f the respective sub tpics, including whether r nt durable messaging is enabled. Neurn ships with 6 transprts fr Tpics TCP This transprt is based n the WCF NetTcp binding and ffers rdering, security and sessin reliability as ptins. It is nt a durable transprt s message lss can ccur if n subscribers are nline when a message is published. TCP requires Prt cnfiguratin and is cmmnly used in the fllwing scenaris: Request/Respnse style messaging where neither durability nr transactins are required. A gd example wuld be web service traffic. When the Neurn ESB Client API is hsted in custm applicatins existing n machines REMOTE t the Neurn ESB server Multiple instances f the same Party must receive the same messages Named Pipe This transprt is based n the WCF NetNamedPipe binding. This transprt is slightly faster than TCP, and easier t cnfigure (des nt require Prt cnfiguratin). Hwever, this transprt cannt be cnfigured fr tpics that will be utilized by remte applicatins hsting the Neurn Client API. It is nt a durable transprt s message lss can ccur if n subscribers are nline when a message is published. It is cmmnly used in the fllwing scenaris: Request/Respnse style messaging where neither durability nr transactins are required. A gd example wuld be web service traffic. When the Neurn ESB Client API is hsted in custm applicatins that cexist n the SAME machine as the Neurn ESB server When all messaging traffic is generated by cnfigured Service r Adapter Endpints (i.e. all messaging is lcal t the Neurn ESB Server) and neither durability nr transactins are required. Multiple instances f the same Party must receive the same messages MSMQ This transprt is based n the WCF NetMsmq binding. It is ptinally a durable and transactinal transprt s parties that are nt nline when a message is sent can receive messages when they recnnect. The MSMQ transprt prvides a pull style subscriptin mdel s subscribers cannt be verladed by messages. Because transactins are supprted, the ambient transactin can be accessed within the Receive Handler f the Neurn ESB Client API r within a Neurn ESB Business Prcess. When cnfigured as an in memry transprt (i.e. Durability and Transactin prperties set t False) this transprt can be faster and mre efficient than TCP. This transprt cannt be used t send messages greater than 4 MB in size but can prvide guaranteed, nce nly delivery f messages acrss the bus. It is cmmnly used in the fllwing scenaris:

6 Neurn ESB 3.0 Features Where message lss is nt acceptable. One way (multicast/datagram) message patterns Where XA style transactinal supprt is required Subscribers must receive messages, yet may nt be cnsistently nline Ordered messaging AMQP This transprt is based n RabbitMQ which is an implementatin f the AMQP pen standard fr messaging middleware. It is ptinally a durable transprt s parties that are nt nline when a message is sent will receive messages when they recnnect. This transprt is new in Neurn 3.0 and can be used as an alternative t MSMQ as a tpic transprt. Althugh this transprt des nt supprt transactins, it des nt have the 4MB message size limit that MSMQ has. It is cmmnly used in the fllwing scenaris: Where message lss is nt acceptable. One way (multicast/datagram) message patterns Subscribers must receive messages, yet may nt be cnsistently nline Peer This transprt is based n the WCF NetPeerTcp binding and uses a custm reslver. It is ideal fr real time cmmunicatins but sme message lss may be tlerated. This transprt may be used t scale Neurn messaging t 1000 s f subscribers and prvide rich client apps with real time updates. This transprt des nt supprt durable r transactinal messaging but may be used fr either ne way r request/respnse style messaging. It is cmmnly used in the fllwing scenaris: Where there are 100 s r mre subscribers t the same message Multiple instances f the same Party must receive the same messages BizTalk This transprt is a specialized transprt fr use by users wh want specific Neurn ESB messaging t flw thrugh the Micrsft BizTalk Server message bx. Neurn des nt require BizTalk. Hwever t cnfigure a Neurn Tpic t use the BizTalk transprt, Micrsft BizTalk Server must be installed n a machine accessible t the Neurn ESB server. Using the BizTalk transprt is a cnvenient way t integrate the capabilities f Neurn ESB and Micrsft BizTalk server. This transprt requires that the Neurn ESB BizTalk plugin MSI package is installed n a Micrsft BizTalk Server. It is cmmnly used in the fllwing scenaris: Where the user desires t rute messaging traffic t a BizTalk server fr extended prcessing In additin t Transprts, Neurn ESB allws ther QOS f elements t be cnfigured at the Tpic level: Auditing (message tracking) Cmpressin Publisher based thrttling Encryptin Neurn is a self- hsting applicatin. This means it des nt require IIS r WAS being installed t run.

7 Neurn ESB 3.0 Features Parties A Party may subscribe t 1 r mre Tpics r sub Tpics. Parties use Subscriptins t restrict which Tpics they can publish messages t, as well as determine what messages they are interested in receiving frm the bus. Parties that send messages are knwn as publishers, and parties that receive messages are knwn as subscribers. A party culd be bth a publisher and a subscriber. One r mre Subscriptins can be assigned t a Party. Subscriptins A Subscriptin is cmpsed f a Tpic r sub Tpic, the permissin in which a message can be sent t r frm that Tpic (i.e. Send/Receive) and can be further ptinally restricted using ne r mre Cnditins. A Cnditin is either a preexisting r ad hc filter expressin (using predicates) that can include message header prperties as well as message cntent. Smetimes this is referred t as Cntent Based Ruting. Managing subscriptins fr Publishers and Subscribers can be dne thrugh the Neurn ESB Explrer. Users can quickly add tpics, wildcards, reusable cnditins (i.e. cntent based ruting), and ad hc cnditins t define a subscriptin and activate it instantaneusly. Messages A message is infrmatin that ne Party sends t, r receives frm the bus. A message cntains bth data, (the infrmatin that sme ther system, resurce r persn may be interested in), as well as metadata. Respectively, these are referred t as the paylad and header (cntext) prperties f the message. Bth are defined as parts f a Neurn ESB Message. The paylad f a Neurn ESB Message can be ne f several frmats: Serializable.NET Object - The ability t pass.net bjects prvides flexibility fr develpers wh prefer use f bjects ver XML Binary data - The ability t pass binary data prvides flexibility fr develpers wh have t share cntent that is neither serializable nr XML. Text data Any type f string data XML data Any XML data. XSD schemas are nt required t use XML as the paylad Parties are created within the Neurn ESB Explrer and are represented by a lgical name, ften referred t as the Party ID, Subscriber ID r Publisher ID. Because Parties cntrl the interactin f messages t Tpics, all Adapter Endpints, Client Cnnectrs and Service Cnnectrs MUST be cnfigured with a Party. The cnfigured Party will determine what messages are received by Adapter Endpints r Service Cnnectrs, and where (what Tpic) messages will be published t by Adapter Endpints and Client Cnnectrs.

8 Neurn ESB 3.0 Features A Party may als ptinally manipulate the message it is sending r the message it receives. This manipulatin ccurs via a Neurn ESB Business Prcess. Neurn ESB Client API The Neurn ESB Client API is an event based, distributable API that can be hsted in.net applicatins t publish and receive messages t and frm Tpics. Tpics are the cre f the Neurn ESB messaging sub system and are hsted by the Neurn ESB runtime windws service. At the cre f the Neurn ESB Client API are the Publisher and Subscriber.NET classes, which are derived frm the Party class. Generally, users will create either an instance f Publisher r Subscriber class (r Party class) in.net cde, Cnnect t the bus and either send r receive messages. Creating an instance f either the Publisher r Subscriber requires passing in several parameters which can be passed either by embedding them within the app.cnfig file r by specifically declaring them using the SubscriberCnfiguratin class. The example belw demnstrates hw t create an instance f a Publisher bject, using the SubscriberCnfiguratin class: SubscriberCnfiguratin cnfig = new SubscriberCnfiguratin("AccuntPublisher", "Enterprise", "net.tcp://lcalhst:50000", ""); using (Publisher client = new Publisher(cnfig)) { } Once an instance f the Publisher r Subscriber class is created, yu can wire in any number f events fr ntificatin if smething f interest ccurs. There are several events, sme f which are: Online, Offline, OnReceive, OnSubscriberDisabled and OnCnfiguratinChanged. After an instance f either a Publisher r Subscriber class is created, it must Cnnect t the Neurn ESB runtime windws service i.e. the bus. using (Publisher publisher = new Publisher(cnfig)) { PartyCnnectExceptins exceptins = publisher.cnnect(); if (exceptins!= null && exceptins.cunt > 0) { freach (var e in exceptins.getresults()) Cnsle.WriteLine(string.Frmat("An errr ccurred cnnecting '{0}' t Tpic, '{1}'. {2}", publisher.cntext.partyid, e.exceptin.message, e.tpic)); } } After a client has cnnected t the bus, it can either send and r receive messages. There are several Send methds ff f the Publisher class fr sending a variety f different messages types. All Send methds publish data t a specific Tpic supplied at runtime. In the example belw, the client publishes bth a System.DateTime bject as well as XML data t the bus. Fr the latter, the Semantic prperty has been changed frm its default f Multicast (indicating Asynchrnus messaging) t Request (indicating Synchrnus messaging). When changed t Request, the Send methd will blck the caller until it either receives a respnse message frm the receiving subscriber r the request times ut:

9 Neurn ESB 3.0 Features #regin Send a.net serializable bject like datetime // Send anything.net serializable like date time r custm class publisher.send( Accunts.Lan, DateTime.Nw); #endregin #regin Send a simple request message that will return a reply // this means that the subscriber must send back a reply message ESBMessage respnse = publisher.sendxml( Accunts.Lan,"<Test>MyRequest</Test>", "",SendOptins.Request); #endregin When subscribing t messages frm the bus, the OnReceive event handler must be used. Within the event handler, messages will be received as they are published t and ruted by the bus. Once a message is received, it data type can be inspected and the message can be cast int its specific datatype using the GetBdy<>() methd f the ESBMessage class as in the example belw: private static vid OnReceive(bject sender, MessageEventArgs e) { ESBMessage message = e.message; if (message.header.bdytype!= null) { if (message.header.bdytype.equals("text/xml")) Cnsle.WriteLine(message.GetBdy<string>()); if (message.header.bdytype.equals("datetime")) Cnsle.WriteLine(message.GetBdy<DateTime>().TString()); } if (message.header.bdytype.equals("testserializatin")) Cnsle.WriteLine(message.GetBdy<TestSerializatin>().Name); } else { Cnsle.WriteLine(message.Text); } Lastly, if a Tpic is cnfigured with a Transactin Transprt such as MSMQ, the ambient transactin can be used within the receive handler t rll the received message all the way back t its underlying Queue fr anther redelivery attempt like s: private static vid OnReceive(bject sender, MessageEventArgs e) { } Transactin tx = System.Transactins.Transactin.Current; if (tx == null) Cnsle.WriteLine(" null transactin"); else Cnsle.WriteLine(" transactin exists"); tx.rllback(); Cnnectivity Neurn ESB prvides many areas f develper prductivity. Neurn ESB expses extremely simplified interfaces fr adapter develpment as well as real time prcess develpment. Adapters functin as bridges t external transprts, prtcls r existing applicatins that may be in use within an rganizatin. Neurn ESB prvides many ut f the bx adapters t simplify cnnectivity thrugh messaging and cnfiguratin. Additinally, several event based publicatin adapters are als included with Neurn ESB.

10 Neurn ESB 3.0 Features Adapters MSMQ IBM DB2 IBM Dataqueues ODBC FTP/FTPS Infrmix SMTP Exchange POP3 IBM MQSeries Apache ActiveMQ Micrsft SQL Server Micrsft SharePint (Event based) Micrsft Dynamics CRM (Event based) Micrsft Dynamics Great Plains Micrsft BizTalk RFID Micrsft Azure Service Bus File Supprt fr Micrsft WCF LOB Adapters SAP/Oracle/Siebel/SQL The fllwing diagram depicts a fictinal Neurn ESB cnfiguratin illustrating intercnnectins in a hetergeneus envirnment, as well as the majr Neurn ESB functinal cmpnents. Neurn ESB is unique in ffering event based publicatin adapter t Micrsft Dynamics CRM and Micrsft SharePint Services. Prviding event based publicatin plugins allws rganizatins t publish infrmatin t the bus when the event happens.

11 Neurn ESB 3.0 Features Adapter Plicies Neurn ESB has bth an adapter and service endpint implementatin f Plicy that allws custmers t manage hw service and adapter endpints behave n failure and define what a failure is. Plicies can als be used t cntrl endpint availability and timeuts. Once a plicy is defined, it can be assigned t manage either ne r mre service and adapter endpints. Micrsft Dynamics CRM 2011 The Micrsft Dynamics CRM 2011 event based publicatin adapter cmpliments the existing Micrsft Dynamics CRM subscriptin adapter. Using Neurn ESB, Micrsft Dynamics CRM 2011 administratrs can easily capture events thrugh the Dynamics CRM 2011 Prcess Designer and cnfigure them t be frwarded t a Neurn ESB Tpic. Prcesses in Micrsft Dynamics CRM 2011 are based n Windws Wrkflw Fundatin. By leveraging the Micrsft Dynamics CRM 2011 prcess engine, Neurn can prvide mre ptins fr business rule creatin, while ffering a greater breadth f event publicatin ptins, including full WCF service capabilities. The Neurn ESB Micrsft Dynamics CRM 2011 publicatin adapter extends Micrsft Dynamics CRM 2011, enabling it t send event ntificatins t web services as well as Neurn tpics using. Sme f the features include: Send entities t tpics and web services. Send dynamic entities t tpics and web services. Send custmized XML with data frm related entities t tpics and web services.

12 Neurn ESB 3.0 Features Execute fetch XML queries and send the results t tpics and web services. Run XSL transfrms befre sending data t web services. Capture detailed tracing infrmatin. Micrsft SharePint 2010 Neurn ESB includes remarkable integratin capabilities with bth Micrsft SharePint 2010 and Micrsft Dynamics CRM The Micrsft SharePint 2010 event based publicatin adapter cmpliments the existing Micrsft SharePint subscriptin adapter by allwing rganizatins t capture SharePint generated events frm lists and libraries and publish thse events in real time t a Neurn ESB Tpic. The Neurn ESB SharePint 2010 Publicatin Adapter has the fllwing features: Publish frm Lists Publish frm Tasks Publish frm Libraries Publish n multiple types f events: Item Added Item Updated Item Deleted Item Checked Out Item Checked In Include Attachments

13 Neurn ESB 3.0 Features Micrsft Azure Supprt Azure Service Bus Adapter Neurn ESB 3.0 includes an Azure Service Bus Adapter t prvide reliable cmmunicatin n either endpint f the Azure Service Bus. The Azure Service Bus Adapter prvides full supprt fr the latest capabilities prvided by the Windws Azure SDK versin 1.7. The Azure Service Bus adapter supprts the fllwing Azure Service Bus Brkered Messaging features: Send t Azure Service Bus Queue Send t Azure Service Bus Tpic Receive frm Azure Service Bus Queue Receive frm Azure Service Bus Subscriptin In additin, the Neurn Azure Service Bus adapter simplifies the develpment experience by prviding additinal capabilities required t ensure reliability typical in prductin scenaris withut the need t write custm cde including: Smart Plling Eventual Cnsistency Transient Errr Detectin and Retry Azure Service Bus Service Bindings Neurn ESB plays a critical rle as rganizatins evlve t lk tward Clud fferings fr service hsting r business t business cmmunicatin. As a web service brker, Neurn ESB includes all f the Azure Service Bus Relay Bindings ( us/library/windwsazure/hh aspx ) t

14 Neurn ESB 3.0 Features facilitate hybrid appraches t bridge On Premise integratin with Clud based slutins. Neurn ESB ensures that cmmunicatin between the Clud and On Premise systems can be handled securely and reliably, while managing prcessing requirements f the rganizatin. Sql Azure supprt fr Neurn Audit database Neurn ESB supprts Micrsft SQL Server versins 2005 and abve, fr the Auditing Service s message stre. Hwever, in Neurn ESB 3.0, supprt fr Micrsft SQL Azure has been added. This prvides users wh hst Neurn ESB in an Azure wrker r VM rle, the ability t cnfigure supprt fr the Neurn ESB Audit Service. Service Brker In cnjunctin with prviding a pwerful integratin platfrm fr the.net Develper, Neurn ESB 3.0 prvides a web service platfrm facilitating critical functins fr rganizatins interested in successfully adpting a SOA strategy: Service Intermediary Service Ruter Service Versining Service Prvider Service Patterns By serving as a brker, Neurn ESB can abstract, prcess, mediate, and dynamically rute incming service requests t existing services thrughut an rganizatin. Neurn ESB can shield custmer facing applicatins frm changes that ccur in an rganizatin s infrastructure, applicatins r services.

15 Neurn ESB 3.0 Features Neurn ESB 3.0 prvides a pwerful runtime envirnment fr hsting either SOAP r REST based services as well as a real- time Business Prcess runtime fr develping cmplex service pattern such as Scatter- Gather as depicted belw: Neurn ESB 3.0 Service Brker supprts hsting services as well as ruting t existing services. Services can be cnfigured within the Neurn ESB Explrer and supprts the fllwing: Supprts WCF bindings Supprts WS* standards Supprts ASMX, WCF and Java- based services Supprts custm bindings, cnfiguratin, behavirs Supprts prtcl mediatin and pass- thru ruting REST One- way and request- respnse MEP Imprt existing services Supprts UDDI and failver URLS Plicy cntrls failure ptins

16 Neurn ESB 3.0 Features Neurn ESB is a pwerful hsting prvider and des nt require IIS r WAS fr hsting services. Neurn ESB hsted services are: Generic service n- ramps (i.e. Type- less, n WSDL Strngly typed with WSDL Publish directly t Bus Services can be virtualized thrugh Neurn ESB cmpletely thrugh cnfiguratin. Develpers can imprt WSDL frm an existing service r create custm WSDL and assciated that WSDL directly with a service cnfigured and hsted by Neurn ESB: REST Neurn ESB is used by many rganizatins t brker, rute and mediate web service calls fr their custmer and partners. Althugh many rganizatins use SOAP based services, REST based services are an imprtant ingredient fr embracing Web 2.0 and mbility scenaris. Many custmers tday use Neurn ESB t expse existing SOAP based services as REST based services, saving a significant amunt f time and develpment effrt in the prcess. Neurn ESB prvides a REST bject mdel as well as JSON supprt that Develpers can directly reference within a Business Prcess Cde Step editr as depicted belw:

17 Neurn ESB 3.0 Features Service Plicies Neurn ESB has bth an adapter and service endpint implementatin f Plicy that allws custmers t manage hw service and adapter endpints behave n failure and define what a failure is. Plicies can als be used t cntrl endpint availability and timeuts. Once a plicy is defined, it can be assigned t manage either ne r mre service and adapter endpints. With the prevalence f REST based services, Neurn ESB 3.0 intrduces REST HTTP Status cde supprt fr service plicies. Users can nw cnfigure a service plicy t retry and fail depending n the HTTP Status cde returned n a REST service endpint.

18 Neurn ESB 3.0 Features Deplyment Multiple Instances f Runtime Neurn ESB ffers pwerful runtime and scalability features that allw businesses t quickly deply slutins. Slutins can scale bth vertically and/r hrizntally using the Neurn ESB Runtime Service acrss ne r mre servers. The Neurn ESB Runtime Service lads a Neurn ESB Cnfiguratin stre which can cntain ne r mre business slutins. Neurn ESB als supprts multiple instances f the runtime service. This allws rganizatins t install and run multiple instances f the Neurn ESB Runtime Service n a single server. Each instance can be cnfigured as either a 32 r 64 bit prcess, capable f running side by side. Each instance f the runtime can lad an independent Neurn ESB Cnfiguratin stre. This allws rganizatins t easily partitin business slutins t run n a single server, effectively eliminating prir cnstraints, as depicted belw.

19 Neurn ESB 3.0 Features Neurn ESB 2.6 Multi Instance supprt enables a number f pwerful scenaris including: 64 bit and 32 bit prcesses side by side Businesses may have slutins that require ODBC cnnectivity. Many ODBC drivers require 32 bit prcess executin envirnments. Using Neurn ESB, businesses can run elements f ne slutin under a 64 bit prcess, while running ODBC elements f anther slutin using a 32 bit prcess. Business Slutin Partitining Departments within an rganizatin may require partitining f applicatins fr management, security r plicy cmpliance. Individual departments may require their wn Neurn ESB Cnfiguratin stre s that they can be independently develped, administered and deplyed. Perfrmance Scale Out Neurn ESB s Multi Instance supprt prvides a new level f scale ut by allwing rganizatins t separate and deply mre resurce elements f a slutin t dedicated servers. Multiple Develper Supprt The ability t deply many independent Neurn ESB Cnfiguratin stres t a single server enables develpers t easily wrk n their wn slutins while deplying t the same servers. Cnfiguratin Stre Neurn ESB s cnfiguratin strage frmat prvides incremental, cmmand line, and simple XCpy deplyment f selected entities. Fr example, in Neurn ESB 3.0, users can select ne r mre entities (and their dependencies) frm ne ESB slutin, exprt them ut as a package, and imprt them int anther ESB Slutin. The Neurn ESB 3.0 cnfiguratin strage frmat is a directry structure cnsisting f flders representing each entity type. Within each flder, an XML frmatted file represents a specific entity such as a Tpic, Endpint, Business Prcess, etc. The Neurn ESB Explrer is designed t wrk and stre all mdificatins t the directry structure.

20 Neurn ESB 3.0 Features After launching the Neurn ESB Explrer, users can Cnnect, Open, r Create a new Neurn ESB 3.0 cnfiguratin. When Open is selected, users are prmpted t select the rt flder f an existing Neurn ESB 3.0 cnfiguratin directry as depicted belw: Once the Neurn ESB 3.0 cnfiguratin is pened, each XML file within the entity flder is laded and managed within the Neurn ESB Explrer. There is a ne- t- ne mapping f XML file t managed entity. The figure belw displays the Tpics represented by XML files within the Tpics sub flder f the DemSlutin directry (pictured abve).

21 Neurn ESB 3.0 Features Multi Develper supprt The Neurn ESB 3.0 cnfiguratin strage frmat allws multiple Develpers t wrk n individual elements f an ESB Slutin. Develpers can use surce cntrl systems t check in and check ut individual entities in a slutin. Develpers mdifying ne entity will have n impact n the ther entities in a slutin. Develpers can then merge their changes int a central cnfiguratin easily, by checking in their updated entities. Incremental Deplyment Althugh Neurn ESB 3.0 still supprts deplying the entire slutin frm ne envirnment t anther, users can nw deply nly the changes r new entities they want, rather than the entire slutin. There are generally three (3) appraches fr incremental deplyment: Using the new exprt/imprt utility f the Neurn ESB Explrer Directly cpying the new r mdified entities t their respective cnfiguratin sub flders n the target server Using the new cmmand line interface t autmate the deplyment f selected entities exprted, using the exprt/imprt utility. The Exprt/Imprt utility can be accessed frm the File menu f the Neurn ESB Explrer. When Exprt is selected, the Exprt dialg bx appears and allws users t select the individual entities t be exprted (r all f them). If an entity is selected that has dependencies, the user is prmpted with thse dependencies and given the ptin f including them in the exprt. Once the selectin is cmplete, all the selected entities are exprted ut t a new *.esb package file.