Connector transport file installation
The
transport files for the adapter for mySAP.com 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 version
4.x Primary transport is located in the 4_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 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 application version 4.x.
Creating the /CWLD/ namespace
- Open the Workbench Organizer: Tools window (transaction SE03).
- Expand the Administration menu and double-click on the Display/change namespaces
option.
- Click the Display->Change button (Ctrl+F1).
- Click the Continue button to close the Information window.
- Click the New entries button (F5) and type /CWLD/ in the Namespace field.
- Select the Namespace role field, expand it (F4) to see options,
and then select Recipient (C).
- 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 SAP4.x delivered ABAP objects, you must have a repair
license to modify the objects. Contact IBM technical support to obtain
the license.
- Open the Workbench Organizer: Tools window (transaction SE03).
- Expand the Administration menu and double-click on the Display/change namespaces
option.
- Click the Display->Change button (Ctrl+F1).
- Click the Continue button to close the Information window.
- Double-click on /CWLD/ and enter the repair license. Click the Save button (Ctrl+S).
- Click the Back button (F3) twice, expand the Administration
menu and double-click on the Set system change option.
- Place a check mark in the Modifiable column of the Namespace
row. Click the Save button (Ctrl+S).
Connector transport files
The connector includes two connector transport files.
Modifications required by the adapter are handled by these 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 ProductDir\connectors\SAP\dependencies, where ProductDir represents the directory where the connector is installed.
Table 40. Connector transport files by version
Version of SAP |
Transport files |
V.4.0, V.4.5, V.4.6 |
- \connectors\SAP\dependencies\transports_40_45_46\40_45_46_Primary.zip
- \connectors\SAP\dependencies\transports_40_45_46\ 40_45_46_Infrastructure.zip
|
V.4.7 |
- \connectors\SAP\dependencies\transports_47\47_Primary.zip
- \connectors\SAP\dependencies\transports_47\47_Infrastructure.zip
|
The functionality provided by the Primary and Infrastructure
files is as follows.
Table 41. Connector transport file functionality
File |
Functionality |
Primary |
This transport file contains the following elements:
- 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. If you apply this transport file
to a system that already has the connector running on it, the contents
of the transport file will overwrite all objects in the existing
environment.
- The four number ranges in their initial state. Reimporting the
Primary 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.
|
Infrastructure |
This client-independent transport file contains
the following elements:
- Objects and functionality that are shared among the request,
delivery, development, and maintenance components. For example,
it contains the log and data elements.
- The functionality required to support business object request
operations.
- The functionality required to support event delivery operations
including event triggering and event polling.
- The functionality required to support maintenance operations
such as displaying the log statistics and event tables.
- 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
the connector. 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:
- Log in as the SAP administrator, <SID>adm.
- Copy the transports to the SAP database server. There are two
kinds of transport files:
- Copy files that have names beginning in K to the \usr\sap\trans\cofiles directory.
- 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 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.
- 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
system (transaction STMS):
- Click the Import overview icon (F5).
- Double-click the appropriate queue to be updated.
- In the menu bar, click Extras, then click Other requests, and
then click Add.
- Populate the transport request field, and then click the check
mark (enter).
- When the Add Transport Request confirmation window appears,
click Yes to attach the import to the queue.
- Place the cursor on the transport that was just added.
- In the menu bar, click Request, and then click Import.
- 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
WebSphere BI Station (transaction /n/CWLD/HOME) to do the following:
- Click the Tools tab, and then click the Transport Layer button.
- 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.
