Using the Data Engine Settings tool

InfoSet Settings

These define settings for handling InfoSets that are stored as relational tables, namely large InfoSets. Large InfoSets are specified in the InfoSet wizard.

These values must be correctly configured for large InfoSets to work properly.

• InfoSet JNDI Datasource is the name of the JNDI data source that has been configured in the application server. This can be set to the same value as the Repository setting, which will cause the InfoSets to be saved in the same database as the rest of the repository. When the settings are saved, the system runs a test will to ensure that this value is valid.
• InfoSet Database Type is the type of database being used to store InfoSets relationally. This must be set correctly for data to be properly stored. Valid database types are:
  • MSSQL
  • Oracle
  • DB2

  This value is not automatically tested.

• InfoSet Table Owner is the optional name of a user in the database that will own all of the tables created for storing InfoSets. The user must have privileges to create, read, write, and use tables in the database.

  Specifying a user provides greater security by limiting the users in the database that have access to the InfoSet content.

AutoLoad Folders

These define the locations to be used to automatically load data source and InfoSet descriptions into the system. These folders and all folders below them will be searched for valid Data Source and InfoSet Description XML files.

If any new files are found, or if the old files were modified, the data will be automatically loaded when the server starts.

• Data Sources is the name of a directory on the server that contains defined data source XML documents.
• InfoSet Description Folder defines the root folder to search for InfoSet description XML documents.

Cache Sizes

These define the number of objects of each type to store in memory. Storing the values of each given type can improve performance, especially if there are a few InfoSets that are used by many users on a regular basis.

Making the cache too large can result in performance degradation due to decreasing available memory for other parts of the application.

• The InfoSet Descriptions cache stores recently accessed InfoSet Descriptions. Lawson recommends that these numbers remain at an average rate.
• The InfoSet IDs cache stores a mapping between the InfoSet ID and the location of the InfoSet in the database. This reduces the amount of time it takes to access the InfoSet. These objects tend to be very small, so many objects can be cached. Set this value to the number of InfoSet descriptions that the system will contain.
• The InfoSets cache stores the complete contents of an InfoSet in memory. Given the large size of some InfoSets, this cache should be small.

Data Upload Settings

These settings define how data should be handled when uploaded by a user to the server. This typically occurs when uploading from the InfoSet wizard using the Upload link.

• The first option is to upload to a directory location on the server. If this option is used, enter the absolute path to a directory to store the data into Root Upload Folder. All files will be stored on the server relative to this folder.
• The second option is to store all uploaded data on an FTP server. This can either be the same server running the system, or a separate server accessible from the server running Smart Notification.

  When using this option you must provide the name of the server and a valid username and password combination. All files will be stored relative to the root location on the FTP server.