OctaSapien

BTP Connectivity Path Doctor

Compare a supplied OnPremise destination, Cloud Connector mapping, Location ID and requested resource path locally.

Use only URL, ProxyType and optional CloudConnectorLocationId.

Use virtualHost, virtualPort and optional locationId.

Use an array of path and policy pairs: exact or path-and-all-sub-paths.

Enter the full absolute HTTP or HTTPS URL for this request.

Runs in this browser. No destination or connector is contacted, and no live reachability is tested.

Exact paths are case-sensitive. Path and all sub-paths uses a case-sensitive literal prefix that does not respect path-segment boundaries; query strings are ignored.

Found something we could improve?
Practical usage guide

Practical usage guide

A practical workflow for BTP Connectivity Path Check

Check supplied SAP BTP OnPremise destination, Cloud Connector virtual mapping, Location ID and HTTP resource path locally. No connection or live reachability is tested.

1. Prepare

Use representative, complete evidence and include the context needed to distinguish a real issue from an expected variation.

2. Review

Prioritize concrete findings, corroborate them against the source and rerun the analysis after correcting the input.

3. Apply

Confirm service version, destination and tenant-specific constraints before applying the result in BTP.

Verification before operational use

  • Use representative samples without passwords, tokens, personal data or production secrets. Keep the smallest input needed to reproduce the behavior you are reviewing.
  • Confirm the result in the authorized target environment when runtime versions, namespaces, extensions, permissions or system configuration can change the outcome.
  • Record the source, assumptions, tool settings and expected result so another reviewer can reproduce the check and distinguish verified facts from recommendations.