Creating a Link ID for Certain Implementations

Use

In Application Server Administrator, you must create a special Link ID if you use Entry and Approval or Model Designer, or you integrate SAP Business Planning and Consolidation data in the application. You use the same Link ID for any of these connections.

Prerequisites

You have Application Server installed in one of these configurations:

• Application Server is installed on a Windows server

• Application Server is installed on a Linux/UNIX server with a client copy of Application Server installed on a Windows machine

The software required for client access to the SAP NetWeaver System database is installed and configured on the server where Application Server is installed. For information, see Setting Up Client Access to the SAP NetWeaver System Database.

In the steps below, when the term Microsoft Windows machine is used, it means either Microsoft Windows server or Microsoft Windows client, depending on your implementation noted above.

If your SAP NetWeaver System database is either MaxDB, SQL Server, Sybase ASE, or HANA, you must create an ODBC System DSN to connect to using your Link ID.

An ODBC connection is not required for Oracle or IBM DB2 because Application Server has internal connections to these databases through Oracle (OCI) and DB2 (CLI). If you are using Oracle or IBM DB2, you can skip this step.

Procedure

1. On the Microsoft Windows machine where Application Server is installed, run the ODBC Administrator.

2. Click the System DSN tab and click Add to create a connection to your MaxDB, SQL Server, Sybase ASE, or HANA database.

   Note the following information:

   • For MaxDB, use the MaxDB (Unicode) driver. On some systems this may be listed as SQLSTUDIOODBC.

   • For SQL Server, the SQL Server authentication method must be specified in the DSN. The specified user needs to match the schema/owner of the CPMS_ tables you want to access in the SAP NetWeaver System database.

   • For Sybase ASE, the Login ID must be the owner of the CPMS_ tables. On the Connection page you must check the Encrypt Password option.

3. Start the Application Server Administrator program on the Microsoft Windows machine.

4. Choose File  New  Link ID to display the Create Link ID dialog box.

5. Do one of the following:

   • If you are using the ODBC drivers for MaxDB, SQL Server, Sybase ASE, or HANA, select the ODBC System Data Source Name you created above as your database type and click OK.

   • If you are using the Oracle OCI connection, select Oracle (OCI) as the database type.

   • If you are connecting to DB2, use the DB2 (CLI) entry to create your Link ID.

6. In the Link ID Properties dialog box, type the name ssm_cb_ea.

   If you are using the Oracle (OCI) or DB2 (CLI) connections, specify the additional information needed to connect to the database server. The username and password must be the owner of the CPMS_ tables.

7. Click Test.

   If you are using an ODBC connection you are prompted for more information. Specify the username and password for the owner of the CPMS_ tables.

8. Click OK when you are finished.

   If the client software needed to connect to your database is installed properly on your Microsoft Windows system, you should see the message Connection successful.

   If the connection is unsuccessful, verify the values entered for the connection and define the Link ID again.

   If the client connectivity software for the database is not installed, you can create and save the Link ID without testing it.

9. If you intend to run Application Server on Linux/UNIX, transfer the lsdal.ini file from the Microsoft Windows client directory to the UNIX server directory where you installed Application Server. Ensure the file name lsdal.ini is in lower case on the Linux/UNIX system.

For information about creating a Link ID, see Application Server Help  Application Server  Working with Link IDs in the online Help in the Application Server Administrator.