Transaction (message) store and Reposerver are different.
Message store captures the outbound SAP idocs you see if you select /Routings / Transactions from the admin console. IIRC WmPartners/congif/xtn.log etc has the header entries for the xml content that is stored in /WmPartners/pub/mailbox. You are correct, you need to set up a scheduled service to call the SweeperTRX service to delete these files.
A couple of times in our production environment this service has stopped working effectively (it writes to server.log, so you can see if it selected 0 files to delete). We then stopped WM/BC, deleted xtn.log etc files and the associated xmls. After a restart all worked OK again. We are not yet sure why this happened.
Reposerver is different. It is a datastore that can be used by WM/BC. Data can be written to file system or database, as you mention above. From looking at the documentation the main use for Reposerver is for guaranteed delivery or clustering functionality. In our Prod environment we originally had 2 x clustered WM servers, and observed that information about clustered scheduled services was stored on Repostore. There were stablity problems with our initial file-based Reposerver, so we went to non-clustered WM servers. After various WM patches the file-based Reposerver is now stable.
If anybody has comments about file-based vs database Reposerver I would like to hear.
Dan: can this post and the previous post be put into a new thread?
#webMethods#Flow-and-Java-services#Integration-Server-and-ESB