Show TOC

6.1.1 Short Form of URL Locate this document in the navigation structure

 

The short variant of the URL described in the table below can be used to start NWBC with just a shell. The long variant of the URL described in 6.1.2 Long Form of URL can load any type of content on startup.

By merging the different URL elements, the complete URL looks as follows:

[optional protocol handler://][optional authentication sequence@]<server sequence>/<ICF path>/[optional cockpit/]

Short URL

Element

Optional

Only NWBC for Desktop

URL

Description

Email bootstrap

yes

url:

This element is specifically available for NWBC for Desktop: If the startup URL is to be embedded in an e-mail, add the url: prefix to signal to Microsoft Outlook that this is a startable link and that should be treated as a hyperlink.

Protocol handler for desktop client

yes

yes

sap-nwbc://

The protocol handler is an extension added to Windows to allow NWBC to be started in the same way as a normal URL. When this "URL" starting with NWBC is used within a browser or from a startup icon, the URL is opened in the NWBC shell itself. This protocol handler is only needed if you intend to start NWBC for Desktop. If NWBC for HTML is to be started, the protocol handler must not be specified.

Authentication

yes

yes

<name>:<password>[optional connection parameters]@optional connection parameters

  ;connection=ABAP|portal

  ;proxy=<server>.<domain>.<ext>:<port>

  ;proxy-secure=<server>.<domain>.<ext>:<port>

  ;proxy-authentication=<name>:<password>

Similar to ftp://<name>.<password>@<server> to imbed authentication into the URL. Only supported with NWBC for Desktop. The connection is used to determine the type of server that will be connected to, the default is an ABAP server.

The proxy parameters can be employed to optionally specify a proxy to use to establish the connection. Note that you must usually specify both an HTTP proxy (;proxy sequence) and a proxy for HTTPS (;proxy-secure sequence). If necessary, supply the proxy authentication information (;proxy-authentication sequence). If a proxy configuration is specified, NWBC changes the Internet Explorer settings to use the proxy settings (for the current process) and restores the original settings when terminated.

Server address

http(s)://<server>.<domain>.<ext>[:<port>]

For the server address, use the regular http(s):// sequence with a fully qualified domain name (FQDN).

NWBC handler path

/nwbc

/sap/bc/nwbc

/<myCompany>/nwbc

This is the path within the ICF service tree to the NWBC handler. By default, use /sap/bc/nwbc, or, if available, the shorter /nwbc alias. You can also have a different ICF path specified in the ICF service tree.

Cockpit

yes

/<myCockpit>

/<ROLE_NAME>

Optional cockpit that is a filter onto the role repository. Alternatively, you can use the name of a role that is used in the same way as a cockpit. This means that only the role is displayed.

Trailing slash /

/

The extra slash / is needed to lock the previous segment.

Examples

A simple link to start NWBC for HTML:

    https://ldcibqi.wdf.sap.corp:44376/sap/bc/nwbc

 

A simple link to start NWBC for Desktop:

    sap-nwbc://https://ldcibqi.wdf.sap.corp:44376/sap/bc/nwbc

 

When the link is to be triggered from an e-mail, add the url: prefix:

    url:sap-nwbc://https://ldcibqi.wdf.sap.corp:44376/sap/bc/nwbc

 

A more complex example (only relevant for NWBC for Desktop) that includes authentication information and also information to traverse a proxy:

    sap-nwbc://user:password;proxy=proxy.domain.corp:8080;proxy-secure=proxy-domain.corp:8083;proxy-authentication=p-user:p-password@https://ldcibqi.wdf.sap.corp:44376/sap/bc/nwbc