Enterprise-Integrator-6-Developer Sample Questions Answers

Data Mapper mediator can perform JSON-to-JSON transformation without converting the message to a canonical form.

All the transformation mediators require SOAP as the canonical message format.

Enrich mediator cannot be used for message transformation.

Header mediator can only work with SOAP headers.

This happens when a soapll message is sent to a soapl2 endpoint or vice versa, resulting in the p, message content type not matching the SOAP namespace URI, e.g., soapll should have text/xml content type and soapl2 should

have application/soap+xml content type. Solution: Enable the relevant message builder/formatter in axis2.xml for the matching content type.

The ESB profile has failed to extract the transport protocol from the given URL. This happens when theO transport defined in the URL is not enabled in the system. Solution: Enable relevant transport sender in axis2.xml.

This happens when a soapll message is sent to a soapl2 endpoint or vice versa. Solution: Correct the SOAP envelope namespace.

Options a, b and c all provide mismatching reasons/solutions, so all of the answers are incorrect.

Any JMS consumer application cannot consume messages from a given store. Only message processors can consume messages in a JMS message store.

Both a and b are correct.

The ESB profile supports the store-and-forward pattern but not guaranteed delivery.

Users have the option to create a custom message store with their own message store implementation.

When a message comes into the ESBprofile, an appropriate message builder converts the message's raw payload data into XML.

Axis2 framework can be used to implement custom message builders and formatters.

When sending a message out from the ESB profile, a message builder is used toconvert XML back into its original format.

When sending a message out from the ESB profile, a message formatters is used to convert XML back into its original format.

The ESB profile can be configured as both a JMS Producer and Consumer.

JMSsupports point-to-point communication models only.

The ESB profile can be configured as a shared topic listener.

Both statements a and c are correct.

API

Inbound endpoint

Proxy service

Message processor

Envelope Wrapper

Process Manager

Aggregator

Composed Msg. Processor

Script mediator, Clone mediator, PayloadFactory mediator, XSLT mediator

Enrich mediator, XSLT mediator, XQuery mediator, Iterate mediator

PayloadFactorymediator, XSLT mediator, Filter mediator, Class mediator

Class mediator, Script mediator, PayloadFactory mediator, XSLT mediator