Previous Topic: Secure Sockets Layer (SSL) FTP UsageNext Topic: Define an SFTP Job


Define an SCP Job

You can define an SCP job to transfer binary files using the Secure Copy Protocol (SCP). The SCP protocol does not support wildcard transfers.

Note: To run these jobs, your system requires CA WA Agent for UNIX, Linux, Windows, or i5/OS.

Follow these steps:

  1. Open the Application that you want to add the job to in the Define perspective.

    The Application appears in the workspace.

  2. Select the SCP job from the File Transfer group in the Palette view, and drag the job to the workspace.

    The SCP icon appears on the Application workspace view.

  3. Right-click the SCP icon, and select Edit from the pop-up menu.

    The Basic page of the SCP dialog opens.

  4. Complete the following required fields:
    Name

    Defines the name of the job that you want to schedule.

    Limits: 128 alphanumeric characters, plus the special characters commercial at (@), pound (#), dollar sign ($), underscore (_), square brackets ([]), brace brackets ({}), and percent sign (%) as a symbolic variable introducer character.

    Agent name

    Specifies the name of the agent where the secure transfer takes place.

    Note: The drop-down list displays all the agents that are defined in the Topology for the specified job type.

    Transfer direction

    Indicates the direction of transfer (Download or Upload).

    Default: Download

    Server address

    Specifies the DNS name or IP address of a remote server.

    Example: 172.24.36.107 (IPv4) or 0:0:0:0:0:FFFF:192.168.00.00 (IPv6)

    Remote directory

    Specifies the file's remote source directory (if downloading) or the file's remote destination directory (if uploading).

    Remote file name

    Specifies the file's source location (if downloading) or the file's destination (if uploading).

    Note: Wildcards are not permitted.

    Local file name

    Specifies the file's destination (if downloading) or the file's source location (if uploading).

    Note: Wildcards are not permitted.

    User

    Specifies the user ID of the user with the authority to download the file from the remote FTP server or upload the file to the remote FTP server. The user must be defined in the Topology. This field supports the use of a namespace for a user that has more than one password. Contact your administrator for the user name defined in the Topology.

    Examples: Bob, Production:Bob

    Note: The drop-down list displays all the user IDs that are defined in the Topology for the specified agent. You must have at least Read access to the ADMIN.Network Topology permission to view this list.

  5. (Optional) Specify the following additional information:
    Server port

    Specifies the port number of the remote server.

    Default: 22

    Local user

    Specifies a user ID on the UNIX or Linux computer where the agent is installed. This user ID determines the access permissions of a downloaded file on the agent computer and does not apply to uploads. When the file is downloaded, the file is created with this user as the file owner. To set the owner of a downloaded file, the agent must run as root.

    Notes:

    • The local user does not need to be defined in the Topology.
    • Your agent administrator can specify a default local user for all FTP, Secure Copy, and Secure FTP jobs by setting the ftp.download.owner parameter in the agent's agentparm.txt file.
    • The value in this field overrides the default setting specified in the ftp.download.owner parameter in the agent's agentparm.txt.
    The remote os type

    Specifies the remote operating system type in a secure file transfer (UNIX or Windows). The remote operating system type is used to determine the path separator on the remote system.

  6. Click OK.

    The Secure Copy job is defined.

Example: Download a File Using the Secure Copy Protocol

Suppose that you want to download the install.log1 file from the root directory on the chi-linux server using the Secure Copy Protocol (SCP).

To download a file using the Secure Copy Protocol

  1. Enter the following information in the Basic page:
  2. Select the Download option button in the Transfer direction section.
  3. Click OK.

Example: Change the Owner of a File Downloaded from a Remote Server

Suppose that you want to download the file_size8 file from the /ul/test/ftpdata directory on the simon server using the Secure Copy Protocol (SCP). After the file is downloaded, the agent computer contains a file named scp_file_size8_local_user in the /u1/causer/data directory. The owner of the file is test.

To change the owner of a file downloaded from a remote server

  1. Enter the following information in the Basic page:
  2. Select the Download option button in the Transfer direction section.
  3. Click OK.

More information:

Using a Namespace for a User that has Different Passwords