Too many questions on Archive/Delete messages.

[Former Member]

Hi,

What is the use of the delete/archive jobs exactly ? does it archive/delete the message/trace/history ???

What is the proper way of cleaning up history and irrelevant data, when do you think I should define that the data turns obsolete ?

In the NW documentation I read that successfully processed messages handles the cleanup automatically, what does it mean, what exaclty is considered as successfully processed (Applicational Ack ? Technical Ack ? etc... ) ?

Thanks,

Elad.

[udo_martens · Accepted solution]

Hi Elad,

delete-jobs are deleting old messages, archive-jobs archive them. They use parameter from SXMB_ADM / Configure Integration Engine / Specific Configuration.

You can configure there for example categorie "deletion", parameter "persist_duration_error" subparameter "SYNC", what means, dont delete synchronous error messages which are younger than the given value with delete job. Look for the F1 help there, to find out meaning of parameters.

The success of acknowledgement does not affect the delete / archive jobs.

Regards,

Udo

[Former Member · Accepted solution]

Hi Udo,

Thank you for the reply.

About the "Processed successfully" issue, I guess that it doesn't relate to the ack. received, but to the message status in the XI (Scheduled/Sys. error/In process etc...).

Do you have any recomendationfor how to define the delete and archive jobs in order to get maximum efficiency out of the XI ?

Thanks,

Elad.

[udo_martens · Accepted solution]

Hi Elad,

ususally put the trace (sxmb_adm / Integration Engine Configuration / specific configuration / runtime / logging to 3 at test system, to 0 or 1 at productive system, coz you want to analyse errors at test and good performance at p system.

Let the delete / archive job run every night (or when ever you have low traffic) and customize the time how long a message should remain in the DB at sxmb_adm / Integration Engine Configuration / specific configuration / deletion resp archive.

If you want to be able to find out later anything about old message, go for archive. Look to the archives from sxmb_moni / archived xml messages.

How long should messages remain in DB?

Go to sxmb_moni / persistenz layer analysis, where you can see the current fill level of your DB. If it is nearly empty, you can increase the days in sxmb_adm, if nearly full than you need a lower intervall.

Usually the messages at test remain longer time coz there is no space problem - not so much traffic.

Regards,

Udo

[Former Member · Accepted solution]

Hi Udo,

If the HD quota is full cuz of the messages from the last 15 days (specified in the configuration to keep messages alive), a good solution could be to decrease this parameter? for example from 15 days to 10 days?

Best regards,

Gerardo.

[Former Member]

Hi Elad,

to get a clear picture about archiving and deleting jobs

chk out this link

http://help.sap.com/saphelp_nw04/helpdata/en/41/b715045ffc11d5b3ea0050da403d6a/frameset.htm

regards

jithesh

[Former Member]

Hi Elad,

Here is a thread where a similar query was handled.

Hope you got some clarity from this.

cheers,

Prashanth