Volumes of running applications are made accessible through scp.
Note: An authorized SSH key must be set up for the user to use the scp access to volumes. See the Command LIne Shell Reference Guide for details on authorizing an ssh key. When using scp access, configure the client program to use the private key that corresponds to the key set up with the user create or user set command and specify root as the username to scp (For example, use root@controllerhost as the target name).
The following commands are supported:
scp -d localdir root@controllerhost:/_impex/
Copies localdir to the controller's import/export area. Same with swapped 1st and 2nd args to copy from the controller to a local file or directory. This is typically used to copy data for the 'app import', 'class import', 'app export' and 'class export' commands.
scp localfile root@controllerhost:/app/appname/compname/filepath
Copies localfile to the filespace of a running appliance. Same with swapped 1st and 2nd args to copy from an appliance to a local file or directory.
Volumes of non-running applications are made accessible through the vol manage command or via the Manage Volumes dialog within the CA 3Tera AppLogic Editor.
When a volume is managed through the shell interface (vol manage command), the user is provided access to the volume through an SSH session to the filer appliance that is exposing the volume contents. In addition, a URL is displayed where the volume may be accessed to upload or download files to or from the volume.
When a volume is managed through the CA 3Tera AppLogic Editor, the user is provided access to the volume through the Volume Browser, which provides a visual interface for viewing and manipulating CA 3Tera AppLogic volume contents.
|
Copyright © 2011 CA.
All rights reserved.
|
|