IBM BJ0NJML - Service And Asset Management, Integration Manual

Page: 235 / 330

Outbound Customization
Integration Framework Customization with Java and XSL
221
The Java Message Service Processing Exit Class
You can use an exit placeholder for customization when sending transactions
from the system to an external system using Java Message Service (JMS). This exit
class is optional and is called before the JMS is called.
The following figure shows the JMS processing exit class the system uses when
sending transactions to an external system.
This class must implement the
psdi.iface.router.JMSExit
class and the
following method:
public Map getMessageProperties(Map metaData, (byte[] data, Map
origProps)throws MXException
This method can perform the following processes:
T Change the properties of the JMS message
T Split the data to multiple properties, to match the JMS message
You enter the fully qualified name of the Java class in the JMSEXIT property of the
endpoint that implements the JMS handler.
The Web Service Processing Exit Class
You can use an exit placeholder for customization when sending transactions
from the system to an external system using a Web service. This exit class is
optional and is called before the Web service is invoked.
The following figure shows the Web service processing exit class the system uses
when sending transactions to an external system.
This class must implement the psdi.iface.router.WSExit interface and the
following methods:
public String getServiceName(Map metaData, String endpointURL,
String serviceName, String interfaceName, String
targetNameSpace) throws MXException
The getServiceName() method returns the service name of the Web service to be
invoked.
public String getEndpointURL(Map metaData, String endpointURL,
String serviceName, String interfaceName, String
targetNameSpace) throws MXException
The
getEndpointURL()
method returns the endpoint URL of the Web service to
be invoked.