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 2 Next »

Naming Conventions

  • There are probably as many naming conventions as there are users of JobScheduler.
  • We do not urge on our users specific conventions, however, some best practices might be interesting to consider.

Installation

  • Installation Path
    • Recommendation
      • We suggest to create a folder structure that includes the vendor name, product name and release
        • Examples: 
          • C:\Program Files\sos-berlin.com\jobscheduler\scheduler110
          • C:\Program Files\sos-berlin.com\jobscheduler_agent\jobscheduler_agent.1.10
      • We suggest to separate the programm installation path and the path for configuration files
        • The installation path 
          • could/should be write protected for normal users. It contains files that are exclusively modified during a software update that is typically perfomred by an administrator. 
          • is pointed to by the environment variable SCHEDULER_HOME.
        • The configuration path 
          • could be writeable for a couple of users who are entitled to manage jobs by use of their personal account.
          • is pointed to by the environment variable SCHEDULER_DATA
        • Examples
          • Windows
            • Installation Path: C:\Program Files\sos-berlin.com\jobscheduler\scheduler110
            • Configuration Path: C:\ProgramData\sos-berlin.com\jobscheduler\scheduler110
          • Unix
            • Installation Path: /opt/sos-berlin.com/jobscheduler/scheduler110
            • Configuration Path: /home/jobscheduler_user/sos-berlin.com/jobscheduler/scheduler110
  • Scheduler ID: this configuration item identifies a JobScheduler environment
    • This ID is used
    • This ID is stored in the JobScheduler database. Therefore, if you run a number of JobScheduler instances that should share the same database connection (and schema) then you have to use different IDs
    • Recommendation: 
      • Use prefixes such as dev, test, uat, prod, to indicate the environment that the respective JobScheduler instance is used for. This would help to identify misconfigured database connection.
  • Port
    • There is no reserved port for JobScheduler. We chose 4444 as a default for the JobScheduler Master and 4445 for the Agent as these ports tend to be rarely used, see Service Name and Transport Protocol Port Number Registry
    • Recommendation
      • Use a four digit port if you access JobScheduler by the built-in web server.
      • Use a five digit port if you access JobScheduler via Jetty.
      • Do not use the same port numbers for Master and Agent. You might not be able to tell from the hostname if the JobScheduler instance works as a Master or Agent, therefore it might be helpful to use the port number to distinguis the components.
      • Use an arbitrary port number for the Master and use the same port number for all Agents. In most cases you will run one Master but you might operate any number of Agents. The automated roll-out of Agents is simplified if they use the same port number. 
  • Account
    • Do not run the JobScheduler with a root account. This would introduce security risks as job scripts could switch to any user accounts and perform jobs for that user.
    • Recommendation
      • Use a system account for the JobScheduler Windows service.
      • Use a dedicated user account for the JobScheduler daemon with Unix.
      • Why not use the same account for running the JobScheduler and for access to the JobScheduler database? For systems with integrated security, e.g. Oracle, SQL Server, this allows to use the same account and to centrally change passwords.

Operation

Jobs

  • It is h

Job Chains

Orders

 

 

  • No labels