In this wiki you have an example of a module implementation with access to the payload:
For the persistence you could use a Z table in the abap stuck, or create a table in the java stuck (i never try this option and i cant assure you the problems that you can find) http://scn.sap.com/docs/DOC-1222
>>>>is it possible and advisable to persist information in a local enterprise bean used in pi adapter module chain?
I don't think so - why not
a) store the data in some jdbc table and populate it with an normal PI adapter
as a second receiver in your flow ?
b) - just read the data in the module
Another approach is use file as a storage media. You can easily do File lookup using UDF during mapping. You might want to check this wiki about file lookup using UDF. This is very simple approach.
I did this kind of requirement but not using adapter module,as per my experience implemnting through adapter module not a right idea,
1)Suppose your receiver is SOAP and you want store the message in Oracle table, this case your adapter module should support sending data to Data base .
you need to maintian the sequence also in Adapte module chain.
This is bit tedious activity that why add one more JDBC receiver adapter and insert data.
I dont recommend file storage domain.
Hi Markus, I have not tried this, but perhaps your modules can read/write to an adapter variable as explained in this blog by Jin: