Show TOC

Background documentationParameters for Non-ABAP Transports Locate this document in the navigation structure

 

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 Systems.

  • 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 Recommendation

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

    End of the recommendation.

    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 more detailed object list for SAP NetWeaver Portal and Development Infrastructure objects, 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 system in TMS.

    Caution 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.

    End of the caution.

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

  • CTS_SYSTEM_TYPE

    Default: Java

    Value range: Java, Others

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

    When you create a non-ABAP system, this parameter is generated with the value Java automatically. For non-SAP systems, change this parameter to Others.

  • COMMUNICATION_SYSTEM

    Default: <SID of CTS System>

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

    Caution Caution

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

    End of the caution.

  • 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 Caution

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

    End of the caution.
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.0

      Deployments use SDM.

      Enter the following URL:

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

      Example Example

      http://<TargetHost>:50018

      End of the example.

      Then choose   Goto   SDM/DC User/Password   and enter the password of the SDM user.

    • Target systems with Release SAP NetWeaver 7.1

      Deployments use Deploy Controller (DC).

      Enter the following URL:

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

      Then choose   Goto   SDM/DC User/PW   and enter a user of the NetWeaver AS Java with DC authorization and the correct password.

  • DEPLOY_XI_URL

    Default: none

    If you need to deploy your software to an SAP NetWeaver PI system, specify the URL of the SAP NetWeaver PI system in the target system as follows:

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

    Then choose   Goto   XI User/PW   and enter a user with SAP NetWeaver 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 as follows: http://<host of target system>:5<system number>00.

    Then choose   Goto   SLD User/PW   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.

  • 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 Target System.

  • DEPLOY_OUTBOX

    Default: none

    You can set this optional parameter in addition to the other deployment methods. It defines the directory to which the transport program tp copies non-ABAP objects.

    Note Note

    You can use this parameter to run a manual deployment, after the import, for non-ABAP objects without automatic deployment methods (such as non-SAP objects).

    End of the note.

    Caution Caution

    If this is the only parameter you specify as a deployment method, you must delete the parameter DEPLOY_WEB_SERVICE.

    End of the caution.

  • CTS_SYSTEM_TYPE

    Default: Java

    Value range: Java, Others

    Classification of the systems in transaction SMSY for SAP Solution Manager scenarios.

    When you create a non-ABAP system, this parameter is generated with the value Java automatically. For non-SAP systems, change this parameter to Others.

  • 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 Caution

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

    End of the caution.