Interview Questions.

Top 100+ Ibm Websphere Esb Interview Questions And Answers

fluid

Top 100+ Ibm Websphere Esb Interview Questions And Answers

Question 1. What Is Esb?

Answer :

An organisation carrier bus (ESB) is software program architecture for middleware that offers fundamental services for extra complicated architectures. For example, an ESB includes the features required to put into effect a provider-oriented architecture (SOA). In a wellknown experience, an ESB can be concept of as a mechanism that manages get right of entry to to packages and offerings (especially legacy variations) to give a single, simple, and regular interface to cease-customers through Web- or forms-primarily based customer-aspect the front ends.

Question 2. What Is The Functionality Of Fan-in And Fan-out?

Answer :

Fan-out:We can use the Fan Out primitive to hearth the output terminal once (with the  enter message) or to hearth the output terminal more than one instances. You can use Fan Out in isolation or as a part of a Fan Out and Fan In combination.

Fan-In: Fan In is continually partnered with a Fan Out in the identical waft and acts   as a choice point for when to continue go with the flow execution. It gets a number of messages until a selection factor is reached, at which factor the last message to be received is propagated to the output terminal. The Fan In primitive may also best be utilized in mixture with Fan Out. 

IBM Websphere Interview Questions
Question 3. What Are All The Configurations Required For Jdbc Adapter Implementation?

Answer :

Data Source want to be created and need to configure with DB. If we have safety, then need to created protection authentication.

Question 4. Different Between Sdo And Smo?

Answer :

SDO: Service Data Object is the representation of the variable or Object.

SMO: The SMO version is a pattern for the usage of SDO Data Objects to represent messages

IBM Websphere Tutorial
Question 5. Difference Between Stop And Fail?

Answer :

Stop: Stops a specific path within the go with the flow, without generating an exception.

Fail: Generates a failure in the flow.

MySQL Interview Questions
Question 6. How Can You Change The Runtime Changes Using Mediation Primitive?

Answer :

We have destiny referred to as Promotable properties in ESB. We can configure this future even as improvement. Then we can make it modified at runtime with out restarting  the server it can be posted.

Question 7. What Are All The Primitives Used In Mediation?

Answer :

We have different sorts of primitives in mediation.

Message Filter

Type Filter
Endpoint Lookup
Service Invoke
Fan-out
Fan-in
XSLT
BO Map
Message Element Setter
DB research
Data Handler
Custom Mediation
Header Setters
Message Logger
Even Emitter
Stop
Fail
Sub Flow
MySQL Tutorial IBM WebSphere Administration Interview Questions
Question eight. What Is Smo? And Wt It Contains?

Answer :

The SMO version is a pattern for using SDO Data Objects to represent messages.

The SMO carries a representation of the following organizations of facts:

The business payload of the message. The payload is the application data exchanged among service endpoints.
Header data associated with the message. For example, Java Message Service (JMS) headers if a message have been conveyed the use of the JMS API.
Context facts (records apart from the message payload).
Question 9. What Are Shared, Transient And Correlation Context?

Answer :

1. Shared Context: Context is a temporary region which is created together with   Service Message Object (SMO) within the Mediation Flows. Shared Context is a sort of context which is present within the SMO. Shared Context is especially used   while we are using Aggregation process wherein we want to Iterate the BO for Certain times. Shared Context keeps Aggregation facts among Aggregation (FanOut and FanIn) primitives. The Content (facts) that is gift inside the shared context BO does not persist across Request and Response flows i.E The Data within the Shared Context which is utilized in Request drift can't be used again in Response drift.

2. Transient Context: Used for passing values between Mediation primitives within the present day float — both the request glide or the responses waft. The brief context can not link requests and responses and for this reason cannot be used across.

Used whilst you need to store an enter message earlier than a service invokes call(inside a request or response float). After the services invoke name, the next primitive can create another message through combining the service invoke response and the authentic message stored inside the transient context.

Three. Correlation Context: Used while Mediation primitives need to skip values from the request glide to the response drift. Used to skip values from the request message onto the response.

IBM Websphere Application Server Interview Questions
Question 10. Difference Between Callout And Service Invoke?

Answer :

Service Invoke: The Service Invoke primitive is used to make a provider request in both a request or response mediation flow. The carrier can be Request/Response or One-Way. Multiple instances of the Service Invoke primitive are accredited in a waft, permitting a series of service invocations to be achieved. 

Callout: The Callout gets the message and calls the asked provider and operation. There is a Callout node for every connected target operation within the mediation waft.

If the call is a success, the Callout Response node inside the reaction flow receives the reaction message.
If the call is unsuccessful, the Callout may be set to retry carrier invocations depending on the form of fault acquired.
Question 11. How Can You Implement Loop In Mediation?

Answer :

By the use of Fan-in and Fan-out primitive.

IBM WebSphere MQ Interview Questions




CFG