SAP BusinessObjects Web Intelligence (Webi) XI - 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) Web Intelligence (Webi)
Tool Version 11.x to 14.x
Tool Web Site http://www.sap.com/solutions/sapbusinessobjects/large/intelligenceplatform/bi/qra/web_intelligence/
Supported Methodology [Business Intelligence] BI Design (Transformation Lineage, Expression Parsing), BI Report (Relational Source, Dimensional Source, Expression Parsing, Report Structure) via Java API
Incremental Harvesting
Multi-Model Harvesting
Remote Repository Browsing for Model Selection
Data Profiling

BRIDGE INFORMATION
Import tool: SAP BusinessObjects (BO) Web Intelligence (Webi) 11.x to 14.x (http://www.sap.com/solutions/sapbusinessobjects/large/intelligenceplatform/bi/qra/web_intelligence/)
Import interface: [Business Intelligence] BI Design (Transformation Lineage, Expression Parsing), BI Report (Relational Source, Dimensional Source, Expression Parsing, Report Structure) via Java API from SAP BusinessObjects Web Intelligence (Webi) XI
Import bridge: 'BoWebIntelligence' 10.1.0

BRIDGE DOCUMENTATION
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 SAP BusinessObjects WebIntelligence Java API to import reporting metadata. Therefore, the SAP BusinessObjects WebIntelligence API must be available on the machine executing this bridge.

For XI versions 4.0 SP6 and newer, this bridges uses the WebIntelligence RESTful Web Service SDK.
For XI versions 4.0 up to SP5, this bridge uses the deprecated WebIntelligence Report Engine (Rebean) SDK, which provides limited metadata.
For XI versions up to 3.x, this bridge uses the WebIntelligence Report Engine (Rebean) SDK.

To ensure the API is correctly installed and working, there must be a BusinessObjects client installation on this machine that is able to connect to the server.

There is a tool available from SAP BusinessObjects which can test for some connectivity issues. Go to Start -> All Programs -> Business Objects XI -> Diagnostic Tool. You must login with the same credentials as you use with the MIMB bridge. Then go to the menu Tests -> Run All Tests. You should see that all tests 'Pass'.

In addition, one may customize the configuration file used to control what tests are performed. It is located at C:\Program Files (x86)\Business Objects\common\4.0\java\lib\TestClasses.xml in the default SAP BusinessObjects client installation.

If any of these tests fail, please contact the local SAP BusinessObjects Administrator to resolve these issues. Please refer to Chapter 5, 'Working with Firewalls' in the SAP BusinessObjects Administration Guide.

At runtime, the bridge requires the following SAP BusinessObjects 'servers' to be started and enabled on the SAP BusinessObjects environment:
- for WebIntelligence Report Engine (Rebean) SDK: WebIntelligenceProcessingServer
- for WebIntelligence RESTful Web Service SDK: WebApplicationContainerServer (applicable for version XI R4.x)

Use the Central Management Console web application to check:
- Under the 'Servers' menu: the above servers are available and running correctly
- Under the 'Applications' menu: the 'RESTful Web Service' is available, it may not be installed by default.

The BusinessObjects BI Platform SDK is based on CORBA technology.
When connecting to a remote server, the CORBA networking layer performs a bi-directional resolution of the server name/address.
Therefore, it is necessary to ensure that the specified server name/address can be resolved in the client environment.
The name resolution is usually successful when the client and server are part of the same enterprise network.
However when connecting from a client network to a server in a different network (for example Amazon AWS),
it may be necessary to configure an entry in the local host file (C:\Windows\System32\drivers\etc\hosts) like so:
1.2.3.4 servername

SUPPORT
Q: How do I provide information to help the support team reproduce an issue?
A: - For BusinessObjects 11.x and 12.x (XI), create a Business Intelligence Archive file (*.BIAR) using the BusinessObjects Import Wizard utility (ImportWiz.exe) and include the document in it.
- for BusinessObjects 14.x (XI R4): using the Lifecycle Management Console, create a promotion job that has the required Infoobjects in it. Export the job as BIAR file. Below is the outline (for more details please see "Lifecycle management console for SAP BusinessObjects Business Intelligence platform 4.0 User Guide"):
1. Log into the lifecycle management console application. By default, you will be taken to the "Promotion Jobs" page.
2. Select New Job.
3. Enter the name, description, and keywords for the job in the appropriate fields.
4. In the "Save Job in" field, browse and select the repository folder where you want to save the job.
5. From the Source drop-down list, select the current system.
If the name of the current system is not listed, select the Login to a new CMS option. A new window is launched. Enter the name of the current system along with the username and password.
6. In the Destination drop-down list, select "Output to LCMBIAR File".
7. Click Create. A new job is created and stored in the CMS repository of the current system.
8. Add Infoobjects to the Job (including universes and connections of interest). You can also use the Manage Dependencies option to include the dependents of the selected Infoobjects.
9. Once done adding Infoobjects to the job, click Promote. The "Promote" window appears.
10.Click Export. You can choose to save the resulting BIAR file to a File System or an FTP location.
Send the BIAR file to the support team.

Q: Is there a way to test that the WebIntelligence RESTful Web Service is working correctly?
A: It is possible to test the BusinessObjects 14.x (XI R4) WebIntelligence RESTful Web Service by connecting to the following URLs:
Login api: http://boserver:6405/biprws/logon/long
InfoStore api: http://boserver:6405/biprws/infostore/12345
About api: http://boserver:6405/biprws/raylight/v1/about

The developer documentation is available at:
http://help.sap.com/businessobject/product_guides/boexir4/en/xi4sp9_webi_restful_ws_en.pdf
The Curl command line utility allows automating such api calls as command line scripts:
http://curl.haxx.se/


Bridge Parameters

Parameter Name Description Type Values Default Scope
Version Select the version of BusinessObjects you want to connect to. This software version must be installed on the computer running this bridge.

For all 14.2 (XI R4.2) Service Packs, select 14.2 as version.

For all 14.1 (XI R4.1) Service Packs, select 14.1 as version.

For 14.0 (XI R4.0) Service Pack 6 and above, select 14.0.6 as version.

For 14.0 (XI R4.0) up to Service Pack 5, select 14.0 as version.

For all 14.0 (XI R4) Service Packs, select 14.0 as version.

For all 12.1 (XI R3.1) Service Packs, select 12.1 as version.

For all 11.5 (XI R2) Service Packs, select 11.5 as version.

For all 11.0 (XI) Service Packs, select 11.0 as version.
ENUMERATED
14.2 (XI R4.2)
14.1 (XI R4.1)
14.0.6 (XI R4.0 SP6 and above)
14.0 (XI R4.0 up to SP5)
12.1 (XI R3.1)
12.0 (XI R3)
11.5 (XI R2)
11.0 (XI)
14.2  
System Enter here the name of the BusinessObjects repository to login to.

For BusinessObjects version 11.x and 12.x (XI), it is the name of the Central Management Server. This server will be used to login, by default on port 6400. For example: localhost
STRING     Mandatory
Authentication mode Select the login authentication mode to be performed.

'Enterprise' - BusinessObjects Enterprise login.
'LDAP' - Login using an LDAP server.
'Windows AD' - Login using a Windows Active Directory server.

The default authentication mode is 'Enterprise'.

Note: Windows AD authentication can be configured using Kerberos configuration files.
Update the file $MetaIntegration/conf/conf.properties to specify the Java virtual machine parameters:
M_JAVA_OPTIONS=-Djava.security.auth.login.config=C:\Windows\bscLogin.conf -Djava.security.krb5.conf=C:\Windows\krb5.ini

For details, see SAP Note 1621106:
http://service.sap.com/sap/support/notes/1621106
ENUMERATED
Enterprise
LDAP
Windows AD
Enterprise  
User name BusinessObjects Web Intelligence requires the user to identify himself/herself by logging into the Central Management Server. Enter the user name here. STRING   Administrator Mandatory
Password BusinessObjects Web Intelligence requires the user to identify himself/herself by logging into the Central Management Server. Enter the user password here. PASSWORD      
WebIntelligence Document ID Specify here the ID number of the Web Intelligence document to retrieve NUMERIC     Mandatory
WebIntelligence locale BusinessObjects Web Intelligence can display metadata object names in different languages, based on a locale.
You can control which language to use to import the document by typing the desired locale in this parameter.
For example, if the universe the document depends on was originally designed in German (de_AT), and later translated with the Translation Manager tool into English (en_US), you can specify either of these locales to import the document in the preferred language.
STRING      
__Connection list Internal semicolon delimited list of connection names and their data types. STRING      
Miscellaneous Specify the following miscellaneous options:
-jre "C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win32_x86\jre8\bin\javaw.exe"

-jre:
You may need to specify a Java environment supported by BusinessObjects, if the default JVM is not compatible (OpenJDK 11 instead of Oracle JVM 8) or if the default JVM is 64 bit but the universes are using ODBC connections, which require a 32 bit JVM.
UNX Universes based on jdbc connections are supported with a 64 bit JVM.
UNX Universes based on other types of connections (odbc, oledb, ...) are only supported if using a 32bit JVM.
You may specify the path to a 32 bit JVM in this option, in order to support UNX universes based on an odbc connection.

-m the maximum Java memory size whole number (e.g. -m 1G or -m 1024M ).
STRING      

 

Bridge Mapping

Meta Integration Repository (MIR)
Metamodel
(based on the OMG CWM standard)
"SAP BusinessObjects Web Intelligence (Webi) XI"
Metamodel
BoWebIntelligence
Mapping Comments
     
BaseType Object Type  
DataType   See datatype conversion array
Name   Based on the datatype
PhysicalName   Derived from the datatype
ClassifierMap   ClassifierMap objects are used to hold the lineage of DataProviders, Queries, DocumentVariables
Operation expression text can be a BO native expression or a SQL statement
Condition Filter  
Name name  
DataAttribute DataProvider Column, Query Column  
Name name  
Position position  
DataSet DataProvider, Query Each DataProvider is imported as DataSet. Each of its queries is also imported as lower-level DataSet
Name name  
DerivedType List Of Values The import of Objects' ListOfValues is controlled by a bridge option
DataType   See datatype conversion array
DesignPackage Universe Class DesignPackages reflect the reporting objects organization hierarchy, as well as the Class structure of objects used from a Universe
Name name  
UserDefined   set to True for Universe Classes
Dimension Universe Class  
Description description  
Name name  
UserDefined   set to True
DimensionAttribute Universe Object Objects of type Dimension or Detail as imported as dimension attributes
Description description  
Name name  
DrillPath Hierarchy  
DrillPathLevelAssociation Hierarchy Element  
FeatureMap   FeatureMap objects are used to hold the lineage of DataProvider columns, Query columns and DocumentVariables
Operation expression text can be a BO native expression or a SQL statement
Filter Universe Filter  
Description description  
Name name  
Level Hierarchy Element  
Measure Universe Object Objects of type measure are imported as measures
Description description  
Name name  
OlapSchema Universe Represents the universes this document depends on
Report Document  
Name name  
ReportAttribute ReportExpression  
Name name  
Usage Axis  
ReportChart Chart  
Name name  
ReportDataSet ReportExpression Represent groups of ReportExpressions by DataProvider or type
ReportField Formula Cell  
ReportList Section, Form  
Name name  
ReportMatrix Crosstab  
Name name  
ReportPage Report  
Name name  
ReportPageBody Report Body  
ReportPageFooter Report Footer  
ReportPageHeader Report Header  
ReportTable Table  
Name name  
ReportText Text Cell  
Value value  
StoreModel Document  
Comment comments  
Name name  
TypeValue List Of Values The import of Objects' ListOfValues is controlled by a bridge option
Value value