TIBCO Scribe® Online Request/Reply Performance Tips

TIBCO Scribe® Online Request/Reply Performance Tips

book

Article ID: KB0072564

calendar_today

Updated On:

Products Versions
TIBCO Cloud Integration - Connect ( Scribe ) -

Description

Each Solution containing one or more Request/Reply Maps is bound to a single TIBCO Scribe® Online Agent which limits the number of requests that can be processed. In addition, you should be aware of the following restrictions when using Request/Reply:
  • If the time to send a reply exceeds the default timeout of 90 seconds, a timeout error is generated.
  • Request processing wait times increase as you increase the number of calls.
  • When using a Cloud Agent, on average, Request/Reply can only support 1 call every 2 seconds.
  • When using an On-Premise Agent the number of calls per second might be improved depending on the CPU and available memory on the server where the Agent is installed. Performance testing in your specific environment would be required to determine the capacity of the server.
  • If, over time, the application that is calling TIBCO Scribe® Online is exceeding the 1 call every 2 seconds limit, the response times take longer creating a backlog of messages. When the backlog reaches 100 or more, the system starts returning 429 errors for new messages and does not add them to the backlog until enough messages are processed to reduce the backlog.
  • Individual message size is limited to a maximum of 20 MB.

Exceeding these limits could trigger governance thresholds causing automatic controls in TIBCO Scribe® Online to restrict your IP address. If you find that your IP address has been restricted, contact Support to request that the restriction be lifted. See section 9 of the TIBCO Cloud Service Terms.

Tips
  • Request/Reply is meant for quick transactions using synchronous requests where a reply is needed.
  • If you have more than one Request/Reply Map in a Solution, consider separating the Maps into different Solutions with each Solution assigned to a different Agent to distribute the workload.
  • Consider using Message Maps.
  • If you are using TIBCO Cloud ™ Integration, consider implementing TIBCO Flogo®.
  • When configuring an application to send a request to TIBCO Scribe® Online, be sure to account for transient fault errors that may result in messages that are not processed. TIBCO Scribe® Online can be configured to send a reply to the application that sent the original request using the Build Reply and Send Reply operation Blocks. The reply can serve as a notification that the message was received. Any message that does not trigger a reply, may have been lost due to a transient fault and should be considered for retry/reprocess from the calling Map.
  • The system used to send requests to TIBCO Scribe® Online receives errors when it can no longer contact TIBCO Scribe® Online. Implement error trapping and monitor your system for those errors so they can be addressed as soon as possible.

Issue/Introduction

Best practices for using Request/Reply Maps.
Powered by Wolken Software