USE:
This procedure shall should be applied for flat-file/EDI scenarios and to all other scenarios that when the inbound or outbound adapter modules executed by the communication channel should be a part of testing.
PROCEDURE:
- Complete the same steps both for sender or receiver communication channels of the tested interface. The only difference is that the MessageLoggerBean should be added as a first module in a chain in the sender channel (to store the message before processing) and . But, in the receiver channel, the module should be added as a the last one (in order to compare results after channel processing).
- In the communication channel, add adapter module localejbs/AF_Modules/MessageLoggerBean of of type: Local Enterprise Bean and Module key, for example example, logger
This module stores flat-file message messages in PI persistence, and thanks to this, IFTT is able to can process the initial version of the flat file message. - In Module configuration tab add following entries
- module key: logger, parameter name: log.condition, parameter value: 1
- module key: logger, parameter name: log.location, parameter value: flat
Example of message from PO monitor that stores flat-file payload:
- The log.location defines the name for the version. This name (in our example flat) needs to be put in automation object configuration in additional parameters: PIMSGVERBI (input message) or PIMSGVERSN (output message)
- For testing sender adapter modules (Test types: PI inbound or PI unit test), you must provide the sender channel name must be provided name in additional parameters in section Testing sender channel's adapter modules.