Installing the JS7 Agent
Prerequisites
- A Java Runtime Environment starting from version 1.8 is required.
- For details see Which Java versions is JobScheduler available for?
Preparation
- Download the Agent archive for the target system from the JS7 - Download page.
- For Unix systems:
- A tarball archive is available that can be extracted to create the Agent's directory structure (see below).
- For Windows systems:
- A .zip archive is available that can be extracted to create the Agent's directory structure (see below)
- For Unix systems:
Installation
- Unzip the downloaded archive file to an arbitrary directory.
- The resulting directory structure includes (only files and folders immediately relevant):
bin
agent.cmd
- The start script for Windows platforms.
agent.sh
- The start script for Unix platforms.
agent_instance.sh-example
- A template for configuring multiple instances of the Universal Agent
lib
- The directory for Java libraries.
var_4445
logs
config/private
(for ssl configuration)tmp
(for internal use)
service
(for Windows)
- On Windows Systems:
- You have to change the directory permissions for the
.\logs
and.\service
directories if you extracted the Agent to e.g. C:\Program Files.- This step is not required if you extracted the Agent to e.g. C:\ProgamData.
Start a command prompt with elevated administrative rights and type e.g.
set full acces for "Users" on .\service and .\logs directorycd "path\to\Agent installation" icacls "service" /L /grant *S-1-5-32-545:(OI)(CI)F icacls "logs" /L /grant *S-1-5-32-545:(OI)(CI)F
- You have to change the directory permissions for the
- If multiple instances are configured then every instance must have its own
./var_4445
data directory (e.g../var_<port of the instance>
)
Updating an Agent
The update to the JS7 Agent is performed from the same download archive as used for any fresh installation:
js7_agent_windows.x.x.x.zip
for windowsjs7_agent_unix.x.x.x.tar.gz
for Linux
Preparation
- Stop the JS7 Agent instance.
- Prepare to rollback in case that the update of the JS7 Agent is not successful:
- Create a .tar.gz/.zip archive for the
- Installation Directory:
- The default installation paths for the Agent are:
/opt/sos-berlin.com/js7/agent
on Linux systems andC:\Program Files\sos-berlin.com\js7\agent
on Windows.
- The default installation paths for the Agent are:
- Configuration Directory
- The default configuration paths for the Agent are:
/home/sos/sos-berlin.com/js7/agent_<port>
on Linux systems andC:\ProgramData\sos-berlin.com\js7\agent_<port>
on Windows.
- The default configuration paths for the Agent are:
- Installation Directory:
- Create a .tar.gz/.zip archive for the
- Take a Backup of the above archives created.
Note: For Linux environments taking the backup of the directories and extracting them at the time of rollback is sufficient, however, in case of Windows it is also required to re-install the service of the Agent.
Update
Installer Options
- When the Agent was previously installed it added the
agent_install.xml
file that includes parameters such as the installation path, ports, etc.- The default location of the
agent
_install.xml
file is:/opt/sos-berlin.com/js7/agent
on Linux systems andC:\Program Files\sos-berlin.com\js7\agent
on Windows.
- The default location of the
The
agent_i
nstall.xml
file is explained with the code listing below. The extensive comments are intended to be self-explanatory.
Running the Installer
Install the JS7 Agent on Linux systems for the root user:
Running the installer of JS7 Agent on Linux systems with root permissions/tmp/agent.[release]> ./setup.sh agent_install.xml
Installer of the JS7 Agent on Linux systems for the current user:
Running the installer of JS7 Agent on Linux systems without root permissions/tmp/agent.[release]> ./setup.sh -u agent_install.xml
Running the installer of JS7 Agent on Windows systems
Running the installer of JS7 Agent on Windows systemsC:\temp\agent.[release]> setup.cmd agent_install.xml
Rollback
To perform a rollback there are different steps to be followed for Windows and Linux.
Rollback JS7 Agent Instance on Windows
- To perform the rollback of a JS7 Agent instance run the uninstaller from the command line.
- The default location of the
uninstall.cm|sh
file is:C:\Program Files\sos-berlin.com\js7\agent\Uninstaller
on Windows.
- The default location of the
- Restore the folders from the backup by unzipping the .tar.gz/.zip archive for the installation directory and configuration directory to the respective location.
- Re-Install the windows service from the command line:
- Switch to the
./bin
directory for the Agent from the command line- The default location of the
./bin
directory is:C:\Program Files\sos-berlin.com\js7\agent\bin
on Windows.
- The default location of the
Run the below command. This command installs the Agent's Windows Service.
agent.cmd
install
-service [-http-port=<number>] [-ip-address=<
hostname
or ip address>]
- Switch to the
Rollback JS7 Agent Instance on Linux
- To perform JS7 Agent instance rollback on Linux remove the newly created Installation and the configuration directory of the JS7 Agent.
- Restore the folders from the backup by unzipping the .tar.gz archive for the installation directory and configuration directory to the respective location.
Installation Log
The installer creates a log file in the directory that is pointed to by the environment variable JS7_AGENT_LOGS
or in the logs
subdirectory of the Agent configuration directory.
- The default paths of the
logs
directory for the Agent are:/home/sos/sos-berlin.com/js7/agent_<port>
on Linux systems andC:\ProgramData\sos-berlin.com\js7\agent_<port>
on Windows.
- Installation log files are named according to the pattern,
Install_V[release]_[date&time]_....log
where release is the version release number and date and time refer to the installation.
- For further references about the logging refer to the complete overview of log files JS7 - Logging
Automated Start-up and Shutdown
For Unix systems, the start-up and shutdown configurations apply that are executed by root
, e.g. in /etc/init.d
or corresponding locations and by systemd
.
- Consider use of the
JS7_USER
environment variable to run an Agent that is started byroot
for a different user account. - For use with
systemd
find a sample service file from./bin/agent.service-example
file.
For Windows systems, the start-up of the Agent by installing it as a Windows Service is recommended.