ENVI Services Engine 5.1 Release Notes

New Features and Updates in ESE 5.1

For additional information on updates and new features in the ESE 5.1 release, see the "What's New" topic in ESE Help.

New Feature: The IDL Workbench now provides support for ESE task development. This includes the ability to easily create JSON and PRO code, edit and validate JSON files, and publish Tasks from IDL directly to an ESE Server.
New Tools: ENVI for ArcGIS - Services Edition. ENVI® for ArcGIS® - Services Edition (EFASE) provides image analysis tools that you can publish to the ArcGIS® for Server environment.
Updated: Enhanced functionality for the Usage Statistics page in the Admin Console. It is now available as a tab in the Admin Console and has updated user interface and graphing functionality.

Known Problems in ESE 5.1

Change request ID numbers are included where applicable.

All Platforms

ID	Description
ESE-68428	Task cannot load DLMs that are located in the ESE Plugins folder. Plugins can include .PRO code, DLMs, data, and the config.json file, all uploaded to the Plugins folder. The ESE worker process' IDL instance cannot find DLMs because the Plugins folder is not on IDL's DLM path(which is only set at startup). The DLM path for workers cannot simply be set to include the main Plugins folder because then jobs may find and run the wrong DLM. Workaround: DLMs should be uploaded to another location, then set the IDL preference for the DLM path to include this alternate location. To change this preference, open the IDL Workbench and choose WINDOW >Preferences > IDL > Paths. Select the DLM path from the drop down,Insert a new path, and make sure it is checked. Click Apply, then OK.
ESE-68448	Performing a full session reset inside an ESE task or at the server level when ENVI is started may cause errors when attempting to run subsequent tasks. If you are running ESE with the server.cfgsetting "using_envi" set to "yes", then use caution when specifying task or server reset options. Running ENVI tasks this way withtaskReset="full" (in the task's config.json file) or with the server.cfg setting "reset_after_each_task" set to "full" may throw unpredictable errors. Workaround: If you are running ENVI tasks, use a server or task reset option other than "full." Do this by checking ESE's server.cfgfile. If the "using_envi" parameter is set to yes, use a reset method other than "full" in the "reset_after_each_task" setting in server.cfg, as well as in the "taskReset" option in the config.json for any tasks run on the server. If you want to use the "full" reset option because you need a completely "clean slate" after running an ENVI task, use the"restart" option instead. Note that this will entail a significant performance hit similar to the one when "full" is used, but "restart"does not throw errors. Additionally, the regular task Reset="yes"option in config.json (or reset_after_each_task="yes" in the server.cfgfile) works well with a smaller performance hit. For more information on reset options, see the ESE Help topic titled "IDL Reset Options".

ID

Description

ESE-68428

Task cannot load DLMs that are located in the ESE Plugins folder. Plugins can include .PRO code, DLMs, data, and the config.json file, all uploaded to the Plugins folder. The ESE worker process' IDL instance cannot find DLMs because the Plugins folder is not on IDL's DLM path(which is only set at startup). The DLM path for workers cannot simply be set to include the main Plugins folder because then jobs may find and run the wrong DLM.

Workaround: DLMs should be uploaded to another location, then set the IDL preference for the DLM path to include this alternate location. To change this preference, open the IDL Workbench and choose WINDOW >Preferences > IDL > Paths. Select the DLM path from the drop down,Insert a new path, and make sure it is checked. Click Apply, then OK.

ESE-68448

Performing a full session reset inside an ESE task or at the server level when ENVI is started may cause errors when attempting to run subsequent tasks.

If you are running ESE with the server.cfgsetting "using_envi" set to "yes", then use caution when specifying task or server reset options. Running ENVI tasks this way withtaskReset="full" (in the task's config.json file) or with the server.cfg setting "reset_after_each_task" set to "full" may throw unpredictable errors.

Workaround: If you are running ENVI tasks, use a server or task reset option other than "full." Do this by checking ESE's server.cfgfile. If the "using_envi" parameter is set to yes, use a reset method other than "full" in the "reset_after_each_task" setting in server.cfg, as well as in the "taskReset" option in the config.json for any tasks run on the server.

If you want to use the "full" reset option because you need a completely "clean slate" after running an ENVI task, use the"restart" option instead. Note that this will entail a significant performance hit similar to the one when "full" is used, but "restart"does not throw errors. Additionally, the regular task Reset="yes"option in config.json (or reset_after_each_task="yes" in the server.cfgfile) works well with a smaller performance hit. For more information on reset options, see the ESE Help topic titled "IDL Reset Options".

Windows Platforms

ID	Description
ESE-68109	On XP-64and Windows7-64, using the Restart option in the Windows Services Management Console is unreliable.Using this option to restart the service will cause the ESE Master to restart so quickly that the worker processes may not notice. Thus they may not pick up important changes, such as to the server.cfg file or to the plugins folder. Workaround:In the Windows Services Management Console, instead of selecting the<RESTART> option, first stop the service using the<STOP> option. Wait a few moments and check Task Manager to makesure all of the worker processes have stopped (EnviServicesEngine.exe),then manually start the service by using the <START> option.

Linux Platforms

ID	Description
	IDL and ENVI require X Server to be present in the OS.
	Linux - problems with ownership of files if installing under sudo ( use chown)

Example how to put an Apache server between ESE and clients on Ubuntu IDL 8.3 Release Notes