on 08-04-2016 12:16 PM
Hello Colleagues,
We need to archive messages with their payloads.
Is there such a possibility?
We have SAP PI 7.4 SP12.
Many thanks in advance!
Regards,
Ekaterina.
Hi Ekaterina,
Go to NWA- Operation - Data and Database - Java Archiving Cockpit.
Here in the overview area selecting your archiving store check when last your messages are archived.
Additionally, check your archive and delete job from background job processing . Check whether its working fine or not. Remember you should additionally create to separate archive and delete job for arching messages in regular interval. Default Archive and Delete job will archive only the error messages not all.
Thanks,
Apu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok Ekaterina,
What is your retention period,Usualy the XML DAS should archive with XML.
Ensure your checking within the archive period.
One more SAP Link ,ensure you followed all the steps
Hello Ekaterina,
Message that you provided as an example, is synchronous. Note that by default, Adapter Engine removes payload of synchronous messages that reached final status, and does not store it - this is done due to performance considerations, and especially memory consumption. This is controlled by property 'messaging.syncMessageRemover.removeBody' of the Java service 'XPI Service: Messaging System' (refer to Properties Related to Synchronous Messages - Configuring Process Integration After Installation - SA...) and is not generally recommended to be changed for production systems. To check this, can you check synchronously processed message which has not yet been archived and see if you can get its payload - with default settings, you shall see no payload.
What you may consider, is enabling logging for synchronous messages with payload persistence (either globally if you need it for all interfaces, or interface specific if only few interfaces are in question) as described in . When such messages are archived, you shall be able to see payload for their logged versions.
Regards,
Vadim
This is error in java log
Reading Message for key 1a73983f-5704-11e6-9bbe-000007829a22(OUTBOUND) from Archive failed, due to: while trying to invoke the method java.io.InputStream.close() of a null object loaded from field java.io.FilterInputStream.in of an object loaded from local variable 'this'
Any idea?
User | Count |
---|---|
84 | |
25 | |
12 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.