This document provides an introduction to using Mule, an open-source enterprise service bus (ESB). It discusses core Mule concepts like the universal message object, endpoints, transports, connectors, routers, filters, transformers and the Mule event flow. It provides examples of using Mule to move files between directories and validate an XML file against a schema. Exceptions are handled by associating an exception strategy to redirect invalid files to an error folder.
WSDL is an XML language used to describe web services, defining operations provided by the service, data formats, and location. It describes what a service does via operations, how it is accessed via protocols and data formats, and where it is located via URLs. A WSDL document defines types, messages, operations, bindings and services. Translators can generate code from WSDL or derive WSDL from existing code.
The document provides an overview of Java Messaging Services (JMS) in MuleSoft Mule ESB 3.6. It describes key JMS concepts like the JMS messaging model with queues and topics, backchannels, message filtering using selectors, transformers, and provides an example ActiveMQ configuration with inbound and outbound endpoints.
This document proposes enhancing Thrift to allow multiple services to be hosted on a single server port through multiplexing. It describes adding components like a Multiplexer processor that directs requests to the appropriate service based on a service context, a protocol wrapper that embeds the service context, and a registry for lookup of available services. This allows Thrift to better meet the needs of enterprises by reducing administrative overhead compared to hosting each service on a separate port.
Clustering technologies in Windows Server 2003 help achieve high availability and scalability for critical applications. Server clusters provide high availability by redistributing workloads from failed servers, while Network Load Balancing provides scalability and availability for web services by load balancing requests across multiple servers. The choice depends on whether applications have long-running in-memory state, with server clusters intended for stateful applications like databases and NLB for stateless applications like web servers.
JUDCon2014-ScalableMessagingWithJBossA-MQ and Apache Camel
Scalable Messaging is the the need of the enterprise messaging infrastructure. JBossA-MQ is one of the leading products for scalable messaging. It also covers some common concepts beween Apache Active MQ and JBoss A-MQ . Apache Camel as a integration framework supports the enterprise messaging greately and the presentation also contains some of its areas of adjunction to Scalable messaging with queues and topics.
The document discusses the open-source enterprise service bus Mule, including what Mule is, its core concepts like the universal message object and endpoints, and how Mule uses technologies like staged event-driven architecture and non-blocking I/O to move data between different systems and formats in a flexible way. It also provides examples of using Mule to move XML files between directories and handling exceptions.
Acceleration Technology: Solving File Transfer Issues
File transfer acceleration can significantly increase file transfer speeds compared to traditional methods like FTP. It works by transferring files over UDP instead of TCP, avoiding issues from network latency and packet loss that slow TCP transfers. This allows files to be sent at full network speed even over long distances or unreliable links. As a result, file transfer acceleration can reduce costs from unused bandwidth and boost productivity by speeding file sharing and project completion.
This document provides an introduction to inbound endpoints in WSO2 ESB. It discusses the key features and benefits of inbound endpoints, including dynamic configuration, multi-tenancy support, coordination in clustered environments, and direct message injection to mediation flows. Specific inbound endpoint types are described, including HTTP/HTTPS, JMS, and file inbound endpoints. Configuration parameters for each of these endpoint types are outlined. The presentation concludes with a demonstration of inbound endpoints.
This document summarizes a content delivery network (CDN) created to host video clips and live broadcasts. The CDN uses edge nodes located in different networks to serve traffic and origin nodes for storage. A redirector selects the best edge node based on location and load. Files are replicated across origin nodes and managed through a bridge that provides a WebDAV interface. Live broadcasts are supported through RTMP and plans include expanding support to additional streaming protocols and platforms.
MPEG DASH – Tomorrow's Format Today by Nicolas Weil
Senior Solutions Architect, Akamai Technologies & Will Law, Chief Architect, Media Cloud Engineering, Akamai Technologies
As an open standard designed to help simplify video delivery across connected devices, MPEG-DASH is continuing to gain momentum in the OTT, broadcast and wireless industries. Join Akamai's DASH experts for a discussion on what differentiates the emerging standard from legacy formats along with a demonstration showing the ease of deploying DASH playback across devices. The panel will also highlight current deployments, offer a review of the industry and provide a three-year outlook.
Akamai Edge is the premier event for Internet innovators, tech professionals and online business pioneers who together are forging a Faster Forward World. At Edge, the architects, experts and implementers of the most innovative global online businesses gather face-to-face for an invaluable three days of sharing, learning and together pushing the limits of the Faster Forward World. Learn more at: http://www.akamai.com/edge
The document provides information about the CCNA certification process and overview. It discusses that the CCNA exam costs $150, has a 90 minute time limit, and consists of 55-65 questions in various formats. It also lists recommended study books. It then provides a detailed overview of each layer of the OSI model, describing the functions and responsibilities of the application, presentation, session, transport, network, data link, and physical layers.
Plongée en eaux profondes dans l'architecture du nouvel Exchange 2013
Attention, session en anglais. Animée par Scott Schnoll, Principal Technical Writer dans l'équipe Exchange à Microsoft corp. Découvrez la nouvelle architecture des serveurs Exchange 2013. Cette nouvelle version apporte des nouveautés fondamentales et bénéficie de l'expérience de gestion du Cloud O365 par les équipes online. Des évolutions de l'architecture fondamentale d'Exchange découlent directement de ce retour d'expérience et ont été intégrées au produit. Venez découvrir celles-ci par l'expert mondial sur le sujet.
This document defines streaming protocols, compares mashups and portals, and describes different types of portals. It outlines several streaming protocols including RTSP, MMS, PNM, RTMP, and HTTP streaming. It also discusses protocol issues such as using UDP vs TCP and unicast vs multicast delivery. Mashups are described as combining content in new ways using APIs, while portals aggregate pre-existing content on servers. Finally, the document lists various types of portals including personal, business, news, government, and domain-specific portals.
RabbitMQ is an open-source message broker software written in Erlang. It uses exchanges to route messages from producers to queues based on routing keys or bindings. There are four main exchange types - direct, fanout, topic, and headers. Mule connects to RabbitMQ using the AMQP connector. It can send and receive messages to/from RabbitMQ queues using different exchange types like direct exchanges as demonstrated in the example config with two flows, one to send and one to receive a message.
This document discusses RSVP and differentiated services (DS) network models. It provides details on:
1) RSVP uses objects like INTEGRITY, SCOPE, and RESV_CONFIRM carried in messages to establish and maintain reservations. Messages include a common header followed by objects.
2) The DS model aggregates traffic by service level agreements rather than per-flow reservations. Packets are marked with DS field codepoints to receive different per-hop behaviors like expedited forwarding or assured forwarding.
3) DS routers classify and condition traffic at ingress based on DS fields and traffic agreements. Core routers provide behaviors like low latency for expedited forwarding or high assurance delivery for assured forwarding traffic within configured rates.
slides are about load balancing as a concept and implementation of load balancing on computer technical level
slides show the server load balancing
different architectures , algorithms and examples
1. O documento discute discordâncias em materiais cristalinos, defeitos que causam distorções na estrutura cristalina e afetam a deformação plástica e resistência mecânica.
2. As discordâncias se movimentam durante a deformação plástica, e a resistência pode ser aumentada restringindo seu movimento, por exemplo, reduzindo o tamanho de grão.
3. Vários tratamentos térmicos como recuperação e recristalização podem alterar as discordâncias e propriedades do material.
1. O documento discute os mecanismos de deformação plástica em metais, especificamente o movimento de discordâncias. 2. A deformação plástica ocorre principalmente pelo escorregamento de planos atômicos, que envolve o movimento de discordâncias. 3. Vários tratamentos como adição de ligas, redução do tamanho de grão e encruamento podem aumentar a resistência mecânica ao restringir o movimento de discordâncias.
O documento discute os principais tipos de defeitos em materiais cristalinos que influenciam a deformação plástica, incluindo discordâncias, maclações e falhas de empilhamento. Explica como o movimento de discordâncias depende de fatores como a estrutura cristalina, a orientação dos cristais e a presença de outros defeitos. Também aborda a termodinâmica por trás da geração e movimentação de defeitos durante a deformação.
O documento descreve processos de conformação de chapas metálicas como estampagem, estampagem profunda e hidroconformação. A estampagem é geralmente realizada a frio em chapas delgadas de aço, alumínio ou cobre. A estampagem profunda é feita em vários estágios usando punções, matrizes e sujeitadores para formar copos e caixas. A hidroconformação usa alta pressão hidráulica para formar peças tubulares complexas.
O documento discute os principais processos de conformação mecânica de metais, incluindo forjamento, laminação, trefilagem, extrusão e estampagem. Explica cada processo e como eles transformam a forma dos metais aplicando força externa para deformação plástica enquanto mantêm o volume e massa originais. O documento também discute trabalhos a quente e a frio durante a conformação mecânica.
O documento descreve os processos de estampagem, incluindo corte de chapas, conformação mecânica e estampagem profunda. A conformação mecânica envolve técnicas como dobramento, rebordamento e enrolamento para dar forma a peças de metal. A estampagem profunda cria objetos ocos de formato cilíndrico. O processo Guerin usa uma "almofada" de borracha ao invés de matriz rígida.
This document provides an introduction to using Mule, an open-source enterprise service bus (ESB). It discusses Mule's core concepts like the universal message object, endpoints, transports, connectors, routers, filters and transformers. It provides examples of using Mule to move files between directories and validate XML files against a schema. The document is intended to explain Mule's declarative approach and how data flows through various stages of receiving, routing, transforming and dispatching events.
This document provides an introduction to Mule, an open-source enterprise service bus (ESB). It discusses what Mule is, how to use it, and some of its core concepts. Mule uses technologies like staged event-driven architecture (SEDA) and Java NIO to process events and messages asynchronously and efficiently. The document then explains Mule concepts like endpoints, transports, connectors, routers, filters, transformers and the universal message object (UMO) that Mule uses to process events through its pipeline. It provides examples of using Mule with file endpoints and XML pipelines.
This document provides an introduction to Mule, an open-source enterprise service bus (ESB). It discusses what Mule is, how it can be used, and its core concepts. Mule uses technologies like staged event-driven architecture (SEDA) and Java NIO to facilitate integration. Core Mule concepts include endpoints, routers, filters, transformers, and the universal message object (UMO). The document also provides examples of using Mule for file processing and XML pipelines. It demonstrates how Mule handles normal processing as well as exceptions.
The document discusses the open-source enterprise service bus Mule, including what Mule is, its core concepts like the universal message object and endpoints, and how Mule uses technologies like staged event-driven architecture and non-blocking I/O to move data between different systems and formats in a flexible way. It also provides examples of using Mule to move XML files between directories and handling exceptions.
The document discusses the open-source enterprise service bus Mule, including what Mule is, its core concepts like the universal message object and endpoints, and how Mule uses technologies like staged event-driven architecture and non-blocking I/O to move data between different systems and formats in a flexible way. It also provides examples of using Mule to move XML files between directories and handling exceptions.
This document provides an introduction and overview of Mule, an open-source enterprise service bus (ESB). It discusses what Mule is, how it uses advanced technologies like staged event-driven architecture (SEDA) and Java NIO. The core concepts of Mule like the universal message object, endpoints, transports, connectors, routers, filters and transformers are explained. Examples are given of using Mule for file processing and XML pipelines. Exception handling in Mule is also covered.
This document provides an overview of Mule, an open-source enterprise service backbone. It discusses key Mule concepts like the universal message object, transports, connectors, routers, filters, transformers and the Mule event flow. It also covers how Mule uses staged event-driven architecture and Java NIO for advanced technologies. Specific examples are provided around using Mule with file endpoints and for XML pipelines. The document concludes with a discussion of exception handling in Mule.
This document provides an overview of Mule, an open-source enterprise service bus (ESB). It discusses key Mule concepts like the universal message object (UMO), endpoints, transports, connectors, routers, filters, transformers, and the Mule event flow. It provides examples of using Mule with file endpoints to move files between directories and validate XML files against a schema. It also covers exception handling in Mule and generating error messages when validation fails.
This document discusses enterprise integration patterns. It covers common integration styles and building blocks like endpoints, channels, and messages. It also describes main message exchange patterns and styles. Popular messaging protocols like AMQP and STOMP are explained. Finally, it discusses enterprise message brokers and frameworks that implement integration patterns.
The document discusses data center network architectures. It begins by describing the goals of data center networks including availability, scalability, low cost, throughput and load balancing. It then discusses conventional network architectures and challenges. It describes fat-tree based networks that provide full bisection bandwidth and commodity switches. Recursive network architectures are also summarized that are highly scalable using commodity networks. Modular data centers and virtualized data center networks are briefly introduced. An example of a 4-4 1-4 data center network architecture is provided and references are listed.
WSDL is an XML language used to describe web services, defining operations provided by the service, data formats, and location. It describes what a service does via operations, how it is accessed via protocols and data formats, and where it is located via URLs. A WSDL document defines types, messages, operations, bindings and services. Translators can generate code from WSDL or derive WSDL from existing code.
The document provides an overview of Java Messaging Services (JMS) in MuleSoft Mule ESB 3.6. It describes key JMS concepts like the JMS messaging model with queues and topics, backchannels, message filtering using selectors, transformers, and provides an example ActiveMQ configuration with inbound and outbound endpoints.
This document proposes enhancing Thrift to allow multiple services to be hosted on a single server port through multiplexing. It describes adding components like a Multiplexer processor that directs requests to the appropriate service based on a service context, a protocol wrapper that embeds the service context, and a registry for lookup of available services. This allows Thrift to better meet the needs of enterprises by reducing administrative overhead compared to hosting each service on a separate port.
Clustering technologies in Windows Server 2003 help achieve high availability and scalability for critical applications. Server clusters provide high availability by redistributing workloads from failed servers, while Network Load Balancing provides scalability and availability for web services by load balancing requests across multiple servers. The choice depends on whether applications have long-running in-memory state, with server clusters intended for stateful applications like databases and NLB for stateless applications like web servers.
Scalable Messaging is the the need of the enterprise messaging infrastructure. JBossA-MQ is one of the leading products for scalable messaging. It also covers some common concepts beween Apache Active MQ and JBoss A-MQ . Apache Camel as a integration framework supports the enterprise messaging greately and the presentation also contains some of its areas of adjunction to Scalable messaging with queues and topics.
The document discusses the open-source enterprise service bus Mule, including what Mule is, its core concepts like the universal message object and endpoints, and how Mule uses technologies like staged event-driven architecture and non-blocking I/O to move data between different systems and formats in a flexible way. It also provides examples of using Mule to move XML files between directories and handling exceptions.
Acceleration Technology: Solving File Transfer IssuesFileCatalyst
File transfer acceleration can significantly increase file transfer speeds compared to traditional methods like FTP. It works by transferring files over UDP instead of TCP, avoiding issues from network latency and packet loss that slow TCP transfers. This allows files to be sent at full network speed even over long distances or unreliable links. As a result, file transfer acceleration can reduce costs from unused bandwidth and boost productivity by speeding file sharing and project completion.
WSO2 ESB Introduction to Inbound EndpointsIsuru Udana
This document provides an introduction to inbound endpoints in WSO2 ESB. It discusses the key features and benefits of inbound endpoints, including dynamic configuration, multi-tenancy support, coordination in clustered environments, and direct message injection to mediation flows. Specific inbound endpoint types are described, including HTTP/HTTPS, JMS, and file inbound endpoints. Configuration parameters for each of these endpoint types are outlined. The presentation concludes with a demonstration of inbound endpoints.
This document summarizes a content delivery network (CDN) created to host video clips and live broadcasts. The CDN uses edge nodes located in different networks to serve traffic and origin nodes for storage. A redirector selects the best edge node based on location and load. Files are replicated across origin nodes and managed through a bridge that provides a WebDAV interface. Live broadcasts are supported through RTMP and plans include expanding support to additional streaming protocols and platforms.
MPEG DASH – Tomorrow's Format Today by Nicolas Weil
Senior Solutions Architect, Akamai Technologies & Will Law, Chief Architect, Media Cloud Engineering, Akamai Technologies
As an open standard designed to help simplify video delivery across connected devices, MPEG-DASH is continuing to gain momentum in the OTT, broadcast and wireless industries. Join Akamai's DASH experts for a discussion on what differentiates the emerging standard from legacy formats along with a demonstration showing the ease of deploying DASH playback across devices. The panel will also highlight current deployments, offer a review of the industry and provide a three-year outlook.
Akamai Edge is the premier event for Internet innovators, tech professionals and online business pioneers who together are forging a Faster Forward World. At Edge, the architects, experts and implementers of the most innovative global online businesses gather face-to-face for an invaluable three days of sharing, learning and together pushing the limits of the Faster Forward World. Learn more at: http://www.akamai.com/edge
The document provides information about the CCNA certification process and overview. It discusses that the CCNA exam costs $150, has a 90 minute time limit, and consists of 55-65 questions in various formats. It also lists recommended study books. It then provides a detailed overview of each layer of the OSI model, describing the functions and responsibilities of the application, presentation, session, transport, network, data link, and physical layers.
Plongée en eaux profondes dans l'architecture du nouvel Exchange 2013Microsoft Décideurs IT
Attention, session en anglais. Animée par Scott Schnoll, Principal Technical Writer dans l'équipe Exchange à Microsoft corp. Découvrez la nouvelle architecture des serveurs Exchange 2013. Cette nouvelle version apporte des nouveautés fondamentales et bénéficie de l'expérience de gestion du Cloud O365 par les équipes online. Des évolutions de l'architecture fondamentale d'Exchange découlent directement de ce retour d'expérience et ont été intégrées au produit. Venez découvrir celles-ci par l'expert mondial sur le sujet.
This document defines streaming protocols, compares mashups and portals, and describes different types of portals. It outlines several streaming protocols including RTSP, MMS, PNM, RTMP, and HTTP streaming. It also discusses protocol issues such as using UDP vs TCP and unicast vs multicast delivery. Mashups are described as combining content in new ways using APIs, while portals aggregate pre-existing content on servers. Finally, the document lists various types of portals including personal, business, news, government, and domain-specific portals.
RabbitMQ is an open-source message broker software written in Erlang. It uses exchanges to route messages from producers to queues based on routing keys or bindings. There are four main exchange types - direct, fanout, topic, and headers. Mule connects to RabbitMQ using the AMQP connector. It can send and receive messages to/from RabbitMQ queues using different exchange types like direct exchanges as demonstrated in the example config with two flows, one to send and one to receive a message.
This document discusses RSVP and differentiated services (DS) network models. It provides details on:
1) RSVP uses objects like INTEGRITY, SCOPE, and RESV_CONFIRM carried in messages to establish and maintain reservations. Messages include a common header followed by objects.
2) The DS model aggregates traffic by service level agreements rather than per-flow reservations. Packets are marked with DS field codepoints to receive different per-hop behaviors like expedited forwarding or assured forwarding.
3) DS routers classify and condition traffic at ingress based on DS fields and traffic agreements. Core routers provide behaviors like low latency for expedited forwarding or high assurance delivery for assured forwarding traffic within configured rates.
slides are about load balancing as a concept and implementation of load balancing on computer technical level
slides show the server load balancing
different architectures , algorithms and examples
1. O documento discute discordâncias em materiais cristalinos, defeitos que causam distorções na estrutura cristalina e afetam a deformação plástica e resistência mecânica.
2. As discordâncias se movimentam durante a deformação plástica, e a resistência pode ser aumentada restringindo seu movimento, por exemplo, reduzindo o tamanho de grão.
3. Vários tratamentos térmicos como recuperação e recristalização podem alterar as discordâncias e propriedades do material.
1. O documento discute os mecanismos de deformação plástica em metais, especificamente o movimento de discordâncias. 2. A deformação plástica ocorre principalmente pelo escorregamento de planos atômicos, que envolve o movimento de discordâncias. 3. Vários tratamentos como adição de ligas, redução do tamanho de grão e encruamento podem aumentar a resistência mecânica ao restringir o movimento de discordâncias.
O documento discute os principais tipos de defeitos em materiais cristalinos que influenciam a deformação plástica, incluindo discordâncias, maclações e falhas de empilhamento. Explica como o movimento de discordâncias depende de fatores como a estrutura cristalina, a orientação dos cristais e a presença de outros defeitos. Também aborda a termodinâmica por trás da geração e movimentação de defeitos durante a deformação.
O documento descreve processos de conformação de chapas metálicas como estampagem, estampagem profunda e hidroconformação. A estampagem é geralmente realizada a frio em chapas delgadas de aço, alumínio ou cobre. A estampagem profunda é feita em vários estágios usando punções, matrizes e sujeitadores para formar copos e caixas. A hidroconformação usa alta pressão hidráulica para formar peças tubulares complexas.
O documento discute os principais processos de conformação mecânica de metais, incluindo forjamento, laminação, trefilagem, extrusão e estampagem. Explica cada processo e como eles transformam a forma dos metais aplicando força externa para deformação plástica enquanto mantêm o volume e massa originais. O documento também discute trabalhos a quente e a frio durante a conformação mecânica.
O documento descreve os processos de estampagem, incluindo corte de chapas, conformação mecânica e estampagem profunda. A conformação mecânica envolve técnicas como dobramento, rebordamento e enrolamento para dar forma a peças de metal. A estampagem profunda cria objetos ocos de formato cilíndrico. O processo Guerin usa uma "almofada" de borracha ao invés de matriz rígida.
This document provides an introduction to using Mule, an open-source enterprise service bus (ESB). It discusses Mule's core concepts like the universal message object, endpoints, transports, connectors, routers, filters and transformers. It provides examples of using Mule to move files between directories and validate XML files against a schema. The document is intended to explain Mule's declarative approach and how data flows through various stages of receiving, routing, transforming and dispatching events.
This document provides an introduction to Mule, an open-source enterprise service bus (ESB). It discusses what Mule is, how to use it, and some of its core concepts. Mule uses technologies like staged event-driven architecture (SEDA) and Java NIO to process events and messages asynchronously and efficiently. The document then explains Mule concepts like endpoints, transports, connectors, routers, filters, transformers and the universal message object (UMO) that Mule uses to process events through its pipeline. It provides examples of using Mule with file endpoints and XML pipelines.
This document provides an introduction to Mule, an open-source enterprise service bus (ESB). It discusses what Mule is, how it can be used, and its core concepts. Mule uses technologies like staged event-driven architecture (SEDA) and Java NIO to facilitate integration. Core Mule concepts include endpoints, routers, filters, transformers, and the universal message object (UMO). The document also provides examples of using Mule for file processing and XML pipelines. It demonstrates how Mule handles normal processing as well as exceptions.
The document discusses the open-source enterprise service bus Mule, including what Mule is, its core concepts like the universal message object and endpoints, and how Mule uses technologies like staged event-driven architecture and non-blocking I/O to move data between different systems and formats in a flexible way. It also provides examples of using Mule to move XML files between directories and handling exceptions.
The document discusses the open-source enterprise service bus Mule, including what Mule is, its core concepts like the universal message object and endpoints, and how Mule uses technologies like staged event-driven architecture and non-blocking I/O to move data between different systems and formats in a flexible way. It also provides examples of using Mule to move XML files between directories and handling exceptions.
This document provides an introduction and overview of Mule, an open-source enterprise service bus (ESB). It discusses what Mule is, how it uses advanced technologies like staged event-driven architecture (SEDA) and Java NIO. The core concepts of Mule like the universal message object, endpoints, transports, connectors, routers, filters and transformers are explained. Examples are given of using Mule for file processing and XML pipelines. Exception handling in Mule is also covered.
This document provides an overview of Mule, an open-source enterprise service backbone. It discusses key Mule concepts like the universal message object, transports, connectors, routers, filters, transformers and the Mule event flow. It also covers how Mule uses staged event-driven architecture and Java NIO for advanced technologies. Specific examples are provided around using Mule with file endpoints and for XML pipelines. The document concludes with a discussion of exception handling in Mule.
This document provides an introduction to Mule, an open-source enterprise service backbone. It describes some of Mule's core concepts including its use of staged event-driven architecture (SEDA) and Java NIO for efficient I/O operations. Key components of Mule discussed include universal message objects (UMO), endpoints, transports, connectors, routers, filters and transformers. The document emphasizes Mule's declarative approach to specify what operations to perform rather than how to perform them.
The document discusses the open-source Mule Enterprise Service Bus (ESB). Mule is an ESB that uses a staged event-driven architecture (SEDA) and non-blocking Java NIO to move data between different endpoints and applications in a flexible way. The core Mule concepts include connectors that interface with endpoints, routers that route messages, filters that filter messages, and transformers that transform message formats.
This document provides an introduction and overview of Mule, an open-source enterprise service bus (ESB). It discusses what Mule is, how it is used, and its core concepts. Mule uses a staged event-driven architecture and Java NIO for advanced technologies. Core concepts covered include the universal message object, endpoints, transports, connectors, routers, filters, transformers, and the mule event flow. The document provides examples of using Mule with file endpoints and XML pipelines. It also discusses exception handling in Mule.
The document discusses the Enterprise Service Bus (ESB) Mule and its core concepts. Mule is an open-source ESB that uses advanced technologies like Staged Event-Driven Architecture (SEDA) and Java New Input/Output (NIO) to route messages between applications. It decomposes applications into stages connected by queues to improve performance. Mule's universal message object (UMO) allows messages to be received and sent from anywhere. Core concepts include endpoints, transports, connectors, routers, filters and transformers that define how messages flow through the system.
Mule is an open-source ESB that uses a staged event-driven architecture and non-blocking I/O. It allows components to be connected through queues and employs dynamic control to manage load. Mule configurations are defined through XML files and involve endpoints, routers, transformers and other components to route events through the ESB. Exceptions can be handled through defined exception strategies that redirect invalid messages.
The document provides an introduction to Mule, an open-source enterprise service backbone. It describes key Mule concepts like staged event-driven architecture (SEDA) and Java NIO, and how Mule uses these concepts to provide a scalable and modular integration platform. It also summarizes core Mule components like endpoints, routers, transformers and how they facilitate message flow and integration. XML examples are provided to demonstrate basic Mule configuration and exception handling.
Apache Camel is an open-source integration framework that allows applications to integrate various systems together. It uses Enterprise Integration Patterns to provide routing and mediation between endpoints. Camel supports various languages and has a large number of components for integration with different systems like files, databases, messaging systems etc. It allows configuration of routes using a simple domain specific language to perform operations like transforming messages, splitting/aggregating data between endpoints.
Mule is an open-source ESB that uses a staged event-driven architecture. It decomposes applications into stages connected by queues to improve performance. Mule also leverages Java NIO for efficient I/O operations using buffers, character encoding, regular expressions, and non-blocking channels. A Mule flow contains various components like endpoints, routers, transformers to receive, process and dispatch messages. Exception strategies define how errors are handled.
WSO2Con USA 2015: WSO2 Integration Platform Deep DiveWSO2
The world has become a system of connected components. Whether you are going to have breakfast at your favourite restaurant, watch a movie or book a sports event, everything is connected to provide you the best service. Connecting or integrating different systems has been a challenge for the IT industry for the last decade and it will be the same for coming decades. WSO2 provides the world’s fastest open source integration solution – the WSO2 ESB – to connect heterogeneous systems with each other.
This tutorial focuses on
- An in-depth knowledge of the high performance integration platform
- Its upcoming features
- Customer use cases to give you real life insights into the capabilities of the product
- It’s effect on your business
This document discusses web services and the service-oriented architecture. It begins by defining a web service as a network-accessible interface to application functionality built using standard Internet technologies. It then describes the key components of the web services technology stack, including discovery, description, packaging, transport, and network layers. Finally, it provides an overview of the steps to create a web services, including writing the web service method, describing it with WSDL, writing a proxy, and writing a client to invoke the proxy.
Introduction to the client server computing By Attaullah HazratAttaullah Hazrat
This document is a student's term paper on client server computing. It contains an introduction to client server models and discusses different types of servers like file servers, print servers, application servers, and more. It also describes the differences between thin and fat clients and servers, with the current trend being towards fat servers and thin clients. The document provides details on various aspects of client server systems for the student's course assignment.
The document provides an overview of web service architecture, including definitions of key concepts like SOAP, WSDL, and UDDI. SOAP defines the message format for web services communication. WSDL describes web services interfaces and operations. UDDI provides a registry for businesses to publish and discover web services. The architecture supports publishing services, finding services, and binding/invoking services at runtime.
Migrate from Oracle to Aurora PostgreSQL: Best Practices, Design Patterns, & ...Amazon Web Services
In this session, we show you how to set the source Oracle database environment, the target PostgreSQL environment, and parameter group configuration. We also recommended database parameters to disable foreign keys and triggers. Finally, we discuss best practices for using AWS Database Migration Service (AWS DMS) and AWS Schema Conversion Tool (AWS SCT) and show you how to choose the instance type and configure AWS DMS.
The Anypoint Connector DevKit enables the development of connectors that facilitate communication between third-party systems and Mule applications. It provides tools for visual design, implementation, testing, packaging and more using Anypoint Studio. Connectors act as an interface between a Mule application and an external resource like a database or API using various protocols. They are reusable components that simplify integration.
The document discusses various components in Mule ESB including the File, Database, Web Service, REST, and DataWeave components.
The File component allows exchanging files with the file system and can act as an inbound or outbound endpoint. The Database component connects to relational databases using JDBC to perform SQL operations. The Web Service component allows consuming and building web services. The REST component enables configuring Mule as a RESTful service. The DataWeave component replaces the DataMapper and uses a JSON-like language to transform data.
The document discusses various topics related to testing Mule applications including:
1. It describes different types of testing for Mule like unit testing, functional testing, integration testing, and performance testing.
2. It provides details on the unit testing framework in Mule, including base test classes for different components.
3. It discusses how to perform functional testing in Mule using the FunctionalTestCase and supporting classes like FunctionalTestComponent.
The document discusses Enterprise Service Bus (ESB) software, including popular ESB products from IBM, Tibco, Oracle, Sonic, Microsoft, Mule, Apache, and JBoss. It defines that an ESB is a modular architecture for designing and implementing interaction between software applications in a Service-Oriented Architecture (SOA). It also defines that SOA designs business functions as reusable software components or services, while an ESB handles communication and interaction between those services through mediation, routing, transformation, orchestration and conversion. The presentation concludes with thanking the audience.
The document describes implementing a loan broker application using Mule ESB. It involves receiving loan requests from clients over HTTP, enriching the request with credit profile data from a credit agency system, selecting potential lenders using a lender service, requesting loan quotes from bank systems, and returning the best quote to the client. Key aspects covered include the system components, message flow, design considerations using Mule transports and components, and how the application is implemented within Mule including message transformation and routing.
The HDFS connector allows bidirectional communication between applications and the Hadoop Distributed File System (HDFS). It requires a working Apache Hadoop server and Anypoint Studio. The connector configuration involves general options like the display name and operation. The connection tab specifies the connection key. The config reference specifies configuration properties like the file system name and pooling profiles with options like maximum connections. The reconnection tab sets strategies to reconnect if a connection fails.
Mule is a lightweight Java-based messaging framework that allows for integration of applications regardless of technology. It uses an enterprise service bus architecture to route messages between applications, handling interactions transparently across platforms and protocols. Mule represents application functionality as reusable services that process data through components, routers, and transports while transformers convert message formats as needed. This enables complex yet decoupled integration with various systems.
There are several ways to deploy Mule applications including:
1) Deploying to the Studio embedded test server for local testing.
2) Exporting the application from Studio as a zip file and deploying it to an enterprise Mule server for production.
3) Deploying directly to the Mule Management Console Application Repository to make the application available for deployment to multiple servers.
MuleSoft's Anypoint platform is an integration platform as a service (iPaaS) that includes tools like API Manager, API Portal, API Gateway, API Designer and connectors. The platform allows users to design APIs and integration flows using Anypoint Studio and then deploy them to Mule runtime engine for on-premises or cloud-based integration. It also includes services for security, scalability, reliability and high availability as well as management tools to administer APIs and integrations.
The document provides an overview of the Web Service Description Language (WSDL) which is an XML format for describing network services. It describes the key components of a WSDL document including the types, messages, portTypes, bindings and services sections. It also provides an example WSDL document and demonstrates how to create a web service and its corresponding WSDL.
This document discusses different types of pollution in the natural environment, focusing on air pollution. It defines air pollution as the presence of substances in the atmosphere that exceed natural levels and negatively impact living beings. Air pollutants come from natural sources like volcanoes and fires, as well as man-made sources such as factories, power plants, and automobiles. The document also outlines different approaches to reducing pollution, comparing cleaner production which prevents pollution at the source through efficient material use, to end-of-pipe treatment which focuses on treating existing waste and emissions.
This document discusses algorithm analysis and efficiency. It defines an algorithm as a step-by-step set of instructions to solve a problem with a definite end point. Algorithm analysis is important to establish if a given algorithm uses reasonable resources. Algorithm efficiency relates to the amount of computational resources used, and the goal is to minimize usage. The main measures of efficiency are time complexity, or how long an algorithm takes, and space complexity, or how much memory is needed. Less common measures include transmission size, external risk, response time, and total cost of ownership.
The E-Procure System aims to maintain tender details, employee details by department, and item information online. It allows customers to access tender documents online. The system generates reports automatically with granted tender details once a tender is closed. The least amount bidder will be awarded the tender. The system has modules for administrators, employees, purchase departments, and suppliers. Administrators maintain master data. Employees create indents for required products and check status. Purchase departments display indents and prepare tenders to invite suppliers. Suppliers bid on invited tenders and check tender statuses.
Discover the Power of ONEMONITAR: The Ultimate Mobile Spy App for Android Dev...onemonitarsoftware
Unlock the full potential of mobile monitoring with ONEMONITAR. Our advanced and discreet app offers a comprehensive suite of features, including hidden call recording, real-time GPS tracking, message monitoring, and much more.
Perfect for parents, employers, and anyone needing a reliable solution, ONEMONITAR ensures you stay informed and in control. Explore the key features of ONEMONITAR and see why it’s the trusted choice for Android device monitoring.
Share this infographic to spread the word about the ultimate mobile spy app!
Responsibilities of Fleet Managers and How TrackoBit Can Assist.pdfTrackobit
What do fleet managers do? What are their duties, responsibilities, and challenges? And what makes a fleet manager effective and successful? This blog answers all these questions.
In this talk, we will explore strategies to optimize the success rate of storing and retaining new information. We will discuss scientifically proven ideal learning intervals and content structures. Additionally, we will examine how to create an environment that improves our focus while you remain in the “flow”. Lastly we will also address the influence of AI on learning capabilities.
In the dynamic field of software development, this knowledge will empower you to accelerate your learning curve and support others in their learning journeys.
NBFC Software: Optimize Your Non-Banking Financial CompanyNBFC Softwares
NBFC Software: Optimize Your Non-Banking Financial Company
Enhance Your Financial Services with Comprehensive NBFC Software
NBFC software provides a complete solution for non-banking financial companies, streamlining banking and accounting functions to reduce operational costs. Our software is designed to meet the diverse needs of NBFCs, including investment banks, insurance companies, and hedge funds.
Key Features of NBFC Software:
Centralized Database: Facilitates inter-branch collaboration and smooth operations with a unified platform.
Automation: Simplifies loan lifecycle management and account maintenance, ensuring efficient delivery of financial services.
Customization: Highly customizable to fit specific business needs, offering flexibility in managing various loan types such as home loans, mortgage loans, personal loans, and more.
Security: Ensures safe and secure handling of financial transactions and sensitive data.
User-Friendly Interface: Designed to be intuitive and easy to use, reducing the learning curve for employees.
Cost-Effective: Reduces the need for additional manpower by automating tasks, making it a budget-friendly solution. Benefits of NBFC Software:
Go Paperless: Transition to a fully digital operation, eliminating offline work.
Transparency: Enables managers and executives to monitor various points of the banking process easily.
Defaulter Tracking: Helps track loan defaulters, maintaining a healthy loan management system.
Increased Accessibility: Cutting-edge technology increases the accessibility and usability of NBFC operations. Request a Demo Now!
Software development... for all? (keynote at ICSOFT'2024)miso_uam
Our world runs on software. It governs all major aspects of our life. It is an enabler for research and innovation, and is critical for business competitivity. Traditional software engineering techniques have achieved high effectiveness, but still may fall short on delivering software at the accelerated pace and with the increasing quality that future scenarios will require.
To attack this issue, some software paradigms raise the automation of software development via higher levels of abstraction through domain-specific languages (e.g., in model-driven engineering) and empowering non-professional developers with the possibility to build their own software (e.g., in low-code development approaches). In a software-demanding world, this is an attractive possibility, and perhaps -- paraphrasing Andy Warhol -- "in the future, everyone will be a developer for 15 minutes". However, to make this possible, methods are required to tweak languages to their context of use (crucial given the diversity of backgrounds and purposes), and the assistance to developers throughout the development process (especially critical for non-professionals).
In this keynote talk at ICSOFT'2024 I presented enabling techniques for this vision, supporting the creation of families of domain-specific languages, their adaptation to the usage context; and the augmentation of low-code environments with assistants and recommender systems to guide developers (professional or not) in the development process.
CViewSurvey Digitech Pvt Ltd that works on a proven C.A.A.G. model.bhatinidhi2001
CViewSurvey is a SaaS-based Web & Mobile application that provides digital transformation to traditional paper surveys and feedback for customer & employee experience, field & market research that helps you evaluate your customer's as well as employee's loyalty.
With our unique C.A.A.G. Collect, Analysis, Act & Grow approach; business & industry’s can create customized surveys on web, publish on app to collect unlimited response & review AI backed real-time data analytics on mobile & tablets anytime, anywhere. Data collected when offline is securely stored in the device, which syncs to the cloud server when connected to any network.
Explore the rapid development journey of TryBoxLang, completed in just 48 hours. This session delves into the innovative process behind creating TryBoxLang, a platform designed to showcase the capabilities of BoxLang by Ortus Solutions. Discover the challenges, strategies, and outcomes of this accelerated development effort, highlighting how TryBoxLang provides a practical introduction to BoxLang's features and benefits.
Overview of ERP - Mechlin Technologies.pptxMitchell Marsh
This PowerPoint presentation provides a comprehensive overview of Enterprise Resource Planning (ERP) systems. It covers the fundamental concepts, benefits, and key functionalities of ERP software, illustrating how it integrates various business processes into a unified system. From finance and HR to supply chain and customer relationship management, ERP facilitates efficient data management and decision-making across organizations. Whether you're new to ERP or looking to deepen your understanding, this presentation offers valuable insights into leveraging ERP for business success.
React and Next.js are complementary tools in web development. React, a JavaScript library, specializes in building user interfaces with its component-based architecture and efficient state management. Next.js extends React by providing server-side rendering, routing, and other utilities, making it ideal for building SEO-friendly, high-performance web applications.
React vs Next js: Which is Better for Web Development? - Semiosis Software Pr...
Mule overview
1. Copyright 2006-2009 Dan 1
M
D
The Enterprise Service Bus
Introduction using Mule
Introduction to Open-Source ESB
Authors: Dan McCreary and Arun Batchu
Date: 11/20/2006
Version: DRAFT 0.2
2. Copyright 2006-2009 Dan 2
M
D
Agenda
• What is Mule?
• How do you use Mule?
• What are the core Mule concepts?
• Learning mule with File endpoints
3. Copyright 2006-2009 Dan 3
M
D
Enterprise Service Backbone
• Mule is an open-source Enterprise Service
Backbone (ESB)
4. Copyright 2006-2009 Dan 4
M
D
Mule is Has Advanced
Technologies
• SEDA
– Staged Event-Driven Architecture
• Java NIO
– Java New Input/Output
5. Copyright 2006-2009 Dan 5
M
D
SEDA
• SEDA decomposes a complex, event-driven software application into a set
of stages connected by queues
• This design avoids the high overhead associated with thread-based
concurrency models, and decouples event and thread scheduling from
application logic
• By performing admission control on each event queue, the service can be
well-conditioned to load, preventing resources from being overcommitted
when demand exceeds service capacity
• SEDA employs dynamic control to automatically tune runtime parameters
(such as the scheduling parameters of each stage) as well as to manage
load, for example, by performing adaptive load shedding
• Decomposing services into a set of stages also enables modularity and code
reuse, as well as the development of debugging tools for complex event-
driven applications
6. Copyright 2006-2009 Dan 6
M
D
Java NIO
• NIO is a collection of Java programming language APIs
that offer advanced features for intensive I/O operations
• NIO facilitates an implementations that can directly use
the most efficient operations of the underlying platform
• NIO includes:
– Buffers for data of primitive types
– Character set encoders and decoders
– A pattern-matching facility based on Perl-style regular expressions
(in package java.util.regex)
– Channels, a new primitive I/O abstraction
– A file interface that supports locks and memory mapping
– A multiplexed, non-blocking I/O facility for writing scalable
servers
7. Copyright 2006-2009 Dan 7
M
D
Mule’s “Moves Things Around”
• Folder to folder
• Queue to queue
• Shared memory to shared memory
• Using different types of transports
• In a flexible way
8. Copyright 2006-2009 Dan 8
M
D
XML Pipeline
• An XML pipeline is a series of operation
that are performed on one or more XML
files
• Examples include:
– validate
– transform
– prune (remove nodes)
– split (break a single XML file into many files)
– merge (join two or more files together)
9. Copyright 2006-2009 Dan 9
M
D
CRV Example
• Flow of XML document through approval
processes
Submit
CRV
Deed
Matched
CRV
SSN
Stripped
CRV
Income
Tax
Audit
County
Audit
County
Approval
State
Audit
State
Approval
10. Copyright 2006-2009 Dan 10
M
D
Decomposition
• Example of XML Operations used on CRV
Validate Split
Remove
SSN
Element
Store
Modify
Value
Add
Element
Modify
Value
Add
Element
11. Copyright 2006-2009 Dan 11
M
D
Declarative Approach
• Focus on specifying "What" not "How"
• Empower business analysis to write
machine-readable specifications
• Hide the "How" behind services with clear
interfaces (SOA)
12. Copyright 2006-2009 Dan 12
M
D
Core Mule Concepts
• Mule Manager
• Mule Model
• Universal Message Object (UMO)
• Endpoints
• External Applications
13. Copyright 2006-2009 Dan 13
M
D
Universal Message Object (UMO)
• A UMO is a type of Java object that can
– receive events "from anywhere"
– send events
• UMO Components are usually your business
objects. They are components that execute
business logic on an incoming event
• UMO are standard JavaBeans (containers)
• There is no Mule-specific code in your
components
• Mule handles all routing and transformation of
events to and from your objects based on the
configuration of your component
14. Copyright 2006-2009 Dan 14
M
D
Transport
• A transport or "provider", is a set of objects
that add support to Mule to handle a
specific kind of transport or protocol
• Examples
– the "Email Provider" enables Mule to send and
receive messages via the SMTP, POP and
IMAP protocols
15. Copyright 2006-2009 Dan 15
M
D
Connector
• A connector is the object that sends and
receives messages on behalf of an endpoint.
• Connectors are bundled as part of specific
transports or providers.
• For example, the FileConnector can
read and write file system files.
16. Copyright 2006-2009 Dan 16
M
D
Router
• A router is the object that do something
with messages once they have been
received by a connector, or prior to being
sent out by the connector
17. Copyright 2006-2009 Dan 17
M
D
Filter
• A filter optionally filters incoming or outgoing
messages that are coming into or going out from a
connector.
• For example, the File Provider comes with a
FilenameWildcardFilter that restricts
which files are read by the connector based on file
name patterns. For example only files with the
.xml extension can be routed.
• Filters are used in conjunction with Routers.
18. Copyright 2006-2009 Dan 18
M
D
Transformer
• A transformer optionally changes incoming
or outgoing messages in some way
• This is usually done to make the message
format useable by a downstream function
• Examples:
– the ByteArrayToString transformer converts
byte arrays into String objects.
19. Copyright 2006-2009 Dan 19
M
D
Mule Event Flow
• The nine stages of a
mule event
– first 2 – inbound
– middle 4 –
component
– last 2 – outbound
Endpoint
(Message Receiver)
Endpoint
(Message Dispatcher)
Inbound Router
Outbound Router
Inbound Transformer
Outbound Transformer
Interceptor
Service Invocation
Interceptor
Inbound
Component
Outbound
Optional Step
20. Copyright 2006-2009 Dan 20
M
D
Message Receiver Endpoint
• Some event triggers a
message flow
– A file being written into a
folder
– A message arriving on a
message queue
– A record in a database
– Data written to a socket
Endpoint
(Message Dispatcher)
Inbound Router
Outbound Router
Inbound Transformer
Outbound Transformer
Interceptor
Service Invocation
Interceptor
Endpoint
(Message Receiver)
21. Copyright 2006-2009 Dan 21
M
D
Inbound Router
• The inbound router is the fist step in a
message. Functions typically
performed by an inbound router
– Filtering
– Remove duplicate messages
– Matching messages
– Aggregation (combining)
– Re-sequence data
– Forwarding
• See also
– IdempotentReceiver
– CorrolationAggregator
– CorrelationResequencer
Endpoint
(Message Dispatcher)
Inbound Router
Outbound Router
Inbound Transformer
Outbound Transformer
Interceptor
Service Invocation
Interceptor
Endpoint
(Message Receiver)
22. Copyright 2006-2009 Dan 22
M
D
Interceptor
• Used to intercept message flow
into your service component
• Used trigger monitor/events or
interrupt the flow of the message
• Example: an authorization
interceptor could ensure that the
current request has the correct
credentials to invoke the service.
Endpoint
(Message Dispatcher)
Inbound Router
Outbound Router
Inbound Transformer
Outbound Transformer
Service Invocation
Interceptor
Endpoint
(Message Receiver)
Interceptor
23. Copyright 2006-2009 Dan 23
M
D
Inbound Transformer
• If the inbound data is
not in the correct
format for the
service it must be
transformed at this
point
Endpoint
(Message Receiver)
Endpoint
(Message Dispatcher)
Inbound Router
Outbound Router
Outbound Transformer
Interceptor
Service Invocation
Interceptor
Inbound Transformer
24. Copyright 2006-2009 Dan 24
M
D
Service Invocation
• The actual service is
performed
• In mule, this is generally a
Java object
• Service invocation can also
be a "pass through"
Endpoint
(Message Receiver)
Endpoint
(Message Dispatcher)
Inbound Router
Outbound Router
Outbound Transformer
Interceptor
Interceptor
Inbound Transformer
Service Invocation
25. Copyright 2006-2009 Dan 25
M
D
Outbound Router
• Dispatching the data
to all the relevant
endpoints
Endpoint
(Message Receiver)
Endpoint
(Message Dispatcher)
Inbound Router
Outbound Transformer
Interceptor
Interceptor
Inbound Transformer
Service Invocation
Outbound Router
26. Copyright 2006-2009 Dan 26
M
D
Built-in Router Classes
Inbound Outbound Response
Idempotent Receiver Filtering Outbound Router Response Aggregator
Selective Consumer Recipient List
Aggregator Multicasting Router
Resequencer Chaining Router
Forwarding Consumer Message Splitter
Filtering List Message
Splitter
Filtering Xml Message
Splitter
Exception Based Router
27. Copyright 2006-2009 Dan 27
M
D
Outbound Transformer
• Any transformations that needs to be
done on the message after a service
has been performed on the message
can be executed before it is put into
the endpoint
• See Also
– EnvelopeInterceptor
Endpoint
(Message Receiver)
Endpoint
(Message Dispatcher)
Inbound Router
Interceptor
Interceptor
Inbound Transformer
Service Invocation
Outbound Router
Outbound Transformer
29. Copyright 2006-2009 Dan 29
M
D
Omitted From Examples for Brevity
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE mule-configuration PUBLIC "-//MuleSource
//DTD mule-configuration XML V1.0//EN"
"http://mule.mulesource.org/dtds/mule-
configuration.dtd">
30. Copyright 2006-2009 Dan 30
M
D
Outline of Move All Files
<mule-configuration>
<model>
<mule-descriptor>
<inbound-router>
<endpoint
address="file:///c:/mule-class/in"/>
</inbound-router>
<outbound-router>
<router>
<endpoint
address="file:///c:/mule-class/out"/>
</router>
</outbound-router>
</mule-descriptor>
</model>
</mule-configuration>
32. Copyright 2006-2009 Dan 32
M
D
Only Moving XML Files
<inbound-router>
<endpoint address="file:///c:/mule-class/in">
<filter pattern="*.xml"
className=
"org.mule.providers.file.filters.FilenameWildcardFilter"/>
</endpoint>
</inbound-router>
Add the filter line to only move files with the extension
"*.xml". If you add a file "foobar.txt to the input folder it
will not be moved.
33. Copyright 2006-2009 Dan 33
M
D
Keeping the Name The Same
<outbound-router>
<router
className="org.mule.routing.outbound.OutboundPassThroughRouter">
<endpoint
address=
"file:///c:/mule-class/out?outputPattern=$[ORIGINALNAME]"
/>
</router>
</outbound-router>
Add the outputPattern parameter to keep the output
name the same as the input.
34. Copyright 2006-2009 Dan 34
M
D
Happy Path and Exceptions
• By default, error free documents follow a central path known as
the "happy path"
• Documents that have errors may be handled in different ways
(rejected, warnings etc.)
Start StopStep 1 Step 2 Step 3
Stop Stop Stop
35. Copyright 2006-2009 Dan 35
M
D
Exception Handling
• Mule has a special way of handling non-happy path processing. This
is called an "Exception Strategy" but is it really just and exception
path and there is very little strategy involved.
• There are three places you can associate an exception strategy
– connector
– component
– model (set for all components in a model)
36. Copyright 2006-2009 Dan 36
M
D
Exception Strategy
<exception-strategy
className=org.mule.impl.DefaultComponentExceptionStrategy">
<endpoint address="file:///c:/mule-class/error"/>
</exception-strategy>
We want all invalid documents to be moved into the
error folder.
37. Copyright 2006-2009 Dan 37
M
D
Sample XML
<?xml version="1.0" encoding="UTF-8"?>
<Data>
<Element1>Hello World!</Element1>
<Element2>String</Element2>
<Element3>String</Element3>
<DansInvalidDataElement>This is Dans invalid data element</DansInvalidDataElement>
</Data>
XML Schema validation will generate an error message
when it gets to the fourth invalid data element:
Given the following XML Schema file:
38. Copyright 2006-2009 Dan 38
M
D
Validating against an XML Schema
<outbound-router>
<router className="org.mule.routing.outbound.FilteringXmlMessageSplitter">
<endpoint
address="file:///c:/mule-class/out?outputPattern=$[ORIGINALNAME]"/>
<properties>
<property name="validateSchema" value="true"/>
<property name="externalSchemaLocation"
value="file:///c:/mule-class/labs/07-validate/my-
schema.xsd"/>
</properties>
</router>
</outbound-router>
To validate the XML Schema, just add two properties:
1) tell it to validate the document
2) tell it what file to use and where to find it
39. Copyright 2006-2009 Dan 39
M
D
Error Message
document : cvc-complex-type.2.4.d: Invalid content was found
starting with element 'DansInvalidDataElement'. No child
element is expected at this point.
This error message is generated on the Mule console
when an invalid data element is found. But what should
we do with it? How do we redirect it to the appropriate
user?
40. Copyright 2006-2009 Dan 40
M
D
Thank You!
Please contact me for more information:
• Enterprise Service Bus
• Enterprise Integration
• Metadata Management
• Metadata Registries
• Service Oriented Architectures
• Business Intelligence and Data Warehouse
• Semantic Web
Dan McCreary, President
Dan McCreary & Associates
Metadata Strategy Development
dan@danmccreary.com
(952) 931-9198