Outbound Customization
220
Integration Guide
The Enterprise Bean Processing Exit Class
You can use an exit placeholder for class customization when transactions are sent
to an external system using an enterprise bean. This exit class is optional and is
called before the enterprise bean is called.
The following figure shows the various enterprise bean processing exit classes the
system uses when sending transactions to an external system.
The implementation of this Java class must resolve the method signature of the
enterprise bean that is being invoked through this handler and the parameters
that the method requires. If no value is specified for this property, the system
applies a default exit called DefaultEJBExit. This default exit attempts to resolve
the enterprise bean method signature and parameters.
This class must implement the psdi.iface.router.EJBExit interface and the
following methods:
public Class[] getClassParams()
The
getClassParams()
method returns the method signature in the form of an
array of Java classes.
The following method can perform the noted processes:
T
Create an array of parameter values that correspond with the signature of
the external enterprise bean method to be called.
public Object[] getObjectParams(byte[] data, String
interfaceName, String destinationName)
The parameters of the enterprise beans are returned in the form of an array of Java
Objects.
The following method can perform the noted processes:
T
Returns callback after the successful invocation of the enterprise bean
with an object as the response of the invocation.
public void responseOk(Object response)throws MXException
The
responseOk()
method is called after a successful enterprise bean invocation.
The following method can perform the noted processes:
T
Returns callback after the unsuccessful invocation of the enterprise bean.
public void responseError(Exception e) throws MXException
If an error is encountered during the enterprise bean invocation, the
responseError()
method is called with the originating exception as a parameter.
You enter the fully qualified name of the Java class in the EJBEXIT property of the
endpoint that implements the enterprise bean handler.
Summary of Contents for BJ0NJML - Service And Asset Management
Page 12: ...xii Integration Guide ...
Page 14: ...xiv Integration Guide ...
Page 16: ......
Page 31: ...Integration Framework for User Interface Integration Integration Framework Architecture 17 ...
Page 32: ...Integration Framework for User Interface Integration 18 Integration Guide ...
Page 60: ...Synchronous Inbound Integration Processing 46 Integration Guide ...
Page 122: ...Configuring External Systems 108 Integration Guide ...
Page 142: ...Non queue Error Management 128 Integration Guide ...
Page 154: ...Integration Components 140 Integration Guide ...
Page 156: ......
Page 172: ...Writing Custom Handlers 158 Integration Guide ...
Page 176: ...Queue Tables 162 Integration Guide ...
Page 190: ...IBM WebSphere MQ 176 Integration Guide ...
Page 212: ...Inbound Message Receipt 198 Integration Guide ...
Page 226: ...Integration Controls 212 Integration Guide ...
Page 252: ...Predefined External System Modifications 238 Integration Guide ...
Page 263: ...Web Service Queries Integration Queries 249 ...
Page 264: ...Web Service Queries 250 Integration Guide ...
Page 272: ...Integration Web Service Invocations 258 Integration Guide ...
Page 276: ...Multilanguage Attributes 262 Integration Guide ...
Page 293: ...Integration Module Invocation Integration Modules 279 ...
Page 294: ...Integration Module Invocation 280 Integration Guide ...
Page 302: ...Associating a Condition with a Signature Option 288 Integration Guide ...
Page 320: ...Work Order Collaboration Switches 306 Integration Guide ...
Page 324: ...310 Integration Guide ...