Skip to content

Testing OData Destinations

You can now test destination links for OData applications from the Connections window, via a test wizard.

The destination's SSO Basic Authentication must be configured with a technical user. If the icon does not appear, the OData application destination is not configured correctly.

This test tool enables an Admin User to verify an OData service, and provides an easy way to browse metadata information and preview back-end data.

  1. In Mobile Services cockpit, select Mobile Applications > Native/Hybrid or SAP Mobile Cards

  2. Select an application, then select Mobile Connectivity under Assigned Features (or add it first)

  3. Under Actions, click the OData application test destination icon show-edit .

    The OData Application Destination Test wizard appears.

  4. On the first page, view the basic information about the application and destination. You can enter the relative OData path of the destination URL, and check the OData metadata definition.

  5. On the second page, view the OData service entities, the properties and data of the entities; and the JSON raw data and XML raw data of each entity.

Pinging a Destination

Test whether a destination is accessible.

  1. In Mobile Services cockpit, select Mobile Applications > Native/Hybrid or SAP Mobile Cards.

  2. Select an application, then select Mobile Connectivity under Assigned Features (or add it first)

  3. Select a destination and click Ping.

    You see either:

    • Ping Successful – connection is accessible.

    • Ping Failed – connection is not accessible. Click Show Details to see more information.

Testing Destinations in a Browser

You can test destination connectivity from a web browser. This is especially useful for destinations that cannot be tested via Ping, or OData Application Destination Test.

Testing destination links from a browser enables you to test scenarios that do not work from Mobile Services cockpit, such as "Cloud Connector SSO", "Forward", and "OAuth2 User Token exchange", because they require a business user token.

In this scenario, a new browser tab is launched using the mobile application URL, the same URL that the application uses to interact with the destination. The URL is modified (the parameter, ?auth=uaa, is appended), and the request is routed through AppRouter. This is the same way that a mobile application that is used by an end user interacts with the destination.

  1. In Mobile Services cockpit, select Mobile Applications > Native/Hybrid or SAP Mobile Cards.

  2. Select an application, then select Mobile Connectivity under Assigned Features (or add it first).

  3. Select a destination and click popup-window . This launches a new browser tab, using a modified destination URL.

  4. Upon successful authentication, the destination's data appears in the browser window in XML file format. This indicates that the destination link works.

Note

If you check the browser URL, you will see that the URL has been changed and ?auth=uaa has been appended. This indicates the destination was tested through the AppRouter.

  1. Close the web browser window when ready.

Last update: September 29, 2020