General tab

Select the General tab and complete the following fields to configure the ODL application:

Active – make the application active. Inactive applications are not loaded when the cluster starts.
Tracking – allows the ODL application’s working directory to be set automatically. Selecting this option dynamically keeps the working directory the same as the ODL application name.
Name – enter a name for this ODL application. Application names should indicate their purpose; for example, a acquisition AIM could be named “ADT_ACQ.”
Working Directory – unselect Tracking to enable the Working Directory text box. Enter the working directory or accept the default, which matches the ODL application name. This directory tells the e-Biz Impact executable where to find the configuration information for this ODL application once the configuration files are deployed to the server.
Project File – enter the optional path and file name of the AIM project files generated by MSG-IDE that are associated with this ODL application. Paths are relative to the application working directory.
Command Line – enter any optional parameters into your ODL application. These arguments can be accessed by the ODL application by using clGetArgc() and clGetArgv(). See the e-Biz Impact ODL Guide for more information.
Log Limit (KB) – defines the size of the ODL application log file. The default of 1024 (1MB) is suggested for optimum performance. If you select the Debug option on the Advanced tab, increase the size of the log.
Depth – the number of copies of the log file that e-Biz Impact maintains. The default setting of 2 indicates that e-Biz Impact creates an additional file when the main activity log reaches its maximum size. If the second file reaches the limit, e-Biz Impact rolls back to the first file, overwriting the content.
Instances – enter or select the minimum and maximum number of instances of this ODL application that can be created.
Mode – select the ODL application mode:
- Acquire – acquire applications are simple acquisition AIMs that acquire data from an endpoint.
  
  Acquire applications run on a single thread and cannot receive DFCs from another application, and cannot use timers or protocols.
- Server – server applications can be acquisition or delivery AIMs that acquire or deliver data to or from endpoints. Most acquisition or delivery AIMs are server applications. Server applications support DFCs, timers, and communication protocols.
TRAN-IDE Functionality – ODL, like SFM, can use tables. You must keep all tables for an ODL application in the same directory. The Table field is the path to the table directory, which can be an absolute or relative path, starting from the current application working directory.
- Table – the location of production object tables, if used.
  
  Tables allows you to view table objects in TRAN-IDE. A table object contains columns of data. Use one of the columns to search for a match to data in a field object, then place data from one or more of the other columns into the output transaction. Table objects are not IDE objects; they are wrapped flat files.
- Dynamic Table Reload – reload the ODL lookup tables during runtime when changes have been made to the table files. The table is also reloaded when the application is restarted (disabled, then enabled).

Click Apply.