Hi All,
As a brief webMethods is a 24/7 application in our project so it is hard to get a down time for wM restart. Currently we are facing some errors related txStore where SAG recommending to schedule sweep service. But it is observed that all the SAP transactions are being hold in the execution of sweep service which is affecting the business flow.

We planned to develop a java service which executes the Unix command and clear outdated txStore logs but SAG is not recommending this idea.

what is the max size of txStore we can keep?
So can you advice, how can we clear txStore logs with out bringing down webMethods application.

Environment Details:
wM IS 6.5 SP3
SAP Adapter 6.5 - Fix17

Thanks in Advance.

But why not using pub.sap.transaction:sweep ?

If the store is huge it will take time and hold all transactions, however once sweeped running regulary will solve the problem? (Holding time will be low).

The store is only used for auditing, so if no auditing is needed just remove it. (transactions will be processed anyway).

Hi Dev, Thanks for the response.

Yes we can use Sweep service but it is taking more than 20 Min to finish sweep process. Therefore SAP business transactions are bieng hold in sweep window which is affecting business process.

SLA - SAP (Critical Job) tranaction shouldn’t delay for more than 1 minute which is not possible if sweep service is scheduled.

Is it recommended to develop a java service which executes the Unix command and clear outdated txStore logs when IS is running.

Any work around to clear txStore at IS runtime is much appreciated.

We also using sweep service and no issues so far:

pub.sap.transaction:sweep (deletes all 12hrs old up to 5000 confirmed trans) and scheduled all week every 5hrs.

HTH,
RMG

Hi RMG,

Can we know how much time its taking to sweep the txStore logs in your system as per the mentioned criteria.

As per our SLA, SAP transaction shouldn’t delay for more than a minute. But in SAP adapter 6.5 design when ever sweep service runs all the wM transactions to/from SAP system are hold. This design is affecting our business transactions (in hold) as the sweep service is running more than a minute.

So can you advice a solution to over come this issue.

What is your settings on the sweep service currently?

I am not sure how much time its taking in Production…If possible will find out and let you know.But i can say no runtime issues reported so far.

Also do you have this fix in place WmSAP_6-5_Fix3? It has fixed some issues related to sweep service like elapsedTime etc…

HTH,
RMG

SAP Adapter (WmSAP_6-5-0_SP1_Fix17) we had already applied but still the problem is persisting.
Parameters configured in our system, scheduled daily once when business transactions are low
maxTrxCount “10000”
elapsedTime “1380”
state “Confirmed”

We have equal amount of transactions with committed status, so is it required to run additional schedular to clear xtn logs with status “commited”.

DevNull,
“The store is only used for auditing, so if no auditing is needed just remove it. (transactions will be processed anyway).”

How can we remove/stop writing .xtn logs to txstore? Is it recomended ??

Can you try with lower numbers and run complex scheduler every 5hrs all week.we didn’t set state though.

maxTrxCount “5000”
elapsedTime “720”

Hi RMG, Thanks for your response & support, we are scheduling complex scheduler for sweep and testing.

Will get back to you on output.

Thanks for the update!

RMG, We scheduled Sweep service with elapsed state as 1440 and tansaction limit as 15000. Its taking approximately 15 minutes to clear 13000 transactions.

Where none of the messages flowing through/from SAP adapter.

Anyways thanks for your timely response.

So were you satisfied with the above result? or you can tweak numbers per your requirement/design with complex schedule and test it.

HTH,
RMg