InterviewSolution
This section includes InterviewSolutions, each offering curated multiple-choice questions to sharpen your knowledge and support exam preparation. Choose a topic below to get started.
| 51. |
What Is The Uniqueness Of Mb Over Ics? |
|
Answer» Parallel processing |
|
| 52. |
Use Of Configmanager? |
|
Answer» To DEPLOY the MESSAGE FLOWS ONTO the BROKER. To deploy the message flows onto the Broker. |
|
| 53. |
How To Create Broker From Command Prompt? |
|
Answer» USING mqsicreatebroker COMMAND. Using mqsicreatebroker command. |
|
| 54. |
In Which Perspective We Deploy The Flow? |
|
Answer» Administrator perspective |
|
| 55. |
What Are The Perspectives We Have? |
Answer»
|
|
| 56. |
How Many Builtin Nodes Are There? Categories Them? |
|
Answer» WebSphere Message BROKER supplies built-in nodes that you can use to define your message flows. For INFORMATION about each of these nodes, FOLLOW the appropriate link below. The nodes listed here are grouped according to the function that they provide. INPUT and output Message manipulation and transformation Collating requests Decision making Subflow identification Error handling and reporting WebSphere Message Broker supplies built-in nodes that you can use to define your message flows. For information about each of these nodes, follow the appropriate link below. The nodes listed here are grouped according to the function that they provide. Input and output Message manipulation and transformation Collating requests Decision making Subflow identification Error handling and reporting |
|
| 57. |
Mqinput Node And Input Node Differences? |
|
Answer» You MUST USE an INPUT NODE to provide the in terminal to a SUBFLOW. The Input node provides an in terminal for an embedded message flow (a subflow). You must use an Input node to provide the in terminal to a subflow. The Input node provides an in terminal for an embedded message flow (a subflow). |
|
| 58. |
Define Correlation Names? |
|
Answer» A correlation name is a field reference that identifies a well-defined STARTING point in the LOGICAL MESSAGE tree and is used in field REFERENCES to describe a standard part of the tree FORMAT. A correlation name is a field reference that identifies a well-defined starting point in the logical message tree and is used in field references to describe a standard part of the tree format. |
|
| 59. |
What Is The Use Of Commit For Connection To Databases? |
|
Answer» Any work that has been done USING the respective data source in a message flow (INCLUDING any ACTIONS taken in the node) is committed regardless of the subsequent SUCCESS or failure of the message flow. Any work that has been done using the respective data source in a message flow (including any actions taken in the node) is committed regardless of the subsequent success or failure of the message flow. |
|
| 60. |
Which Node Is Used To Change The Message In The Flow? |
|
Answer» COMPUTE NODE, FILTER Node and ResetContentDescriptor. Compute Node, Filter Node and ResetContentDescriptor. |
|
| 61. |
How Can We See The Error Log Files In Broker? |
|
Answer» The WINDOWS EVENT Viewer is where WEBSPHERE Message BROKER writes records to the local system. The Windows Event Viewer is where WebSphere Message Broker writes records to the local system. |
|
| 62. |
What Is Schema Of Broker? |
|
Answer» A broker SCHEMA is a symbol space that defines the scope of UNIQUENESS of the names of resources DEFINED WITHIN it. The resources are message flows, ESQL FILES, and mapping files. A broker schema is a symbol space that defines the scope of uniqueness of the names of resources defined within it. The resources are message flows, ESQL files, and mapping files. |
|
| 63. |
What Is User Name Server And Where It Is Defined? |
|
Answer» The User Name SERVER is an optional RUNTIME component that provides authentication of USERS and GROUPS performing publish/subscribe OPERATIONS. The User Name Server is an optional runtime component that provides authentication of users and groups performing publish/subscribe operations. |
|
| 64. |
What Is Resetcontentdescriptor Node? |
|
Answer» USE the ResetContentDescriptor node to request that the MESSAGE is reparsed by a DIFFERENT parser. Use the ResetContentDescriptor node to request that the message is reparsed by a different parser. |
|
| 65. |
What Is Parser And Difference Between Parser And Format? |
|
Answer» A Parser is defined as a program that INTERPRETS the bit stream of an incoming message and creates an internal representation of it in a tree structure Ex: MRM parser A FORMAT is a physical representation of a message. Ex: XML wire format A Parser is defined as a program that interprets the bit stream of an incoming message and creates an internal representation of it in a tree structure Ex: MRM parser A Format is a physical representation of a message. Ex: XML wire format |
|
| 66. |
Define Broker, Bar, Execution Group, Scada, And Components Of Broker? |
|
Answer» BROKER: A broker is a set of execution PROCESSES that hosts one or more message flows to route, transform, and enrich inflight messages. BAR: Flows and sets that are to be deployed are packed in it and sent to CONFIGURATION manager EXECUTION GROUP:An execution group is a named grouping of message flows that have been ASSIGNED to a broker. The broker enforces a DEGREE of isolation between message flows in distinct execution groups by ensuring that they execute in separate address spaces, or as unique processes. SCADA: The SCADAInput node is used to receive messages from clients that connect to the broker across the WebSphere MQ Telemetry Transport. SCADA device clients use the MQIsdp protocol to send messages, which are converted by the SCADAInput node into a FORMAT recognized by WebSphere Message Broker. The node also establishes the processing environment for these messages. COMPONENTS OF BROKER: Broker, Configmgr, User name service.
BROKER: A broker is a set of execution processes that hosts one or more message flows to route, transform, and enrich inflight messages. BAR: Flows and sets that are to be deployed are packed in it and sent to configuration manager EXECUTION GROUP:An execution group is a named grouping of message flows that have been assigned to a broker. The broker enforces a degree of isolation between message flows in distinct execution groups by ensuring that they execute in separate address spaces, or as unique processes. SCADA: The SCADAInput node is used to receive messages from clients that connect to the broker across the WebSphere MQ Telemetry Transport. SCADA device clients use the MQIsdp protocol to send messages, which are converted by the SCADAInput node into a format recognized by WebSphere Message Broker. The node also establishes the processing environment for these messages. COMPONENTS OF BROKER: Broker, Configmgr, User name service.
|
|
| 67. |
Difference Between Rad And Ordinary Deployment? |
|
Answer» USING Resource ADAPTER DEPLOYMENT, we can REUSE the deployment TILL the server is rebooted. Using Resource adapter deployment, we can reuse the deployment till the server is rebooted. |
|
| 68. |
Which Interface We Have To Implement When We Are Going To Create An Input Custom Node? |
|
Answer» MbInputNodeInterface MbInputNodeInterface |
|
| 69. |
Difference Between Root And Output Root? |
|
Answer» ROOT is used in the Database content changing and in FILTER node. Output Root is used in the ESQL code for a Compute node that creates a new output message based on the INPUT message. Root is used in the Database content changing and in Filter node. Output Root is used in the ESQL code for a Compute node that creates a new output message based on the input message. |
|