Page Comparison

...

1. In the subdirectory "\webapps" of the Web Application Server, you can find the deployment installed so far (usually with the name "\gtc").
2. Rename this directory (e.g. "\gtc_old") and then move it to a directory outside the "\webapps" directory. Under no circumstances may the backuped deployment remain in the "\webapps" directory. This would lead to serious errors later on in the update process. 

1.4) Update SAPJCO

The GTC is working with a new SAPJCO version. Provided RFC connections are addressed with the GTC, you must perform the following steps when updating to GTC version 20.11.03 or newer:

1. Remove the "sapjco3{*}.jar" file from the deployment directory "<gtc-root>/lib".
   The following steps must be performed only once:
2. Remove the "sapjco3{*}.jar" file from the "<Tomcat-root>/lib" directory, if necessary.
3. For licensing reasons, we are not allowed to offer these files for download or distribute them in the package. Download the files "sapjco3*.dll" or "libsapjco3.so" and "sapjco3{*}.jar" from the SAP support website.
4. Replace the dll or so file. (The Windows dll is usually placed in the system32 folder).
5. Place the downloaded "sapjco3{*}.jar" file in the "<Tomcat-root>/lib" directory. Do not rename the file.

After the preparations are complete, you can update the database and then the deployment.

...

"Host" and "Port" must be entered according to the TC installation. If the Web Service URL of the TC does not end in "eric", the last part of the URL (e.g. eric29) in the connection must be entered in the field Parameter 1.

6.2) Proxy between GTC and TransferClient

The proxy is maintained as a separate connection parameter on the administration page.

6.3) Connection test to the TransferClient

...

The proxy is maintained as a separate connection parameter on the administration page.