As an administrator, you can use the same infrastructure to define and distribute system connections for usage by SAP GUI for Windows and SAP Business Client.
<?xml version="1.0" encoding="UTF-8"?> <Landscape updated=" 2015-07-06T12:13:46Z"> <Messageservers> <Messageserver port=" 1234" host=" ms1server.mycorp.com" name=" MS1" uuid=" 3b764f2a-edba-493e-a470-2ad33b57f429"/> <Messageserver port=" 2345" host=" ms2server.mycorp.com" name=" MS2" uuid=" 0dfd524e-a4cb-4534-8c44-2e5bcd39b3f0"/> </Messageservers> <Routers> <Router name=" MyCorp Router" uuid=" c63af9a6-47db-4a5b-a632-359c09465fdf" router=" /H/sapgateway.mycorp.com/S/3456/H/"/> </Routers> <Services> <Service name=" AB1 [PUBLIC]" uuid=" 6fe11a42-bfb9-4683-8013-9aa4a69abb2a" sncname=" p:CN=AB1, O=SAP-AG, C=DE" dcpg=" 2" sapcpg=" 1100" sncop=" 9" server=" PUBLIC" systemid=" AB1" type=" SAPGUI" msid=" 3b764f2a-edba-493e-a470-2ad33b57f429"/> <Service name=" CD2 [PUBLIC]" uuid=" 449feb59-18e7-4f0c-9ee6-9835a0ff9298" sncname=" p:CN=CD2, O=SAP-AG, C=DE" dcpg=" 2" sapcpg=" 1100" sncop=" 9" server=" PUBLIC" systemid=" CD2" type=" SAPGUI" msid=" 0dfd524e-a4cb-4534-8c44-2e5bcd39b3f0" routerid=" c63af9a6-47db-4a5b-a632-359c09465fdf"/> <Service name=" CD2 in NWBC" uuid=" 3d06eada-7c75-4667-b0c3-2a09e0c6036d" server=" app1server.mycorp.com" systemid=" CD2" type=" NWBC" msid=" 0dfd524e-a4cb-4534-8c44-2e5bcd39b3f0" sapguiid=" 449feb59-18e7-4f0c-9ee6-9835a0ff9298" client=" 120" url=" https://app1server.mycorp.com:54321/ui2/nwbc" description=" Inheriting CD2[PUBLIC] properties for applications rendered with SAP GUI"/> <Service name=" Fiori Launchpad" uuid=" b9369204-9215-42f5-92ff-1abac32e24e0" url=" https://frontendserver.mycorp.com:54321/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html" client=" 120" type=" FIORI" systemid="UV2"/> <Service name=" Search SAP.com" uuid=" 8cd44ab2-ff99-4d24-bfdd-c00238c0bc4e" type=" Search" url=" http://www.sap.com/search/search-results.html?Query={0}" mnemonic=" sap"/> </Services> <Workspaces> <Workspace name=" Information Developers' Workspace" uuid=" e8c4bafe-8f48-4834-84e0-4243bec67ff6" description=" Lorem ipsum" hidden=" 0" expanded=" 1"> <Node name=" Online Documentation Backends" uuid=" 2aaa8f34-0093-47dd-b088-d1817a98c863" 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=" 55d306b0-2e45-4593-96a3-bebca62089f4" serviceid="b9369204-9215-42f5-92ff-1abac32e24e0" /> <Item uuid=" 02416208-5c9d-4326-94ce-fc958e906865" serviceid=" 449feb59-18e7-4f0c-9ee6-9835a0ff9298"/> </Workspace> </Workspaces> <Includes> <include url=" http://corpwebserver.mycorp.com/saplandscapes/AdditionalSAPUILandscape_1.xml" index=" 1"/> </Includes> </Landscape>
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, SAP Business Client connection to Web AS ABAP or Portal, SAP Fiori launchpad connection, or search provider used by SAP Business Client).
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).
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 .
For information on LDAP support, see SAP Note 608781 . To use message servers provided by Active Directory Support in SAP Business Client connections, first create a corresponding SAP GUI connection.