Importing the SAP transport

The SAP agent provides a set of Advanced Business Application Programming (ABAP) routines to support data collection in the SAP system. This ABAP code is delivered as an SAP transport that must be installed on each SAP system that is to be monitored. Your SAP administrator installs the transport.

1. Copy the IBM Tivoli® Monitoring transport file from the following paths on the computer where the agent is installed.
   • For Windows: install_dir\TMAITM6_x64\ABAP
   • For Non-Windows: install_dir/intrp/sa/ABAP, where intrp must be lx8266 or aix526.
2. Copy the following transport files from the paths that are mentioned in step 1 into the SAP environment:
   • K711_00xxxU.ITM and R711_00xxxU.ITM

     These files are Unicode versions of the transport. They contain the SAP agent ABAP code and Unicode support for text strings for Latin code pages and double-byte code pages.

   • K711_00xxx_DELETE.ITM and R711_00xxx_DELETE.ITM

     These files remove the ABAP code. The DELETE transport does not need to be imported, unless you stop the use of product entirely and want to remove the transports from the SAP systems. See Deleting the ABAP transport from the SAP system

3. Copy your transport files to the SAP Transport System data directory as follows, and do not change the transport file name:
   Unicode transport

   1. Copy the K711_00xxxU.ITM file to the cofiles directory
   2. Copy the R711_00xxxU.ITM file to the data directory.
4. To install the single IBM Tivoli Monitoring transport file on the SAP system, select one of the following file import options:
   • For the SAP system that is a Solution Manager 7.1 Service Pack 6 level, or later and has MAI configured, you must create the transport.prop file in the usr/sap/SID/DVEBMGS<instancenumber>/work work directory of the SAP system. If the SAP system is a distributed system with ABAP SAP Central Services (ASCS), create the transport.prop file in the Central Instance (CI) usr/sap/SID directory. Then, add MAI_CONFIGURED = YES entry in that file. This entry creates a MAI_CONFIGURED = YES entry in the /IBMMON/ITM_CNFG table. You can now import the single IBM Tivoli Monitoring transport file on the SAP system.
     Note: Before you import the single IBM Tivoli Monitoring transport file, you must create the transport.prop file in the usr/sap/SID/DVEBMGS<instancenumber>/work work directory of the SAP system and add MAI_CONFIGURED = YES entry in that file. You must not edit the entry in the /IBMMON/ITM_CNFG table.
   • For all other SAP systems with basis version equal to 7.0, or later and Solution Manager V7.1 without MAI configuration, you must directly import the single IBM Tivoli Monitoring transport file.
5. Run the following command to import SAP transport:

   tp addtobuffer ITMK711_00xxxU SID 
   pf=\usr\sap\trans\bin\PROFILE_NAME

   Where:

   SID

   Target SAP system ID.

   PROFILE_NAME

   Name of the tp profile file. Make sure that the current tp parameter file is specified when you import the agent transport files from the command line. The tp parameter file is typically named TP_DOMAIN_SID.PFL. This file name is case sensitive on UNIX systems.

   nnn

   Number for the target client where the agent runs and for which the user ID, IBMMON_AGENT, authorization profile, and /IBMMON/AUTH, are defined.

   Alternately, you can use the SAP STMS transaction to import the ITMK711_00xxxU.ITM transport requests. Ensure that the following options are selected in the Import Options tab of the Import Transport Request window.
   • Leave Transport Request in Queue for Later Import
   • Import Transport Request Again
   • Overwrite Originals
   • Overwrite Objects in Unconfirmed Repairs

   For the SAP Basis version, if the Ignore Invalid Component Version option is enabled, ensure that it is selected.