How You Share Update Files

To reduce the bandwidth and disk space required for application updates, you can define a shared network location (SNL) for storing and applying updates.

This option can greatly reduce the impact of updating multiple workstations by locally mirroring the update content from the Oracle host servers. The first client to detect an available update will download the .zip file to the location you define and extract the contents to its application files location. The .zip file is then retained so it can be extracted by the remaining clients upon subsequent logins.

Note: By default, updates are automatically downloaded to the Updates subdirectory of the application files location. For this reason, if a custom deployment location (CDL) has been specified, update files will already be shared from that location’s Updates subdirectory just as they would be if the same location were defined in this setting. However, you can still use this setting to define a different location to store updates if you prefer to do so. For example, if the CDL you have defined is on the workstation hard drive, you can still reduce resource impact by downloading updates to a shared network location.

You can also specify the protocol used to perform the updates, and enable the Oracle servers as a fallback resource should the location you define become unavailable, such as during server maintenance. You can define an SNL for your entire site, for specific profiles, or both. If both are defined, the location defined in the profile will override the location defined for the site for all staff members who share that profile.