Defining a Method for the File Transfer to the Target System

The transport directory transdir/data is set as the default directory where the CTS Deploy Web Service searches for data that was stored by the transport program tp. If you want to use another mount/share directory, proceed as follows:

1. Open the Transport Tool tab in the TMS configuration in the Transport Management System on the AS ABAP of the CTS system.

2. Change the value of the DEPLOY_DATA_SHARE parameter to the path of the directory you want to use.

Authorizations for the JCo Connection

Procedure

1. If you want to use a static JCo connection create it on the AS Java where the Deploy Web Service runs, or use an existing one. You do this in the SAP NetWeaver Administrator. Proceed as described under Configuring Export Destinations. However, enter a different name for the destination.

2. If you want to use a dynamic JCo connection, configure a user for it in the TMS Configuration of the AS ABAP of the CTS system. To do this, choose  Goto  File Provider User/PW . Enter a user for SAP NetWeaver Application Server ABAP that has the relevant authorizations as described above, as well as the password.

3. In the TMS configuration on the Transport Tool tab delete the DEPLOY_DATA_SHARE parameter.

4. Set the CTS_FILE_PROVIDER_URI parameter and specify the properties of the connection as values.

Possible Connection Properties

Here you enter the connection data for the communication system. You can either specify a static destination or list the properties of a connection dynamically.

• You enter the static destination in the following format: jco:destination=<MyDestination>. This destination must exist on the system where the CTS Deploy Web service is running, as described above.

• You enter the dynamic connection with properties and values in the following format: jco:<property1>=<value1>,<property2>=<value2>,<...>.

  The following properties are available for dynamic connections:

  • If you use a message server (with load balancing), you can use these properties:

    • mshost

      Default: none

      Message Server Host

    • r3name

      Default: none

      System ID of the CTS system

    • group

      Default: PUBLIC

      Logon group

    • client

      Default: none

      Client of the CTS system

    Note

    These properties are only used if the ashost and sysnr properties are not set.

  • If you use an application server (without load balancing), you can use these properties:

    • ashost

      Default: none

      Application Server Host

      This property is only used if the sysnr is also set.

    • sysnr

      Default: none

      System Number

      This property is only used if the ashost is also set.

    • client

      Default: none

      Client of the SAP System

  • Optional properties (for message server and application server):

    • idletimeout

      Default: 720, smallest value: 0

      Example: jco:idletimeout=600

      Idle timeout in seconds

    • chunks

      Default: 1

      Value range: 1 - 100

      Number of chunks that a file is split into and which are transmitted in parallel. Values greater than 1 acclerate the data transfer for higher resource consumption (work processes). Files smaller than 1 MB are not split, regardless of the value specified in the parameter.

    • buffersize

      Default: 51200, (500KB), smallest value: 1

      Buffer size of input stream in bytes.

    • transfertimeout

      Default: 1800000 (30 Minuten)

      Transfer timeout for a file in milliseconds. If the transfer takes longer than the specified time, the system terminates the transfer.