Skip to Content

Purpose

UD Connect (Universal Data Connect) uses Application Server J2EE connectivity to enable reporting and analysis of relational SAP and non-SAP data. To connect to data sources, UD Connect can use the JCA-compatible (J2EE Connector Architecture) BI Java Connector.

Terminology

1. UD Connect Source: The UD Connect Sources is the instances that can be addressed as data sources using the BI JDBC Connector.UD Connect Source Object You have installed the J2EE Engine with BI Java components. For more information, seethe SAP NetWeaver Installation Guide on the SAP Service Marketplace at service.sap.com/instguides. UD Connect source objects are relational data store tables in the UD Connect source.

2. Source Object Element: are the components of UD Connect source objects – fields in the tables.

Process Flow


1. Create the connection to the data source with your relational or multi-dimensional source objects (relational database management system with tables and views) on the J2EE Engine.

2. Create RFC destinations on the J2EE Engine and in BI to enable communication between the J2EE Engine and BI.

For more information, see the Implementation Guide for SAP NetWeaver →Business Intelligence →UDI Settings by Purpose →UD Connect Settings.

3. Model the InfoObjects required in accordance with the source object elements in BI.

4.Define a DataSource in BI.

Result

You can now integrate the data for the source object into BI. You now have two choices. Firstly, you can extract the data, load it into BI and store it there physically. Secondly, provided that the conditions for this are met, you can read the data directly in the source using a VirtualProvider.

BI Java Connectors:

BI JDBC Connector is a JCA-enabled (J2EE Connector Architecture) resource adapter. It implements the APIs for the BI Java SDK and allows you to connect various data sources to the applications you have created using the SDK. You can also use BI Java JDBC Connector to make these data sources available in SAP BI systems (by means of UD Connect), or to create systems in the portal to use in Visual Composer scenarios. The following diagram outlines potential usage scenarios for BI Java Connectors:

/wp-content/uploads/2013/02/p3_185965.png

As illustrated, you can use BI Java JDBC Connector to create systems for use in four different scenarios. Since BI Java JDBC Connector is part of SAP Universal Data Integration (UDI), these are often referred to as UDI scenarios:

Scenario 1: UD Connect

On the BI platform, you can use UD Connect to make data from systems based on the BI Java Connectors available in SAP BI. More information: Transferring Data with UD Connect. You can find more information about configuring BI Java Connector for this scenario in the SAP Implementation Guide, under SAP NetWeaver →Business Intelligence →UDI Settings by Purpose →UD Connect Settings. You can find more information about the configuring connector properties under Configuring BI Java Connector.

Scenario 2: Visual Composer

You can use data from systems based on BI Java Connector in Visual Composer, the portal-based visual modeling application. More information: Visual Composer Modeler’s Guide. To configure BI Java Connector for this scenario, see the Visual Composer Installation and Configuration Guide, and see Running the System Landscape Wizard and Editing Systems to configure the systems on the portal.

Scenario 3: BI Java SDK

You can build custom Java applications based on data in systems created with BI Java Connector. More information: BI Java SDK. You can find more info about configuring the BI Java Connectors for this scenario under Configuring BI Java Connector.

Configuring BI Java:

Use

To prepare a data source for use with the BI Java SDK or with UD Connect, you first need to configure the properties in BI Java Connector used to connect to the data source. You do this in SAP NetWeaver Application Server’s Visual Administrator by following the steps below.

For information on how to create and configure systems in the portal for use in BEx Web and Visual Composer scenarios, see Running the System Landscape Wizard and Editing Systems in the NetWeaver Portal System Landscape documentation.

Prerequisites

In order to configure the properties for a data source based on a BI Java Connector, the connector’s resource adapter archive (RAR file) (delivered as part of Universal Data Integration, or UDI) and the Metamodel Repository (MMR) that the connector is based on, must first be deployed to the server. UDI and MMR are part of usage type AS-Java (Application Server – Java) in NetWeaver 7.0.

Further prerequisites can be found in the documentation on the Connector. (This document also provides information about the list of specific properties that have to be configured)

Procedure

1. Start the Visual Administrator:

    UNIX: On your central instance host, change to the admin directory /usr/sap/<SAPSID>/<instance_number>/j2ee/admin and execute go.sh.

    Windows: On your central instance host, change to the admin directory \usr\sap\<SAPSID>\<instance_number>\j2ee\admin and execute go.bat.

2. On the Cluster tab, choose Server x  → Services → Connector Container.

3. Locate your connector in the Connector Containertree and double-click it to open the connector definition

    BI JDBC Connector: SDK_JDBC under the node sap.com/com.sap.ip.bi.sdk.dac.connector.jdbc

4. On the Runtime tab (in the right screen area), choose Managed Connection Factory  → Properties.

5. Select and edit each property according to the Connector Properties table n the documentation below: BI JDBC Connector

6. After configuring each property, choose Add to transfer the changes to the active properties list.

7. Save the settings.

For the BI JDBC Connector:

In the service Connector Container, configure a reference to the JDBC driver of your data source. This can be done by performing the following steps:

8. Select the BI JDBC Connector in the Connectors tree.

9. Choose the Resource Adapter tab.

10. In the Loader Reference box, choose Add to add a reference to your JDBC driver.

11. Enter library:<jdbc driver name> and choose OK.

The <jdbc driver name> is the name you entered for your driver when you loaded it (see Prerequisites in BI JDBC Connector).

12. Save the settings.

 

JNDI Names

When creating applications with the BI Java SDK, refer to a connector by its JNDI name: The BI JDBC Connector has the JNDI name SDK_JDBC.

Cloning the Connections

You can clone an existing connection by using the Clone button in the toolbar.

Note: For Universal Data Connect (UD Connect) only: If you enter the name of the resource adapter in the duplication process, you have to add the prefix SDK_ to the JNDI name. Only use uppercase letters in the name to ensure that UD connect can recognize the connector.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply