Connector transport file installation

The connector's transport files contain a variety of objects such as, table structures, functions, and data. These development objects need to be imported into your SAP installation to provide specific functionality required by the ABAP Extension Module.

Transport files

Each transport file is included in a .zip file. For example, the transport file for the SAP R/3 version 3.x Primary transport is located in the Primary.zip file. These files can be found in \connectors\SAP\dependencies\transports_3x.

Modifications required by IBM WebSphere Business Integration Adapter for mySAP.com (SAP R/3 Version 3.x) are handled by a set of three required transport files along with one transport file for each business object. To ensure that all necessary tables are created before the data for those tables is added, the transport files must be imported in the following order:

  1. Primary
  2. Infrastructure_1
  3. Infrastructure_2

Once the required transport files have been successfully loaded, the business object-specific transports can be loaded in any order. See the transport note included in each transport .zip file for detailed information about the transport file.

Primary
This transport file contains the development objects, which should only be loaded once into the recipient system. It contains the number range objects, the development class for YXR1 as well as the restriction include, which can be used to make customer-specific changes to the triggering logic. Caution should be used when applying this transport file to a system that already has the connector running on it, because the contents of the transport file may overwrite changes that were made to these objects.

Infrastructure_1
This transport file contains the programs and data dictionary objects associated with the connector that are not business object specific.

All of the objects begin with YXR with the following exceptions:

Infrastructure_2
This transport contains SAP customizing data necessary for the connector log and for the transaction to maintain the connector's tables. All of the keys begin with YXR. The customizing table entries in the connector's tables do not begin with YXR.

Installing connector transport files

The connector transport files make all necessary modifications to SAP by importing programs and other development objects included with the IBM WebSphere Business Integration Adapter for mySAP.com. They do not alter any SAP programs or modify user exits.

In the following instructions, SID refers to your SAP system ID and TransportFileName refers to the name of the transport file. However, the characters that make up the transport file name appear in a different order in the installation directory from the way the name is passed as a parameter to the various tp commands. In the \usr\sap\trans\cofiles directory, the format of a transport file name is K9xxxxx.SID, but when the file name is passed as a parameter it has the format SIDK9xxxxx. For example, the file name K912345.D30 would be passed as a parameter as D30K912345 if your SID is D30.

To install the transports:

  1. Log in as the SAP administrator, SIDadm.
  2. Copy the transports to the SAP database server.The transports consist of two kinds of files and should be copied as described below:
    1. Copy files that have names beginning in K to the \usr\sap\trans\cofiles directory.
    2. Copy the other files to the \usr\sap\trans data directory.

      Check the connection to the database and determine the path of the tpparam file by running the tp connect command:

      tp connect SID

      If this command fails, try adding the path of the tpparam file as a second parameter:

      tp connect SID pf = path_of_tpparam

      For example, if the SID is P11 and the path of the tpparam file is \usr\sap\trans\bin\tpparam, the command would be:

      tp connect P11 pf = \usr\sap\trans\bin\tpparam

      If tp connect succeeds when you specify the path of the tpparam file and fails when you do not, you should specify the optional tpparam path in the commands described below in step 3.

  3. The transports can be imported in one of the following two ways:
  4. When the transports are installed, change the development class to follow the migration path of your development classes. In SAP R/3 versions 3.x the development class is YXR1.

    Using the IBM CrossWorlds Connector Tools window (transaction YXR1):

    1. From the Customizing menu, click Connector, and click Reassign Transp Lyr.
    2. Select the appropriate Transport layer entry, and then click the Save button.

For additional configuration requirements of particular application-specific business objects, see the reference page for that business object.

Caution:
Any changes you make to development objects which were in the connector transports, should be well documented outside of SAP. Changes could be overwritten by the next release of the adapter's transport files and would need to be re-applied manually.

Copyright IBM Corp. 1997, 2004