Date: Fri, 29 Mar 2024 10:00:45 +0000 (UTC) Message-ID: <2022366671.12705.1711706445500@change.sos-berlin.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_12704_1773749028.1711706445500" ------=_Part_12704_1773749028.1711706445500 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Development for the "Managed Jobs GUI" (JMJ) has been stopped. Here are = some of the reasons for this decision: the technology mix of JMJ produces c= omplex dependencies between web server, db systems, PHP versions and PHP pa= ckages and this leads to difficulties for many users during installation an= d often causes ongoing problems for users of this feature. In other words i= ssues around JMJ are in front of all other issues in the support service of= SOS GmbH. Added to this, for us this means doubled up capacities are requi= red in maintaining JMJ and JOE (JobScheduler Object Editor) - capacities th= at are urgently needed for other issues.
However: you can still continue to use JMJ, we also will support our com= mercial customers that wish to continue to use this feature. A separate ins= taller for JMJ is available at
It is our strategy to concentrate the software development on the JVM. T= his means that the focus continues to be Java and we also expect that the u= sage of e.g. Scala will increase. Choosing JVM for JobScheduler means, that= all script languages will be available to create jobs.
JOE (JobScheduler Object Editor) is used to manage objects of the JobSch= eduler (jobs, job chains, orders, schedules etc.). JOE is a SWT-/JFACE appl= ication and is installed at the client, but can also access JobScheduler ob= jects remotely. JOE has features in the area of the template-based creation= of objects that are not available in JMC. The installation of JOE is inclu= ded in the JobScheduler set-up.
JobScheduler also offers the concept of "remote configuration". This fea= ture has the possibility to create and administrate objects centrally and i= t automates the distribution to instances of the JobSchedulers that are ins= talled on other servers. Available for central monitoring is the JobSchedul= er Operations Centre (JOC). This is also embedded in JMJ, which means there= is no difference here. JOC works with each browser and will be integrated = into JOE.