Product Knowledge Base

Space shortcuts

Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 63 Next »

Installing the JobScheduler Universal Agent

  • Prerequisites
    • A Java Runtime Environment starting from version 1.8 is required.
    • Choose the JobScheduler Universal Agent for your platform from the Downloads section.
  • Installation
    • Unzip the downloaded file to an arbitrary directory.
    • Directory Structure
      • bin
        • jobscheduler_agent.cmd
          • The start script for Windows platforms.
        • jobscheduler_agent.sh
          • The start script for Unix platforms.
      • lib
        • The directory for Java libraries.
        • Consider the settings in logback.xml should you want to adjust the log output format.
      • logs
      • service (for Windows)
    • On Windows you have to change the directory permissions for the .\logs and .\service directories if you have extracted the JobScheduler Agent under e.g. C:\Program Files.
      • This step is not necessary if you have extracted the JobScheduler Agent under e.g. C:\ProgamData.

      • Start a command prompt with elevated administrator permissions and type e.g. ...

        set full acces for "Users" on .\service and .\logs directory
        cd "path\to\JobScheduler 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 

Patching JobScheduler Master

To control JobScheduler Universal Agent, a patched JobScheduler Master is required:

  • install JobScheduler 1.9.3
  • download patch archive for the platform of the JobScheduler Master server
  • stop JobScheduler Master
  • extract the patch into your SCHEDULER_HOME directory
  • remove com.sos-berlin.jobscheduler.engine-1.9.3.jar from SCHEDULER_HOME/lib/sos

  • remove akka-actor_2.11-2.3.9.jar from SCHEDULER_HOME/lib/3rd-party

  • remove akka-slf4j_2.11-2.3.9.jar from SCHEDULER_HOME/lib/3rd-party

  • remove spray-json_2.11-1.3.1.jar from SCHEDULER_HOME/lib/3rd-party

Running the JobScheduler Universal Agent

  • SOS does not recommend to run the JobScheduler Agent as root (for Unix) or as Administrator (for Windows).
  • Instead the user account should be used that jobs are executed for. Should jobs be executed for a number of user accounts then consider the chapter Running multiple instances of JobScheduler Universal Agent.

Usage

Running the start script without parameters shows the usage clause:

usage on Unix
Usage: jobscheduler_agent.sh command [options]
  command:
    start           [options]
    start_docker    [options]
    stop            [options]
    abort           [options]
    restart         [options]
    status          [options]
    start           [options]
 options:
    -http-port=<number> | default: 4445
    -timeout=<number> | in seconds; only for stop and restart
usage on Windows
Usage: jobscheduler_agent.cmd command [options]
  command:
    start           [options]
    stop            [options]
    abort           [options]
    restart         [options]
    status          [options]
    debug           [options]
    kill            [options]
    install-service [options]
    remove-service  [options]
    start-service   [options]
 options:
    -http-port=<number> | default: 4445
    -timeout=<number> | in seconds; only for stop and restart

Command Line Options

 

  • -http-port=<number>
    •  is the HTTP port that the Agent is listening to in order to receive requests from a JobScheduler Master:
      • jobscheduler_agent.cmd|sh command -http-port=####
      • where #### is the numeric port.
    • Without this option being used the port defaults to 4445.
    • Should you want to specify a port then the following precedence applies:
      • First precedence: command line option
      • Second precedence: environment variable SCHEDULER_HTTP_PORT (see below)
      • Third precedence: use of default value
  • -timeout=<number>
    • This option can be used to specify the number of seconds that the Agent will wait for tasks to stop. 
    • This option can be applied for stop and restart commands.
    • The Agent sends a SIGTERM signal to the taksk and having reached the timeout a SIGKILL signal will be sent to stop any tasks immediately.

Start the Agent

jobscheduler_agent.cmd|sh start [options]

Stop the Agent

jobscheduler_agent.cmd|sh stop [options]

This command will safely terminate the Agent (recommended).

  • The Agent waits for running processes to be completed.
  • Any child processes will be killed by the Agent.

 

jobscheduler_agent.cmd|sh abort [options]

