We are taking steps to make our moderation process friendlier while ensuring that SAP Community continues to comply with the Digital Services Act (DSA). Learn more in this What’s New post.
Introduction:I often come across integrations that have not been designed to exploit the Message bandwidth optimally.Before I expand any further on this, it would be good to familiarize yourself with the following blog.https://www.integration-excelle...
In SAP the best run projects are the one's that have been best scoped!No one likes surprises and Change requests are fairly common in projects where the estimation wasn't done correctly due to uncertainty in the initially scoped requirements or tech...
IntroductionEOIO was a long awaited functionality that every Integration consultant was waiting for in SAP CI. We had this in SAP PO where we would use it to preserve the order of messages. Messages using EOIO were stored in a FIFO queue that ensured...
Hello Everyone,I am trying to expose a SAP CI api via SAP API management. SAP CI Iflow has a Http Sender Adapter that accepts the payload and pushes it to a JMS Queue.Inbound requests from postman towards the SAP CI HTTP url using the client id clien...
Hello Everyone,I have a scenario where I have two packages PackageA and PackageB both packages contain Synchronous iflows with HTTP Sender adapter,PackageA iflows are accessible only via custom role PackageAMessaging.send and PackageB iflows are acce...
@devang_mandli Yes I assumed it would be there but then I checked its not there. The only option is to maintain a counter in a datastore with datastore id as "1" that holds the message id of the JMS message and updates a counter if its already there...
@devang_mandli This can be done by checking the JMSRetries Header and if it exceeds a certain number of retries then end that message in a endMessage Event just dont process it any further. This check needs to be done as soon as you read the message...
Gunjan, It will get rolled out to all tenants / data centers slowly. As we have seen in past SAP never publishes a experimental update / new feature globally on same day. They do it gradually, Unless it is a hot fix or a security patch.
<BasicAuthentication async='false' continueOnError='false' enabled='true' xmlns='http://www.sap.com/apimgmt'>async was true which resulted in a scenario was API management didnt wait to fetch the password which in turn was pending on key value map lo...
