wiiisdom logo colored

Configure 360Eyes to run on SAP Business Objects 4.3SP2

Symptom

You run 360Eyes using the 360Eyes GUI or Command-Line against an SAP Business Objects Environment 4.3SP2.
or 
  1. java -Xmx1024m -cp "../libs/;*%SDK_LIB_FOLDER%/*" com.gbs.eyes.Launcher <job> <cms> <BO_user> <BO_user_passwd> <auth> <360Eyes_dir>
Thrown error:
  1. Exception in thread "Thread-2" java.lang.UnsatisfiedLinkError: no sapcrypto in java.library.path



If you launch 360Eyes jobs directly from the SAP BusinessObjects CMC you do not need to follow this KB article as the SAP JVM is used by default in that case.

Environment

  • 360Eyes
  • SAP BusinessObjects Business Intelligence 4.3SP2 and above

Resolution

In all cases, you must use the SAP JVM to execute 360Eyes.

SAP JVM is already installed on the server where you run 360Eyes

You need to make sure the JVM used by the 360Eyes java program is the SAP JVM.
If the server contains the path to the SAP JVM in its PATH environment variable, you don't need to do any specific action.
Just make sure the SAP JVM is used by default running the java -version command from a terminal


If the SAP JVM is not used by default
360Eyes GUI (if the SAP JVM is not the default java / Windows only)
Update the 360eyes_GUI_BI4.bat with a text editor in order to use the appropriate SAP JVM
Change
  1. java -Xmx1024m -cp "../libs/*;C:\lib_bo\432\*" com.gbs.eyes.LauncherGui
to
  1. <PATH TO SAP JVM JRE BIN FOLDER>\java -Xmx1024m -cp "../libs/*;C:\lib_bo\432\*" com.gbs.eyes.LauncherGui
360Eyes Command Line (if the SAP JVM is not the default java)
Execute the command line from the SAP JVM JRE BIN folder.

SAP JVM is not installed on the server where you run 360Eyes

Copy the SAP JVM from the SAP BusinessObjects server and follow the previous paragraph.

Last updated over 2 years ago