...
Anchor | ||||
---|---|---|---|---|
|
- Set up a development environment for Linux and Windows. The following packages are required:
- gcc - GNU Compiler, starting with version 4.1.3
- zlib-devel
- binutils (version corresponding to gcc)
- SOS uses gcc 4.4.6
Download from the Repositories
Prepare a folder in your file system where you can clone the repositories into.
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
Folder LINKS
After the build has completed you find all created .jar files in
- the target folder under each project and subproject.
- the local ./m2 repository in your home folder (
%USERPROFILE%\.m2\repository\com\sos-berlin
or$HOME/.m2/repository/com/sos-berlin
)
At this point you already have all the library files to update an exisiting JobScheduler installation in your system.
You can find the specific libraries for the different platform in the target folder of the engine-setup:
.\scheduler-engine\engine-setup\target\setup\scheduler.windows-x64\bin
jobscheduler-engine.dll
scheduler.exe
.\scheduler-engine\engine-setup\target\setup\scheduler.windows-x86\bin
spidermonkey.dll
scheduler.exe
./scheduler-engine/engine-setup/target/setup/scheduler.linux-x64/bin
scheduler
setuid
./scheduler-engine/engine-setup/target/setup/scheduler.linux-x64/lib
./scheduler-engine/engine-setup/target/setup/scheduler.linux-x86/bin
javavscript
scheduler
setuid
./scheduler-engine/engine-setup/target/setup/scheduler.linux-x86/lib
Once the folder scheduler-engine
is created (from cloning the repositories), change into scheduler-engine/engine-kernelcpp
and create a folder LINKS
:
Code Block | ||
---|---|---|
| ||
# cd scheduler-engine/engine-kernelcpp
# mkdir LINKS |
Access to the folder LINKS and set 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 |
libjobscheduler-engine.so
libspidermonkey.so
Support
Commercial License
If you purchased a Commercial License with the Service Request Support Option, then the build process will be supported by our Support Team should you face 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 building on a Windows system where Cygwin is not available. The error log states "cannot run program bash" which is a Linux shell command and has to be executed by Cygwin when running on a Windows system. Please see cygwin explanations for resolving this problem. |
Error: "make: *** No rule to make target '.../LINKS/perl/CORE/EXTERN.h', needed by `perl.o'. Stop."
Expand |
---|
This error occurs when a Java JDK 32-bit is installed on a 64-bit system, or when the global variable "JAVA_HOME" is either not set or not properly set. Please see Java explanations for resolving this problem. |
...