Skip to end of metadata
Go to start of metadata

SAP Visual Business supports a number of raster-based map tile providers. To access maps from a particular map provider inside SAP, a map provider must fulfil the following requirements:

      • The map provider must support a quad key interface. This is the standard interface for map tiles.
      • The maps tiles can be retrieved using a REST web service.
      • The map tiles must be raster-based image tiles (not a vector format)

If you want to change the map provider or install Visual Business for the first time, you must enter the license information and/or switch to your preferred map provider. This information is maintained in the backend system and sent to the frontend when it is initialized. 

The maintenance of the application definitions can be found in Maintain Application Definitions in the SAP Reference IMG under SAP NetWeaver > UI Technologies > SAP Visual Business 

The definitions are structured in 3 parts, which build upon each other:

      • Map Products
      • Map Layer Stacks
      • Applications

In a production environment scenario, there is no map licensed by default.  You will need to purchase a map license directly from a map provider or use your own maps.

The GeoMap component has a pre-defined default setup, which is also shipped to customers.

Map Product Definition

Map products are the base for all further definitions. Therefore, at least one Map Product needs to be defined before any further definitions can be made. The Map Product describes a single map with its technical parameters and the service location.

Each map product needs a unique ID and should have a description. In the technical parameters, you describe the size of the map tiles in pixels, the supported zoom levels (LOD), the name of the service provider, the copyright information, the Projection, the Resolution, the Number of Retries (in the event of failure in obtaining map tiles from a map server). The details of each of the parameters is described in the F1-help of the respective field. The available service URLs need to be provided in the sub-node Map Server.

The actual service URLs are specified as templates, using a certain set of placeholders, which will be filled at runtime. The available placeholders and their meaning are described in the F1-help for the URL field. Map Server URL Configuration also provides a detailed description of the placeholders. If the map service provider runs multiple servers for the service, you can specify all of them for load distribution. At runtime, this URL scheme with the placeholders is filled with their values and the URL is requested. The URL scheme entry can be tested with the Test Server Entry button.

For descriptions on the different URL scheme map providers, refer to the following topics:

Map Layer Stack Definition

A map layer stack describes what is displayed as a map by the Visual Business frontend. It has a unique ID and a description. It allows to stack multiple layers, where each layer refers to a map product. The layers are combined in the given sequence, where the first layer is the bottom most one and each succeeding layer will be painted on top of the previous layer. Due to this layering, it may be useful to reduce the opacity of succeeding layers, if they are opaque in nature. It may also be useful to specify the background colour for transparent parts, whether the map is a tile-based map or a single picture layer, the layer dependency. The F1-help on each of these fields describes their significance. 

Application Definition

The application definition is the final bracket around the prior definitions. Like the map layer stack definition, the application definition also has a unique ID and a description. On the application level, you can define a scene’s navigation behaviour and the visual appearance of the navigation control.

In the NavControl Function Settings section, you can disable certain functions; for example, map rotation. In the NavControl Visual Appearance section, you can disable parts of the navigation control; for example, the zoom slider to save space. It makes sense to suppress the control parts related to disabled functions. However, it is a valid case to visually reduce the navigation control, but to retain its full functionally. Hence, the two sections are separated. 

Finally, you need to assign one or more map layer stacks to an application. If more than one is assigned it is also necessary to mark one as the default map layer stack. All other map layer stacks can be made available to the user through personalization in the context menu. After choosing a layer stack the user must press F5 to update the screen to see a new map.