please type in english.

if u are a developer no need to answer this question because
as a developer we cannot have the chance to test.

Mapping is the process of performing transformations to 
resolve data representation differences between services or 
document formats. By linking variables to each other on the 
Pipeline tab, you can accomplish name transformations and 
structural transformations. However, to perform value 
transformations you must execute some code or logic. 
Developer provides two ways for you to invoke services: You 
can insert INVOKE steps or you can insert transformers onto 
the Pipeline tab. Transformers are the services you use to 
accomplish value transformations on the Pipeline tab.

When we are performing only one data operation we can go 
ahead with directly invoking the corresponding flow 
service. If we want to perform the multiple operations in a 
single step, it is good to go with transformers in a map 
step. This increases the memory usage and readability.

Transformer emcompass mapping logic. Flow Service can be 
implemented as a trsndsformer.

Both invoking Flow services and 
transformers can be used to provide the same functionality,
but there are certain differences
In case of transformers the order of execution 
is not strict(i.e the order of transformer execution)
is not determined and multiple transformers can be 
executed at the same time.
And also transformers cannot be used whenever the
underlying data structure dimension is different(for ex: 
can't execute a transformer on a document when iterating 
over a loop on a document list)

Services that you insert using the INVOKE step might also 
perform value transformations. However, only transformers 
can accomplish multiple value transformations in a single 
flow step.

Usually the brokers like WebSphere ICS,WAS are built on J2EE
technology

There is an adapter for each application which helps to
interact respective application with the integration broker

Hi Adapters are used for connecting different vendors.for 
each application there wil be adapters

Integration is nothing but integrating different
applications softwares like SAP, Oracle, PeopleSoft, Seibel
etc. which belongs to different vendors.

integration is sharing and transaction data between entity 
is nothing appalication customer

integration nothing but shating and transaction data 
between entity. 
entity nothing people and company
ex:defferent appl like oracle , sap , seibel

Integration is binding of different applications, may 
belongs to different vendors together to achieve effective 
communication and sharing of data.

EAI is Enterprise Application Integration. 

Tools used are: WebSphere ICS, WebSphere MQ series,
WebSphere Application Server, Tibco, Seebeyond, Vitria etc.

also IBM product  DATAPOWER XI50

Why isn't Biztalk been listed? :(

EAI = Enterprise Application Integration.
Tools: Biztalk, Webmethods, SeeBeyond, TIBCO, Vitria etc

EAI is Enterprise Application Integration. 

Tools used are: WebSphere ICS, WebSphere MQ series,
WebSphere Application Server, Tibco, Seebeyond, Vitria etc.
 SAP XI.

Enterprise Application Integration (EAI) is the integration 
of new application software such as middleware tools with 
existing software which provides the functionality that 
supports the enterprise’s business processes. 

A framework which allows rapid development and Reuse of 
interfaces among Disparate enterprise systems by achieving 
isolation of business logic and improved administrative 
control.

There are basically two architecture HUB & SPOKE/BUS. Based 
on that various integration tools are vailable in the 
martket. Few of them are-

1) Hub & Spoke architecture- WebMethods – Integration 
Platform, Vitria Technology – BusinessWare, WBI – 
Collaborators, Connectors  
2) Bus architecture- Tibco Active Enterprise , SeeBeyond 
eGATE Integrator

webMethods Modeler is a graphical tool for building a 
business process model and
executing the model. After you create the business process 
model, you can elect to
generate the run‐time components needed to execute the 
model in the underlying
webMethods integration platform.
You can build process models that bring together data from 
diverse sources in your
Enterprise such as:
�� Internal systems and applications
�� Databases and data warehouses
�� Trading Partners
�� Web services
�� Mainframes
�� Workflows (human interactions)