NSH Script Jobs and permissions
Some BLCLI commands create files in a directory that the user specifies. For example, the ImportExport exportObject command exports an object into an XML file that resides in a directory that the user specifies as an argument to the command. For details, see BLCLI-reference.
Other commands read files from a local path.
If you are a running a command that reads or writes to a local path (a path local to the computer on which the BLCLI is running), you must have read or write access to the specified path at the OS level. The "user" in this context is the OS user, not the BMC Server Automation user.
The following table provides examples of required permissions in typical scenarios:
Example scenario | Details of required permissions |
|---|---|
Running a command manually at the command line | Suppose user foo runs exportObject (or any other command that writes a file to user-specified local directory). User foo must have OS-level write access to the specified directory. |
Running a command within an NSH Script Job | When the BLCLI is invoked by using an NSH Script Job, that BLCLI process is run as whatever OS user the Application Server is running as.
|