Additional Steps

There are additional steps beyond publishing that must be taken in order for your datatype to be recognized and available within Isight. Specifically, the classes for the datatype must be added to the classpath because they are not dynamically loaded.

To perform this step (on any computer that will serve as an Isight client), the jar file for your datatype must be placed in some location and added by either of the following means:

  • Modify the fiperenv.bat file (in the <Isight_install_directory>\<operating_system>\code\command\ directory) by adding the location of your jar file to the end of the set FiperJars= line.

  • Add an operating system environment variable FIPER_ADDPATH and specify the location of the jar file in the variable setting.

If deploying the new datatype to a SIMULIA Execution Engine, there are additional steps that must be taken for the server to load the datatype classes properly. These steps are not documented in this guide. Contact SIMULIA for support when deploying a new datatype to a SIMULIA Execution Engine.

The SDK Generator does not support the creation of datatypes.