Connector transport file installation

The transport files for the IBM WebSphere Business Integration Adapter for mySAP.com (SAP R/3 Version 3.x) contain a variety of objects, such as table structures, functions, and data. These development objects must be imported into your SAP installation to provide specific functionality required by the ABAP Extension Module.

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 3_Primary.zip file.

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.

Creating the namespace for connector transport installation

Create the namespace for the connector before installing the connector transport files. This step is mandatory for SAP R/3 version 4.0, as some of the transports will fail if the namespace is not created.

Note:
You must create the connector's namespace prior to modifying one of the connector's ABAP objects in any SAP R/3 application version 3.x.

Creating the /CWLD/ namespace

  1. Open the Workbench Organizer: Tools window (transaction SE03).
  2. Expand the Administration menu and double-click on the Display/change namespaces option.
  3. Click the Display->Change button (Ctrl+F1).
  4. Click the Continue button to close the Information window.
  5. Click the New entries button (F5) and type /CWLD/ in the Namespace field.
  6. Select the Namespace role field, expand it (F4) to see options, and then select Recipient (C).
  7. Type CrossWorlds Namespace in the Short text field and type CrossWorlds in the Owner field. Click the save button (Ctrl+S). If your system is set up to track customizing changes, you will be prompted for a change request which will allow you to transport the namespace to another system.

Making the namespace available for modifications

ABAP objects in the connector's namespace cannot be modified until you make the Namespace available for modification. To update SAP 3.x delivered ABAP objects, you must have a repair license to modify the objects. Contact IBM technical support to obtain the license.

  1. Open the Workbench Organizer: Tools window (transaction SE03).
  2. Expand the Administration menu and double-click on the Display/change namespaces option.
  3. Click the Display->Change button (Ctrl+F1).
  4. Click the Continue button to close the Information window.
  5. Double-click on /CWLD/ and enter the repair license. Click the Save button (Ctrl+S).
  6. Click the Back button (F3) twice, expand the Administration menu and double-click on the Set system change option.
  7. Place a check mark in the Modifiable column of the Namespace row. Click the Save button (Ctrl+S).

Connector transport files

The IBM WebSphere Business Integration Adapter for mySAP.com includes seven connector transport files. Modifications required by the adapter are handled by these connector transport files. The Primary, Utilities, and Request transport files are required.

The following is a list of the SAP R/3 version 3.x connector transport files. To ensure that all necessary tables are created before the data for those tables is added, you must install the transports in the order listed. These files can be found in \connectors\SAP\dependencies\transports_4x.

The functionality provided by the Primary, Utilities, Request, and Delivery transport files make up the runtime components. The Tools_Maintenance and Tools_Development transport files can be installed at anytime after the required transport files are installed. They are not required for your runtime environment.

4_Primary
This transport file contains the development objects, which should be loaded only once into the system. It contains the number range objects, the development classes, the dynamic transaction declaration include program as well as the restriction include program, which can be used to make customer-specific changes to the triggering logic.
Important:
If you apply this transport file to a system that already has the connector running on it, the contents of the transport file may overwrite changes that were made to the existing environment.
4_Utilities
This client-independent transport file contains objects and functionality that are shared among the request, delivery, development, and maintenance components. For example, it contains the log and data elements.
4_Request
This client-independent transport file contains the functionality required to support business object request operations.
4_Delivery
This client-independent transport file contains the functionality required to support event delivery operations including event triggering and event polling.
4_Number Range
This client-dependent transport file contains the four number ranges in their initial state. You can use these intervals or create the number range intervals themselves.

Attention: Reimporting the Number Range transport file initializes your existing number range intervals for the connector. This corrupts the data in the connector's log, current event, future event, and archive tables if those tables are not refreshed before reusing.

This transport file can be installed at any time after the Primary transport has been installed.

4_Tools_Maintenance
This client-independent transport file contains the functionality required to support maintenance operations such as displaying the log statistics and event tables.
4_Tools_Development
This client-independent transport file contains the functionality required to support the development of objects.

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, 2004