Show TOC

4.2 Active Services in ICFLocate this document in the navigation structure


The Internet Communication Framework (ICF) allows you to communicate with the SAP system using Internet standard protocols (HTTP, HTTPS, and SMTP). In the ICF tree, the NWBC runtime also has a node that is available by default under the path /sap/bc/nwbc. This node must be active to enable any NWBC client to access the server.

Below the nwbc node, there are a number of nodes in the format nwbc_* that are used to limit access to specific NWBC services. For more information about when these nodes must be active, see 7.6 ICF Configuration .

In addition, the various cockpits are configured within ICF. Each cockpit is defined as a subnode under /sap/bc/nwbc , for example /sap/bc/nwbc/solman. A subnode must be active so that the cockpit can work.

The table shows the ICF nodes relevant for NWBC:


Representation in Browser




Transaction NWBC (started in the SAP GUI by entering /nNWBC) displays a launch page with a complete list of all available cockpits and all roles that are assigned to the user through this cockpit. For more information, see 4.9 Transaction NWBC . Effectively, the transaction starts the nwbc_launch node of NWBC.

For security reasons, the ~launch page is controlled through the nwbc_launch node in the ICF tree and can be deactivated here. For more information, see 4.8 ~launch Page .

If this node is deactivated , transaction NWBC directly starts NWBC for HTML client without allowing the user to select a specific cockpit; the access involves all roles.



This is an access channel that dumps, in raw format, all relevant troubleshooting information that help to resolve a problem.

The information from ~test includes the complete NWBC configuration, all roles assigned, and a large amount of user-relevant information. For more information, see 4.7 ~test Page .

When NWBC creates a support ZIP file, it also includes all this information, if available.

This node can selectively be disabled.

Activate this node in low security systems because the additional troubleshooting information from the server can help extensively. We recommend that you disable this node for high security systems or systems directly connected to the internet.



This node is used for internal development only. Therefore, it should be disabled in all productive systems.

This is a test content area that is loaded into the NWBC shell with a test role to test different APIs.



This node is used for internal development only. Therefore, it should be disabled in all productive systems.

This allows you to run an alternative $TMP runtime for troubleshooting purposes.



This node controls the activation of an API that can be used by SAP NetWeaver Portal (SAP NetWeaver 7.02 or higher) to retrieve role information for using dynamically in an enterprise portal. For more information, see 6.5 HTTP REST Based APIs and SAP Library for SAP NetWeaver on SAP Help Portal at Start of the navigation path SAP NetWeaver Next navigation step SAP NetWeaver 7.0 including Enhancement Package 2 Next navigation step English Next navigation step SAP NetWeaver Developer's Guide Next navigation step IT-Scenario-Driven Enhancements to Applications Next navigation step Running an Enterprise Portal Next navigation step Reference Next navigation step Portal Web Services Next navigation step Navigation Web Service Next navigation step Navigation Data Types Next navigation step NavigationTreeRequest End of the navigation path.



This node is used when data is to be displayed in a side panel. The node converts the external representation of UI elements to an internal representation.

All remote systems must have a TRUST relationship to the NWBC logon system. Otherwise the HTTP request doing the conversion fails. For more information about authentication, see 7 Security Aspects and SAP Note 1611298 Information published on SAP site.



This node is used to test roles. You can start NWBC with roles that are not assigned to your user, but only with display authorization. This node makes the Other section on the ~launch page visible. For more information, see 4.8 ~launch Page .

This node is used for internal development only. Therefore, it should be disabled on all productive systems.

Customer Paths

We recommend that application groups and customers do not work under the path /sap/bc . If necessary, you can create new paths: /myCustomer/.../nwbc/myCockpit .

For NWBC nodes, the CL_NWBC_HTTP runtime handler must be configured. Access over the myCockpit node is also monitored; it must be available and active.

In addition, the system logon must be configured. For more information, see System Logon and Namespaces and Naming Conventions (BC-CTS-NAM) .

BSP and Web Dynpro ABAP

For BSP or Web Dynpro ABAP applications in NWBC, the relevant BSP/Web Dynpro ABAP-specific nodes must be active in the ICF service tree.

  • For more information about BSP settings, see Prerequisites in Administration of Business Server Pages

  • For more information about Web Dynpro ABAP settings, see Initial Configuration Settings in Initial System-Wide Configuration Settings for Web Dynpro ABAP and Active Services in SICF .

  1. From the back-end system, go to the ICF service tree ( SICF) transaction.

  2. Set the Hierarchy Type to SERVICE and choose Execute (F8) .

  3. Expand the nodes under the default_host .

    To access the cockpit subnode for NWBC, navigate to the following service tree: default_host/sap/bc/nwbc .

    Standard ICF service tree

  4. Select the relevant service node(s) and choose Start of the navigation path Service/Host Next navigation step Activate End of the navigation path.

More Information

4.5 Cockpits

7.6 ICF Configuration

Active Services in SICF

Internet Communication Framework