The Agent process is terminated immediately.

  • Any running tasks and child processes are killed immediately with a SIGKILL signal.
  • Should task have used resources such as database connections then they will not be properly closed.

 

jobscheduler_agent.cmd|sh kill [options]

The Agent process is killed.

  • This corresponds to sending SIGKILL with a kill command.
  • Should jobs be running that started detached child processes then it is not guaranteed that child processes will be killed.

Restart the Agent

jobscheduler_agent.cmd|sh restart [options]

Query the Agent Status

jobscheduler_agent.cmd|sh status [options]

Should the Agent be up and running then this command will result in some output such as:

isTerminating: false
system:
  hostname: agenthost
  mxBeans:
    operatingSystem:
      processCpuLoad: 2.5630713121704744E-5
      availableProcessors: 4
      freePhysicalMemorySize: 311668736
      systemCpuLoad: 0.046373903924522855
      committedVirtualMemorySize: 4475301888
      totalPhysicalMemorySize: 3155517440
java:
  systemProperties:
    java.vendor: Oracle Corporation
    os.arch: amd64
    os.version: 2.6.32-220.17.1.el6.x86_64
    os.name: Linux
    java.version: 1.8.0_31
version: 1.10.0-SNAPSHOT (6956c56a535d15fcf659f293c42d22dcf92e9e12 2015-07-15 21:23:24+02:00)
startedAt: '2015-07-17T08:38:30.516Z'
totalProcessCount: 21
currentProcessCount: 0

 

Should the Agent not be running then some output is provided such as:

ERROR: spray.can.Http$ConnectionAttemptFailedException: Connection attempt to localhost:4445 failed
...JobScheduler Agent(4445) not started!

Windows Service Interface: Usage 

The JobScheduler Universal Agent is operable as a Windows Service starting from release TP3 of the Agent. The start script of the JobScheduler Universal Agent allows to install/uninstall the Windows Service:

Install the Windows Service

jobscheduler_agent.cmd install-service [-http-port=<number>]

This command installs the Windows Service. After the installation you find the Windows Service with the name SOS JobScheduler Agent -port=<number> in the Services Manager Console. The Windows service uses the "local system" account.

During the service installation it tries to copy the executable for the Windows service to the .\service directory. This operation could fail with the error "Access denied" if you have extracted the JobScheduler Universal Agent under e.g. C:\Program Files\. In this case you can change the permissions of the .\service directory or open the command prompt with elevated administrator permissions and execute the above command once more.

Start the Windows Service

jobscheduler_agent.cmd start-service [-http-port=<number>]

This command starts the Windows Service with the name SOS JobScheduler Agent -port=<number>.

The stop command contains more than a simple stop-service command: the stop command checks whether the Agent was started through the CLI or as a Windows Service and stops the Agent accordingly. Therefore there is no stop-service command.

Remove the Windows Service

jobscheduler_agent.cmd remove-service [-http-port=<number>]

This command uninstalls the Windows Service. After executing this command you will not find the Windows Service with the name SOS JobScheduler Agent -port=<number> in the Services Manager Console any longer.

During removal of the service it tries to remove the executable of the Windows Service from the .\service directory. This operation could fail with the error "Access denied" if you have extracted the JobScheduler Agent under e.g. C:\Program Files\. In this case you can change the permissions of the .\service directory or open the command prompt with elevated administrator permissions and execute the above command once more.

Logging

  • Log File
    • On startup the Agent creates a log file in the directory that is pointed to by the environment variable SCHEDULER_LOG_DIR or in the logs subdirectory of the Agent installation directory.
    • Log file names are created from a prefix and the port used by the Agent like this:
      • jobscheduler_agent_4445.log
    • Log files are rotated for each day and are kept for one week (see ./lib/log4j.xml).
    • Rotated log files get the name of the form jobscheduler_agent_4445.log.<yyyy-MM-dd>
  • PID File
    • On startup the Agent creates a PID file in the directory that is pointed to by the environment variable SCHEDULER_PID_FILE_DIR or in the log directory. The PID file contains the Process ID of the system process that the Agent is running in.
    • The PID file is used in order to prevent the Agent to be started twice with the same settings and it can be used for shutdown scripts that require the PID to terminate the process.
    • PID file names are created from a prefix and from the port used by the Agent like this:
      • jobscheduler_agent_4445.pid

