SAP UI Landscape

As an administrator, you can use the same infrastructure to define and distribute system connections for usage by SAP GUI for Windows and NWBC for Desktop.

SAP UI landscape covers:

NWBC Web AS ABAP or Portal connections
SAP GUI connections
SAP Shortcuts

NWBC can read, write, and parse the new landscape format. Thus, the system selection dialog is based on the landscape files SAPUILandscapeGlobal.xml and SAPUILandscape.xml, and the NwbcOptions.xml file is reduced to single options only. If no landscape files exist, NWBC performs a migration as described in Migration of Configuration Data.

SAP UI Landscape XML Description

This section describes the SAP UI Landscape XML format. This file format is used in the SAP GUI configuration with NWBC. The following picture shows the basic elements of the xml file:

<?xml version="1.0" encoding="UTF-8" ?> 
<Landscape>

<Messageservers>
	<Messageserver uuid="3b764f2a-edba-493e-a470-2ad33b57f429" name="MS1" host="ms1server.mycorp.com" port="1234" /> 
	<Messageserver uuid="0dfd524e-a4cb-4534-8c44-2e5bcd39b3f0" name="MS2" host="ms2server.mycorp.com" port="2345" /> 
</Messageservers>

<Routers>
  <Router uuid="c63af9a6-47db-4a5b-a632-359c09465fdf" name="MyCorp Router" router="/H/sapgateway.mycorp.com/S/3456/H/" /> 
  </Routers>

<Services>
	<Service uuid="6fe11a42-bfb9-4683-8013-9aa4a69abb2a" name="AB1 [PUBLIC]" msid="3b764f2a-edba-493e-a470-2ad33b57f429" type="SAPGUI"
             systemid="AB1" server="PUBLIC" sncop="9" low_speed_connection="0" sapcpg="1100" dcpg="2" sncname="p:CN=AB1, O=SAP-AG, C=DE" /> 
	<Service uuid="449feb59-18e7-4f0c-9ee6-9835a0ff9298" name="CD2 [PUBLIC]" msid="0dfd524e-a4cb-4534-8c44-2e5bcd39b3f0" type="SAPGUI"
             systemid="CD2" server="PUBLIC" sncop="9" low_speed_connection="0" sapcpg="1100" dcpg="2" sncname="p:CN=CD2, O=SAP-AG, C=DE" routerid="c63af9a6-47db-4a5b-a632-359c09465fdf" /> 
	<Service uuid="3d06eada-7c75-4667-b0c3-2a09e0c6036d" name="CD2 in NWBC" type="NWBC" description="Inheriting CD2[PUBLIC] properties for applications rendered with SAP GUI" 
			 systemid="CD2" msid="0dfd524e-a4cb-4534-8c44-2e5bcd39b3f0" server="app1server.mycorp.com" url="https://app1server.mycorp.com:54321/ui2/nwbc" 
			 client="120" sapguiid="449feb59-18e7-4f0c-9ee6-9835a0ff9298" />
	<Service uuid="8cd44ab2-ff99-4d24-bfdd-c00238c0bc4e" name="Search SAP.com" type="SEARCH" 
			 url="http://www.sap.com/search/search-results.html?Query={0}" mnemonic="sap"/>		 
</Services>

<Workspaces>
	<Workspace uuid="e8c4bafe-8f48-4834-84e0-4243bec67ff6" name="Information Developers' Workspace" expanded="1" hidden="0" description="Lorem ipsum">
		<Node uuid="2aaa8f34-0093-47dd-b088-d1817a98c863" name="Online Documentation Backends" description="Store your ongoing online texts in these systems." >
			<Item uuid="e685d4e8-2d74-44bf-8728-a89fc8b38c69" serviceid="6fe11a42-bfb9-4683-8013-9aa4a69abb2a" />
			<Item uuid="f8ef9181-5fec-4d8d-833e-aca554128c31" serviceid="449feb59-18e7-4f0c-9ee6-9835a0ff9298" />
			<Item uuid="d5970be4-8ba1-43f2-a460-8f62a329fdad" serviceid="3d06eada-7c75-4667-b0c3-2a09e0c6036d" />
		</Node>
		<Item uuid="02416208-5c9d-4326-94ce-fc958e906865" serviceid="449feb59-18e7-4f0c-9ee6-9835a0ff9298" />
	</Workspace>
