Step 3: Validate standard profile upgrade
- Last Updated: August 12, 2026
- 1 minute read
- OpenEdge MCP Server
- Version 1.1
- Documentation
Validation confirms that the upgrade was successful and that all functionality remains intact.
To verify that the upgrade preserved functionality and configuration, run the same known
tool invocation used in baseline validation:
|
Validation checklist
To confirm the upgrade completed successfully, verify the following:
For more information, see Configure middleware settings.
- Verify the known tool invocation succeeds with expected results.
- Confirm TLS/client connectivity is functional.
- Test that invalid service-account tokens are properly rejected.
- Verify profile configuration, certificates, SA key material, and tokens remain unchanged (apart from intentional configuration updates).
request_timeout from 500 ms
to 30,000 ms (30 seconds). Profiles that do not explicitly configure this value will
observe significantly longer timeout behavior. To retain the previous 500 ms
timeout, add the following to your profile's
generated/$PROFILE/server/mcp_server_config.json:
|
Important:
- The chosen timeout must account for downstream OpenEdge service response times and client timeout expectations. The new 30-second default accommodates longer-running operations but may not be appropriate for all deployment scenarios.
- A successful tool call alone does not prove that authorization is enforced. Always verify that invalid credentials are rejected.