You have the folllowing options to send non-ABAP objects from transport requests to the target system:
You can use a mount directory or a share directory. Transport directory transdir/data is used by default. To change this, set the parameter DEPLOY_DATA_SHARE and specify which directory the CTS Deploy Web Service should search in for the data stored by the transport program tp.
If errors occur when working with the Deploy Data Share (for example, authorization problems, problems between Unix and Windows) or if you have configured multiple servers that take on different tasks and which cannot be connected using file shares, you can create an SAP Java Connector connection (JCo connection). The JCo connection is for communication between the system where the CTS Deploy Web service is running and the CTS server. You can either specify a static or a dynamic JCo destination.
When you create a JCo connection you have to set the CTS_FILE_PROVIDER_URI parameter and specify the properties of the connection as values.
Note
You have to delete the DEPLOY_DATA_SHARE parameter to be able to use the CTS_FILE_PROVIDER_URI parameter. Otherwise the system tries to access the Deploy Data share.
You are in the Transport Management System in TMS configuration on the Transport Tool tab.
For further information, see Changing Standard Settings for Target Systems.
If you want to use a dynamic connection: The Java user that the CTS Deploy Web service runs under has the action Destination_Service_Write_Permission.
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 or you must create it there.
Note
If you want to create a static destination, proceed as described under Configuring Export Destinations. You can, of course, enter a name of your choice for the destination.
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.
Example
Example for a static destination:
jco:destination=MyDestination,buffersize=100000
Example for a dynamic connection (with load balancing):
jco:mshost=pwdf2318,client=001,r3name=CTS
Example for a dynamic connection (without load balancing):
jco:ashost=pwdf2318,client=001,sysnr=20
Example for a dynamic connection (with load balancing and optional properties):
jco:mshost=pwdf2318,client=001,r3name=CTS,idletimeout=600,group=PUBLIC,buffersize=100000,transfertimeout=1200000