SAP BO Resource Configuration

Note: Before you configure your scanner, make sure you meet the prerequisites. Read our guide on SAP BO Integration Requirements to double-check.

Source System Properties

This configuration can be setup by creating a new connection on Admin UI > Connections tab or editing an existing connection in Admin UI > Connections > Reporting & BI > SAP BO > specific connection. New connection can also be created via Manta Orchestration API General Walkthrough Example.

One IBM Automatic Data Lineage connection corresponds to one SAP BO server and its content store. Reports, universes, and database connection information that are stored inside the server will be analyzed.

This automatic extraction requires a connection via SAP BO SDK libraries, which are distributed with SAP BO Client Tools.

Common Source System Properties

Property name	Description	Example
sapbo.extractor.host	Host name or IP address of the SAP BO server	localhost
sapbo.extractor.port	Port for a connection to the SAP BO server; the default port is 6400	6400
sapbo.extractor.port_rest	Port for SAP BO server HTTP requests; the default port is 6405	6405
sapbo.extractor.user	User name for a connection to the SAP BO server	UserName
sapbo.extractor.password	Password for a connection to the SAP BO server	`*******`
sapbo.extractor.auth	Authentication method for a connection to the SAP BO server; the default is secEnterprise	secEnterprise
sapbo.extractor.id	Artificial ID for distinction between different SAP BO connections	123 abc
sapbo.extractor.include	Comma-separated list of document IDs to include in the extraction; empty if all documents should be included in the extraction	6655,5599
sapbo.extractor.exclude	Comma-separated list of document IDs to exclude from the extraction; empty if no special documents should be excluded from the extraction	6655,5599
sapbo.extraction.method	Set to Agent:default when the desired extraction method is the default Manta Extractor Agent, set to Agent:{remote_agent_name} when a remote Agent is the desired extraction method, set to Git:{git.dictionary.id} when the Git ingest method is the desired extraction method. For more information on setting up a remote extractor Agent please refer to the Manta Flow Agent Configuration for Extraction documentation. For additional details on configuring a Git ingest method, please refer to the Manta Flow Agent Configuration for Extraction:Git Source documentation.	default Git agent
sapbo.installation.path	Enter the path to the SAP BO folder; if Client Tools are not installed, leave empty. The window path must have the folder separators escaped (duplicated).	C:\\Program Files (x86)\\SAP BusinessObjects\\SAP BusinessObjects Enterprise XI 4.0

Common Scanner Properties

This configuration is common for all SAP BO source systems and for all SAP BO scenarios, and is configure in Admin UI > Configuration > CLI > SAP BO > SAP BO Common. It can be overridden on individual connection level.

Property name	Description	Example
sapbo.input.dir	Directory with files extracted from the SAP BO server	${manta.dir.temp}/sapbo/${sapbo.extractor.id}
sapbo.odbc.connection.definition.file	Path to the optional ODBC connection definition file	${manta.dir.input}/sapbo/${sapbo.extractor.id}/connection_definition/odbcConnectionDefinition.ini
sapbo.odbc.connection.definition.encoding	Encoding of the ODBC connection definition file. See Encodings for applicable values.	UTF-8
manta.extraction.agent.additional.classpath.sapbo.sdk.lib	List of the Semantic Layer Java SDK JAR files used from the java/lib folder	${sapbo.installation.path}/java/lib/sapjce.jar
manta.extraction.agent.additional.classpath.sapbo.sdk.plugins	List of the Semantic Layer Java SDK JAR files used from the eclipse/plugins folder	${sapbo.installation.path}/SL SDK/eclipse/plugins/org.eclipse.emf.common.jar
manta.extraction.agent.additional.classpath.sapbo.sdk.axis	List of the Semantic Layer Java SDK JAR files used from the external/axis2 folder	${sapbo.installation.path}/java/lib/external/axis2/1.7.9/axis2-adb-1.7.9.jar

ODBC Connection Definition Settings

The connection settings for SAP BO are automatically exported by Automatic Data Lineage during lineage analysis, but to resolve the ODBC connector, Automatic Data Lineage needs more information about the source/destination system. The settings can be configured manually as follows.

Create or open the file referenced using the sapbo.odbc.connection.definition.file property (e.g., <MANTA_DIR_HOME>/input/sapbo/${sapbo.extractor.id}/connection_definition/odbcConnectionDefinition.ini).
Fill in each connection as much as possible. If you don't know how to fill in a property, leave it empty or don't even add it to the configuration file.
Add a new section for each connection shortcut; for example:
- [Shortcut_Name] — the data source name used in the ODBC connector
- Type=Oracle — a type of system such as:
  - Oracle
  - Teradata
  - MS SQL
  - Sybase
  - Netezza
  - Db2
  - JDBC
  - ODBC
  - FTP
  - Etc.
- Connection_String=orcl — it can be a JDBC connection string or any database identification such as the SID or host name; it can match the Connection_Id in the manual dictionary mapping
- Server_Name=Server — the value depends on the type of system:
  - Microsoft SQL Server, Sybase, Teradata, Db2, Netezza — the name of the server
  - Oracle and other databases — this value is ignored
  - FTP — host name
- Database_Name=ORCL11 — the value depends on the type of system:
  - Oracle — global database name
  - Teradata, Microsoft SQL Server, Sybase, Db2, Netezza, and other databases — name of the default database
- Schema_Name=Default — the value depends on the type of system:
  - Teradata — this value is ignored
  - Microsoft SQL Server, Sybase, Oracle, Db2, Netezza, and other databases — name of the default schema
- User_Name=user — user name that logs in to the database (helps map the default database or schema; can be ignored)
Add a new line at the end of the parameters for each section.

Example of a section in the configuration file:

[Medical]
Type=MSSQL
Connection_String=jdbc:sqlserver://192.168.0.16:1433
Server_Name=
Database_Name=
Schema_Name=TestSchema
User_Name=user