This documentation is for WSO2 API Manager 2.0.0 View documentation for the latest release.
Page Comparison - Adding Mediation Extensions (v.5 vs v.6) - API Manager 2.0.0 - WSO2 Documentation

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.



Please note that following mediators are not usable within custom sequences since they are not supported by API Gateway custom medicationsmediations.

  • Call mediator in non-blocking mode
  • Send mediator


In this example, you have constructed the service_ep property dynamically and assigned the value of this property to the To header. The default endpoint sends the message to the address specified in the To header, in this case,

titleAdding a non-blocking send operation

In this example, the Send mediator in a proxy service using the VFS transport is transferring a file to a VFS endpoint. VFS is a non-blocking transport by default, which means a new thread is spawned for each outgoing message. The Property mediator added before the Send mediator removes the ClientAPINonBlocking property from the message to perform the mediation in a single thread. This is required when the file being transferred is large and you want to avoid out-of-memory failures.

Code Block
   <property name="ClientApiNonBlocking"
      <endpoint name="FileEpr">
         <address uri="vfs:file:////home/shammi/file-out"/>


Creating per-API extensions