Configuring Servers with the NWBC_CONFIG Configuration Table 

You use the NWBC_CONFIG table to define the basic configuration settings for your cockpit.  The table is delivered without entries. You maintain the table in transaction SE16. You can define a set of name/value pairs for each existing cockpit, as specified below. The cockpit name corresponds to the relevant node in the HTTP service tree in transaction SICF. If you specify * instead of a specific cockpit, the settings are valid for all existing cockpits. The individual entries are evaluated in the listed sequence.

The following entires are used if there are no relevant entries in the NWBCClient.ini file.

BRANDING_ROLE

Name of the customer role in transaction PFCG.

When you set up a cockpit you normally define the corresponding administrator role, either for cockpits delivered by SAP or for cockpits in the customer namespace. However, if you did not make this setting, the system uses BRANDING_ROLE.

BRANDING_PAGE

External URL pointing to a customer application to be started: http://<app>

If using BRANDING_ROLE, the first application to be started is BRANDING_PAGE.

BRANDING_URL

URL pointing to a customer logo: http://...<name>.<ext>

jpg, gif, and so on formats can be used (size: n x m pixels).

You have to provide the image in question for download using HTTP. You have the following options here:

●      Copy the image to the AS-ABAP drives. Add the relevant code line for the profile so that the ICM can stream out the files in the relevant directories. We recommend you to do this.

●      Store the image in the MIME repository.

●      Place the image in a Web service or on a shared drive that can be accessed using file://.

●      Link to images on the SAP Service Marketplace.

We recommend that you do not use authentication here (public).

Customers can then add their own branding element beneath the home area. When the NWBC is next started, the new branding element is displayed instead of the standard SAP branding element.

SAPGUI_ROUTING

Route string that must be used for SAP GUI sessions started by the Business Client in order to reach the correct server: sapgui://<application server>:<application port>

An SAP route string has the format (/H/host/S/service/W/pass)*. Multiple sequences may be used. See also Route Strings.

However, a format like the one for HTTP should be used in the Business Client. A typical URL is http://host.domain.ext:port/segments/application?name1=value1&...&nameN=valueN. So the format defined as start URLs for SAP GUI transactions looks like: sapgui://host:port//host:port/application.variant?name1=value1&...&nameN=valueN. Here // indicates a jump in the SAP route string. When the SAP GUI is started, the string is converted into (multiple) sequences of /H/host/S/port.

INFO_CENTER_URL

URL to a customer-specific information page.

SERVER_HOMEPAGE

URL to a server home page with information on server-based installation and distribution.