Show TOC

Parameters for Non-ABAP TransportsLocate this document in the navigation structure

Use

You can display, change, add, or delete the parameters introduced here for non-ABAP transports in the Transport Management System in TMS Configuration using the Transport Tool tab page.

For more information, see Changing the Standard Settings for Source Systems or Changing the Standard Settings for Target Systems.

Parameters for Source Systems

  • NON_ABAP_WBO_CLIENT

    Default: none

    Value range: 000-999

    This value specifies the logon client of the Transport Organizer in the communication system of this non-ABAP system. It makes sure that transport requests are created in the correct client. When creating a non-ABAP or dual stack source system in which you want to use Transport Organizer you must specify a value for this parameter. You can change the value here.

  • NON_ABAP_WBO_INBOX

    Default: none

    Path to the directory where Transport Organizer searches for files.

    For this parameter you must choose between a close or loose coupling between your SAP applications and CTS:

    • Close Coupling: You need this parameter setting when you attach files to a transport request from a server share/mount. However, the default setting uses file streaming (see parameter WBO_FILE_TRANSFER).

    • Loose Coupling: You need this parameter setting when you attach files to a transport request from a server and not from a desktop (client).

    For more information, see Defining a Method for the File Transfer from the Source System.

  • WBO_FILE_TRANSFER

    Default: Stream

    Value range: Stream, Share

    File transfer method between applications (clients) and the CTS system (streaming or file share/mount)

    You need this parameter only if you choose a close coupling.

    For more information, see Defining a Method for the File Transfer from the Source System.

  • WBO_GET_REQ_STRATEGY

    Default: Tagged

    Value range: Tagged, Create, Smart

    This value controls the automatic creation of a transport request when exporting an object.

    When creating a non-ABAP or dual-stack system, the value is automatically set to Smart. If you delete the parameter, the standard value Tagged applies.

    You need this parameter only if you choose a close coupling.

    For more information, see Choosing a Transport Strategy.

  • WBO_REL_REQ_STRATEGY

    Default: Manual

    Value range: Manual, Auto

    This value controls the automatic release of a transport request.

    You need this parameter only if you choose a close coupling.

    For more information, see Choosing a Transport Strategy.

  • WBO_USR_MAP_STRATEGY

    Default: Application

    Value range: Application, System

    User responsible for transport requests

    When transport requests are created, the SAP application determines the user responsible for the requests by default.

    If you want the CTS system (backend system) to determine the responsible person of the transport request when creating transport requests according to the data in the export destination (for example, the user that is entered in the logon ticket) then you can set the value to System.

    Recommendation If you use single sign-on, always set this parameter to System.

    You need this parameter only if you choose a close coupling.

  • WBO_SUPPRESS_OBJLIST

    Default: False

    Value range: False, True

    If you want to stop recording the detailed object list, set this parameter to the value True. Only objects of type File Container are then displayed in the object list. The default setting for this parameter is False.

    You need this parameter only if you choose a close coupling.

  • CTS_SYSTEM_MAPPING

    Default: none

    Enter the system ID of your non-ABAP system if it is not the same as the name of the corresponding non-ABAP or dual stack system in TMS.

    Caution If possible, always create your non-ABAP systems in TMS with the same system ID that you gave the non-ABAP system when you installed it.

    You need this parameter only if you choose a close coupling.

  • CTS_SYSTEM_TYPE

    Classification of the systems in transactions SMSY or LMDB for SAP Solution Manager scenarios.

    For source non-ABAP systems used in SAP Solution Manager scenarios, you must manually add this parameter as required by your scenario. Examples are Java, HANADB, or BOBJ.

  • COMMUNICATION_SYSTEM

    Default:<SID of CTS System>

    Name of ABAP communication system that was specified when creating a non-ABAP system.

    Caution You may not edit this parameter using the Transport Tool tab page. Choose the tab Communication to makes changes. Otherwise errors can occur.

  • DI_SYSTEM

    Default: False

    Value range: True, False

    Only when using NWDI in connection with CM Services: Classify the system as DI system. If the Create Development Configuration checkbox is checked when creating a non-ABAP system, then the paramter is automatically set to the value True.

  • DI_SLD_URL

    Default: none

    Only when using NWDI in connection with CM Services: URL to System Landscape Directory (SLD) that was specified when creating the first non-ABAP system.

    Caution This parameter is set globally. If you change the SLD URL, then this change applies for all systems in your transport landscape.

