IBM InfoSphere Master Data Management, Version 11.3

mpi_handler

The mpi_handler table defines the handlers that are started per callback type and interaction code combination.

Expanded name: Callback Handler Configuration
Table category: Runtime configuration
Purpose: Indicates what handlers are started for any given callback type and IxnCode (transaction code) combination.
Cross-reference: Not applicable.

Table 1. mpi_handler Attribute Descriptions
Attribute	Description
caudrecno	Creation of this particular record, from mpi_audhead
maudrecno	Last time the record value was modified, from mpi_audhead
recstat	Record status
handlerno	Unique ID for the handler
callbacktype	Indicates the callback type to which this handler applies; values are 0 = ALL 1 + PREIXN 2 = POSTIXN 3 = ENTMNG
ixncode	Unique number assigned per defined interaction
handlerseqno	Order the handler is started if more than one handler is registered for any given Callback Type and IxnCode combination
handlername	For Java™ handlers, the fully qualified class name (for example, com.initiate.handler.MyHandler). For .NET handlers, the dll name and class name (for example, handler.dll: com.initiate.handler.MyHandler)
handlerargs	Optional string passed to the handlers init() method

mpi_handler SQL:

CREATE TABLE mpi_handler
(
caudrecno	bigint		NOT NULL,
maudrecno	bigint		NOT NULL,
recstat		nchar(1)	NOT NULL,
handlerno	int		NOT NULL,
callbacktype	int		NOT NULL,
ixncode		nvarchar(16)	NOT NULL,
handlerseqno	int		NOT NULL,
handlername	nvarchar(255)	NOT NULL,
handlerargs	nvarchar(255)	NULL 
)  
CREATE UNIQUE INDEX mpi_handler on mpi_handler (handlerno)

Last updated: 27 June 2014