webMethods

Hi webMethods community,

My client uses SAP adapter in an AWS Kubernetes (EKS) environment with webMethods 10.15.

The Tx Store is configured to store transactions in an EFS.

volumesConfig:  storageClassNameSTS: eks-efs-sc  accessModesSTS:ReadWriteMany  storageSTS: 1Gi

We have several million daily transactions (14To transactions on EFS).
The SAP purge service (pub.sap.transaction:sweep) is scheduled but purges too slowly.
The customer does not operate SAP transactions. So we don't need to keep them.

What implementation do you recommend to implement the TxStore in this environment and be able to purge transactions more quickly or don't save transactions ?

Hi webMethods community,

My client uses SAP adapter in an AWS Kubernetes (EKS) environment with webMethods 10.15.

The Tx Store is configured to store transactions in an EFS.

volumesConfig:  storageClassNameSTS: eks-efs-sc  accessModesSTS:ReadWriteMany  storageSTS: 1Gi

We have several million daily transactions (14To transactions on EFS).
The SAP purge service (pub.sap.transaction:sweep) is scheduled but purges too slowly.
The customer does not operate SAP transactions. So we don't need to keep them.

What implementation do you recommend to implement the TxStore in this environment and be able to purge transactions more quickly or don't save transactions ?

I'm certainly not a SAP adapter expert, but from what I see you're using EFS to persist your SAP transactions store.

There is possibly a way of deactivating persistence for this store, but I haven't found it in the documentation.

So, here's what you could do if you have no interest in this data:

1. Switch to a local transaction store (since you're using EFS in RWX mode, I have every reason to believe you have configured a shared store)
2. Bind the folder in which you write data to an emptyDir, which uses local pod storage (see https://kubernetes.io/docs/concepts/storage/volumes/#emptydir)

With this, SAP purge service will now make local IO which are much faster than network IO you currently perform to access your EFS.

Have you tried to tune the parameters described here to reduce the amount of data send to the store?

Hi webMethods community,

My client uses SAP adapter in an AWS Kubernetes (EKS) environment with webMethods 10.15.

The Tx Store is configured to store transactions in an EFS.

volumesConfig:  storageClassNameSTS: eks-efs-sc  accessModesSTS:ReadWriteMany  storageSTS: 1Gi

We have several million daily transactions (14To transactions on EFS).
The SAP purge service (pub.sap.transaction:sweep) is scheduled but purges too slowly.
The customer does not operate SAP transactions. So we don't need to keep them.

What implementation do you recommend to implement the TxStore in this environment and be able to purge transactions more quickly or don't save transactions ?