APIs to Export Detailed Information

Use

The NWBC runtime exposes some of the API calls available on interface IF_NWBC_RUNTIME also as HTTP REST based API calls. Each of the HTTP based API calls wraps the internal ABAP API call. All calls have effectively the same URL format: ../nwbc/~api/method?parameters. The following methods are provided:

Web Service	Maps to	Description
.../nwbc/~api/GetSystemInfo	IF_NWBC_RUNTIME=>GET_CONFIGURATION and IF_NWBC_RUNTIME=>GET_USER_INFO	The call has no input parameters. It returns an XML response of the GET_CONFIGURATION and GET_USER_INFO calls together in one structure. For more information about GET_CONFIGURATION, see ABAP-Based APIs. The XML format follows the normal ABAP identify transformation.
.../nwbc/~api/GetNavigationTree	IF_NWBC_RUNTIME=>GET_NAVIGATION_TREE	The call has no input parameters. It returns an XML response of the GET_NAVIGATION_TREE call. The XML format follows the normal ABAP identify transformation.
.../nwbc/~api/ResolveNavigation	IF_NWBC_RUNTIME=> RESOLVE_NAVIGATION	The call returns an XML response of the RESOLVE_NAVIGATION call. The XML format follows the normal ABAP identify transformation. This API call accepts a number of incoming parameters that are mapped onto the ABAP-internal API call. The HTTP exposed parameters are: SOURCE, SOURCE_ROLE, and so on.

Web Service

Maps to

Description

.../nwbc/~api/GetSystemInfo

IF_NWBC_RUNTIME=>GET_CONFIGURATION and IF_NWBC_RUNTIME=>GET_USER_INFO

The call has no input parameters. It returns an XML response of the GET_CONFIGURATION and GET_USER_INFO calls together in one structure.

For more information about GET_CONFIGURATION, see ABAP-Based APIs. The XML format follows the normal ABAP identify transformation.

.../nwbc/~api/GetNavigationTree

IF_NWBC_RUNTIME=>GET_NAVIGATION_TREE

The call has no input parameters. It returns an XML response of the GET_NAVIGATION_TREE call.

The XML format follows the normal ABAP identify transformation.

.../nwbc/~api/ResolveNavigation

IF_NWBC_RUNTIME=> RESOLVE_NAVIGATION

The call returns an XML response of the RESOLVE_NAVIGATION call.

The XML format follows the normal ABAP identify transformation.

This API call accepts a number of incoming parameters that are mapped onto the ABAP-internal API call. The HTTP exposed parameters are: SOURCE, SOURCE_ROLE, and so on.

For a quick test of the REST based APIs, call the URL .../nwbc/~api directly.

More Information

ABAP-Based APIs