Skip to content

Verification

After deploying AgentCube, follow these steps to verify your installation is working correctly.

Step 1: Health Check

curl https://{connector_hostname}/health

Expected Response — Basic Auth

{
  "status": "healthy",
  "version": "{connector_version}",
  "backend_connected": true,
  "backend_system": "Oracle Essbase",
  "auth_mode": "basic"
}

Key fields to verify:

Field Expected Value
status healthy
backend_connected true
auth_mode basic

Expected Response — OIDC Mode

{
  "status": "healthy",
  "version": "{connector_version}",
  "backend_connected": null,
  "backend_system": "Oracle Essbase",
  "auth_mode": "oidc",
  "oidc_issuer": "{oidc_config_url}"
}

In OIDC mode, backend_connected is null because the backend cannot be verified without a user context — it is verified on each authenticated request.

Step 2: Test Connectivity

Use the test_datasource tool from your AI platform, or call it directly if your platform supports tool testing.

Expected result: connection status, server URL, and Oracle system details.

Step 3: Test a Tool Call

From your AI platform, ask a question that triggers a data query:

  • Essbase: "List all Essbase applications"
  • Planning: "List all Planning applications"

If the response includes application names from your Oracle environment, your deployment is working correctly.

Step 4: Verify SSO (OIDC Only)

For SSO deployments, verify per-user authentication:

  1. Connect from your AI platform and authenticate via SSO
  2. Run list_applications — verify the results match what the authenticated user should see in Oracle
  3. If possible, test with a second user who has different Oracle permissions to confirm per-user data scoping

Common Issues

See Troubleshooting for a complete list of common issues and resolutions.