How-to Guide SAP NetWeaver ‘04

How to … Configure UD Connect on the J2EE Server for JDBC Access to External Databases
Version 1.05 – Jan. 2004 Applicable Releases: SAP NetWeaver ’04 (SAP BW3.5)

without representation or warranty of any kind. z/OS. Java is a registered trademark of Sun Microsystems. OS/400. OSF/1. SAP NetWeaver “How-to” Guides are intended to simplify the product implementation. R/3. JavaScript is a registered trademark of Sun Microsystems. and PowerPoint are registered trademarks of Microsoft Corporation. xApp. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. text. Nothing herein should be construed as constituting an additional warranty. please refer to SAP Consulting. The information contained herein may be changed without prior notice. While specific product features and procedures typically are explained in a practical business context. and SAP Group shall not be liable for errors or omissions with respect to the materials. indirect. and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. xSeries. SAP. either express or implied. . and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. and Motif are registered trademarks of the Open Group. except if such damages were caused by SAP intentionally or grossly negligent. and SAP shall not be liable for errors or damages caused by the usage of the Code. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. special. xApps. SAP NetWeaver. Parallel Sysplex. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services. iSeries. Intelligent Miner. mySAP. mySAP. X/Open. OS/390. Outlook. including but not limited to. ICA. National product specifications may vary. Oracle is a registered trademark of Oracle Corporation. SAP does not warrant the accuracy or completeness of the information. Windows. MetaFrame. S/390. AS/400. These materials are subject to change without notice. All other product and service names mentioned are the trademarks of their respective companies. XML. MaxDB is a trademark of MySQL AB. XHTML and W3C are trademarks or ® registered trademarks of W3C . clarification or support. fitness for a particular purpose. AFP.© Copyright 2004 SAP AG.. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages. DB2. Microsoft. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. HTML. UNIX. Should you wish to receive additional information. DB2 Universal Database. Massachusetts Institute of Technology. Program Neighborhood. Inc. OS/2. SAP does not warrant the correctness and completeness of the Code given herein. or non-infringement. used under license for technology invented and implemented by Netscape. Inc. WebSphere. Any software coding and/or code lines / strings (“Code”) included in this documentation are only examples and are not intended to be used in a productive system environment. if Tivoli. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only. VideoFrame. zSeries. pSeries. World Wide Web Consortium. Citrix. links or other items contained within these materials. Inc. SAP shall not be liable for damages of any kind including without limitation direct. it is not implied that those features and procedures are the only approach in solving a specific business problem using SAP NetWeaver. IBM. and MultiWin are trademarks or registered trademarks of Citrix Systems. Netfinity. WinFrame. or consequential damages that may result from the use of these materials. MVS/ESA. Sweden. These materials are provided “as is” without a warranty of any kind. AIX. graphics. the implied warranties of merchantability. Data contained in this document serves informational purposes only.

Connectors to access multi-dimensional OLAP databases are also available. . you can create queries.5. By using a remote cube to access the external data.1 Scenario You have data in a non-SAP database that you wish to report against using the new Universal Data Connect (UDC) functionality introduced in SAP BW 3. It is assumed you have installed the J2EE server and the Universal Data Integration (UDI) specific add-ons from the installation DVD. 2 Introduction UD Connect utilizes the J2EE engine of the SAP Web Application server to access external data. This Howto will deal with the set-up and configuration of the relational JDBC connector. use the Bex Analyzer and create web applications just like you would for SAP BW data. but not covered in this guide. This guide will detail the steps necessary to connect the SAP BW ABAP stack with the J2EE stack via RFC as well as configuring the JDBC connector to use the database vendor provided JDBC driver.

Note: Creating a shortcut to ‘go. . After you are authenticated.bat file located here: <drive>\usr\sap\<SID>\DVEBMGS00\j2ee\ admin. Start the J2EE ‘Visual Administrator’ via the go.3 The Step By Step Solution 1.bat’ and placing it on the desktop will make future access more convenient 2. you should see a screen similar to the one on the right. Logon to the J2EE server.

4. ‘User’ is a ‘system’ user. Note: If your BW system is Unicode. You will add a RFC server that upon startup. Complete the fields.5 system and registers itself. The RFC server will automatically start. but write it down. make sure the ‘Unicode’ field is checked. Expand the ‘Server’ node and the ‘Services’ node and click on the ‘JCo RFC Provider’ service. you will need it later. otherwise leave it unchecked. . similar to the ALE_REMOTE user. click on ‘Set’. Once all the fields are filled in.3. The field ‘Program ID’ is freely definable. logs into your SAP BW 3.

6. Enter the name of the RFC server from the previous step in the field ‘Program ID’.5. Click on the ‘Technical Settings’ tab and select the ‘Registered Server Program’ radio ils. select the ‘JDBC Connector’ Service and expand the ‘Drivers’ Click on the sheet-of-paper icon to create a new entry. Defining a RFC destination in BW. enter a freely definable name and click ‘OK’. Create a new RFC destination of type ‘TCP/IP’ via transaction SM59. Test your connection. In this example – ‘rgphl101_j2ee’. 7. Specify the location of the JDBC driver JARs provided to you by your RDBMS vendor. Back in in the J2EE Visual Administrator.aspx?FamilyID=9f1874b6-f8e1-4bd6-947c0fc5bf05bf71&DisplayLang=en . Note: The JDBC driver for Microsoft SQL Server is available from Microsoft at http://www. In the dialog box. Keep adding JARs until you are done.

where you defined the DB Driver! Example: library:MSSQL . IMPORTANT: The string after the colon must match the name you used in step 7. 9. Navigate to the ‘Connector Container’ Service and select the ‘BI_JDBC_CONNECTOR’. click on the ‘Resource Adaptor’ tab and click on ‘Add’. 8.When you are done adding JARs you should have an entry for your new driver. We need to add a load reference that starts with ‘library:’. Next.

10.sqlserver. Example (MS SQLServer only!): DriverName: com.g. Navigate to the ‘Connector Container’ service. Click on on the ‘DriverName’ key row and change the value to the string specified in your JDBC The default port for MS SQLServer is 1433.jdbc. myhost. Important: Click on the ‘Save’ icon when you are done with the configuration .SQLServerDri ver URL: jdbc:microsoft:sqlserver://<server>:<port >.microsoft. Repeat for the ‘URL’ key. click on your connector and then on the right hand side of the screen click on the ‘Managed Connection Factory’ and then the ‘Properties’ tab. Enter the database username and password used for logging into the DB. 11.database=Northwind Notes: <server> is the complete hostname (e.acme.

e. replacing the placeholders with your server name and J2EE port. execute the following URL in your browser. To perform a quick ‘smoke test’. Note: You must start cloned connector names with ‘SDK_’ in order for them to be visible in the BW backend system for selection during the mapping process. using different users and schemas). . http://<server>:<port>/TJdbc/servlet/Test Jdbc 13.12. You have successfully configured the J2EE server for UD Connect! At this point you can clone the BI_JDBC_CONNECTOR in order to provide more granular access to your database (i. .

Sign up to vote on this title
UsefulNot useful