SAP BusinessObjects Repository 6.x - Import - 7.1

Talend Data Catalog Bridges

author
Talend Documentation Team
EnrichVersion
7.1
EnrichProdName
Talend Big Data Platform
Talend Data Fabric
Talend Data Management Platform
Talend Data Services Platform
Talend MDM Platform
Talend Real-Time Big Data Platform
EnrichPlatform
Talend Data Catalog

Bridge Requirements

This bridge:
  • is only supported on Microsoft Windows.

  • requires the tool to be installed to access its SDK.

Bridge Specifications

Vendor SAP
Tool Name BusinessObjects (BO) Repository
Tool Version 6.x
Tool Web Site http://www.sap.com/solutions/sapbusinessobjects/large/intelligenceplatform/bi/information-infrastructure/enterprise
Supported Methodology [Business Intelligence] Multi-Model, Metadata Repository, BI Design (RDBMS Source, Dimensional Target, Transformation Lineage, Expression Parsing), BI Report (Relational Source, Dimensional Source, Expression Parsing, Report Structure), Graphical Layout via ODBC API
Incremental Harvesting
Multi-Model Harvesting
Remote Repository Browsing for Model Selection
Data Profiling

Import tool: SAP BusinessObjects (BO) Repository 6.x (http://www.sap.com/solutions/sapbusinessobjects/large/intelligenceplatform/bi/information-infrastructure/enterprise)
Import interface: [Business Intelligence] Multi-Model, Metadata Repository, BI Design (RDBMS Source, Dimensional Target, Transformation Lineage, Expression Parsing), BI Report (Relational Source, Dimensional Source, Expression Parsing, Report Structure), Graphical Layout via ODBC API from SAP BusinessObjects Repository 6.x Import bridge: 'BoRepository5to6' 10.1.0

This bridge requires SAP BusinessObjects SDKs and a specific Java JRE as explained below.

JAVA REQUIREMENTS
BusinessObjects supports Java 8 only and is not compatible with any version of OpenJDK which may be the default JRE.
Use the Miscellaneous parameter to point to a Java Environment supported by BusinessObjects.

BUSINESS OBJECTS SDK REQUIREMENTS
The bridge relies on the BusinessObjects Designer OLE/COM API to import the Universe metadata. Therefore, SAP BusinessObjects Designer must be properly installed on the machine executing this bridge.

The bridge relies on the SAP BusinessObjects Desktop Intelligence COM/OLE API to import the Report metadata. Therefore, SAP BusinessObjects Desktop Intelligence must be properly installed on the machine executing this bridge.

FREQUENTLY ASKED QUESTIONS
Q: What username and password should I supply as BO login?
A: Please provide a valid BO username and password, the same way you would login with Designer or Desktop Intelligence.
For example: supervisor (version 6.x)
If you are not sure about which username and password to use, you should contact your BO system administrator.

Q: The bridge fails to import some universes or reports for an unknown reasons, what can I do ?
A: Please try to run the bridge again with parameter 'Execution mode' set to 'Interactive'.
The application may display an error in a popup window.

Q: What report file formats does this bridge support?
A: This bridge can read the report formats supported by BusinessObjects Desktop Intelligence:
- BusinessObjects documents (*.rep)
- BusinessObjects document templates (*.ret)
- BusinessQuery Files (*.bqy)
- WebIntelligence 2.x documents (*.wqy)

Q: What report file formats are not supported?
A: BusinessObjects Desktop Intelligence and this bridge do not support:
- WebIntelligence 6.x documents (*.wid)
- Crystal reports (*.rpt)
- Crystal OLAP Analysis reports (*.car)

Q: Can this bridge run from an application server as a Windows service?
A: No, BO Designer is a desktop application, running the Designer COM api and this bridge as a service is not supported. Please make sure that if running from a remote bridge server, it is configured to run as a regular desktop application, not as a service.

SUPPORT
Q: How do I provide metadata to the support team to reproduce an issue?
A: For BusinessObjects 6.x, save the universe(s) as UNV file(s) and document(s) as REP file(s) with check the check-box 'Save for all users' enabled.


Bridge Parameters

Parameter Name Description Type Values Default Scope
Version Select here the version of BusinessObjects you want to connect to.
This software version must be installed on the computer that runs this bridge.
ENUMERATED
6.5.1
6.1.3
6.1b
6.1
6.0
6.5.1  
Repository name Enter here the name of the BusinessObjects repository to login to.

For BusinessObjects version 6.x it is the name of the repository defined by the Supervisor application. For example: bomain
STRING   bomain Mandatory
Repository user name A repository installation of BusinessObjects (BO) requires the user to identify himself/herself using a login.
For example: supervisor (version 6.x)
If you are not sure about which username and password to use, you should contact your BO system administrator.

This import bridge is warrantied to be read only and will never affect the Repository contents. It is therefore safe to attempt the initial metadata harvesting as 'Administrator' in order to ensure that the entire Repository content is extracted without any access permission issue. Eventually, the administrator can set up a 'read only' user.

Refer to the tool documentation on permissions and security for more details.
STRING   supervisor Mandatory
Repository user password A repository installation of BusinessObjects (BO) requires the user to identify himself/herself using a login. Enter the user password here. PASSWORD      
Repository ODBC DSN This bridge can connect to the BusinessObjects repository database to retrieve the list of domains, categories and documents.

Specify here the ODBC Data Source Name (DSN) to connect to the repository database.

Use the ODBC Administrator to configure the DSN for the repository database.
STRING     Mandatory
Repository ODBC user name This bridge can connect to the BusinessObjects repository database to retrieve the list of domains, categories and documents.

Specify here the ODBC user to connect to the repository database.

Use the ODBC Administrator to configure the DSN for the repository database.
STRING      
Repository ODBC user password This bridge can connect to the BusinessObjects repository database to retrieve the list of domains, categories and documents.

Specify here the ODBC password to connect to the repository database.

Use the ODBC Administrator to configure the DSN for the repository database.
PASSWORD      
Repository subset This option is used to access objects stored in a remote BusinessObjects Repository.

You can specify here multiple paths of universes to be retrieved, separated by semicolon (;) characters.

For BusinessObjects version 6.x, the format of universes path is: UniverseDomain/UniverseName. Example: Universe/beach; Universe/efashion
REPOSITORY_SUBSET      
Add dependent objects This parameter allows selection of documents that depend on the selected universes.

'True' - The documents dependent on selected universes are imported. (default)
'False' - The documents dependent on selected universes are not imported.

WARNING: This feature relies on the BO Repository metadata cache of dependency between universes and report documents, and therefore works well on production environments where all reports are actively used. However, in the context of BO Repositories in development and test environments, some universes and/or report documents may have been redesigned or moved leaving inaccurate dependency information in the BO Repository cache. In such case, all dependent report documents of a given universe may not be detected. The BO repository cache can be refreshed by loading such modified or moved report documents and refreshing the queries.
BOOLEAN   True  
Add specific objects This parameter allows selection of additional objects.

'Universe independent Documents' - The documents that do not depend on any universe are imported.
ENUMERATED
None
Universe independent Documents
None  
Class representation This parameter controls how the tree structure of Classes and subClasses should be imported. The bridge will import each Class containing Objects as a Dimension (as defined by the CWM OLAP standard). In addition, Classes and subClasses can also be imported as a tree of Packages (as defined by the CWM and UML standards).

'As a flat structure' - No Packages are created (default).
'As a simplified tree structure' - A Package is created for each Class with subClasses.
'As a full tree structure' - A Package is created for each Class.
ENUMERATED
As a flat structure
As a simplified tree structure
As a full tree structure
As a flat structure  
Import joins Specify whether joins and contexts should be imported.

'True' - The joins and contexts are imported. (Default)
'False' - The joins and contexts are not imported.
BOOLEAN   True  
Import hierarchies Specify whether hierarchies should be imported.

'True' - The hierarchies are imported. (Default)
'False' - The hierarchies are not imported.
BOOLEAN   True  

 

Bridge Mapping

Meta Integration Repository (MIR)
Metamodel
(based on the OMG CWM standard)
"SAP BusinessObjects Repository 6.x"
Metamodel
BoRepository
Mapping Comments
     
ClassifierMap   The Mapping Models use many ClassifierMaps to connect QuerySubjects and Filters defined in FM models with QuerySubjects and Filters used in reports
Connection   Used to store stitching mappings between report models and universe models
DirectoryStructureModel Repository  
Name name  
FeatureMap   The Mapping Models use many ClassifierMaps to connect Objects and Filters defined in Universe models with Objects and Filters used in documents
Folder Folder, Category  
Description description  
Name name  
MappingVersion   Used to store stitching mappings between report models and universe models
ModelVersion Universe, Document  
MultiModelVersion Repository  
StoreContent Universe, Document  
Name name  
NativeId path or id  
StoreModel Universe, Desktop Intelligence Document, WebIntelligence Document All runiverses and documents are imported using the Designer, Reporter and WebIntelligence import bridges. See the respective bridges specification for details on metadata mapping of each tool.
Name name