YouTube Icon

Interview Questions.

Ibm Websphere Esb Placement Papers - Ibm Websphere Esb Interview Questions and Answers - Jul 28, 2022

fluid

Ibm Websphere Esb Placement Papers - Ibm Websphere Esb Interview Questions and Answers

Q1. Different Between Sdo And Smo?

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

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

Q2. How Can You Implement Loop In Mediation?

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

Q3. What Is Smo? And Wt It Contains?

The SMO model is a sample for using SDO Data Objects to symbolize messages.

The SMO incorporates a representation of the subsequent agencies of facts:

The enterprise payload of the message. The payload is the software facts exchanged among carrier endpoints.

Header information related to the message. For instance, Java Message Service (JMS) headers if a message have been conveyed the usage of the JMS API.

Context statistics (statistics apart from the message payload).

Q4. What Are All The Configurations Required For Jdbc Adapter Implementation?

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

Q5. Difference Between Stop And Fail?

Stop: Stops a selected direction in the glide, with out generating an exception.

Fail: Generates a failure inside the flow.

Q6. What Are All The Primitives Used In Mediation?

We have distinctive varieties 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

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

Fan-out:We can use the Fan Out primitive to hearth the output terminal once (with the  input message) or to fireplace the output terminal multiple times. You can use Fan Out in isolation or as part of a Fan Out and Fan In combination.

Fan-In: Fan In is usually partnered with a Fan Out in the same float and acts   as a decision factor for while to retain flow execution. It gets a number of messages until a decision factor is reached, at which factor the final message to be obtained is propagated to the output terminal. The Fan In primitive may additionally best be utilized in combination with Fan Out. 

Q8. How Can You Change The Runtime Changes Using Mediation Primitive?

We have future referred to as Promotable homes in ESB. We can configure this destiny even as development. Then we are able to make it changed at runtime without restarting  the server it may be published.

Q9. What Are Shared, Trient And Correlation Context?

@Shared Context: Context is a brief vicinity that's created along side   Service Message Object (SMO) within the Mediation Flows. Shared Context is a type of context that is gift inside the SMO. Shared Context is specially used   when we're using Aggregation technique in which we need to Iterate the BO for Certain times. Shared Context keeps Aggregation data between Aggregation (FanOut and FanIn) primitives. The Content (records) that is present within the shared context BO does now not persist throughout Request and Response flows i.E The Data inside the Shared Context that's used in Request drift can not be used once more in Response float.

@Trient Context: Used for passing values between Mediation primitives inside the modern-day drift — both the request waft or the responses drift. The trient context can not link requests and responses and as a result can't be used across.

Used whilst you need to shop an input message before a provider invokes call(inside a request or response waft). After the services invoke call, the subsequent primitive can create every other message by combining the provider invoke reaction and the unique message saved inside the trient context.

@Correlation Context: Used while Mediation primitives need to pass values from the request drift to the response waft. Used to skip values from the request message onto the response.

Q10. What Is Esb?

An business enterprise service bus (ESB) is software program architecture for middleware that gives fundamental offerings for more complex architectures. For example, an ESB carries the features required to implement a carrier-oriented structure (SOA). In a standard sense, an ESB can be thought of as a mechanism that manages get admission to to packages and offerings (especially legacy variations) to give a single, simple, and constant interface to stop-customers via Web- or paperwork-based client-facet the front ends.

Q11. Difference Between Callout And Service Invoke?

Service Invoke: The Service Invoke primitive is used to make a service request in both a request or reaction mediation go with the flow. The service may be Request/Response or One-Way. Multiple times of the Service Invoke primitive are accepted in a waft, permitting a sequence of carrier invocations to be completed. 

Callout: The Callout receives the message and calls the requested carrier and operation. There is a Callout node for each related goal operation within the mediation glide.

If the decision is a hit, the Callout Response node inside the reaction glide gets the reaction message.

If the decision is unsuccessful, the Callout can be set to retry carrier invocations depending on the type of fault obtained.




CFG