Cisco Cisco Process Orchestrator 3.1 User Guide

Page of 786
 
13-130
Cisco Process Orchestrator 3.1 User Guide
 
Appendix 13      Using Adapters 
  Terminal Adapter
Adding a Remote File to a Get File Activity
The Get File activity copies files from remote target systems to a local directory. The Add button on this 
activity launches the Enter Remote File to Add dialog box for users to specify the file name to be added 
to the list on the Get File activity.
Step 1
On the Get File property page, click Add.
Step 2
Enter or select the file name to be added to the list and click OK.
The file is added to the list of remote files to be retrieved by the Get File activity.
Viewing Results
Click the instance tabs to view the retrieve files from a Unix/Linux system target. See also, 
.
Defining a Put File Activity
Use the Put File activity to push local files to a Unix/Linux system target if SFTP or SCP is available on 
the given target.
If both protocols are available, SFTP will be used. If one file in the list fails while uploading, the activity 
will fail.
The file transfer results of the Put File activity are displayed from the Operations Workspace activity 
instance view.
Step 1
In the Process Editor Toolbox, choose Secure Shell (SSH) > Put File and drag and drop the activity onto 
the Workflow pane.
Step 2
Click the General tab and enter the appropriate information.
Step 3
Click the Put File tab and specify the local files and file path to the remote directory to where the files 
will be copied:
  •
Local windows runtime user for accessing local file systems—From the drop-down list, select the 
windows runtime user account that contains the credentials to access local files.
The user must have the Log on as batch job and Allow log on locally User Rights Assignment. To 
adjust the user right assignments (see Administrative Tools/Local Security Policy/Security 
Settings/Local Policies/User Rights Assignment).
  •
Local files on the target to copy from—The list of files on the local computer to put on remote target 
systems. If a relative path is specified, it will be a relative to the product local application data 
directory.
  •
Remote directory on the target to copy files to—the file path to the local directory on the target 
systems where the files will be transferred.
An absolute path is recommended. The default file path is relative to the product local application 
data directory. For example:
C:\Documents and Settings\test\Local Settings\Application Data
  •
Overwrite—Select the appropriate option to determine the circumstances in which the copied file 
should overwrite any existing file in the local directory.