X
32051

ENVI Services Engine 1.0 Service Pack 1

What's New in ESE 1.0 Service Pack 1


ENVI Services Engine 1.0.1 introduces new functionality in usage statistics, folders, and service endpoints. Updates in this Service Pack include changes to the names of the default service endpoints, as well as modifications to select parameters within SERVER.CFG.

New Features

ESE Usage Statistics

A new Usage Statistics feature is available in the Admin Console. Open the ESE Admin Console and click on the "Usage Statistics" link at the right side of the navigation bar.

Folders and Service Endpoints

A new feature available in ESE 1.0.1 is the ability to create and customize your own service endpoints, then organize them into any folder structure you like using the Admin Console. This allows you to better organize your tasks and services into logical groups of related operations, based on the specific requirements of your enterprise. For example, if you have a number of related tasks, you can create a new service endpoint with any name and description you like and upload those tasks under it, keeping them logically separated from other unrelated tasks stored under other service endpoints. Furthermore, the Admin Console allows you to organize service endpoints into logical folder structures under the top level catalog, going as flat or as deep as you like. A side effect of this change is that the two default service endpoints that shipped with ESE 1.0, GPSync and GPASync (to hold sync and async tasks respectively) are no longer hardcoded but are fully customizable. Additionally, the names of these two default service endpoints have changed to SyncService and AsyncService (see below for more information).

Updates

GPSync and GPAsync Names Change

The names of the services "GPSync" and "GPAsync" have been changed to "SyncService" and "AsyncService", respectively. If you have existing client applications using the older versions of the names, they will no longer work under ESE 1.0.1. You have two ways to address this issue in your ESE 1.0.1 installation:
1. Either rename the services back to the original names in the Admin Console (see below).
2. Or, within your client applications, update all references to "GPSync" and "GPAsync" to the new names "SyncService" and "AsyncService".

How to Rename the Services Back to their Original Names

1. Open the Admin Console and navigate to the Tasks tab.
2. On the left portion of the screen, in the folder navigation interface, click on the service whose name you want to change (for example, "AsyncService").
3. Right-click on its name and choose "Edit Properties" to open the Properties popup.
4. Delete the existing Service Name ("AsyncService" in our example) and type the original name (for example, "GPAsync").
5. Click OK.
6. Your updated service name should now appear in place of its ESE 1.0.1 name in the Admin Console.
Changes that you make to the Properties inside the Admin Console are stored in the catalog.cfg file in its default location:
Linux:/plugins/catalog.cfg
Windows: :\Exelis\se10\plugins\catalog.cfg

SERVER.CFG Parameters Have Changed

The following parameters have been removed from the server.cfg file:

  • catalog_name
  • sync_service_name
  • sync_service_description
  • async_service_name
  • async_service_description

If you have customized these parameters, you will need to modify those parameters inside the Tasks tab of the Admin Console.

Additionally, a new parameter, max_runtime, is now included in the server.cfg file for ESE 1.0.1. This new parameter enables you to set a maximum amount of time (in seconds) an ESE job can run. If an job exceeds this limit, the ESE Master will cancel the job. The default for this new parameter is "unlimited." See Configuration for more information on max_runtime.

Updating Properties of Services in the Admin Console

1. Open the Admin Console and navigate to the Tasks tab.
2. On left portion of the screen, in the folder navigation interface, click on the service whose Properties you want to change (for example, "AsyncService").
3. Right-click on its name and choose "Edit Properties" to open the Properties popup.
4. Update the Service Name or Description as necessary to recreate your customized settings.
5. Click OK.
Changes that you make to the Properties inside the Admin Console are stored in the catalog.cfg file in its default location:
Linux:/plugins/catalog.cfg
Windows: :\Exelis\se10\plugins\catalog.cfg
Beware the behavior of SMOOTH ENVI LiDAR 3.2 Service Pack 1