Shared Context is a type of context which is present in the SMO. Shared Context is mainly used when we are using Aggregation process where we need to Iterate the BO for Certain times. The Content data which is present in the shared context BO does not persist across Request and Response flows i. What is Transient Context? Transient Context: Used for passing values between Mediation primitives within the current flow — either the request flow or the responses flow. The transient context cannot link requests and responses and hence cannot be used across.
|Published (Last):||10 June 2005|
|PDF File Size:||10.7 Mb|
|ePub File Size:||18.49 Mb|
|Price:||Free* [*Free Regsitration Required]|
Question 1. What Is Mule? Answer : Mule is a lightweight event-driven enterprise service bus ESB and an integration platform. It is a lightweight and modular solution that could scale from an application-level messaging framework to an enterprise-wide highly distributable object broker. Question 3. Why Mule Was Designed? These modules would provide support for a wide range of transports or add extra features, such as distributed transactions, security, or management.
Mule was also designed as a programmatic framework offering programmers the means to graft additional behavior such as specific message processing or custom data transformation.
Question 4. Why The Name Mule? Answer : There is a lot of infrastructure work to be done before we can really start thinking about implementing any logic. A Mule is also commonly referred to as a carrier of load, moving it from one place to another.
The load it specializes in moving is our enterprise information. Question 5. It is unremarkably based on their middleware technologies and is usually at the core of a much broader SOA product suite. Question 6. Answer : Prescriptive deployment model, whereas Mule supports a wide variety of deployment strategies. Mainly focused on higher-level concerns, whereas Mule deals extensively with all the details of integration.
Comprehensive documentation, a subject on which MuleSource has made huge progress recently. Question 7. Answer : The first logical layer is the model layer. A Mule model represents the runtime environment that hosts services.
It defines the behavior of Mule when processing requests handled by services. The model provides services with supporting features, such as exception strategies. It also provides services with default values that simplify their configuration.
Question 8. Answer : A Mule service is composed of all the Mule entities involved in processing particular requests in predefined manners. A service is defined by a specific configuration. This configuration determines the different elements, from the different layers of responsibility, that will be mobilized to process the requests that it will be open to receive.
Depending on the type of input channel it uses, a service may or may not be publicly accessible outside of the ESB. Question 9. Answer : The transport layer is in charge of receiving or sending messages. This is why it is involved with both inbound and outbound communications. A transport manifests itself in the configuration by the following elements: connectors, endpoints and transformers.
A transport also defines one message adapter. A message adapter is responsible for extracting all the information available in a particular request data, meta information, attachments, and so on and storing them in transport-agnostic fashion in a Mule message. Question What Is Connector In Mule? Answer : A connector is in charge of controlling the usage of a particular protocol. It is configured with parameters that are specific to this protocol and holds any state that can be shared with the underlying entities in charge of the actual communications.
What Is Endpoint In Mule? Hence it controls what underlying entities will be used with the connector they depend on. The target destination itself is defined as a URI. What Is Transformer In Mule? Answer : A transformer takes care of translating the content of a message from one form to another. It is possible to chain transformers to cumulate their effects. Transformers can kick in at different stages while a message transits through a service.
What Is Router In Mule? Answer : Routers play a crucial role in controlling the trajectory a message will follow when it transits in Mule. They are the gatekeepers of the endpoints of a service, taking care of keeping messages on the right succession of tracks so they can reach their intended destinations. Certain routers act like the big classification yards: they can split, sort, or regroup messages based on certain conditions.
What Is Filter In Mule? Answer : Filters are a powerful complement to the routers. Filters provide the brains routers need to make smart decisions about what to do with messages in transit. Some filters go as far as deeply analyzing the content of a message for a particular value on which their outcome will be based. What Is Component In Mule? Each service is organized with a component at its core and inbound and outbound routers around it.
Components are used to implement a specific behavior in a service. This behavior can be as simple as logging messages or can go as far as invoking other services.
Components can also have no behavior at all; in that case they are pass-through and make the service act as a bridge between its inbound and outbound routers. Answer : A Mule message is composed of different parts: The payload, which is the main data content carried by the message. Optionally, multiple named attachments, to support the notion of multipart messages. Optionally, an exception payload, which holds any error that occurred during the processing of the event.
Answer : Mule uses configuration builders that can translate a human-authored configuration file into the complex graph of objects that constitutes a running node of this ESB. The main builders are of two kinds: a Spring-driven builder, which works with XML files, and a script builder, which can accept scripting language files.
Mule ESB Interview Questions & Answers
Question 1. What Is Mule? Answer : Mule is a lightweight event-driven enterprise service bus ESB and an integration platform. It is a lightweight and modular solution that could scale from an application-level messaging framework to an enterprise-wide highly distributable object broker.
Fuse ESB Interview Questions & Answers
There are lot of opportunities from many reputed companies in the world. According to research MuleSoft has a market share of about 5. Overview What is ESB? An enterprise service bus ESB is software architecture for middleware that provides fundamental services for more complex architectures.
ESB interview questions
What are the advantages of using an ESB? Subscribe to our youtube channel to get new updates..! High level of operational control from the central web-based portal. Wide range of connectivity through more than leading SaaS-based applications on-premises. Ensuring zero message loss reliability and gives you high availability.
Mulesoft Interview Questions And Answers For Experienced
What Is Mule? Ans: Mule is a lightweight event-driven enterprise service bus ESB and an integration platform. It is a lightweight and modular solution that could scale from an application-level messaging framework to an enterprise-wide highly distributable object broker. What Difficulties Mule Does Encompass? Ans: Transport: applications can accept input from a variety of means, from the file system to the network. Data format: speaking the right protocol is only part of the solution, as applications can use almost any form of representation for the data they exchange. Invocation styles: synchronous, asynchronous, or batch call semantics entail very different integration strategies.