Setting the Classpath
DEPRECATED Information on this page is deprecated and applicable only to expanders <4.0. See NSX-Prime instead.
To execute the NSF functions, a number of jar files need to be included in the classpath. This section will describe the use of each file and when you will need which.
The full classpath needed will look like this:
The nsx-prime jar contains classes for expanding, harvesting etc.
The elements-io jar contains classes for communicating with the Prime radiant and reading/writing the XML model of the application. Needed for export, import as well as expanding, harvesting etc.
These libraries contains the meta-model of the Prime radiant. Needed for export, import as well as expanding, harvesting etc.
These libraries contain the actual classes that generate the code for the project. Needed for expansion.
nsx-shared-common, nsx-common, nsx-logging
Basic dependencies for most nsx libraries.
This jar contains all classes necessary to connect with the Prime radiant through RMI. Needed when importing, exporting or expanding and harvesting from the Prime radiant. This library is not needed when expanding or harvesting from XML.
JNDI_PROPS_URI environment variable
In order for communication with the Prime Radiant to work, the JNDI_PROPS_URI environment variable must be configured correctly to point towards the jndi conf folder of the server where the Prime Radiant is installed: