Embedded Configuration

Administrators can create customized versions of MTPexpedat which are pre-configured with certain defaults or overrides.  This should be used when the network is known to require certain settings or when you wish to prevent users from choosing settings which may be disruptive.  For example, if you are running your server on a port other than 8080, you may wish to change the default server port to match that of your server.

None of the option settings require adjustment in a normal installation.  Incorrect settings may severely degrade performance or disrupt the network.  Take the time to understand what these Settings do before experimenting with them.

To create a custom configured MTPexpedat, first make a copy of the application binary and change its name.  You may wish to maintain multiple configurations of the client, so be sure to choose a name that is distinctive.

Drag a new or existing MTPexpedat client onto the DropDat master application to edit the client's settings.  If any settings are already embedded in that application instance, they will be displayed.  The example below shows settings for a fresh (unconfigured) copy of MTPexpedat.

The chapter about distributing DropDat droplets also applies to pre-configured MTPexpedat applications.  In general, if you have an established means of sending applications to an end-user, you should use that same means to send MTPexpedat.

Defaults

Values entered into the text fields will be recorded in the MTPexpedat client executable as defaults.  Users will be able to view these settings using the Options dialog, and may change them unless they are locked.

Locking Settings

Clicking the checkbox next to a setting will prevent the user from changing this value via the Options dialog.  You can lock a setting without specifying a value, in which case the application default will be used.

Considerations

Remember that the settings you create here may not be appropriate for all network environments.  You may wish to provide end-users with multiple configurations for different use scenarios, and name them appropriately.

If you set Log File, remember that it will be necessary to periodically clean out the log file or it may grow very large.  Make sure you choose a pathname that you know will exist on the end-user's system.

Settings are embedded into the application executable and only apply to that executable.  End-users running a different copy of MTPexpedat will be subject to that copy's settings.