Adding an SAP BO Connection

Prerequisites

• A user with sufficient permissions is required to connect to SAP BO.
• Zeenea traffic flows towards the database must be opened.

note

A template of the configuration file can be downloaded here: sap-bo.conf.

Supported Versions

The SAP BO connector is compatible with all recent versions in which the Rest API is exposed (necessary for the connector to access and harvest metadata).

Installing the Plugin

The SAP BO connector can be downloaded here: Zeenea Connector Downloads

For more information on how to install a plugin, please refer to the following article: Installing and Configuring Connectors as a Plugin.

Declaring the Connection

Creating and configuring connectors is done through a dedicated configuration file located in the /connections folder of the relevant scanner. The scanner frequently checks for any change and resynchronises automatically.

Read more: Managing Connections

The following parameters are required in order to establish a connection with SAP BO.

Parameter	Expected value
name	The name that will be displayed to catalog users for this connection.
code	The unique identifier of the connection on the Zeenea platform. Once registered on the platform, this code must not be modified or the connection will be considered as new and the old one removed from the scanner.
connector_id	The connector type to use for the connection. Here, the value must be sap-bo and this value must not be modified.
connection.url	URL towards the SAP BO REST API (e.g., http://:6405). This URL can be obtained from the Central Management Console (CMC)
connection.username	User’s technical identifier
connection.password	User password
connection.auth_type	Authentication type (secEnterprise, secLDAP, secWinAD, secSAPR3). Default value secEnterprise.
tls.truststore.path	The Trust Store file path. This file must be provided in case TLS encryption is activated (HTTPS protocol) and when the server's certificates have been delivered by a specific Certification Authority. The file must contain the certification chain.
tls.truststore.password	Trust Store password
tls.truststore.type	Trust Store type. Possible options are pkcs12 or jks.
proxy.scheme	Depending on the proxy, http or https
proxy.hostname	Proxy address
proxy.port	Proxy port
proxy.username	Proxy username
proxy.password	Proxy user password

User Permissions

In order for the connector to harvest metadata, the running user associated with it must be able to list and read objects that need to be cataloged.

Metadata Extraction

To harvest metadata, the connector will run the following API queries:

• GET & POST /biprws/logon/long : authentication query
• /universes
• /universes/$param
• /documents
• /documents/$param
• /documents/$param/dataproviders
• /documents/$param/dataproviders/$param to harvest all assets (visualizations, datasets, fields)

Collected Metadata

Inventory

The inventory lists all visualizations (Webi Documents) the running user has access to.

Visualization

A visualization is a Webi Document.

• Name
• Source Description
• Technical Data:
  • SAP ID
  • UUID

Datasets

A dataset is a Data Provider or an SAP Universe.

• Name
• Source Description
• Technical Data:
  • SAP Identifier
  • RowNumber (Data Provider)
  • Universe type (SAP Universe)

Fields

One field per table (dataset) column.