Start of Content Area

Procedure documentation Configuring BI Java Connector  Locate the document in its SAP Library structure

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.

Note

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):

More information: BI JDBC Connector

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 in 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.

For more information on using the Connector Container service, see Connector Container Service.

Result

Your BI Java Connector properties are configured and your data source is ready to use.

Testing the Connections

After you have configured the BI Java Connector, you can perform a rough installation check by displaying the page for the connector in your server. Perform the tests for the connector by visiting the URLs in the table below:

Connector Test Servlets

Connector

URL

Successful Result

BI JDBC Connector

http://<host>:<port>/TestJDBC_Web/TestJDBCPage.jsp

A list of tables is displayed

Note

These tests are designed to work with the default installation of the BI Java Connector. Cloned connectors with new JNDI names are not tested by these servlets.

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.

Caution

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 CD connect can recognize the connector.

 

 

 

End of Content Area