3.4.1 Configuring System Connections
In NWBC you can define one or more connections to different servers. A connection contains all relevant data required to instruct a server to retrieve all the relevant roles for a user. Since NWBC, as the shell, uses HTTP connections for its server communications, the connection data is also defined as a URL.
Although you can define several connections, you can have only one connection active at a time. If a new connection to a different system is started, NWBC is restarted to clear all cookies that were stored in process.
The connection data is usually provided by the system administrator and must be configured before you can use the connection.
You select the current system and configure system connections by choosing
Settings 
Connections Systems 
The following figure shows an example of the
Systems dialog box:
The table explains the system connection settings:
|
Setting |
Description |
|---|---|
|
Name |
The name for the system connection Note
Connections names must be unique names. |
|
URL |
The HTTP URL that is needed to connect to the server The server name must include a fully qualified domain part as well. The protocol is either http:// or https://. You must provide the complete domain and extension for the server name. For example, for a server at SAP, the complete string would be theServer.sap.com. If the default ports 80 for HTTP and 443 for HTTPS are not used, you can define a port. The path is usually either /sap/bc/nwbc for an ABAP-based connection, or /irj/portal for a portal-based connection. The complete syntax for the URL is as follows: http(s)://<server>.<domain>.<ext>:<port>/<path> |
|
Type |
You can connect with NWBC either directly to a single ABAP server (connection type Application Server ABAP ) or to a portal server (connection type Portal ). |
|
Client (only visible for a connection to an ABAP system) |
3-digit client for the connection, for example, 000 |
|
Language (only visible for a connection to an ABAP system) |
UI language of NWBC |
|
SAP GUI Logon Description (only visible for a connection to an ABAP system) |
If SAP Logon settings have been specified, SAP GUI for Windows running in NWBC uses them. The entry in the SAP GUI Logon Description field, for example, SYS [PUBLIC] , must correspond exactly to what is specified in SAP Logon (or else NWBC cannot find and use the settings). Examples of SAP Logon settings are SAProuter, group selection, and so on. The following figure shows the similarity of an entry in the Systems dialog to the same entry in SAP Logon.
Configure and test this SAP Logon entry by double-clicking it in SAP Logon. The connection can only work correctly in NWBC if it also works in SAP Logon. For more information about SAP Logon configuration, press F1 on the SAP Logon window to display the documentation. For more information about load balancing, see 3.6 Using NWBC with a Load Balancer . Secure Network Settings (SNC) work as of SAP GUI 7.20 patch level 4. Example
In this example scenario with one SAP Logon system and several remote systems, you can maintain the SAP GUI Logon Description not only for the SAP Logon system but also for the remote systems. This allows you to configure load balancing on the client side for the SAP Logon system and also for the remote systems. NWBC connects to the server Server_A of the system SYS. The roles for this system comprise the following remote clients and servers:
You have the following options to configure load balancing:
Then configure all necessary entries in SAP Logon (RMA [PUBLIC] and RMB [PUBLIC]) and configure load balancing for them. |
|
Comment |
A user-defined comment that can contain any textual information. This is typically used to write short descriptions about the system. |
