Introduction
For JS7 - Automated Deployment use of a Deployment Area is recommended.
The JS7 - Deployment Area is used for the following purposes:
- to hold the script environment for JS7 - Automated Installation and Update and for JS7 - Deployment Packaging,
- to hold the configuration files and optionally certificates for deployment of JS7 components,
- to hold the JS7 installations per JS7 release and component such as JOC Cockpit, Controller, Agent,
- to hold the archive of Deployment Packages per JS7 releases and target host,
The article explains
- how to manage ownership for the installation and configuration directories of JS7 components.
- how to manage permissions to set up JS7 components
Managing Ownership
When it comes to ownership of directories used by JS7 components consider
- Directories
- The installation directory tree includes files that are executed to start a JS7 component.
- The configuration directory tree includes files for which read access is required. In addition write access is required for example for log files in this directory tree.
- Accounts
- Run-time Account
- The account runs the JS7 component service.
- The account requires access to read and to execute files in the installation directory.
- The account requires access to read and to write files in the configuration directory.
- Home Owner Account
- The account owns the installation directory.
- Data Owner Account
- The account owns the configuration directory.
- Run-time Account
Setting up ownership is fairly simple if a single account is used, for example, a non-root account or root account, that owns both the installation and configuration directories.
User Ownership
Root Ownership
Limited Use of sudo for Ownership by individual Accounts
Unlimited Use of sudo for Ownership by individual Accounts
Resources
Overview
Content Tools