Skip to end of metadata
Go to start of metadata


The cheat sheet provides a concise overview of JS7 features in different areas.

Cheat Sheet

Download: js7_cheat_sheet.xlsx

Functional Features

JS7 Functional Features
FF-1Monitor and Control
FF-1-1 Dashboard View• Component status information, Cluster status information • Near real-time information about current workflow execution status • Provides summary information about past workflow and job executions • Offers user interventions to stop and to restart components and to switch-over cluster components • Offers bulk operations to start, to stop, to suspend, to resume workflow executionJS7 - DashboardJS7 - Orders
FF-1-2 Monitor View• Monitors availability of JS7 Controllers and Agents • Offers availability reports for past periods • Near real-time information on job execution warnings and errors • Overview of job execution warnings and errorsJS7 - Monitor
FF-1-3 Daily Plan View• Visualizes the planning of workflow executions for future periods • Near real-time information on planned, submitted, finished status of workflow executions • Supports user interventions to modify the start times and parametrization of workflows for specific days • Offers to plan and to control daily workflow executionJS7 - Daily Plan
FF-1-4 Workflows View• Visualizes workflow execution in tabular and in graphical views • Visualizes dependencies between jobs and workflows • Offers control of workflow execution including bulk operationsJS7 - Workflows
FF-1-5 Resources View• Monitors Agent job executions • Monitors Resource Locks • Monitors ConditionsJS7 - Resource LocksJS7 - Notice Boards
FF-1-6 History View• History information about job and workflow execution • Offers information about past file transfers • Offers information about past deployments of scheduling objectsJS7 - HistoryJS7 - Order HistoryJS7 - Task History
FF-2Inventory Management
FF-2-1 Inventory View• Management of workflows, jobs, calendars, schedules etc. • Graphical workflow editor • JSON persistence format for scheduling objects such as workflows, jobs • Inventory persisted with a databaseJS7 - Inventory
FF-2-2 Deployment• Deploys scheduling objects to Controllers and Agents • Offers bulk operations for mass deploymentJS7 - Deployment
FF-2-3 Export/Import• Export of scheduling objects to .tar.gz/.zip archives • Import of .tar.gz/.zip archivesJS7 - Inventory Export and Import
FF-3Job Dependencies
FF-3-1 Parallel Execution• Jobs within a workflow can be executed in parallel • Forking of job execution in parallel branches can be nested • Dynamic branching based on run-time parameters availableJS7 - Fork / Join InstructionJS7 - ForkList / Join Instruction
FF-3-2 Sequential Execution• Jobs are executed if their predecessor job completes successfullyJS7 - Job Instruction
FF-3-3 Conditional Execution• Conditional execution of jobs in branches based on execution results of previous jobs, based on calculated results etc. • If-Then-Else branches with nesting and expression languageJS7 - If Instruction
FF-3-4 Conditions• Jobs wait for conditions that are resolved by jobs in other workflows • Users can control use of conditions with the JOC Cockpit user interface • Offers user intervention to add and to drop conditionsJS7 - Notice BoardsJS7 - ExpectNotice InstructionJS7 - PostNotice Instruction
FF-3-5 Chained Workflows• Workflows trigger execution of subsequent workflows • Triggers for subsequent workflows are available from any position in the current workflowJS7 - AddOrder Instruction
FF-3-6 Resource Locks• Limits parallelism of jobs and job groups • Exclusive resource locks • Quantitative resource locksJS7 - Lock Instruction
FF-3-7 Workflow Patterns• Support for a larger number of workflow patterns • Synchronization, Exclusive Choice, Parallel Split etc.JS7 - Workflow Patterns
FF-4Job Execution
FF-4-1 Parallelism• The same workflow can be executed in parallel • Any number of workflows can be executed in parallel • Unlimited parallelism, limits can be configuredJS7 - Job Instruction
FF-4-2 Run Job as different User• Jobs for execution with Unix Agents use sudo to switch user context • Job for execution with Windows Agents securely switch the user context by access to the Windows Credential ManagerJS7 - Running jobs as a different user
FF-4-3 Running Log• Running jobs log output to the stdout/stederr channels • Job log output is reported in near-real time
FF-5Timed Execution
FF-5-1 Calendars• Rule based calendars, e.g. first of month, last of month etc. • Consideration of non-working daysJS7 - Calendars
FF-5-2 Schedules• Schedules specify start times for workflows and jobs • Schedules parameterize execution of workflowsJS7 - Schedules
FF-5-3 Daily Plan• Workflows are executed automatically at the given date and time • Calculation of future start times is performed automatically • Users can update the Daily PlanJS7 - Daily Plan Service
FF-5-4 Cyclic Execution• Jobs are executed in cycles, for example every 30s within a given period • Periodical cycles per hour, for example 15m, 20m, 33m etc. • Continuous cycles specify intervals between job executions • Ticking cycles specify the periods of job executionJS7 - Cycle Instruction
FF-5-5 Admission Times• Jobs are executed for specific periods in a day and wait until they reach the admission time • Jobs can be skipped in case of non-matching days with admission times • Admission times specific for day of weekJS7 - Admission Times for Jobs
FF-5-6 Time Zone Support• JOC Cockpit, Controller and Agent operated in different time zones • Jobs scheduled for execution in different time zones • Schedules specified for different time zones • JOC Cockpit user interface converts dates/times to the user's time zoneJS7 - Time Zone Support
FF-6Triggered Execution
FF-6-1 File Watching• Agents watch directories for incoming files • Workflows are triggered to start on arrival of incoming filesJS7 - File Watching
FF-6-2 External Events• External scripts and programs use the JS7 REST Web Service API to trigger execution of workflows and jobs • External scripts use the JS7 PowerShell ModuleJS7 - REST Web Service APIJS7 - PowerShelll Module
FF-7File Transfer
FF-7-1 File Transfer• Built-in file transfer capabilities with Agents • Configuration for complex file transfers • Performs pre- and post-processing per file and per transfer • Renames files at source or target of a transfer • Offers transactional transfer for a group of files • Supports use of jump host transfers, e.g. for use with a DMZ • Supports use of proxies • Deployment of file transfer configurations to AgentsJS7 - File Transfer ConfigurationJS7 - File Transfer Deployment
FF-7-2 File Transfer View• Monitors ongoing file transfers • Offers history of file transfers including file names and systems involved • Offers seach capabilitiesJS7 - File Transfer
FF-7-3 Authentication Methods• User/password authentication • Public/private key authentication • Offers use of a credential store
FF-7-4 Protocol Support• SFTP, FTP, FTPS • WebDAV, WebDAVS • HTTP, HTTPS • CIFSYADE - Implementation Architecture
FF-8Job Templates
FF-8-1 Database Jobs• Built-in job templates to execute SQL statements with databases • JDBC based support for any DBMS • Supports Oracle® PL/SQL • Supports Oracle® SQL*Plus • Parametrization of SQL statements • Export of resultsJS7 - JITL Database Jobs
FF-8-2 File Operation Jobs• Built-in job templates to manage files • Checks if files exist or not exist • Copies files • Moves and removes filesJS7 - JITL File Operation Jobs
FF-8-3 Mail Jobs• Built-in job templates for mail processing • Send mail • Read mail inboxJS7 - JITL Mail Jobs
FF-9Agentless Schedudling
FF-9-1 SSH Job Execution• Jobs executed by SSH on remote machines • Built-in SSH client for use with any platforms • Supports standard-compliant SSH serversJS7 - Agentless Scheduling
FF-10Error Handling
FF-10-1 Exit Codes• Exit codes considered to determine successful/failed execution • Supports ranges of exit codesJS7 - Job Instruction
FF-10-2 Error Messages from stderr• Output to the stderr channel indicates failed execution
FF-10-3 Terminate Job on Timeout• Jobs are terminated when reaching a configurable timeout
FF-10-4 Terminate Job on User Intervention• Users can cancel and can kill jobs • Supports Unix SIGTERM and SIGKILL signals
FF-10-5 Terminate Child Processes• Child processes are killed by AgentsJS7 - FAQ
FF-10-6 Warn on Long Job Execution• Notify by warnings if jobs run longer than expected
FF-10-7 Warn on Short Job Execution• Notify by warnings if jobs run shorter than expected
FF-10-8 Retry Failed Jobs• Jobs and groups of jobs are restarted after failure • Configurable retries and restart intervalsJS7 - Retry Instruction
FF-10-9 Catch Errors• Catch errors of failed jobs and execute alternative jobs • Try/Catch logic to handle failed jobsJS7 - Try / Catch Instruction
FF-11-1 Notification View• Visualizes notifications in the JOC Cockpit user interfaceJS7 - Notification
FF-11-2 Notification by Mail• Sends mail in case of warnings and errors, optionally in case of success • Sends mail in case of jobs running longer or shorter than expected • Supports different notifications to be sent per workflow or job group • Supports use of different mail recipients per job • Supports customized mail subject and bodyJS7 - How To
FF-11-3 Notification to System Monitor• Supports to notify System Monitors about failed workflows and jobsJS7 - Monitoring
FF-12Audit Trail
FF-12-1 Audit Log for Authentication, Changes to Objects and Deployments• Audit Log holds information about changes to objects such as to modify workflows, to manually start and to stop workflows etc. • Audit Log includes the full information about any operation and about the objects in use • Information about login/logout of users is available from a separae log file for administrative accessJS7 - Audit Log
FF-13-1 Reporting Views• Any views that visualize data such as the History View, Daily Plan View, File Transfer View etc. provide capabilities for export to Excel® files • Filter functions allow to limit data by date range, status etc. • Export files are immediately available for download
FF-13-2 Report Automation• Reports are automatically created by template jobs that access the JS7 REST Web Service API preferably from the JS7 PowerShell Module • Report output by default is stored to Excel® files • Reports can be sent mailJS7 - How To - ReportingJS7 - REST Web Service APIJS7 - PowerShell Module