Environment Variables

The following environment variables can be used:

  • JAVA_HOME
    • points to the location of the Java Runtime Environment (JRE).
    • Without setting this environment variable Java will be used from the location specified by the system path.
    • Please consider that JAVA_HOME does not point to the location of a JDK but to a JRE directory where the bin/java executable resides.
  • SCHEDULER_HOME
    • points to the directory where the JobScheduler Agent has been installed.
    • Without setting this environment variable the default value is the parent directory of the start script.
    • Should you want to start the Agent from a directory different to the Agent installation directory, e.g. by copying the start script to some other location, then this environment variable has to be set in order to locate the JobScheduler Agent installation directory.
  • SCHEDULER_HTTP_PORT
    • sets the port that the JobScheduler Agent is listening to.
    • Without setting this environment variable the port defaults to 4445.
  • SCHEDULER_USER
    • sets the user account that the JobScheduler Agent is operated for. This includes running jobs with the permissions of the specified user.
    • This setting is available for Unix systems only. For Windows systems the user account that runs the start script is used.
    • Without setting this environment variable the user acount that runs the start script is used.
    • This setting can be used when running the Agent start script in system start-up and shutdown configurations that are executed by root, e.g. in /etc/init.d or corresponding locations.
  • SCHEDULER_LOG_DIR
    • sets the directory where the JobScheduler Agent log file is created.
    • This setting defaults to the directory logs in the Agent installation directory.
    • For Windows systems for which the Agent is installed in the program directory that is pointed to by the %ProgramFiles% environment variable it is recommended not to use the default setting. Instead specify a different path via the SCHEDULER_LOG_DIR environment variable, e.g. some location in the data directory that is pointed to by the %ProgramData% environment variable.
  • SCHEDULER_PID_FILE_DIR
    • sets the directory where the JobScheduler Agent pid file is created.
    • This setting defaults to the directory that is specified with the SCHEDULER_LOG_DIR environment variable or the log directory default value.

Usage Examples

Running the JobScheduler Agent on Windows

For Windows® operating systems the location of the Java Runtime Environment and of the log directory can be specified like this:

set JAVA_HOME=%ProgramFiles%\Java\jre8
set SCHEDULER_LOG_DIR=%ProgramData%\sos-berlin.com\agent\jobscheduler_agent_1.10-TP1\logs
 
"%ProgramFiles%\sos-berlin.com\agent\jobscheduler_agent_1.10-TP1\bin\jobscheduler_agent.cmd" start

Running the JobScheduler Agent on Mac OS X

For Mac® OS X the location of the Java Runtime Environment can be specified like this:

JAVA_HOME=/Library/Internet\ Plug-Ins/JavaAppletPlugin.plugin/Contents/Home
export JAVA_HOME
/Users/ap/Documents/jobscheduler_agent/bin/jobscheduler_agent.sh start

Automated Start-up and Shutdown of JobScheduler Universal Agent

  • For Unix systems the start-up and shutdown configurations apply that are executed by root, e.g. in /etc/init.d or corresponding locations.
    • Consider use of the SCHEDULER_USER environment variable to run an Agent that is started by root for a different user account.
  • For Windows systems the start-up of the Agent by installing it as a Windows Service is recommended.

Running multiple instances of JobScheduler Universal Agent

  • Multiple instances of the JobScheduler Agent on the same computer can be operated, e.g. for different user accounts that jobs should be executed for.
  • Any number of Agent instances can be started from the same installation, however, different ports have to be used that the Agent is listening to for requests of a JobScheduler Master.
  • Running the Agent for different user accounts and ports 
    • Use the environment variable SCHEDULER_USER to operate the Agent for a user account that is different from the one that starts the Agent.
    • Use the environment variable SCHEDULER_HTTP_PORT or the option -http-port=#### to start the Agent for a port that is different from the default setting.
    • Make sure that the directories SCHEDULER_LOG_DIR and SCHEDULER_PID_FILE_DIR are readable and writable for the different user accounts

  • Add the startup options as given in the following examples to your individual startup script.