Parameters for Target Systems

  • DEPLOY_URL

    Default: none

    If you need to deploy your software using Software Deployment Manager (SDM) or the Deploy Controller (DC), specify the Deploy Tool URL in the target system.

    You must take into account the release of the target systems:

    • Target systems with Release SAP NetWeaver 7.1 or higher

      Deployments use Deploy Controller (DC).

      Enter the URL in one of the following formats:

      • For secure communication use the P4S port: P4S://<host of target system>:5<system number>05 or https://<host of target system>:5<system number>05.
        Note Technically, the P4S protocol is used even if https is specified. For secure deployment, make sure that secure communication is possible between the AS Java that is used as Deploy Web Service host and the AS Java target system. For more information on configuring secure connections, see Configuring the Use of SSL on the J2EE Engine or Using SSL to the AS Java via the ICM in the Transport Layer Security section of the Security Guide for SAP NetWeaver.

      • P4://<host of target system>:5<system number>04 or http://<host of target system>:5<system number>04

        Note Technically, the P4 protocol is used even if http is specified.

      Then choose Start of the navigation path Goto Next navigation step SDM/DC User/PW End of the navigation path and enter a user of the SAP NetWeaver AS Java with DC authorization and the correct password.

    • Target systems with Release SAP NetWeaver 7.0

      Deployments use SDM.

      Enter the following URL:

      http://<host of target system>:5<system number>18

      Example

      http://<TargetHost>:50018

      Then choose Start of the navigation path Goto Next navigation step SDM/DC User/Password End of the navigation path and enter the password of the SDM user.

  • DEPLOY_XI_URL

    Default: none

    If you need to deploy your software to an SAP PI system, specify the URL of the SAP PI system in the target system in one of the following formats:

    • For secure communication, use the https port: https://<host of target system>:5<system number>01

      Note Make sure that secure communication is possible between the AS Java that is used as Deploy Web Service host and the SAP PI target system. For more information on configuring secure connections, see Configuring the Use of SSL on the J2EE Engine or Using SSL to the AS Java via the ICM in the Transport Layer Security section of the Security Guide for SAP NetWeaver.

    • http://<host of target system>:5<system number>00

    Then choose Start of the navigation path Goto Next navigation step XI User/PW End of the navigation path and enter a user with SAP PI authorization.

  • DEPLOY_SLD_URL

    Default: none

    If you need to deploy your software to an SAP NetWeaver system landscape directory system (SLD system), specify the URL of the SLD system in the target system in one of the following formats:
    • For secure communication, use the https port: https://<host of target system>:5<system number>01
      Note Make sure that secure communication is possible between the AS Java that is used as Deploy Web Service host and the SLD target system. For more information on configuring secure connections, see Configuring the Use of SSL on the J2EE Engine or Using SSL to the AS Java via the ICM in the Transport Layer Security section of the Security Guide for SAP NetWeaver.
    • http://<host of target system>:5<system number>00

    Then choose Start of the navigation path Goto Next navigation step SLD User/PW End of the navigation path and enter a user with SLD authorization.

  • DEPLOY_WEB_SERVICE

    Default: CTSDEPLOY

    Name of the deploy Web service in transaction LPCONFIG.

  • DEPLOY_DATA_SHARE

    Default: None

    The directory where the CTS Deploy Web service accesses the data saved by the transport program tp.

    When creating a non-ABAP system, the value is automatically set to transdir/data on the communication system of the non-ABAP system. This is the data subdirectory of the transport directory. You can change this value to a different directory.

    For more information on this parameter, see Defining a Method for the File Transfer to the Target System.

  • CTS_FILE_PROVIDER_URI

    Default: none

    With this parameter you define an SAP Java Connector connection (JCo connection) for transferring data to the target system. This parameter is only evaluated if the parameter DEPLOY_DATA_SHARE is not set.

    For more information on this parameter, see Defining a Method for the File Transfer to the Target System.

  • DEPLOY_OUTBOX and DEPLOY_OUTBOX-<APPLICATION_TYPE>
    Note DEPLOY_OUTBOX-<APPLICATION_TYPE> is only available if the CTS plug-in is installed in the SAP system.

    Default: none

    You can set these optional parameters in addition to the other deployment methods. The parameters define the directory to which the transport program tp copies non-ABAP objects. You can use these parameters to run a manual deployment, after the import, for non-ABAP objects without automatic deployment methods (such as non-SAP objects). If you do not set any of these parameters, no deployment to a file system takes place.

    If the parameter DEPLOY_OUTBOX-<APPLICATION_TYPE> is not set, the value of parameter DEPLOY_OUTBOX is used.

    If the parameter DEPLOY_OUTBOX-<APPLICATION_TYPE> is set without a value, the transport program tp does not execute a copy of the non-ABAP objects on the file system for the application type. This makes sense if, for example, an automatic deployment has been defined for this application type by default.

    Note

    Pay attention to upper and lowercase with the value for <APPLICATION_TYPE>. The value must be written in exactly the same way as the definition of the application type.

    For more information, see Connecting Further Applications with the Change and Transport System.

    Caution If these are the only parameters you specify as a deployment method, you must delete the parameter DEPLOY_WEB_SERVICE.

  • CTS_SYSTEM_TYPE

    Classification of the systems in transactions SMSY or LMDB for SAP Solution Manager scenarios.

    When you create a non-ABAP target system, this parameter is generated automatically. Possible values are Java and others. Depending on your SAP Solution Manager scenario, you can adjust it to the required value, for example HANADB or BOBJ.

  • DI_SYSTEM

    Default: False

    Value range: True, False

    Only when using NWDI in connection with CM Services: Classify the system as DI system. If the Create Development Configuration checkbox is checked when creating a non-ABAP system, then the paramter is automatically set to the value True.

  • COMMUNICATION_SYSTEM

    Default: <SID of CTS system>

    Name of ABAP communication system that was specified when creating a non-ABAP system.

    Caution You may not edit this parameter using the Transport Tool tab page. Choose the tab Communication to make changes. Otherwise errors can occur.