Non-functional Features

JS7 Non-functional Features
NF-1-1 Operations On Premises• JOC Cockpit, Controller available for Linux and Windows platforms • Agents available for any platforms operating a Java Virtual Machine starting from 1.8, for example Linux, Windows, AIX, Solaris, HP-UX, Mac OS, …JS7 - Platforms - On PremisesJS7 - Platforms
NF-1-2 Container Operations• JOC Cockpit, Controller, Agents support use with containers for Docker®, Kubernetes®, OpenShift® • Official images provided via Docker HubJS7 - Docker ContainersDocker Hub
NF-1-3 Cloud Operations• JOC Cockpit, Controller, Agents available for Amazon AWS® (EC2), Azure®, Google Cloud® • VM instances tailored on demand to customer needsJS7 - Cloud
NF-2SaaS / PaaS
NF-2-1 Cloud Hosting Service• JOC Cockpit, Controller components managed by SOS • Agents managed by customers in their respective environmentsJS7 - Cloud Hosting Service
NF-2-2 Cloud Managed Service• JOC Cockpit, Controller components managed by SOS • Agents managed by customers in their respective environments • SOS manages workflows and jobs, performs monitoring and interventionJS7 - Cloud Managed Service
NF-3-1 DBMS• MariaDB® • MySQL® • Oracle® • PostgreSQL® • SQL Server®JS7 - Database
NF-3-2 Cloud DBMS Service• Amazon RDS® • Azure® Databases
NF-3-3 DBMS Interfacing• JDBC • No DBMS client required
NF-4-1 Product Knowledge Base• Technical documentation publicly available in English language • Technical aspects of installation, configuration and operation of the product explained with step-by-step instructionsJS7
NF-4-2 Installation• Installation procedures documented for any platforms and modes of installation • Installation modes include headless installation and use of a graphical installerJS7 - InstallationJS7 - Installation On PremisesJS7 - Installation for Docker Containers
NF-4-3 Configuration• Configuration includes network access by HTTP, HTTPS • Support for use of X.509 certificates including mutual authentication • Password-free configuration for operation of JS7 componentsJS7 - ConfigurationJS7 - Configuration ItemsJS7 - Configuration for Docker Containers

