Installing connector transport files

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

Attention: If you are reapplying transports, note that this resets your environment. Any development done prior to reapplying the transport files will be overwritten.

In the following instructions, SID refers to the 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 filename is passed as a parameter it has the format SIDK9xxxxx. For example, the file name K912345.D30 is passed as a parameter as D30K912345 because D30 is the SID of the source system.

Attention: Do not change the names of the connector transport files.

To install the transports:

  1. Log in as the SAP administrator, <SID>adm.
  2. Copy the transports to the SAP database server. There are two kinds of transport files:
    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.
  3. 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 is:

    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 in step 3.

  4. Import the transport files in one of the following two ways:

Use adapter-delivered commands

In \usr\sap\trans\bin, execute the following commands for each transport, in the order specified:

tp addtobuffer <TransportFileName> <SID> pf = tpparamFilePath
 tp import <TransportFileName> <SID> u023689 CLIENT=<CLIENT#> pf = tpparamFilePath
 

Use an SAP transaction code

In the Transport Management s ystem (transaction STMS):

  1. Click the Import overview icon (F5).
  2. Double-click the appropriate queue to be updated.
  3. In the menu bar, click Extras, then click Other requests, and then click Add.
  4. Populate the transport request field, and then click the check mark (enter).
  5. When the Add Transport Request confirmation window appears, click Yes to attach the import to the queue.
  6. Place the cursor on the transport that was just added.
  7. In the menu bar, click Request, and then click Import.
  8. Populate the Target client field, and click the check mark to import the transport file.

You must install the transports in the order listed in Connector transport file installation.

After the transports are installed, change the development class to follow the migration path of your development classes. Use IBM CrossWorlds Station (transaction /n/CWLD/HOME) to do the following:

  1. Click the Tools tab, and then click the Transport Layer button.
  2. Select the appropriate Transport layer entry, and then click the Save button.

Attention: Any changes you make to development objects that were in the connector transports should be well documented outside of SAP. Changes can be overwritten by the next release of transport files. If changes are overwritten, they must be reapplied manually. For more information on upgrade issues, see Upgrading the ABAP Extension module.

Copyright IBM Corp. 1997, 2003