SOAP can be used over HTTP only.

SOAP is extensible with encryption and signing.

SOAP allows for any programmable model.

SOAP is built using XML.

If your Class mediator is a regular non-OSGI JAR file, copy it into the < EI_HOME > /repository/classmediators directory.

Both a and c are correct.

If you develop your mediator as a OSGI bundle, copy jar file into < EI_HOME > /dropins directory.

If your mediator is a regular non-OSGI JAR file, copy it into the < EI_HOME > \lib directory.

Create a separate endpoints CAR file for each environment (Dev, QA, Prod) and deploy the endpoints CAR and the ESB profile configurations CAR file.

All of the above approaches can be used for externalizing endpoints.

Parameterize the endpoints values and replace those with matching endpoint values at build time using a Maven project.

Externalize and store the endpoints in the registry and refer to them by name in the ESB profile configuration.

Specifying a url-template or a url-mapping is mandatory for all the resources in a REST API.

APIs can be exposed through HTTP inbound endpoints.

REST APIs are exposed over one of the HTTP listener ports opened by the EI http transport.

Each REST API can have multiple resources, and each resource can have different service orchestration logic of backend services.

Periodically connect to an external service and extract some data.

Trigger some Java code when certain types of data (for instance, stock price of IBM) comes to the sequence.

Periodically run some Java code inside a sequence.

Run a piece of code just once after the ESB profile starts.

< task name=\"CheckPrice\n class=\"org.wso2.esb.tutorial.tasks.PlaceStockOrderTask\" >

< trigger interval=\"1800\7 >

< /task >

< task name=\"CheckPrice\" class=\"org.wso2.esb.tutorial.tasks.PlaceStockOrderTask\"

< trigger interval=\"30\", continuous=\"true\7 >

< /task >

< task name=\"CheckPrice\n class=\"org.wso2.esb.tutorial.tasks.PlaceStockOrderTask\" >

trigger interval=\"30\7 >

< /task >

All three configurations are incorrect.

If it is a class mediator, you can put that JAR file in the < EI_HOME > /lib directory.

If you have developed your custom mediator as a regular non-OSGI JAR, you have to put it in the < EI_HOME > /extensions directory.

All of the above.

If you have developed your custom mediator as an OSGI bundle, you have to put it in the < EI_HOME > /dropins directory.

To enable binary file transfer, you must enable the message builder and formatter for the relevant content type in axis2.xml.

You can enable streaming within your ESB pfoeile configuration using a parameter.

All of the above.

Files can be transferred as binary files using streaming to reduce processing and memory requirements.

Define a resource for each API, and only allow that HTTP verb for that particular resource.

Each HTTP method can be identified by the transport, and you can configure a sequence for each method at transport configuration logic.

Only define the message filtering switching logic inside a sequence, and each path can handle the specific HTTP verb.

Wrap a given REST API with an inbound so that you can filter out requests based on an HTTP verb.

When retry count is 0.

When the suspend timeout is reached.

When there is a response from the endpoint.

When the retry count is a positive integer.