30. 09. 2025
DevOps, Kubernetes, Uncategorized
18. 07. 2025
Tobias Goller
Automation, Cloud
Running SOS Berlin JobScheduler in Containers: A Step Toward Cloud-Native Scheduling
As enterprises move toward containerization and microservices, traditional job schedulers are often left behind. However, many organizations still rely on tried-and-true tools like SOS Berlin’s JobScheduler (now known as JADE under the JOC Cockpit umbrella).
The good news? With a bit of engineering effort, you can bring JobScheduler into the world of containers.
In this blog, we’ll explore the possibilities and considerations when running JobScheduler in Docker containers – and how this opens the doors for hybrid or cloud-native job scheduling solutions.
What Is SOS Berlin JobScheduler?
SOS Berlin JobScheduler is a workload automation tool that lets you to define, manage, and monitor job execution workflows. It supports:
- Complex job dependencies
- Cron-like scheduling
- Cross-platform execution
- A web UI (JOC Cockpit) for orchestration
Although robust and battle-tested, it wasn’t designed with containers or orchestration tools like Kubernetes in mind. That said, it is flexible enough to adapt.
Considerations for Container Deployment
- Persistent Volumes
JobScheduler uses configuration and log files that may need to persist. Mount host volumes or use Docker volumes for:
config/
logs/
data/
This ensures state isn’t lost on container restarts. - Networking
Expose necessary ports:
JobScheduler engine (typically 4444)
JOC Cockpit (if included, port 4446)
Also, consider service discovery if running in a cluster. - Environment Variables
Use ENV or Docker Compose to manage different configurations across environments (e.g., DB credentials, paths, log levels).
Monitoring and Logging
You can forward logs from the container to a centralized logging system like ELK or Loki. The JobScheduler logs (in /logs) contain detailed execution info and errors.
Conclusion: Is It Worth It?
Containerizing the SOS Berlin JobScheduler is very doable – and for many, it’s a strategic move. You gain the flexibility to:
- Run multiple schedulers in parallel
- Integrate with modern infrastructure
- Scale batch workloads more effectively
If you’re not ready to abandon your current job definitions, containers offer a bridge between legacy systems and the cloud-native future.
Tobias Goller
NetEye Solution Architect at Würth Phoenix
I started my professional career as a system administrator.
Over the years, my area of responsibility changed from administrative work to the architectural planning of systems.
During my activities at Würth Phoenix, the focus of my area of responsibility changed to the installation and consulting of the IT system management solution WÜRTHPHOENIX NetEye.
In the meantime, I take care of the implementation and planning of customer projects in the area of our unified monitoring solution.
Author
Latest posts by Tobias Goller
13. 10. 2025
Log-SIEM, Unified Monitoring
Elastic Defend: Experiences
16. 04. 2025
NetEye, Unified Monitoring
Application Performance Monitoring in NetEye with Elastic APM and OpenTelemetry
25. 10. 2024
Log-SIEM
Enhancing Cybersecurity with Elastic Defend: A Technical Consultant’s Perspective
28. 08. 2024
Unified Monitoring
ntopng Updates