You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

 

Scope

  • The libsosperlscript.so will no longer be included in the setup.

  • This documentation should describe how the library libsosperlscript.so can be built on UNIX environments.
  • This library is required for Perl API jobs.

Prerequisites

  • The sources have to be downloaded from the Git repositories. The sources are available from https://github.com/sos-berlin
  • Additional tools will be referenced in this documentation

As mentioned above, additional 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.

Java JDK

  • The path to your Java JDK is required 
  • 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. 

 

C++ Compiler

  • 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:

git clone https://github.com/sos-berlin/scheduler-engine

to download the project "scheduler-engine".

Compile the Library

After the build has completed you find all created .jar files in

  1. the target folder under each project and subproject.
  2. 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:

  1. Windows-x64 in .\scheduler-engine\engine-setup\target\setup\scheduler.windows-x64\bin
      • jobscheduler-engine.dll
      • scheduler.exe
  2. Windows-x86 in .\scheduler-engine\engine-setup\target\setup\scheduler.windows-x86\bin
      • spidermonkey.dll
      • scheduler.exe
  3. Linux-x64 in 
    1. ./scheduler-engine/engine-setup/target/setup/scheduler.linux-x64/bin
      • scheduler
      • setuid
    2. ./scheduler-engine/engine-setup/target/setup/scheduler.linux-x64/lib
  4. Linux-x86 in 
    1. ./scheduler-engine/engine-setup/target/setup/scheduler.linux-x86/bin
      • javavscript
      • scheduler
      • setuid
    2. ./scheduler-engine/engine-setup/target/setup/scheduler.linux-x86/lib

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: 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"

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."

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.

 

 

 

  • No labels