Uniqueness in Activator

In order to process message flows in a coherent and predictable manner, Activator enforces the uniqueness of processing configurations at two levels:

  • Unique object names
  • Unique exchange context

Unique object names

In order to configure Activator, you create objects and assign values to attributes of these objects.

As a general rule, each object that you create in the Activator interface must have a unique name.

Object creation: If you try to create an object with a name that already exists, Activator displays a message informing you of the naming conflict and instructing you to enter a unique name.

Object importing: If you import an object or set of objects with a name that is already used in a configuration, the importer executes one of the following actions to insure uniqueness:

  • ignore - ignores the imported object and conserves the existing object
  • replace - replaces the existing object with the imported version of the object
  • update - modifies the existing object by adding, deleting or revaluing attributes from the imported object

Upgrades: If you upgrade from a previous version, the upgrade logic never deletes previous data. When the upgrade logic detects or must generate a potentially duplicated object, it automatically renames the duplicates with unique names. In some cases it may also have to disable the renamed object to conserve the functional uniqueness of the configuration.

Related topics

Related Links