Versions Compared

Old Version 14

changes.mady.by.user Former user

Saved on

compared with

New Version 15

changes.mady.by.user Former user

Saved on

Key

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

...

As the Callout mediator performs a blocking call, it cannot use the default non-blocking HTTP/S transports based on Java NIO. Instead, it defaults to using <ESB_HOME>/repository/conf/axis2/axis2_blocking_client.xml as the Axis2 configuration, and <ESB_HOME>/repository/deployment/client as the client repository unless these are specified separately. 

...

Parameter NameDescription
Specify As

This parameter determines whether the target external service should be configured by using either a  serviceURL attribute or an endpointKey attribute.

  • URL: Select URL if you want to call the external service by specifying its URL in the Call mediator configuration.
  • Address Endpoint: Selected Address Endpoint if you want to call the external service via an Endpoint which is already saved in the Registry. This option should be selected if you want to make use of the WSO2 functionality related to endpoints such as format conversions, security etc. Note that only Leaf endpoint types (i.e. Address, WSDL, Default and Http) are supported for the Callout mediator.

If neither a URL or an address endpoint is specified, the To header on the request is used as the target endpoint.

URLIf you selected URL for the Specify As parameter, use this parameter to enter the URL of the external service that you want to call. This URL will be used as the End Point Reference (EPR) of the external service.
Address EndpointIf you selected Address Endpoint for the Specify As parameter, use this parameter to enter key to access the endpoint that should be used to call the external service. Click Configuration Registry or Governance Registry as relevant to select the required endpoint from the resource tree.
ActionThe SOAP action which should be appended to the service call.
Axis2 RepositoryThe path to Axis2 client repository where the services and modules are located. The purpose of this parameter is to make the Callout mediator initialize with the relevant Axis2 configurationsrequired client repository.
Axis2 XMLThe path to the location of the Axis2.xml configuration file. The purpose of this parameter is to make the Callout mediator initialize with the relevant Axis2 configurations.
Source

This parameter defines the payload for the request. It can be defined using one of the following options.

  • XPath - This option allows you to specify an expression that defines the location in the message.

    Info
    titleTip

    You can click NameSpaces to add namespaces if you are providing an expression. Then the Namespace Editor panel would appear where you can provide any number of namespace prefixes and URLs used in the XPath expression. 

  • Property - This option allows you to specify the payload for a request via a property included in the mediation flow.
  • Envelope - This option allows you to select the entire envelope which is available in the message flow as the source.
Target

The node or the property of the request message to which the payload (resulting from the value specified for the Source parameter) would be attached. The target can be specified using one of the following options.

  • XPath - This option allows you to specify an expression that defines the location in the message.

    Info
    titleTip

    You can click NameSpaces to add namespaces if you are providing an expression. Then the Namespace Editor panel would appear where you can provide any number of namespace prefixes and URLs used in the XPath expression. 

  • Property - This option allows you to specify a property included in the mediation flow.
WS-Security

If this check box is selected, WS-Security is enabled for the Callout mediator. This section would expand as shown below when you select this check box.

Specify as Inbound and Outbound Policies

If this check box is selected, you can define separate security policies for the inbound and outbound messages (flows). This is done by entering the required policy keys in the Outbound Policy Key and Inbound Policy Key parameters which are displayed as follows when this check box is selected. You can click Configuration Registry or Governance Registry to select a security policy saved in the Registry from the resource tree.

Policy KeyIf the Specify as Inbound and Outbound Policies check box is not selected, this parameter is used to enter a key to access a security policy which will be applied to both inbound and outbound messages. You can click Configuration Registry or Governance Registry to select a security policy saved in the Registry from the resource tree.

...