Using the CA Harvest Remote Transport Option (RTO)

Document ID : KB000055381
Last Modified Date : 14/02/2018
Show Technical Document Details

The CA Harvest Remote Transport Option (RTO) is a client-server add-in which allows CA Harvest Change Manager to control code on any platform equipped with an SFTP (Secure Shell) server and FTP for Unix, Windows and IBM iSeries platforms. The new option also can manage application development on remote machines and connect to Windows, UNIX and Linux platforms.

The advantage of this approach is that no software needs to be installed on the controlled platform. Harvest Agents are not necessary.

Components

RTO Server: This is installed on the same machine as the Harvest Server. The RTO Server has FTP and SFTP clients built in, which allow communication with FTP and SFTP servers running on external systems.

RTO Client: A PC-based client GUI. This is installed on each client PC which needs to use RTO to control code on external systems. This GUI replicates the look-and-feel of the conventional Harvest Checkout and Check-in dialogs and - when invoked as a stand-alone client-side UDP from the Harvest

Command-line tools: These tools have the same switches "rtoco" as hco and "rtoci"as hci in harvest plus new switches that permit check-in and check-out operations over FTP/SFTP.

Configuring RTO

RTO operation is controlled by a configuration file rto.conf in RTO Home. This file simply controls which port the server and client should communicate over. It also contain a number of additional directives to control the protocols over which RTO is allowed to operate, the creation of server-side log files and so on.

RTO with IBM iSeries

RTO allows Harvest to control code with an SFTP & FTP for IBM iSeries.

To enable Secure Shell (and the corresponding SFTP protocol) you need to install Portable Utilities for i5/OS (5733-SC1) on the iSeries machine. The 5733-SC1 LPO consists of two options (*BASE and option 1) that both need to be installed.

OS400, the iSeries Operating System has two types of file systems -the native file system (which contains libraries, files and members) and the Integrated File System (IFS) which has a hierarchy of files and directories similar to a Unix System. FTP can transfer files to and from both IFS and the Native File System. SFTP can transfer files to and from the IFS only. If you connect to an iSeries machine using SFTP then you will be able to browse the native file system but you will be unable to check-in and check-out from this file system.

Checking In from iSeries

We can check in files from IFS using either SFTP or FTP in the conventional way. Directories in the IFS map to folders within the repository and files become versions.

You can only check in files from the native file system using FTP. In this case, Libraries and Files become folders within the repository and members become versions.

Some file types within the native file system cannot be transferred directly (such as Data Areas - DTAARA). The only way to transfer these files is to create a Save File and then check the Save File into Harvest.

Checking out to iSeries

You can check out files from Harvest to the IFS using either SFTP or FTP in the conventional way. In this scenario, new directories are created as required.

When checking out to the native file system, if the folder name ends in '.LIB' then RTO issues a MKD command, specifying the library name in order to create the library in the native file system. If the folder name does not end in '.LIB' then RTO issues a CRTS FILE(folder name) command via FTP. This is the equivalent of the CRTSRCPF command, or "Create Source Physical File". This can result in problems when creating new file/member hierarchies within the native file system. Checking out a member to an existing file will work with no issues.