When preparing Ready! API and SoapUI projects for monitoring, follow the guidelines outlined below.
AlertSite supports only one test case per monitor.
If you want to monitor multiple test cases, you can do one of the following:
The maximum allowed file size for SoapUI project files (.xml) is 12,000,000 bytes. However, please avoid uploading large projects that contain many test cases. Instead, create a copy of your project that contains just the test case you want to monitor, and upload this copy.
This is especially important if you use private locations (Private Node Server or InSite) – using minimal, stripped-down projects notably reduces the location resource usage.
Your API tests should include assertions to verify the API call results. Assertions are similar to validations in scripts. Without assertions, you can check only the API availability, you will not be able to check API call results.
AlertSite reports failed assertions as availability errors, for example:
Content assertions – status 5 (validation failed).
Invalid HTTP status codes assertions – status 7 (an HTTP error).
Response SLA assertions – status 6570 (a timeout error).
|Tip:||Most errors caused by failed SoapUI assertions have the 65xx status code.|
There is a limit on the maximum number of test steps for SoapUI monitors. On most usage-based monitoring plans, the limit is 50 steps. Check with your AlertSite account manager for details.
If you use private locations (Private Node Server or InSite), the limit is 25 steps for monitors using the
VMNODE-25 plan, and 50 steps on other
VMNODE-nn plans. The plan in question is the one selected in the monitor settings. For example, a monitor that uses a usage-based plan and both global and private locations is subject to the usage plan limits.
AlertSite does not provide a way to set a timeout for your SoapUI API tests. You can set the timeout in the test case settings in SoapUI or Ready! API before uploading your project to AlertSite. For details, see Configuring a Timeout for Your SoapUI Monitor.
If your project requires specific values of SoapUI global preferences (for example, Preferences > HTTP > Request compressions), you should explicitly set these preferences from your project:
For example, to set the Request Compression option, use the following setup script:
To learn more about scripting in Ready! API and SoapUI, see the documentation for Scripting and Script Library.
SoapUI tests can use certificates and Java keystore files for several purposes:
Accessing secure API endpoints using a client-side certificate. You can configure these certificates in SoapUI global preferences, in File > Preferences > SSL > Keystore.
Signing and encrypting SOAP messages. You can configure these certificates in WSS Config at the project level.
Currently, AlertSite supports only client-side certificates and does not support SOAP messaging certificates.
If your API requires a client-side security certificate, you can upload it to AlertSite, and it will be automatically distributed to the monitoring locations used by your API monitor. For more information, see Using SSL Certificates and Java Keystores.
You will be informed when the certificate is in place. After that, you can run a test on demand to verify the monitor can connect to your API.
Tests with external dependencies (such as Excel files or similar external data sources) are not supported.
Most AlertSite locations use Ready! API 1.9 (see Ready! API Versions), so the features added in later versions of Ready! API are not supported at this time.