Interface Features

JS7 Interface Features
IF-1User Interface
IF-1-1 Browser User Interface• Browser based user interface • Supported browser products: Firefox, Chrome, Edge, Safari, VivaldiJS7 - Browser User Interface
IF-1-2 User Interface Language Support• English • French • German • JapaneseJS7 - Language Support
IF-2Application Programming Interface (API)
IF-2-1 REST Web Service API• Any operations can be effected by use of the REST API • Operations include inventory management, monitoring and control of workflows and jobs, for example to start workflows, to cancel jobs etc.JS7 - REST Web Service APIJS7 - How To - API
IF-3Command Line Interface
IF-3-1 Shell• JOC Cockpit, Controller, Agent components can be started, stopped, restarted and controlled from the command lineJS7- Command Line Operation
IF-3-2 PowerShell Module• For Linux, Windows, Mac OS platforms a PowerShell Module offers command line operation for inventory management, monitoring and control • The PowerShell Module implements a wrapper for the JS7 REST Web Service API and supports the majority of operations available by the APIJS7 - PowerShell ModulePowerShell CLI 2.0 - Cmdlets
IF-4Git Interface
IF-4-1 Git Repository Interface• Inventory objects such as workflows can be managed with Git repositories • Inventory objects that are local to an environment such as schedules can be mapped to individual repositories • Full support for automated CI/CD deployment chainsJS7 - Git Repository InterfaceJS7 - Inventory Git IntegrationJS7 - Rollout of Scheduling Objects