</Workspaces>
	
<Includes>
	<include index="1" url="http://corpwebserver.mycorp.com/saplandscapes/AdditionalSAPUILandscape_1.xml"/>
	<include index="2" url="http://corpwebserver.mycorp.com/saplandscapes/AdditionalSAPUILandscape_2.xml"/>
</Includes>

</Landscape>

The file consists of the following basic elements:

Specification of the encoding.
Definition of the message servers available in the current system landscape with uuid, name, host and port.
Note You can find the resources to generate UUIDs in the Internet.
The message server list should contain at least the message server definitions used in the services section described below.
Definition of the routers with uuid, name and complete router string.
Definition of services
This is a flat, non-hierarchical list of all services referred to from within Workspaces. The list can also contain services not referred to that are used on client-side for creating user workspaces or for building other features such as a Favorites list or search provider list.

Generally, a service entry consists of uuid, name and type (= service type, for example SAP GUI connection, SAP GUI shortcut, NWBC connection to WebAS ABAP or Portal, or search provider used by NWBC).
Depending on the service type, you can specify additional attributes:
- For SAP GUI connections, the service entry contains message server uuid , systemid , server (group or hostname:port), SNC and codepage entries. You can set the following SNC entries:
  - with sncop, you define, if single-sign-on is disabled (disabled = 0)
  - with sncname the SNC name is defined, for example, p/secude:CN=ACM, 0=ACME, C=DE.
  With regard to the encoding, you have the following possibilities:
  - With sapcpg, the SAP Codepage can be selected, for example 0,1,2,11000, and so on.
  - With dcpg, the Sap Codepage for upload and download is defined. Example values: 0,1,2,1100, and so on.
- For NWBC connections to Web AS ABAP backends, the service entry must contain the connection URL. Message server UUID, system ID, server, client, language, and UUID of a referenced SAP GUI connection are optional.
- For NWBC connections to Portal backends, the service entry must contain the connection URL.
- In search-provider service entries, the search URL (according to the NWBC End User Guide chapter Search Types) is defined. Mnemonics are optional.
Definition of workspaces, its nodes and items
A workspace is a group of connections for certain users, for example, for information developers. It consists of a group of services (items) and folders (nodes). A workspace can be used to show a predefined service set in the UI or be used for multi-logon for all services in the workspace. The workspace is a special kind of top node.

A workspace is defined by uuid, name, expanded (the state of the folder in the UI: open or closed; the default is true), hidden (this marks the workspace as hidden and invisible in the UI).

The nodes (folders) are item-grouping elements of the workspace; they are used to organize the items (services) within the workspace. From nodes and items, tree structures can be built. Items are placeholders for services, and the data is taken from the service description. You can define items directly in the workspace or in a node.

A node is defined with uuid, name, description, expanded (see above paragraph), hidden (this marks the node as hidden and invisible in the UI, and allows changing workspace configuration locally).

An item is defined with uuid, serviceID (ID of the service that the items refer to; it should be one of the known services from the service repository), hidden (marks the item as hidden and invisible in the UI, and allows changing the workspace configuration locally).
Includes
An include is a file or URL containing information that you want to merge with the content in your XML. This means, for example, that you do not need to define message servers directly in this XML file, but that you can point to this information from within the includes section. An include node describes a single source to include, and can have the following attributes: URL, index (shows which include is loaded first), name, and description.

For information on validating your XML file that you have adapted in line with your landscape, see the SAP Note 2112449 Information published on SAP site .

Active Directory (LDAP) Support

For information on Active Directory (LDAP) support see SAP Note 608781 Information published on SAP site . To use the message servers provided by Active Directory support in NWBC connections, you must first create a corresponding SAP GUI connection.