Mediator Java Callout API

The Java callout API defines two interfaces: oracle.tip.mediator.common.api.IjavaCallout and oracle.tip.mediator.common.api.CalloutMediatorMessage.

Table 20-5 lists and describes the methods in the oracle.tip.mediator.common.api.IjavaCallout interface.

Table 20-5 Description of Methods in the IjavaCallout Interface

Method	Description
`initialize`	This method is invoked when the callout implementation class is instantiated for the first time.
`preRouting`	This method is called before Mediator starts executing the cases. You can customize this method to include validations and enhancements.
`preRoutingRule`	This method is called before Mediator starts executing any particular case. You can customize this method to include case-specific validations and enhancements.
`preCallbackRouting`	This method is called before Mediator finishes executing callback handling. You can customize this method to perform callback auditing and custom fault tracking.
`postRouting`	This method is called after Mediator finishes executing the cases. You can customize this method to perform response auditing and custom fault tracking. Post-processing methods are called after all sequential routing rules are executed and do not wait for parallel routing rules to complete.
`postRoutingRule`	This method is called after Mediator starts executing the cases. You can customize this method to perform response auditing and custom fault tracking.
`postCallbackRouting`	This method is called after Mediator finishes executing callback handling. You can customize this method to perform callback auditing and custom fault tracking.

Note:

If you change the message properties of a Mediator by using a Java callout in the preRoutingRule method or the preRouting method, then you must explicitly copy the changed property to the outbound message by using Mediator assignment functionality. For example, if you are changing the jca.file.FileName property in a Java callout, then you must update the Mediator assignment statement as follows:

<assign>
<copy target="$out.property.jca.file.FileName"
expression="$in.property.jca.file.FileName"/>
</assign>

Table 20-6 discusses the methods in the CalloutMediatorMessage interface.

Table 20-6 Description of Methods in the CalloutMediatorMessage Interface

Method	Description
`addPayload`	This method sets a payload of the Mediator messages.
`addProperty`	This method adds a property to the Mediator messages.
`addHeader`	This method adds a header to the Mediator messages.
`getProperty`	This method retrieves Mediator message properties by providing the property name.
`getProperties`	This method retrieves Mediator message properties.
`getId`	This method retrieves the instance ID of the Mediator messages. This instance ID is the Mediator instance ID created for that particular message.
`getPayload`	This method retrieves a payload of the Mediator messages.
`getHeaders`	This method retrieves a header of the Mediator messages.
`getComponentDN`	This method retrieves a componentDN for the Mediator service component.

Note:

The oracle.tip.mediator.common.api.AbstractJavaCalloutImpl class is a dummy implementation of the IJavaCallout interface. This class defines all the methods present in the IJavaCallout interface. Therefore, you can extend this class to override only a few specific methods of the IJavaCallout interface.

Dummy implementation of an interface means that the implementation class provides definitions for all the methods declared in the particular interface, but one or more defined methods may have an empty method body. Extending a dummy implementation class is much easier because you can choose to override only a subset of the methods, unlike implementing an interface and defining all the methods.
Details of the processing occurring within the Java callout are not displayed in the Mediator audit trail screen.