Operational Features

JS7 Operational Features
OF-1-1 Object Definitions• > 1 000 000 jobs • > 200 000 workflows • > 500 000 ordersJS7 - Performance
OF-1-2 Job Executions• > 4 000 000 job executions/day and per Controller • > 500 000 workflow executions/day and per Controller
OF-1-3 Task Parallelism• > 15 000 parallel tasks per Agent • > 60 000 parallel tasks across Agents
OF-2High Availability
OF-2-1 JOC Cockpit Cluster• Active/Passive cluster with automated fail-overJS7 - JOC Cockpit Cluster
OF-2-2 Controller Cluster• Active/Passive cluster with automated fail-overJS7 - Controller Cluster
OF-2-3 Agent Cluster• Active/Active cluster with automated fail-over * Fixed-priority scheduling * Round-robin schedulingJS7 - Agent Cluster
OF-3-1 Connections• Connections between components are automatically re-established after outagesJS7 - Resilience
OF-3-2 Availability Impact• Components continue to work if a partnering component becoms inavailable, for example Controllers and Agents work independently from the JOC CockpitJS7 - Impact of a Controller outage
OF-3-3 Workflow Execution• Workflows for execution with a single Agent are continued in case of outage of the Controller or of JOC Cockpit • Workflows for cross-Agent execution require Controller availability • Timed execution of workflows is considered by Agents in case of outage of Controller or JOC CockpitJS7 - Impact of an Agent outage
OF-4-1 Job Logs• Job log output is forwarded from Agents and Controllers to JOC Cockpit and is stored to the database • Job logs are available from the JOC Cockpit user interfaceJS7 - HistoryJS7 - History Service
OF-4-2 Job Log Rotation• Job logs are retained in the database for a configurable period • Automated purge of outdated logsJS7 - Cleanup Service
OF-4-3 System Logs• System logs are available per component • Configurable log levels for detailed log analysisJS7 - Log Files and Locations
OF-4-4 System Log Rotation• Configurable log rotation by date and sizeJS7 - Log Rotation
OF-5-1 Self-monitoring• Self monitoring about availability of Controllers and Agents • Self-monitoring of workflow and job executionsJS7 - Monitor Service
OF-5-2 System Monitor Integration• Integration with 3rd-party System Monitors such as Nagios®, Opsview®, Zabbix® etc. • Support for Active Checks by System Monitors * Supports Passive Checks to System MonitorsJS7 - Monitoring
OF-5-3 Java Message Queue• Integration available with Apache MQ

