The process used to save changes while configuring the Administration Client has changed from version 2.3.x to 3.0.x.

DataSplice 2.3.x

In DataSplice 2.3.x, committing changes permanently was a two-step process. One type of save, involving the Update button , committed changes to memory. With this button, the changes were immediately visible the next time the Remote Client connected to the DataSplice Server, but the changes were not saved permanently to disk on the server machine. The other type of save was performed by using the File menu and choosing Save Server Config. This save committed the changes permanently to disk. It was important to remember to perform this type of save in addition to the Update button save if multiple configurations were being performed. If there were changes still pending and the administrator disconnected from the Administration Client without clicking the Save Server Config menu item, those changes were permanently lost.

DataSplice 3.0.x

The saving process has been consolidated for DataSplice 3.0.x. While changes are being made, nothing is committed to memory or disk until the Save Changes button is clicked. This button saves the changes to both memory and disk. If changes are pending and the administrator disconnects, a message prompt is displayed to allow the changes to be saved and not lost. This feature was not included in DataSplice 2.3.x.