JEM the BEE (Job Entry Manager, the Batch Execution environment) is cloud-aware application server to manage batch execution
JEM the BEE node itself it’s a Java™ application and you can run it on different platforms, fully horizontal and vertical scalable
JEM the BEE can handle jobs written for Apache ANT, Spring Batch, BASH, Windows command, Windows Powershell and JBoss JBPM. For business logic, you can use every programming language
Using a flexible RBAC, JEM the BEE is able to manage all actions on web and Eclipse user interface, connecting cluster and accessing on the resources from jobs
Integration with Apache Hadoop by SpringBatch for Hadoop and usage of Apache HDFS as common file system
JEM is freely usable, licensed under the GNU General Public License version 3 (GPLv3). JEM Eclipse plugin is licensed under Eclipse Public Licence v1.0
Extend JEM the BEE with your customizations, adding your logic to fit your needs
JEM the BEE is hosted on GITHUB, where you can find all source code and a detailed documentation on wiki
Provide an open source solutions for batch management, reliable and consistent to meet the enterprise needs, leveraging on source quality
Batch processing is still a fundamental and mission-critical component, having significant advantages to perform repetitive logic. It remains a viable and strategic option for bulk processing with the need to be run at any time during the day, in parallel with the OLTP window, balancing blend of Batch and Online processing.
JEM, the BEE is able to control the complete job life-cycle management (Submit, Stop, Cancel, etc) and monitoring. It is leverage on existing assets, as scripts and business logic (all programming languages) reuse, where applicable, with a easy integration with job schedulers. It reinforces enterprise capability, like high availability, horizontal (cloudawareness) and vertical scalability and security, on all platforms.
Technical debt ratio
about 1% of tech debt ration which can be thought of as work that needs to be done before a particular job can be considered complete or proper. Go to SonarQube
32 issues discovered by FindBugs on about 80,000 lines of code
To be readable and easily customazible, the public API are almost all documented
Every 3 lines of code there is a comment to explain the source code itself
Pepstock is a community that is developing and maintaining JEM, the BEE.
Pepstock community is pleased to announce that JEM, the BEE BERGAMOTTO version 2.3 has been released. Here are main features: Multiple java runtimes which allows you to use the JRE you need for business logic SpringBatch restartability out of the box, provided by JEM PowerShell integration, as JCL Generic Shell JCL, which allows you to create[…]
The REST interface of JEM the BEE has been rebuilt. On the previous version, this interface was more oriented to java implementation. Now the interface is leveraging on all REST features (path and query parameters,HTTP status code implementation) and easier to use it from different languages and also from command line if such kinds of[…]
Even if JEM the BEE provides some JCL out-of-the-box, you could want to submit jobs using you favorite scripting language, not already included in JEM the BEE. Now you can do it! Read here for more details.
Within of BERGAMOTTO 2.3 (coming soon), Global Resource System (GRS) will be released under GPLv3 license. GRS is a JEM teh BEE component responsible for enabling fair access to serially reusable computing resources, such as datasets or virtual resources, such as lists, queues, and control blocks. Jobs (or programs using java API) can request: exclusive[…]
Windows PowerShell is a task automation and configuration management framework from Microsoft, consisting of a command-line shell and associated scripting language built on the .NET Framework. PowerShell provides full access to COM and WMI, enabling administrators to perform administrative tasks on both local and remote Windows systems as well as WS-Management and CIM enabling management[…]
One key issue when executing a batch job concerns the behavior of a job when it is restarted. The launching of a job is considered to be a ‘restart’ if a job execution already exists for the particular job instance. Ideally, all jobs should be able to start up where they left off, but there[…]
In the version BERGAMOTTO 2.3, JEM the BEE will be able to manage different java versions (and supplier) runtimes. This is feature will help the developer to use JRE which he needs, reusing on the code that he has written without impact with JRE used by JEM itself. In this way the business logic doesn’t[…]
See the video how to configure JEM the BEE and GlusterFS can work together. Leveraging on GlusterFS, JEM the BEE is able to have a reliable global file system which can share data and common data both to the whole JEM the BEE cluster and all jobs executed on JEM the BEE. Read here more[…]