Security Features

JS7 Security Features
SF-1Identity Management
SF-1-1 JS7 Managed Identities• Identities managed with the JOC Cockpit Identity Service • User accounts are assigned roles that are assigned permissions • Users can be authenticated from a number of optional or required Identity ServicesJS7 - Identity and Access ManagementJS7 - JOC Identity ServiceJS7 - Security Architecture
SF-1-2 LDAP Managed Identities• Supports authentication with LDAP Directory Services, such as Active Directory® • Supports authorization with LDAP Directory Services by membership in Security GroupsJS7 - LDAP Identity Service
SF-1-3 HashiCorp® Vault Managed Identities• Supports authentication with Vault • Supports authorization from Vault policies • Provides authorization from local role assignmentJS7 - HashiCorp® Vault Identity Service
SF-1-4 Certificate Based Authentication• X.509 certificates can act as a proof of identity • Optionally certificates can be used for single-factor authenticationJS7 - Certificate based Authentication
SF-1-5 Two-factor Authentication• In addition to user/password authentication use of X.509 certificates for two-factor authentication can be enforced with any Identity Service
SF-1-6 Password Change Policy• Passsword change can be enforced
SF-1-7 Password Length Policy• Minimum password length is considered
SF-1-8 Password Hashing• Passwords stored as strong hashes
SF-2Access Management
SF-2-1 Role based Access Management• Any operations effected by the JS7 REST Web Service API are assigned permissions such as to view and to manage the inventory, to deploy objects, to start and to stop workflows etc. • Permissions can be freely grouped to roles • Users are assigned rolesJS7 - REST Web Service APIJS7 - Management of User Accounts, Roles and Permissions
SF-2-2 Roles limit Access to Controllers• Permissions and roles can be managed on a per Controller basis
IF-3Secure Connections
SF-3-1 TLS/SSL Certificates for HTTPS Connections• JOC Cockpit, Controller and Agents can be configured to use TLS/SSL certificates • Certificates can be used for mutual authentication between componentsJS7- Secure Connections
SF-3-2 Certificate Authority• Certificates from external Certificate Authorities are supported • JS7 provides its own Certificate Authority that can be used to create and to deploy certificates to Controllers and AgentsJS7 - Certificate Authority
SF-3-3 Database Connections without Use of Credentials• Access to the database without use of user/password is supported within the scope of the DBMS features available with JDBC • Connections to the Oracle® DBMS can use Oracle® Wallet • Connections to the SQL Server® DBMS can use Integrated SecurityJS7 - How To - OracleJS7 - How To - SQL Server
SF-3-4 Credential Store for Database Connections• Credentials for databae connections of JS7 and of user jobs can be managed from a Credential Store such as KeePass® • Hibernate configuration files for database access include references to the Credential StoreJS7 - Credential Store
SF-4Secure Deployment
SF-4-1 Digital Signatures for Deployment• Inventory objects such as workflows are digitally signed for deployment • Controllers and Agents verify digital signatures of deployed objectsJS7 - Secure Deployment
SF-4-2 Security Levels for Deployment• Security Levels act in addition to use of permissions and roles, they are determined during installation of JOC Cockpit • Security Level LOW allows any user accounts with a deployment permission to digitally sign objects such as workflows • Security Level MEDIUM enforces use of individual user certificates to digitally sign objects for deployment • Security Level HIGH entorces external signing of objects for deployment on a secure deviceJS7 - Security Architecture
SF-5Secure Job Operation
SF-5-1 Job Credentials• Credentials that are used by jobs can be securely managed with a Credential Store • At run-time jobs can read credentials from the storeJS7 - Credential Store
SF-5-1 File Transfer Credentials• File Transfer configurations can include user/password and/or private keys for example with public key authentication • Such credentials can be managed with a Credential Store and are used at run-time by the JS7 File Transfer jobs

  • No labels
Write a comment…