About the SAP BI ODBO Connector

Version 3.50 SP12

This document is called howto.html and is delivered in the resource adapter archive (RAR file) bi_sdk_odbo.rar. You may extract howto.html to a separate location for your reference before deploying the resource adapter archive.

Note that the BI ODBO Connector is deployed to the Web Application Server by default with the BW 3.5 installer. Refer to this document for configuration information, or to manually deploy this connector if, for example, you did not choose to deploy it during the BW 3.5 installation.

This document contains the following information:

• Overview
• System Requirements
• Connection Properties
• Deployment Procedure
• Additional Information

Overview

Microsoft's OLE DB for OLAP (ODBO) is the established industry-standard OLAP API for the Windows platform. The BI ODBO Connector is based on ODBO, and allows you to connect applications built with the BI Java SDK to ODBO-compliant OLAP data sources such as Microsoft Analysis Services, SAS, Microsoft PivotTable Services, and SAP's BW. This connector is fully compliant with the J2EE Connector Architecture (JCA) and may be deployed into SAP's J2EE Server.

You can also use the BI ODBO Connector to make these data sources available in BW, via UD Connect.

The BI ODBO Connector uses Microsoft's ADO (ActiveX Data Objects) and ADO MD (ActiveX Data Objects Multidimensional) to support connectivity to OLAP data sources. ADO provides access to the schema object; ADO MD adds easy access to multidimensional data by extending ADO with objects specific to multidimensional data, such as the cubes and cellsets. With ADO and ADO MD, you can browse multidimensional schema, query a cube, and retrieve the results, thus providing convenient access to OLAP data from languages such as Microsoft Visual Basic, Microsoft Visual C++, and Microsoft Visual J++. Like ADO, ADO MD uses an underlying OLE DB provider to gain access to data.

The BI ODBO Connector implements the BI Java SDK's IBIOlap interface.

System Requirements

Connection Properties

* Note: Using a specific Windows domain account:

You may wish to set a specific Windows domain account in certain situations where the BI ODBO Connector needs to use security credentials different from the credentials used by J2EE server itself. Examples of this include when the OLE DB driver for Microsoft Analysis Server supports only Windows domain security and ignores credentials supplied in the connection string, if any, or with a connection to MS SQL Server where MS SQL Server is configured for Windows authentication only.

Configuring these properties will result in the BI ODBO Connector attempting to impersonate the specified Windows domain account when establishing a connection to the target system. The J2EE server will create a local COM component using the account information provided, and this component, in turn, will access the remote computer (such as that which hosts the database server). These properties are ignored if LogonAsUserID and/or LogonAsUserDomain contain an empty string or are absent.

 

Deployment Procedure

The BI ODBO Connector is deployed to the Web Application Server by default with the BW 3.5 installer. Follow the instructions below if you have not selected this connector for installation or to manually deploy the resource adapter archive onto the Web Application Server:

1. Check system requirements
   
   Ensure that your system is properly configured and that any software prerequisites are satisfied (see System Requirements table above).
   
   
   1. SAP BW 3.5 Java Components:
      
      The BW system installer allows you to deploy the necessary components to the Web Application Server. Verify that these components are present by using the Web Application Server's SDM (Software Deployment Manager).
      
      These components are required by this connector's deployment descriptor. You will receive a warning during the deployment process if they are not already present.
      
      
   2. DLL files:
      
      Ensure that your Windows system is properly configured with Microsoft Data Access Components (MDAC) 2.6 or later.
      
      The required JNI library sapbiado.dll is delivered inside the bi_sdk_odbo.sda archive. Deploy this archive to the Web Application Server using the following steps:
      
      
      1. In the SDM, select the Deployment tab
      2. Press the Add SCA/SWC/SDA to Deployment List button
      3. Navigate to and select the bi_sdk_odbo.sda file
      4. Continue pressing Next until the Start button appears
      5. Press Start
      6. Once finished, press Confirm
      7. Restart the server for your changes to take effect
         
         
2. Deploy the resource adapter archive
   
   Deploy the archive using the SDM:
   
   
   1. In the SDM, select the Deployment tab
   2. Press the Add SCA/SWC/SDA to Deployment List button
   3. Navigate to and select the bi_sdk_odbo.rar file
   4. Continue pressing Next until the Start button appears
   5. Press Start
   6. Once finished, press Confirm
      
      
3. Configure the connection properties
   
   Configure your connector with the properties in the Connection Properties table above by using the Connector Container service of the Web Application Server's Visual Administrator:
   
   
   1. In the Connector Container service, select the Runtime tab
   2. Find your connector in the Connector Container tree which shows the currently-installed resource adapters, and select it
   3. Select the Managed Connection Factory tab
   4. Select the Properties sub-tab
   5. Select and edit each property as appropriate
   6. Press Add to transfer the changes back into the active properties
   7. Save changes with the Save button in the toolbar
   
   Note: You may also clone an existing connection by using the Clone button in the toolbar. If you are using this connector with UD Connect, when entering the resource adapter name during the cloning process, you must prefix the name with "SDK_" in order for UD Connect to properly recognize the connector.
   

Your BI ODBO Connector is now ready for use in a managed environment. Refer to this connector in your application by its JNDI name: SDK_ODBO. For code samples, refer to the Connection Interfaces Javadocs package in the documentation set delivered with the BI Java SDK.

Additional Information

For more information about Sun's J2EE Connector Architecture, see:

• http://java.sun.com/j2ee/connector/

For information about the Visual Administrator in SAP's Web Application Server, see:

• http://help.sap.com/saphelp_nw04/helpdata/en/
  39/83682615CD4F8197D0612529F2165F/frameset.htm

For more information about the connection architecture in the BI Java SDK, refer to the following documentation in the SDK distribution package:

• Connection Interfaces Javadocs package
• Developer's Guide (PDF)

For more information about UD Connect, see:

• http://help.sap.com/saphelp_nw04/helpdata/en/
  78/EF1441A509064ABEE6FFD6F38278FD/frameset.htm

For more information about Microsoft's ADO, see:

• http://msdn.microsoft.com/library/default.asp?URL=/library/psdk/dasdk/mdac3sc7.htm