BICsuite and schedulix not affected by Java Log4j security vulnerability

There is currently a lot of media attention for a discovered security vulnerability in the Java Log4j library. As we take security risks very seriously, we have checked whether the components of our BICsuite and schedulix Workload Automation System written in Java are affected by the issue. We are pleased to inform our customers and interested parties that our system is not affected by the issue because the Log4j library is not used in our systems.

The BICsuite Run Program Part 6: Security Considerations and Conclusion

Although, as we’ve seen, the run program on itself is a powerful feature, it is not without risks. Code injectionis the appropriate keyword here. Just imagine a run program like the following has been configured: run program = /bin/bash -c "ls -l $DIRSPEC" And that DIRSPEC is a parameter of type parameter. That means that if someone has operating privilegesfor that job, that person is able to change the contents of the DIRSPEC parameter. Hence, it wouldn’t be aproblem at all to change the...

The BICsuite Run Program Part 5: Circumventing limitations

Part 5 of the run program workshop for BICsuite and schedulix
The maximum length of the run program is limited to 512 characters. Usually this doesn’t feel like any kindof limitation. Sometimes though, especially when creating long inline scripts, the limit is easily reached.But even if the run program field is limited in length, the command line, that is executed after parametersubstitution, isn’t. This is because there is also no practical limitation to the maximum length of a parametervalue, parameters can be used to circumvent the 512 bytes limitation...

The BICsuite Run Program Part 4: Other interpreters

Part 4 of the run program workshop for BICsuite and schedulix
There’s nothing special about the Bourne shell. Other command interpreters or even a mix of them, typicallyshell and something else, can be used. Naturally adding languages does result in a more complex quoting;each level of interpretation adds another level of quoting. As an example we create a small script that is used to find the IP addresses from where an invalid loginattempt has been attempted. The output should have iptables format. As a script that could be called onitself, the task i...

The BICsuite Run Program Part 3: Backticks

Part 3 of the run program workshop for BICsuite and schedulix
In the Bourne shell it is possible to assign a variable the output (stdout) of a program. Expressions like A=`expr $A + 1` used to be very common. (Since many environments now use the Bash instead of the Bourne shell, this kindof expressions is gradually disappearing). The good news is that the scheduling server knows about the backticks. It treats them as if they were doublequotes, but it doesn’t remove them. Parameter substitution is still performed and the argument doesn’tbreak at a...

The BICsuite Run Program Part 2: Advanced usage

Part 2 of the run program workshop for BICsuite and schedulix
The previous section showed how to use quoting in the run program of the job scheduler systems BICsuite and schedulix. But sometimes we need to access environment variables, in order to adapt the behaviour of our program to the special requirements of the execution environment. As an example we assume that some input file lies in the $HOME/input directory. We’d like to tell our printargs program about it. To do so, we assume that printargs expects two command line arguments, a -i indicates t...

The BICsuite Run Program Part 1: Introduction and Simple Usage

Part 1 of the run program workshop for BICsuite and schedulix
BICsuite and schedulix offer powerful functions that enable scripts to be saved and executed in the scheduling server. The linchpin is the Run Program, which we would like to introduce to you in more detail in this series of articles. The following also applies for the Rerun Program and the Kill Program. The field run program contains the definition of the command line to be executed. This field is parsed by the scheduling server and split into an array of arguments. This array of argume...

That’s the Version 2.10

Monitoring of jobs in the workload automation platforms BiCsuite and schedulix
With the new release 2.10, BICsuite and schedulix have become even more user-friendly. In Release 2.10 released on 21/05/04, these changes and additions have been made: Zope 4 / 5 Web GUIZope 4 / 5 based on Python 3 is now officially supported for the BICsuite / schedulix Web GUI. Zope 2 based on Python 2 is still supported but will be deprecated in the next release. Single Sign On with Active DirectoryThe BICsuite and schedulix Web GUI (Zope 2 as well as Zope 4 / 5) can now optionally co...

Migration to BICsuite and schedulix Workload Automation

Time for change: Migration from enterprise job scheduling systems to the BICsuite workload automation platform
High costs, poor support, missing features: there are many reasons for wanting to migrate an existing enterprise job scheduling system to the BICsuite Workload Automation System. A hurdle for the decision to migrate is often the uncertainty about how migration is possible during operation and how the process is designed. We answer these questions in the white paper on our migration method. The document describes a methodology that has proven itself in practice and which follows the principl...

Dependency resolution and ambiguous dependencies

Under certain circumstances, the submission of a batch or job to BICsuite or schedulix is prevented with the error message “Ambigous resolution”.
Under certain circumstances, the submission of a batch or job to BICsuite or schedulix is prevented with the error message "Ambigous resolution". In this article we will show you how this error message can occur and how you can define dependencies so that they can be clearly and unambiguously processed in your Workload Automation System. Example 1 Let’s start with a very simple example. Someone wants to do some processing on a database table. Data needs to be extracted, transformed and ...