UNIT-II

TWO MARKS
1.Draw the pattern diagram for integration style?

2.What is scatter-gather?
In the order processing example introduced in the previous patterns , each order item that is
notcurrently in stock could be supplied by one of multiple external suppliers. However, the suppliers may or
may not have the respective item in stock themselves, they may charge a different price and may be able to
supply the part by a different date. To fill the order in the best way possible, we should request quotes from all
suppliers and decide which one provides uswith the best term for the requested item.

3.Need for enterprise integration?

First of all, writing business applications is hard. Creating a single, big application to run a
complete business is next to impossible. The ERP vendors have had some success at creating
larger-than-ever business applications. The reality, though, is that even the heavyweights like

SAP, Oracle, Peoplesoft and the like only perform a fraction of the business functions required in
a typical enterprise. We can see this easily by the fact that ERP systems are one of the most
popular integration points in todays enterprises.
Second, spreading business functions across multiple applications provides the business with the
flexibility to select the best accounting package, the best customer relationship management
or the order processing system that best suits the business needs. One-stop-shopping for
enterprise applications is usually not what IT organizations are interested in, nor is possible
given the number individual business requirements.

4.What is correlation?
One of the key differences between asynchronous messaging architectures and synchronous, callstack based architectures is the fact that we have to work with a thinner safety net when building
asynchronous solutions. For example, in synchronous applications the call stack keeps track of the return
address and local variables so that we never have to worry about which method to return to and what the
local state of that method was. Asynchronous architectures do not provide such mechanisms so that we
have to track state and return addresses ourselves. A key mechanism to regaining local state is the notion
of Correlation.

17. Comparisons between notification and application.

18. Draw the pattern for Publish/Subscribe using the Pull Model?

19. What is mean by messaging gateway?

The Messaging Gateway encapsulates messaging-specific code (e.g., the code required to send or
receive a message) and separates it from the rest of the application code. This way, only the
Messaging Gateway code knows about the messaging system; the rest of the application code
does not. The Messaging Gateway exposes a business function to the rest of the application so
that instead of requiring the application to set properties like
Message.MessageReadPropertyFilter.AppSpecific, a Messaging Gateway exposes methods such
as GetCreditScore that accept strongly typed parameters just like any other method. A Messaging
Gateway is a messaging-specific version of the more general Gateway pattern.

20. What are the patterns available for message transformation?

Message transformation is a deep topic in integration. Message Channels and Message Routers
can remove basic dependencies between applications by eliminating the need for one application
to be aware of the other's location.
One application can send a message to a Message Channel and worry about what application
will consume it. However, message formats impose another set of dependency. If one application
has to format messages in another application's data format, the decoupling in form of the
Message Channel is somewhat of an illusion. Any change to the receiving application or the
switch from one receiving application to another still requires a change to the sending
application.
Message Translators help remove this dependency. Due to the importance of message formats
and the transformation between them, we can view any integration solution as two parallel
systems. One deals with actual message data, the other one with metadata, the data that describes
message data. Many of the patterns used in creation of the message flow can also be used to
manage metadata.