Update sets

An update set is a group of configuration changes that can be moved from one instance to another. This feature allows administrators to group a series of changes into a named set and then move them as a unit to other systems for testing or deployment.

For example, an update set called Incident Management 2.0 might hold a set of enhancements to incident management. While Incident Management 2.0 is marked as the current update set, all changes are tracked in it.

An update set consists of:

  • A set of record details that uniquely identify the update set.
  • A list of configuration changes.
  • A state that determines whether another instance can retrieve and apply configuration changes.

Update sets track changes to applications and system platform features. This allows developers to create new functionality on a sub-production instance and promote the changes to another instance .

Administrators have the following options with update sets.

  • Create an update set to store local changes.
  • Select the current update set to store local changes.
  • Commit an update set to prepare it for distribution.
  • Report on the contents of update sets.
  • Compare update sets to determine what differences they contains.
  • Merge separate update sets into a single update set.
  • Create an external file from an update set.
  • Retrieve update sets from remote instances.
  • Apply retrieved update sets.
  • Back out changes applied from an update set.
Note: Properties that are tagged as Private are excluded from update sets. Keeping system properties private prevents settings in one instance from overwriting values in another instance. For example, you may not want a system property in a production instance to use a particular value from a development instance. Add a property using sys_properties.list.

Application developers have additional options with update sets such as:

  • Create an update set for a specific version of an application.
  • Specify which application tables to track in update sets.