|
Bucket Commander
is a command line tool for Amazon S3. Bucket Explorer does all operations manually but Bucket Commander helps you in Scheduling and Automation of upload/download/copy/setaclstodefault features. Here Automation means the scheduled operations will be carried on automatically as per configured in schedule, so you can use Bucket commander instead of Bucket Explorer when you want to schedule a big process.
Bucket Commander needs a configuration file, which can be created using Bucket Explorer's UI or manually.
Bucket Commander takes four arguments. "
-action
" , "
-authenticate
”, "
-emailprofile
” and "-configfilename"
-
Action:-
Valid values for "-action" are:
-
Upload
-
Download
-
Copy
-
Setaclstodefault
-
Authenticate:-
This argument will be optional if only one credentials is saved For "-authenticate" specify the nick name that you specified at the time of save credentials
To run Bucket Commander at least one credential should be saved. If you run bucket commander first time then it will ask you for credentials with nick-name to save and run bucket commander operation.
-
Emailprofile:-
-emailprofile is optional argument , you need to specify it only when you have configured the Email profile for getting report of Bucket Commander operations (Upload, Download and Copy) via Email. For " -emailprofile " specify the profile name that you have saved in Email profile configuration from Bucket Explorer's UI.
-
Configfilename:-
-configfilename is an optional argument; this will take full path of commander configuration file saved on your system. This will perform commander operation according to Upload, download and copy content saved in the specified file. If this argument is not being specified then Bucket commander will perform operation according to default “BucketCommander.xml” exist in config folder. If commander configuration file, that have been supplied through –configfilename argument does not exist on your system, then Bucket Commander will create a blank file with supplied name and with proper message and commander will exit.
|
For Bucket Commander to work it needs-
-
“Config” folder and .Lic file for Bucket Commander; Config folder contains “BucketCommander.xml” and “Bucketexplorer.xml”. Upload /Download/Copy details are picked from the commander xml and authentication details are picked from Bucket Explorer xml.
-
If user wants to create commander configuration file using Edit commander config option, then it must need to have .lic file for Bucket Explorer UI.
-
If you do not have .Lic file for Bucket Commander, then Bucket Commander will ask you to download trial license or activate Bucket Commander. If you enter yes option then BucketCommandertrial.Lic file would be downloaded at home directory else you will be asked to activate for Bucket Commander. When you were able to activate the Bucket Commander then BucketCommander.lic file would be downloaded at home directory.
-
To download license file for Bucket Commander you will be asked to use proxy setting. If you enter yes then it will ask you for proxy setting details as port address, host address, username, and password, domain name.
Commands required to run an operation -
-
If you want to use default configuration file i.e. BucketCommander.xml :
-action: upload/download/copy/setaclstodefault [-authenticate: saved credentials] [-emailprofile: emailprofile-name] [-bucketname: name-of-bucket-on-which-default-acl-set]
-
If you want to use other then default configuration file: To run Bucket Commander there is default Bucket Commander.xml file. You can also create same configuration file with different name at your desired location .you can create this file manually or by using Edit Commander config option using Bucket Explorer .
-action: upload/download/copy/setaclstodefault [-authenticate: saved credentials] [-emailprofile: emailprofile-name] [-configfilename: full path of commander configuration file] [-bucketname: name-of-bucket-on-which-default-acl-set]
If you want Create/Edit commander configuration file manually then you must know the format of commander conflagration file.
The format has been described at –
How to run multiple instances of Bucket Commander
To configure Email Profile please refer this page:
http://www.bucketexplorer.com/documentation/amazon-s3--how-to-send-report-with-bucket-commander.html
You can specify more than one Email Profile by comma separator for getting report of Bucket Commander Operations via email to each specified profile.
NOTE:
If you have changed your saved credentials (Access Key or Secret Key) then it will prompt a message to update your credentials, now you need to update saved credentials by giving changed Access Key and Secret Key.
If BucketCommander.exe runs on different machines then it will not be able to decrypt your saved credentials so it will prompt a message to update saved credentials, now you need to update credentials by giving Access Key and Secret Key.
An example of working command looks like:
Command on Windows
BucketCommander.exe -action: upload/download/copy [-authenticate: nick-name] [-emailprofile: profilename1, profilename2]
[-configfilename: full path of commander configuration file]
Or
BucketCommander.exe -action: setaclstodefault [-authenticate: nick-name] -bucketname: name-of-bucket-on-which-default-acl-set]
Command on
Linux
BucketCommander.sh/BucketCommander-jre.sh -action: upload/download/copy [-authenticate: nick-name] [-emailprofile: profilename1, profilename2] [-configfilename: full path of commander configuration file]
Or
BucketCommander.sh/BucketCommander-jre.sh -action: setaclstodefault [-authenticate: nick-name] bucketname: name-of-bucket-on-which-default-acl-set]
Note:
On Linux you can open terminal from Applications->Accessories->Terminal
Command on
Mac OSX
java -jar BucketCommander.jar -action: upload/download/copy [-authenticate: nick-name] [-emailprofile: profilename1, profilename2] [-configfilename: full path of commander configuration file]
Or
java -jar BucketCommander.jar -action: setaclstodefault [-authenticate: nick-name] bucketname: name-of-bucket-on-which-default-acl-set] Note: On Mac OSX you can open terminal from Applications->Utilities->Terminal in Finder.
Note:
On Mac OSX you can open terminal from Applications->Utilities->Terminal in Finder. |
Related Topics
:
|
|
|