Examples for Windows

Set port by commands and options
set JAVA_HOME=%ProgramFiles%\Java\jre8
 
"%ProgramFiles%\sos-berlin.com\agent\jobscheduler_agent_1.10-TP3\bin\jobscheduler_agent.cmd" start -http-port=4446
Set log directory and port by environment variables
set JAVA_HOME=%ProgramFiles%\Java\jre8
set SCHEDULER_LOG_DIR=%ProgramData%\sos-berlin.com\agent\jobscheduler_agent_1.10-TP3\logs
set SCHEDULER_HTTP_PORT=4446
 
"%ProgramFiles%\sos-berlin.com\agent\jobscheduler_agent_1.10-TP3\bin\jobscheduler_agent.cmd" start

Examples for Unix

Switch user account and port by commands and options
su - js
jobscheduler_agent.sh start -http-port=4446
Switch user account and port by environment variables
SCHEDULER_USER=js
SCHEDULER_HTTP_PORT=4446
export SCHEDULER_USER SCHEDULER_HTTP_PORT

jobscheduler_agent.sh start

Testing the JobScheduler Universal Agent Operability

A simple way to test if the installed and running JobScheduler Agent works as expected is to carry out a test using Process Classes. The Process Class and the corresponding job will be defined in your JobScheduler Master, which will connect to the JobScheduler Agent. SOS recommends to do the test locally to exclude connection problems, e.g. firewall settings, since the goal of the test is to see whether the JobScheduler Agent is working properly.

Process Class and Standalone Job

First create a Process Class, for example the following (find attached example: agent1.process_class.xml):

Example Process Class
<?xml version="1.0" encoding="ISO-8859-1"?>

<process_class  max_processes="10" remote_scheduler="http://localhost:4445"/>

Important! When defining the remote JobScheduler host, it is required to add http://, e.g. like above http://localhost.

 

Second, you should define a Standalone Job and associate the Process Class defined above to the job (find an example attached: standalone_hello.job.xml):

Example Standalone Job
<?xml version="1.0" encoding="ISO-8859-1"?>

<job  process_class="agent1">
    <script  language="shell">
        <![CDATA[
echo "hello world"
        ]]>
    </script>
    <run_time />
</job>

Finally:

  • store both XML files (agent1.process_class.xml and  standalone_hello.job.xml) to the JobScheduler live folder in ./config/live. 
  • start the Job in JOC (start task immediately). 

Logs

The easiest way to check if the test was successful is to have a look at the job log in JOC and to see if the job completed successfully. Otherwise an error will be reported in JOC.

For a double check you can verify the log from the JobScheduler Universal Agent. If the JobScheduler Universal Agent is running and the steps above were correctly completed then you should see something like this in the JobScheduler Universal Agent log:

JobScheduler Universal Agent Log
2015-04-28 16:11:24.462 +0200 [DEBUG] akka.io.TcpListener - New connection accepted
......
......
2015-04-28 16:13:39.231 +0200 [DEBUG] spray.can.server.HttpServerConnection - TcpConnection terminated, stopping

Remote file watching

To configure remote file watching, JobScheduler Agent TP3 provides the process_class attribute for the job_chain element:

<job_chain process_class="agent">
    <file_order_source directory="/srv/files/in"/>
    <job_chain_node state="start" job="job1"/>
</job_chain>

 

Running the remove file order example

  • Download agent_file_order.zip
  • Extract the archive into the live folder of your JobScheduler Master
  • edit files:
    • agent.process_class.xml: configure the host and port of your agent
    • job_chain1.job_chain.xml
      • set the input directory
    • job1.job.xml
      • linux users: make adjustments to the shell script
    • job2.job.xml
      • set the output directory
      • linux users: make adjustments to the shell script

Failed Tests

In case that you receive an error in JOC when running the job, then let us know by use of the SourceForge ticket system:

  1. Create a Ticket in SourceForge
  2. Attach the following logs: scheduler.log (from JobScheduler Master) and jobscheduler_agent_<port>.log (from JobScheduler Universal Agent)

 

 

  • No labels