Skip to content
Last updated:

Use Explorer

Search everything Discovery found, filter it by status, adapter or address, and open the details of each artifact.

Explorer is the searchable inventory of what Discovery read from your environment: iFlows, API proxies, Event Mesh queues and topics, and the external interfaces found behind iFlow receivers.

ColumnWhat it shows
NameThe artifact.
TypeiFlow, API Proxy, Queue, Topic, or the interface type: ERP, HCM, external or unclassified.
PackageIts package.
SenderThe sender in the design, Scheduled for a timer, or ProcessDirect when another iFlow calls it.
ReceiversThe kinds of systems it calls, by adapter.
StatusFor iFlows: Deployed, In exception (the runtime reports an error in the deployment, not in messages) or Undeployed.

Group, the default, gathers the rows under their package or system; List shows them flat. Click a column header to sort.

A coloured dot next to an iFlow shows its health from Monitoring: Error above 20% of failed messages, Warning above 5%, otherwise OK, or No data without Monitoring.

  • Search matches name, package, sender, type and any address.
  • TYPE chips and PROTOCOL pills narrow the list in one click. Use the protocol pills to find iFlows by adapter.
  • Filter narrows by Status, Health, Sender, Receiver, Credential, Deployed by or URL.
  • Clear filters removes the filters and keeps the search.

To find everything that calls a host or a path, open Filter → URL and type part of it. It looks in inbound endpoints, design addresses, ProcessDirect addresses, receiver addresses and API Management targets.

Click a row to see its details on the right. For an iFlow:

SectionWhat it shows
InformationStatus, package, how it is triggered, sender and channel, and a link to its design in SAP Integration Suite.
Version and deploymentDesign and deployed versions, who deployed it and when. A warning appears when the design changed after the last deployment.
Inbound endpointIts URL or address, or why it has none (timer, ProcessDirect).
ReceiversEach receiver with its address, and the credential, authentication and certificate it uses, by alias only. When the address is resolved only at runtime, where it is set.
SchemaWhether it has a detected payload or a registered contract, with Open in Schema.
PerformanceMessages, failures, error rate and response times, from Monitoring.

API proxies show their base path, target, resources and the iFlows they call; queues show their subscriptions.

The arrow to the left of an iFlow, proxy or queue opens its flow under the row. Drag to move, scroll to zoom, and Expand diagram to see it full screen.

Explorer shows what the last Discovery sync read, at the interval set in Settings → Discovery → General. The sync button, next to the search, runs one now and reloads the list when it finishes. A scheduled sync appears after you reload the page.

Each row becomes a card; tap it to see the details full screen.