Question:

I’m checking if AppSync 2.2.2 can be controlled by non AppSync server’s CLI. And I found the following on page 38 of “EMC® AppSync™ 2.2.2 User and Administration Guide” (https://support.emc.com/docu61180_AppSync-2.2.2-User-and-Administration-Guide.pdf?language=en_US) but I can’t do that so far. I am thinking that I will be able to do that if I edit a file “C:\EMC\Appsync\appsync-cli\appsync-cli.bat” where I use Windows 2012 R2 for both AppSync server and the non AppSync server which I will issue the command on. So please tell me how I should modify the appsync-cli.bat file.

Using the CLI You can run the AppSync CLI on the server where the AppSync installation resides. Also, you can move the \EMC\Appsync\appsync-cli directory to another location/host. All actions that are performed, for scripting purposes, return code zero 0 for success and local system failure code -1 for Windows or 255 for Linux). The syntax for using the AppSync CLI follows:

Answer:

You don’t have to edit the appsync-cli.bat file.

To issue the CLI command on the non AppSync server, just copy the “C:\EMC\Appsync\appsync-cli” folder on the AppSync server to the non AppSync server which you issue on. You need java in the non AppSync server because the substance of CLI is a jar file. If you issue the CLI commands on the AppSync server, a java.exe, which was installed when you installed AppSync server, is used, but you need to prepare it & the path to issue the CLI when you issue the CLI on the non AppSync server . (Issuing the CLI in Linux environment is same.)

After the above, you should be able to login after the following. Of course, you need to get the AppSync server from the non AppSync server from the network perspective.

$ cd <directory where appsync-cli is copied>

$ appsync-cli.bat -login server=<appsync_server> user=admin password=xxxxxx

Author: Hiroki