Java application on Windows

The following document gives the list of Open Inventor files that your Java application must embed on Windows.

All jar files of Open Inventor Java are located in the folder %OIVJHOME%/jre/lib/ext where %OIVJHOME% specifies the root folder where Open Inventor SDK is installed on your machine.

All required native DLLs of Open Inventor Java are located in the folder %OIVJHOME%/jre/bin.

Those path are referred to as [...]/jre/lib/ext and [...]/jre/bin in the rest of this document.

The required files that are described below must be copied in a targeted runtime folder of your application.

Note

You are not allowed to distribute any Open Inventor SDK files that are only used to debug your Java application. So do not copy any file from the folder %OIVJHOME%/jre/bin-debug

Inventor Core

kernel (always required)

Component	Windows file name	default path	comments
Inventor	com.openinventor.inventor.jar	[...]/jre/lib/ext	main jar of Open Inventor
	com.openinventor.inventor.dll	[...]/jre/bin
	fei_inventor.dll	[...]/jre/bin
	fei_inventor_image.dll	[...]/jre/bin
	fei_inventor_gl.dll	[...]/jre/bin
	fei_inventor_renderengine.dll	[...]/jre/bin
	fei_inventor_computing_algorithms.dll	[...]/jre/bin
	fei_glew.dll	[...]/jre/bin
Inventor base	fei_inventor_base.dll	[...]/jre/bin
	fei_inventor_ui.dll	[...]/jre/bin
	fei_scaleViz.dll	[...]/jre/bin
	fei_zlib.dll	[...]/jre/bin
	fei_freetype.dll	[...]/jre/bin
