KB33431: How to avoid storing the Administrative password in MicroStrategy Command Manager 9.0.0-9.0.1 batch files

In Strategy 8.x, the user needs store the Administrative password in a batch file to kick off a script. For more details, please refer to the tech note below:
KB6392: How to execute a command manager script through a command line interface with Strategy Administrator - Command Manager 9.x
 
In Strategy 10.x, the user has an option to use a Procedure to initiate a connection to a server and execute a script without storing the Administrative password in batch files. For more information on how to create a procedure, please see tech note:
KB440526 : How-to-create-a-User-Procedure-based-on-a-Sample-Procedure-in-Strategy-Command-Manager
 
Another method for providing a script to non administrative users for them to use, without giving them access to the adminstrative credentials, is to use encrypted scripts.  This allows the script to be encrypted so it can be executed by users provided the script, but cannot be edited or viewed without the specified password.  This would prevent non-adminstrator users from getting access to adminstative credentials contained in the script. Details on using this method are outined in the tech note below:
KB40525 : How-to-save-scripts-or-procedures-with-encryption-in-Strategy-Command-Manager
 
Note: please make sure Java.exe and Jar.exe are in the system path and also from supported Java SDK version.

• Unzip "example.zip" file.
• Modify the "ConnectionInfo.java" to change the Server name, Login and Administrative password. This file is under "example\src\info" folder:
   
  

• Execute "compile.bat" to create "ConnectionInfo.class" in the folder "example\bin\info".
• Copy "info.jar" to "C:\Temp"
• Copy the file "Outlines\Procedure_Outlines\User_Procedures\ConnectToServer.cmp" to the appropriate Command Manager directory
• Now, the user can use the command below to build connection to the server:
   
  
  Sample Code/Error
  
  EXECUTE PROCEDURE ConnectToServer();
  
  
    
  
• "TestScript.scp" is an example incorporating the "ConnectToServer" procedure to a script.

Disclaimers and Limitation of Liabilities
Disclaimer: The example.zip is provided "as is" and without warranty of any kind. Strategy expressly disclaims all warranties, express, implied or statutory, including, without limitation, the implied warranties of merchantability, fitness for a particular purpose, satisfactory quality and non-infringement.
 
Limitation of Liability: Strategy shall have no liability to licensee for any damages of any kind, including, but not limited to, liability for direct, indirect, special, incidental or consequential, damages (which shall include, but not be limited to, loss of data or information, loss of revenue or anticipated profits or lost business).
000011048