The Preferences section contains the following tabs:
Data File Editor
You can set the following preferences when using the Data File Editor:
- Records per page
- Set the amount of records you want to display per page. The more records you display per page, the more memory that is required;
therefore, reduce the amount of records per page if you receive memory problems. Use the
icons to navigate the pages of records.
Note: You must restart
Data File Editor before any changes to this setting take effect.
- Quick final page access
- For large variable sequential files (files > 10,000 records), select this option to immediately jump to the last page of the
file when it is opened. When this option is in effect, the last
n records are displayed, as per the
Records per page setting; from this point, you can navigate the file as normal.
- Padding Character
- Each new record is immediately padded with the characters you specify here for both ANSI and EBCDIC encoding. Enter the character
in the top cell of the box next to the encoding name.
- Temporary Directory
- Set the location of a temporary directory that is required in order to filter a data file. You can specify either an absolute
or a relative (to the current working directory) path. An invalid path, or no path at all, will produce an error when you
attempt to apply a filter.
- Dialog boxes when using a temporary file
- When using a temporary file whilst making edits, the default behavior is to not display the confirmation dialog boxes each
time you update a record (as the record is only written to the temporary file, not data file, at this point). You can turn
these confirmation messages back on whilst using a temporary file by clearing the option
Do not show update warning when editing using temporary file.
- Max Record
- When using filtering or find/replace on files in Fileshare, use this option to pause the operation every
x records. This limits the performance impact on Fileshare, as the pause allows Fileshare to process other requests. The default
value 0 will not set a limit.
If you are connecting to an enterprise server using an SSL connection, use the
Certificate Authority Trust Store setting to specify the trust store that contains the trusted root certificate used by the connection.
To use this setting requires that you have already created a trust store that includes a CA root certificate or (for non-production
scenarios only) a self-signed certificate on your client, and that the enterprise server that you are connecting to has a
valid server certificate (which is used to establish the server/client connection) and private key (for encryption) configured.
To configure an enterprise server to use an SSL connection, create a listener that specifies the server certificate and keyfile.
This type of listener does not automatically start when you start the enterprise server; it must be authorized after the server
has started, by entering the key's passphrase, before the listener starts.
Tutorial: Configuring SSL Security in the Server explains how to configure an enterprise server to use an SSL connection.
The required trust store is Java-specific, and so we recommend that to create the trust store, you use the
keytool utility from the JDK that matches your version of Java; for more information, refer to the
keytool utility documentation on the Oracle web site (http://docs.oracle.com/en/java/).