Creating Database Management Systems as Source Systems

Prerequisites

• You have made the following settings in the Implementation Guide (IMG) under SAP NetWeaver → Business Intelligence   Links to Other Source Systems:

  • General connection settings

  • Perform automatic workflow Customizing

• As a rule, system changes are not permitted in production systems. However, connecting a system as a source system to a BW, or connecting a BW to a new source system, results in modifcations to the system change options. Therefore, in the client used in the BW system, make sure that the following changes are permitted during the source system connection:

  • Cross-client Customizing and repository changes

    In Implementation Guide (IMG), under SAP NetWeaver → Business Intelligence  Connections to Source Systems  General Connection Settings  Assign Logical System to Client, select the client in question and choose Goto  Details. In the Cross-Client Object Changes field, select Changes to Repository and Cross-Client Customizing Allowed.

  • Changes to the local developments and Business Information Warehouse software components

    You use transaction SE03 (Organizer Tools) to set the change options. Choose Set Organizer Tools  Administration  System Change Option. Choose Execute. On the next screen, make the following settings:.

  • Changes to the customer name range

    You also use transaction SE03 to set the change option for the customer name range.

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

    You also use transaction SE03 to set the change option for 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 user name and password that you want to use for the connection.

  See Database Users and Database Schemas.

Procedure

Before you can open a database connection, all the connection data used to identify the source database and authenticate the database must be made known to the ABAP runtime environment. 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 in the Data Warehousing Workbench, choose Create in the context menu of the DB Connect folder.

2. On the following screen, specify the logical system name (= DB connection) and a descriptive text for the source system. Choose Continue.

   The DB Connect Parameters dialog box appears.

3. Select the connection type Source system = DB connection.

   The system then displays the logical system name that you entered as the DB connection name. If the connection already exists, you can display or change the connection data by choosing . To create the connection data - if it does not exist yet - also choose .

   The Change Description of Database Connection View: Detail screen appears.

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

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

6. When establishing the connection, enter the user DB Password twice for authentication by the database. 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 establish a connection using NATIVE SQL, depends on the database platform and encompasses the database names and the database host on which the database runs. The string informs the client library of the database that you want to establish the connection to.

   Connection information that depends on the database platform

   Supported Database	CON_ENV Connection Information
   SAP DB (ada) or MaxDB (dbs)	<server_name>-<db_name>
   Microsoft SQL Server (mss)	MSSQL_SERVER=<server_name> MSSQL_DBNAME=<db_name>
   Oracle (ora)	TNS Alias (See SAP Note 339092 - DB-Multiconnect with Oracle as a secondary database)
   DB2/390 (db2)	The parameters describe the target system for the connection (see installation handbook DB2/390). The individual parameters (PORT=... SAPSYSTEMNAME=... must be separated with &apos; &apos; , &apos;,&apos; or &apos;;&apos;. (see SAP Note 160484 - DB2/390: Database Multiconnect with EXEC SQL)
   DB2/400 (db4)	<parameter_1>=<value_1>;...;<parameter_n>=<value_n>; You can specify the following parameters: AS4_HOST: Host name of the Remote DB Server. You have to enter the host name in the same format as is used under TCP/IP or OptiConnect, according to the connection type you are using. You have to specify parameter AS4_HOST. AS4_DB_LIBRARY: Library that the DB server job needs to use as the current library on the remote DB server. You have to enter parameter AS4_DB_LIBRARY. AS4_CON_TYPE: Connection type; permitted values are OPTICONNECT and SOCKETS. SOCKETS means that a connection is used using TCP/IP sockets. Parameter AS4_CON_TYPE is optional. If you do not enter a value for this parameter, the system uses connection type SOCKETS. The syntax must be exactly as described above. You cannot have any additional blank spaces between the entries and each entry has to end with a semicolon. Only the optional parameter AS4_CON_TYPE=SOCKETS 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 on which you want to run Connect.
   SAP HANA Database (hdb)	<Hostname>:<SQL Port> (see SAP Note 1597627 - HANA Connection)

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

   If you set this flag, losing an open database connection, for example due to a breakdown in the database itself or in the database connection (network), has a negative impact. Regardless of whether this flag is set, the SAP work process tries to reinstate the lost connection. If this fails, the system responds as follows:

   1. The database connection is not permanent, which means that the flag is not set:

      The system ignores the connection failure and starts the requested transaction. If this transaction accesses the connection that is no longer available however, the transaction terminates.

   2. The database connection is permanent, which means that the flag 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 – regardless 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.

9. Save your entries and go back.

   The Change Description of Database Connections View: Overview screen appears. The system displays the entry for your database connection in the table.

10. Go back.

Result

You have created IDoc basic types, port descriptions, and partner agreements. 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. The system displays the corresponding entry in the source system tree. You can now create DataSources for this source system.