Image readers	iolink.dll	[...]/jre/bin
Image readers	ioformat.dll	[...]/jre/bin
boost	fei_boost_iostreams-mt.dll	[...]/jre/bin
boost	fei_boost_system-mt.dll	[...]/jre/bin
boost	fei_boost_chrono-mt.dll	[...]/jre/bin
boost	fei_boost_thread-mt.dll	[...]/jre/bin
boost	fei_boost_regex-mt.dll	[...]/jre/bin
boost	fei_boost_date_time-mt.dll	[...]/jre/bin
boost	fei_boost_filesystem-mt.dll	[...]/jre/bin
boost	fei_boost_log-mt.dll	[...]/jre/bin
Intel TBB	fei_tbb.dll	[...]/jre/bin
ULM	ULMLicenseCheck.dll	[...]/jre/bin
ULM	ULMLicenseCheck_FNP.dll	[...]/jre/bin
dragger data	draggerDefaults/*	%OIVJHOME%/data	dragger files
OIV fonts	fonts/*	%OIVJHOME%/data	font files

optional files

Depending on file type or specific feature that can be used by your application, the following files may also be necessary. They are dynamically loaded from the application directory, the current directory, the system directory, the Windows directory, %PATH%, or from a path specified by the %OIV_LD_LIBRARY_PATH% environment variable.

Component	Windows file name	default path	comments
	fei_proj4.dll	[...]/jre/bin	required only by SoGeoProjection: Cartographic projection support
	fei_libjpeg.dll	[...]/jre/bin	required only if JPEG images are used, e.g. with SoTexture2 or SoJPEGImageRW
Image readers	ioformat-bmp.dll	[...]/jre/bin/ioplugins	required only if bmp images are used
Image readers	ioformat-gif.dll	[...]/jre/bin/ioplugins	required only if gif images are used
Image readers	ioformat-mrc.dll	[...]/jre/bin/ioplugins	required only if mrc images are used
Image readers	ioformat-openjpeg.dll	[...]/jre/bin/ioplugins	required only if openjpeg images are used
Image readers	ioformat-png.dll	[...]/jre/bin/ioplugins	required only if png images are used
Image readers	ioformat-tiff.dll	[...]/jre/bin/ioplugins	required only if tiff images are used
	fei_inventor_io_dxf.dll	[...]/jre/bin	required only to import DXF file
	fei_inventor_io_vrml.dll	[...]/jre/bin	required only to import VRML file
	fei_smlib.dll	[...]/jre/bin	required only by SoCSGShape

Note

Your application can ask Open Inventor to load alternate versions of these DLLs. For this, you have to use the following environment variables:

• OIV_LIBPROJ4_NAME: Cartographic projection support
• OIV_LIBJPEG_NAME: JPEG support (import/export)
• OIV_ZLIB_NAME: Compression library
• OIV_FREETYPE_NAME: FreeType font support

If you have chosen to use one or more alternate DLLs, be sure to distribute the alternate DLLs that your application needs.

Viewers

AWT viewers

If your application uses some classes from packages com.openinventor.inventor.viewercomponents.awt*, it requires all libraries from Open Inventor core in addition to the following ones:

Component	Windows file name	default path	comments
viewer component	com.openinventor.inventor.viewercomponents.jar	[...]/jre/lib/ext	SceneExaminer, SceneOrbiter, etc
viewer component	com.openinventor.inventor.viewercomponents.awt.jar	[...]/jre/lib/ext
JOGL	jogl-all.jar	[...]/jre/lib/ext
JOGL	jogl-all-natives-windows-amd64	[...]/jre/lib/ext
JOGL	gluegen-rt	[...]/jre/lib/ext
JOGL	gluegen-rt-natives-windows-amd64	[...]/jre/lib/ext

SWT viewers

If your application uses some classes from packages com.openinventor.inventor.viewercomponents.swt*, it requires all libraries from Open Inventor core in addition to the following ones:

Component	Windows file name	default path	comments
viewer component	com.openinventor.inventor.viewercomponents.jar	[...]/jre/lib/ext	SceneExaminer, SceneOrbiter, etc
viewer component	com.openinventor.inventor.viewercomponents.swt.jar	[...]/jre/lib/ext
JOGL	jogl-all.jar	[...]/jre/lib/ext
JOGL	jogl-all-natives-windows-amd64	[...]/jre/lib/ext
JOGL	gluegen-rt	[...]/jre/lib/ext
JOGL	gluegen-rt-natives-windows-amd64	[...]/jre/lib/ext
Eclipse SWT	swt.jar	[...]/jre/lib/ext

Extensions

VolumeViz extension

If your application uses some classes in VolumeViz or in LDM, it requires all libraries from Open Inventor core in addition to the following ones:

Component	Windows file name	default path	comments
VolumeViz	com.openinventor.volumeviz.jar	[...]/jre/lib/ext	jar of VolumeViz
VolumeViz	com.openinventor.volumeviz.dll	[...]/jre/bin
VolumeViz	fei_volumeViz.dll	[...]/jre/bin
LDM	com.openinventor.ldm.jar	[...]/lib/ext	jar of LDM
LDM	com.openinventor.ldm.dll	[...]/jre/bin
LDM	fei_ldm.dll	[...]/jre/bin
	fei_libjpeg.dll	[...]/jre/bin	required only if using jpeg files

RemoteViz, (server side)

If your application uses some classes in RemoteViz, it requires all libraries from Open Inventor core in addition to the following ones:

Component	Windows file name	default path	comments
viewer component	com.openinventor.inventor.viewercomponents.jar	[...]/jre/lib/ext	SceneExaminer, SceneOrbiter, etc
RemoteViz	com.openinventor.remoteviz.rendering.jar	[...]/jre/lib/ext	jar of RemoteViz service
RemoteViz	com.openinventor.remoteviz.rendering.dll	[...]/jre/bin
RemoteViz	fei_remoteViz_services.dll	[...]/jre/bin
RemoteViz	fei_remoteViz_jpeg_codec.dll	[...]/jre/bin
RemoteViz	fei_remoteViz_nvidia_video_codec.dll	[...]/jre/bin
RemoteViz	fei_remoteViz_png_codec.dll	[...]/jre/bin
RemoteViz	fei_remoteViz_FFmpeg_codec.dll	[...]/jre/bin
FFmpeg	fei_FFmpeg_avcodec.dll	[...]/jre/bin
FFmpeg	fei_FFmpeg_avfilter.dll	[...]/jre/bin
FFmpeg	fei_FFmpeg_avformat.dll	[...]/jre/bin
FFmpeg	fei_FFmpeg_avutil.dll	[...]/jre/bin
FFmpeg	fei_FFmpeg_swresample.dll	[...]/jre/bin
FFmpeg	fei_FFmpeg_swscale.dll	[...]/jre/bin

RemoteViz, (client side)

If you want to build a client application without any browser, it requires all libraries from Open Inventor core in addition to the following ones:

Component	Windows file name	default path	comments
RemoteViz client	com.openinventor.remoteviz.clients.jar	[...]/jre/lib/ext	jar of RemoteViz client
RemoteViz client	com.openinventor.remoteviz.clients.dll	[...]/jre/bin
RemoteViz client	fei_remoteViz_client.dll	[...]/jre/bin

MeshViz

If your application uses some classes in MeshViz, it requires all libraries from Open Inventor core in addition to the following ones:

Component	Windows file name	default path	comments
MeshViz	com.openinventor.meshviz.jar	[...]/jre/lib/ext	jar of MeshViz
MeshViz	com.openinventor.meshviz.dll	[...]/jre/bin
MeshViz	fei_meshViz.dll	[...]/jre/bin

MeshViz XLM

If your application uses some classes in MeshVizXLM, it requires all libraries from Open Inventor core in addition to the following ones:

Component	Windows file name	default path	comments
MeshViz XLM	com.openinventor.meshvizxlm.mesh.jar	[...]/jre/lib/ext	jar of MeshViz XLM
MeshViz XLM	com.openinventor.meshvizxlm.extractors.jar	[...]/jre/lib/ext	jar of MeshViz XLM
MeshViz XLM	com.openinventor.meshvizxlm.mapping.jar	[...]/jre/lib/ext	jar of MeshViz XLM

Medical

If your application uses some classes in the packages com.openinventor.medical.*, it requires all libraries from Open Inventor core in addition to the following ones:

Component	Windows file name	default path	comments
Medical	com.openinventor.medical.jar	[...]/jre/lib/ext	jar of medical package

HardCopy

If your application uses some classes in HardCopy, it requires all libraries from Open Inventor core in addition to the following ones:

Component	Windows file name	default path	comments
HardCopy	com.openinventor.hardcopy.jar	[...]/jre/lib/ext	jar of HardCopy
HardCopy	com.openinventor.hardcopy.dll	[...]/jre/bin
	fei_hardCopy.dll	[...]/jre/bin
	fei_hardCopy_pdf.dll	[...]/jre/bin
	fei_ifx_core.dll	[...]/jre/bin
	fei_ifx_exporting.dll	[...]/jre/bin
	fei_ifx_scheduling.dll	[...]/jre/bin
	fei_hpdf.dll	[...]/jre/bin	PDF/U3D support

CAD readers

If your application imports a scene graph from a CAD file format (cf package com.openinventor.inventor.io.cad) all libraries from from Open Inventor core in addition to the following ones:

Component	Windows file name	default path	comments
	com.openinventor.inventor.io.cad.jar	[...]/jre/lib/ext	SoCADInputReader
	com.openinventor.inventor.io.cad.dll	[...]/jre/bin
	fei_inventor_io_cad.dll	[...]/jre/bin

STL readers

If your application imports a scene graph from a STL file format (cf package com.openinventor.inventor.io.stl) all libraries from from Open Inventor core in addition to the following ones:

Component	Windows file name	default path	comments
	com.openinventor.inventor.io.stl.jar	[...]/jre/lib/ext	SoSTLInputReader
	com.openinventor.inventor.io.stl.dll	[...]/jre/bin
	fei_inventor_io_stl.dll	[...]/jre/bin

IvTune

IvTune is an extension mainly designed for scene graph editing or debugging. So we do not recommend to embed any IvTune components in your application: It would be a way for the end user to change the scene graph of your application without any control.

However, we indicate below the list of files used by IvTune for your information.

Component	Windows file name	default path	comments
IvTune	com.openinventor.ivtune.jar	[...]/jre/lib/ext	jar of IvTune
IvTune	com.openinventor.ivtune.dll	[...]/jre/bin
IvTune	fei_ivTune.dll	[...]/jre/bin
IvTune	fei_ivTune_extender.dll	[...]/jre/bin
IvTune	fei_ivTune_extender_base.dll	[...]/jre/bin
IvTune	fei_ivTune_extender_inventor.dll	[...]/jre/bin
IvTune	fei_ivTune_extender_volumeVizLDM.dll	[...]/jre/bin
	fei_hardCopy.dll	[...]/jre/bin
	fei_inventor_io_genericFile.dll	[...]/jre/bin
	fei_inventor_ui_qt.dll	[...]/jre/bin
	Qt5Widgets.dll	[...]/jre/bin
	Qt5Core.dll	[...]/jre/bin
	Qt5Gui.dll	[...]/jre/bin
	Qt5PrintSupport.dll	[...]/jre/bin

OpenInventor Studio

Open Inventor Studio is the alternative to IvTune when the environment variable %OIV_USE_OIVS% is 1. It is also designed for scene graph editing or debugging. So we do not recommend to embed any Open Inventor Studio components in your application: It would be a way for the end user to change the scene graph of your application without any control.

FYI: we indicate below the list of files used by Open Inventor Studio.

Component	Windows file name	default path	comments
OIVStudio	fei_inventor_studio.dll	[...]/jre/bin
	fei_common_components.dll	[...]/jre/bin
	fei_common_models.dll	[...]/jre/bin
	fei_common_notification_system_core.dll	[...]/jre/bin
	fei_common_notification_system_gui.dll	[...]/jre/bin
	fei_common_periodic_table.dll	[...]/jre/bin
	fei_common_theme.dll	[...]/jre/bin
	fei_common_utils.dll	[...]/jre/bin
	Qt5Xml.dll	[...]/jre/bin
	Qt5Network.dll	[...]/jre/bin
	Qt5Quick.dll	[...]/jre/bin
	Qt5QmlModels.dll	[...]/jre/bin
	Qt5Qml.dll	[...]/jre/bin
	Qt5QuickControls2.dll	[...]/jre/bin
	Qt5QuickWidgets.dll	[...]/jre/bin
	Qt5Help.dll	[...]/jre/bin
	Qt5QuickTemplates2.dll	[...]/jre/bin
	Qt5Sql.dll	[...]/jre/bin