Creating Database Management Systems as Source Systems

<!--a11y-->!--A11Y-->

Creating Database Management Systems as Source Systems

Use

With DB Connect, you have the option of opening up extra database connections in addition to the SAP default connection and using these connections to access these databases during a BW extraction in order to transfer data into a BW system. To do this, you have to create a database source system, in which the connection data is determined and made known to the ABAP runtime environment. The connection data is used to identify the source database and authenticate the database.

Prerequisites

· You have made the following settings in the BW Customizing Implementation Guide, under Business Information Warehouse ® Connections to Other Systems.

¡ General connection settings

¡ Verify workflow customizing

· As a rule, no system changes are ever permitted in production systems. Connecting a system as a source system to a BW or connecting a BW to a new source system will, however, require changes as far as the system change options are concerned. In the client used in the BW system, you have therefore made sure that the following changes are permitted during the source system connection:

¡ Cross-client customizing and repository changes.

In the BW Customizing Implementation Guide under Business Information Warehouse ® Connections to Other Systems ® General Connection Settings ® Assign a Client to a Logical System, select the appropriate client and follow the path Goto ® Detail. In the Changes to Cross-Client Objects field, choose the Changes to Repository and Cross-Client Customizing Permitted option.

¡ Changes to the Local Developments and Business Information Warehouse software components.

You use transaction SE03 (Organizer Tools) to set the change options. Choose Organizer Tools ®Administration ® Set Up System Change Option, and then the Execute function. Make the settings in the subsequent screen.

¡ Changes in the customer name range.

Again, you use transaction SE03 to set up the change options for the customer name range.

¡ Changes to BW namespaces /BIC/ and /BI0/

Again, you use transaction SE03 to set up the change options of the BW namespaces.

· If the source DBMS and BW DBMS are different:

¡ You have installed the database-specific DB client software on your BW application server. You can get information about the database-specific DB client from the respective database manufacturers.

¡ You have installed the database-specific DBSL on your BW application server.

· In the database system, you have created a username and password to be used with the connection.

See Database Users and Database Schemas.

Procedure

Before you are able to open a database connection, all the connection data that is used to identify the source database and authenticate the database has to be made known to the ABAP runtime environment. For this, you need to specify the connection data for each of the database connections that you want to set up in addition to the SAP default connection.

...

1. In the source system tree for the BW Administrator Workbench – Modeling, choose Source Systems (Root Nodes) ® Context Menu (right mouse-click) ® Create.

2. In the dialog box that appears, choose the Database Source System source system type and click on the Transfer icon.

3. In the following screen, specify the logical system name (= DB connection) and a descriptive text for the source system, and click on the Continue icon.

You get to the Change “Description of Database Connection” View: Detail screen.

4. Select the database management system (DBMS) that you use to manage the database. This entry determines the database platform for the connection.

5. Under Username, specify the database user under whose name you want the connection to be opened.

6. Enter twice the user DB Password for authentication by the database when the connection is set up. This password is encrypted and stored.

7. Under Connection Info, specify the technical information required to open the database connection. This information, which is needed when you create a connection using NATIVE SQL, depends on the database platform and encompasses in general the database names and the database host on which the database runs. The string shows the client library, to which database the connection needs to be created.

Connection information that depends on the database platform

Supported Database	CON_ENV Connection Information
SAP DB (ada)	<server_name>-<db_name>
Informix (inf)	<db_name>@<informixserver> (See SAP Note 181989 – Multiconnect under EXEC SQL Informix)
Microsoft SQL Server (mss)	MSSQL_SERVER=<server_name> MSSQL_DBNAME=<db_name> MSSQL_SERVER=10.17.34.80 MSSQL_DBNAME=Northwind (See SAP Note 178949 - MSSQL: Database MultiConnect with EXEC SQL)
Oracle (ora)	TNS Alias (See SAP Note 339092 - DB-MultiConnect with Oracle as a secondary database)
DB2/390 (db2)	PORT=4730;SAPSYSTEMNAME=D6B;SSID=D6B0;SAPSYSTEM=71;SAPDBHOST=ihsapfc; ICLILIBRARY=/usr/sap/D6D/SYS/exe/run/ibmiclic.o The parameters describe the target system for the connection (see installation handbook DB2/390). The individual parameters (PORT=... SAPSYSTEMNAME=... .....) must be separated with ' ' , ',' or ';'. (See SAP Note 160484 - DB2/390: Database MultiConnect with EXEC SQL)
DB2/400 (db4)	<parameter_1>=<value_1>;...;<parameter_n>=<value_n>; The following parameters can be specified: · AS4_HOST: Host name for the Remote DB Server. The host name has to be specified in the same form recognized under TCP/IP or OptiConnect, according the connection type used. You have to specify the AS4_HOST parameter. · AS4_DB_LIBRARY: Library that the DB server job needs to use as the current library on the remote DB server. The AS4_DB_LIBRARY parameter has to be specified. · AS4_CON_TYPE: Connection type, permitted values are OPTICONNECT and SOCKETS. SOCKETS means that a connection is used using TCP/IP sockets. The AS4_CON_TYPE parameter is optional. If it is not specified, then the SOCKETS connection type is used. For a connection to the remote DB server as0001 on the RMTLIB library using TCP/IP sockets, the entry has to look like this: AS4_HOST=as0001;AS4_DB_LIBRARY=RMTLIB;AS4_CON_TYPE=SOCKETS; The syntax has to appear exactly as described above. This means that you cannot have any additional blank spaces between the entries and that each entry has to end with a semicolon. Only the AS4_CON_TYPE=SOCKETS optional parameter can be omitted. (See SAP Note 146624 - AS/400: Database MultiConnect with EXEC SQL) (For DB MultiConnect from Windows AS to iSeries, see Note 445872)
DB2 UDB (db6)	DB6_DB_NAME=<db_name> , where <db_name> is the name of the DB2 UDB database, to which the Connect needs to be run. You want to create a connection to the ‘mydb’ database. Enter DB6_DB_NAME=mydb as the connection information. (See SAP Note 200164 - DB6: Database MultiConnect with EXEC SQL)

8. Specify whether your database connection needs to be permanent or not.

If you set this indicator, there will be negative consequences should you lose an open database connection, for example, through a breakdown in the database itself or in the database connection (network).

Regardless of whether or not this indicator is set, the SAP work process tries to reinstate the lost connection. If this fails, the following occurs:

The database connection is not permanent, which means that the indicator is not set:

The failure is ignored, and the requested transaction is started. However, if this transaction accesses the connection that is no longer available, the transaction terminates.

The database connection is permanent, which means that the indicator is set:

After the connection terminates for the first time, each transaction is checked to see if the connection can be reinstated. If this is not possible, the transaction is not started – independently of whether the current transaction would access this special connection or not. The SAP system can only be used again once all the permanent DB connections have been reestablished.

We recommend setting the indicator if an open DB connection is essential or if it is accessed often.

9. Save your entry and go back.

10. You get to the Change “Description of Database Connections” View: Overview screen. Here the entry for your database connection is displayed in the table.

11. Go back.

Result

IDoc basic types, port descriptions, and partner agreements are created. When you use the destinations that have been created, the ALE settings that enable a BW system to communicate with a database source system are created in BW in the background. In addition, the BW settings for the new connection are created in the BW system, and the access paths from the BW system to the database are stored.

You have now successfully created a connection to a database source system. An entry to this effect is displayed in the source system tree. You are now able to generate DataSources for the tables or views of the database.

<!--a11y--><!--a11y-->