Determining update details

After the file update directories have been created, you must place the update files in them. When creating custom updates, the exact folder structure on the clock must be mirrored in the update directory for the update to function as required. If the file updates require other update files first, you must specify the dependencies in a separate file. This dependency file must be stored in a deploy_scripts subdirectory.

Updates that are provided by the system will come with the directory structure and any dependency files already created.

Updating settings

Settings files are located in this directory:

\mnt\hda1\admin\java\apps\wbcs\conf

In a custom update you can add, delete, or modify settings. These actions are performed by creating a merge file that contains the changes. The merge file name must match the settings file that you want to update but with .merge appended to the file name. For example, to update the settings.conf file, create a settings.conf.merge file.

Within the merge file, each line designates a change:

To add or modify settings, specify the line as the line appears in the final version of the settings file. For example, specifying wbsynch.webservice.timeout = 500000 modifies the wbsynch.webservice.timeout setting, if the setting exists. If the setting does not exist, the setting is added to the settings.conf file.
To delete a setting, prefix the setting name with the & character. For example, specifying &wbsynch.webservice.timeout deletes the setting.

Adding or overwriting entire files

To add or overwrite entire files on the clock, copy the updated file into the file update directory, using the exact folder structure on the clock. If the file already exists on the clock, the file is overwritten. If the file does not exist, the file is added to the specified location.