WSO2 Enterprise-Integrator-6-Developer Dumps

JMS distributed transactions are supported in the ESB profile.

The transport.jms.SessionTransacted property is used to enable JMS local transactions in the ESB profile.

ESB profile JMS transactions only work with either the Calloutmediator or the Call mediator in blocking mode.

Only JMS local transactions are supported in the ESB profile.

To handle a content type that is not supported by the ESB profile.

To process an incoming message structure that is not supported by existing constructs in the ESB, convert it

into the ESB profile's canonical message format, and convert the outgoing message from the canonical format to the expected message structure.

To support a transport protocol not available out-of-the-box in the ESB profile.

To handle a messaging structure in the ESB profile.

If you do not define a fault sequence, in the case of an error in a sequence or a proxy service, an exception will be thrown and the message will be dropped.

In situationswhere a fault sequence is not specified explicitly, a default fault sequence will be used to handle errors.

Within the fault sequence, you can access error details using the ERROR_DETAIL property.

The Fault mediator can be used to customize error messages that are sent back to the client.

Connection between the ESB and thebackend times out. Socket timeout of the HTTP sender has been ^. exceeded. Solution: Increase the socket timeout of the passthrough HTTP transport. To do that, add the following line to the passthru-http.properties file: http.socket.timeout=120000. Here socket timeout is set to 120000

Connection between the client and the ESB times out. Socket timeout of the HTTP listener has been ^. exceeded. Solution: Increase the socket timeout of the passthrough HTTP transport. To do that, add the following line to the nhttp.properties file: http.socket.timeout= 120000. Here socket timeout is set to 120000.

Connection between the client and the ESB times out. Socket timeout of the HTTP listener has be exceeded. O Solution: Increase the socket timeout of the passthrough HTTP transport. To do that, add the following line to the passthru-http.properties file: http.socket.timeout=120000. Here socket timeout is set to 120000.

Options a,b, and c are incorrect.

trigger interval=\"30\7>

All three configurations are incorrect.

Inbound endpoints are useful when you have to configure the message sourcesdynamically.

Inbound endpoints can be clustered.

HTTP inbound endpoints can use existing default port 8280.

They always run based on the underlying task execution framework.

Outbound endpoints are mandatory for any integration scenario.

They operate in the same way as inbound endpoints.

When you use message stores, you have to specify the address as an outbound endpoint.

Outbound endpoints can have flags to translate the message.

When looking up secured passwords in a Synapse configuration, it is possible to use theXPath expression ,,wso2:vault-lookup('alias,) to retrieve the actual password by providing 'alias'.

Secure vault can be used to secure plain text passwords stored in ESB profile configuration files.

Secure vault uses the cipher-tool.properties filesto identify the locations of the passwords in configuration U files.

Secure vault always uses the certificate in the primary keystore configured in carbon.xml to encrypt the passwords.

Both statement b and c are correct.

It is not possible to set parameters for custom mediators.

Custom mediator's parameters should be declared as public fields in mediator code. For instance: public String foo, bar;

Synapse properties can be used to pass values to mediator arguments. For instance:

Mutual SSL provides message level security.

Mutual SSL provides higher performance.

All of the above are correct.

Both client and server have to authenticate each other and require certificates to be configured at both server and client ends.

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.

Use of class variables is not recommended.

You can define and use a global variable in the mediator class if and only if those variables are shared with all the messages in that particular message flow.

When we use the mediatorin different artifacts, an instance of the mediator gets created for each occurrence in the configuration.

A mediator instance gets created for each occurrence in the configuration and for each message.