To change the parts of the server file system that workflows and the Orchestrator API can access, modify the js-io-rights.conf configuration file. The js-io-rights.conf file is created when a workflow attempts to access the Orchestrator server file system.

About this task

If the js-io-rights.conf file does not exist on your Windows system, you can manually create it with the default contents. You can create manually the file only on Windows systems. For more information, see Manually Create the js-io-rights.conf File on Windows Systems.

Orchestrator has read, write, and execute rights to a folder named orchestrator, at the root of the server system.

Note:

To locate the js-io-rights.conf on the Orchestrator Appliance, log in to the Orchestrator Appliance Linux console as root and navigate to the /etc/vco/app-server directory.

Procedure

  1. Create the c:/orchestrator folder at the root of the Orchestrator server system.
  2. Navigate to the folder that contains configuration files on the Orchestrator server system.
  3. Open the js-io-rights.conf configuration file in a text editor.
  4. Add the necessary lines to the js-io-rights.conf file to allow or deny access to parts of the file system.

    For example, the following line denies the execution rights in the c:/orchestrator/noexec directory:

    -x c:/orchestrator/noexec

    c:/orchestrator/exec retains execution rights, but c:/orchestrator/noexec/bar does not. Both directories remain readable and writable.

Results

You modified the access rights to the file system from workflows and from the Orchestrator API.