Table of Contents |
---|
Scope
The
libsosperlscript.so
will no longer be included in the setup.
libsosperlscript.so
can be built on UNIX environments.library is included with the JobScheduler setup and acts as an interface to a local Perl installation should Perl API Jobs be used.
- This library is used exclusively used for job scripts of type
<script language="perlscript">
, i.e. for jobs that make use of the JobScheduler API. - This library is not required for Perl scripts that can be executed from the command line independently of a JobScheduler instance.
- This library is used exclusively used for job scripts of type
- This article explains how to build the
libsosperlscript.so
library for Unix environments API jobs.
Prerequisites
- The JobScheduler sources have to be downloaded from the SOS Git repositories. The sources are available from https://github.com/sos-berlin
- Additional tools will be referenced in this documentation
- tools have to be downloaded and configured following the below order
- .
Git
- You can find the Git download and documentation here.
- SOS uses Git 1.7.1. You can download the latest release from here.
Anchor | ||||
---|---|---|---|---|
|
- The path to your Java JDK will be needed is required for the compilation
SOS uses the path
/usr/java/jdk1.8.0_31
Perl
- Version: Perl 5.10 or above
- You can find the downloads here.
- No further configuration is required for Perl.
Anchor | ||||
---|---|---|---|---|
|
- Set up a development environment for Linux and WindowsUnix. The following packages are required:
gcc
- GNU Compiler, starting with version 4.1.3zlib-devel
binutils
(version corresponding togcc
)
- SOS uses
gcc
4.4.6
Download from the Repositories
Prepare a folder in your file system where you can to clone the repositories intoto.
Repository for the JobScheduler Engine
Execute the following command in your Git Shell:
Code Block | ||
---|---|---|
| ||
git clone https://github.com/sos-berlin/scheduler-engine |
to download the project "scheduler-engine
".
Compile the Library
Once the folder scheduler-engine
is created (from cloning the repositories), change into the working directory to scheduler-engine/engine-kernelcpp
and create a folder LINKS
:
Code Block | ||
---|---|---|
| ||
cd scheduler-engine/engine-kernelcpp mkdir LINKS |
Access Switch to the folder LINKS and set create a symbolic link to your Perl installation as it follows:
Code Block | ||
---|---|---|
| ||
cd LINKS ln -s /usr/lib64/perl5/5.10.0/x86_64-linux-thread-multi perl |
Note |
---|
If you are not using multithreading for Perl (or the multithreading links to another folder) you might have to use a shorter path, something like |
In order to compile , the last step is to call the makefile make-libsosperlscript
:
Code Block | ||
---|---|---|
| ||
JAVA_HOME=<path_to_java_jdk> make/make-libsosperlscript |
Support
Commercial License
If you purchased a Commercial License with the Service Request Support Option, then the build process will be supported assisted by our Support Team should you face any problems. The applicable service level is the same as for severity level "minor", see Product Maintenance.
Open Source License
If you use the Open Source License then the build process will be supported by using our Community Resources. A forum for build issues is available at SourceForge, see https://sourceforge.net/p/jobscheduler/discussion/bp/
Note |
---|
Note: no service levels are guaranteed including response times and resolution times. |
Troubleshooting
Error: "z_com.h:10:17: error: jni.h: No such file or directory"
Expand |
---|
This error occurs when the path in the variable J
|
Error: "make: *** No rule to make target '.../LINKS/perl/CORE/EXTERN.h', needed by `perl.o'. Stop."
Expand |
---|
This error occurs when a the symbolic link in the folder LINKS is not set right. As mentioned before, icorrectly. If you are not using multithreading for Perl (or the multithreading links to another a different folder) you might have to use a shorter path, something like |
...