Exploring usage guidelines and limits
Examine the usage guidelines and limits in webMethods Integration.
Important: Limits and quota on usage can vary based on the license model and provisioned
tier.
- Polling triggers
- Polling interval: 5 minutes
- Projects
- Maximum allowed export or publish (compressed file archive) project limit: 15 MB
- Webhooks
- Webhook payload: 10 MB
- Cloud messaging
- For more information, see Messaging.
- Flow services
- Default timeout limit: 360 minutes
- Node.js CLI-based connectors
- Development of File IO and data-streams operations by using a CLI connector: Not supported
- Logs and monitoring
- Retention period for execution logs: 30 days
- Spoke tenants
- Under Spoke tenants, authorizations are created by using only the Custom Authorization option. The Default Authorization option is not enabled.
- Hybrid integration in webMethods Integration
- The maximum limit of an encoded service output to be transported over Hybrid Integration is 50
MB. The following encoding limits are enforced:
- java.lang.String uses a fixed width encoding of 2 bytes per java.lang.Character. In general, all data types excluding java.lang.Integer and java.lang.Byte are converted to java.lang.String before encoding. For example, a java.lang.String must be less than 25 MB, however, a byte [] must be less than 50 MB.
- Each field or value within the Service Output is framed with metadata during encoding, and this is added to the encoded data.
- The Service Output being transported is encoded into a single cumulative piece, so it's important to consider both the number of fields and their total data volume.
- High-volume payload handling
- Sending high-volume payloads for all the connectors in the Cloud is not supported except for the AWS S3 connector. AWS S3 backend provides the capability to handle high-volume documents, hence it is supported. The payload is limited by the available memory and depends on the volume of transactions that are flowing through the system at a time.
- WSDL support
- Cloud REST resource supports only one type of message builder and formatter for all the response codes. Cloud does not support the RPC/encoded style WSDL and the RPC/literal style WSDL.
- Salesforce events
- Salesforce events can be retrieved only if you are using Salesforce v37.0 or later. Currently, the replay options are supported only for Salesforce Push topic. Limitations are also imposed by the Salesforce backend. See the Salesforce documentation for examples on the limits.
- Connector development
- Nested business objects are not handled while creating a custom operation. Provide the details associated with business objects for complex operations when you are creating a custom operation. Currently, webMethods CloudStreams APIs support only one-level business object fields.
- Multipart form data
-
There is no restriction on the amount of data that can be sent as a file part in a multipart request. The data included in the multipart request depends on the available heap memory of the server.
- Streaming listener
- Before using streaming capabilities, it is important to understand the underlying limitation of the protocol and the SaaS backend, for example, Salesforce. If there are networks, proxy, or firewall connectivity-related issues or delays, you might not receive the messages. In such cases, investigate the network and connectivity. The protocols that provide the streaming listener capability are public protocols, which run over HTTP like Bayeux. These protocols are not guaranteed protocols. They do not help ensure delivery of the messages.
- Streaming provider
- Due to network, proxy, or firewall connectivity-related issues, the default timeout values for connection timeout (ms) might not be enough in your environment. Check the timeout settings based on your network conditions and set the values for connection timeout (ms). Due to latency and other issues, some networks might take a long time to exchange messages. In such cases, you might see timeout errors. To avoid that, increase the timeout values and see what values fit your organization. It is applicable for all the outbound and inbound timeout configurations.
- Supported connectors for Private Links
-
You can establish secure connections from your private VPC to self-hosted applications by using private links. The following connectors are certified on webMethods Integration:
Learn how to invoke workflows and flow services with Private links.