Skip to main content

Change a running configuration

On the first day, changing is easy: nothing is running yet. Half a year later, it looks different — nine routes are working, one of them every ten minutes, and the change you are supposed to make is tiny. The worry is rarely the change itself. It is: What happens meanwhile to what is running — and does only what I wanted really go out in the end?

In the example: A. Vogt is to add one row to the value table "Zahlungsarten Webshop". The shop has recently started delivering applepay; the value is missing from the table, so it falls back to the fallback value SO — in future, it should go to the payment method KK. One row. Activation at the end is done by M. Brandt.

What you need​

  • The permission for what you change, at the level Full — here Value Tables, for a route Routes. For the comparison further down, it is enough to be allowed to see the Configuration Snapshots.
  • Someone with the Activation permission. As a rule, another person has it, see Permissions. Clarify beforehand who it is and when this person has time; a finished draft stays put until someone takes care of it.
  • Xchange saves every input automatically. But everything takes effect only with activation.

Changing while everything runs​

Xchange does without a maintenance mode. Make your change while everything runs. A run that has already started works to the end with the snapshot it started under — even if you enter something completely different in the middle of it. What this means in detail is covered under Configuration Snapshots. In short: the time between your first input and the activation is safe.

Step 1: Check whether a draft is already open​

Before you enter anything, look at the header. On the right is the version of the active snapshot and, if there is one, that of the draft.

Header with active version 7 and open draft version 8.

If a draft is already there, it belongs to everyone together. There is at most one. Your change thus lands in the same draft as everything someone else has been collecting in it for days — and is activated together with its content. In that case, ask before you enter anything; the page Two editors on the same object shows how you notice that someone is working at the same time.

In the example: before Vogt's first input, it shows only Active v7; the way is clear. The image shows the same header shortly after nine, with Vogt's finished and validated draft.

Step 2: Change — and only that​

Open the value table "Zahlungsarten Webshop" and enter the row applepay → KK, done. A draft is created by itself in the process, with the first input.

Make sure yourself that only your change lands in it. A draft is a collecting pool: every change you make anywhere goes into the same one, and it is activated as a whole. Activation takes along everything in it — including changes you would rather hold back. That is why a quick change "while you are at it" becomes expensive: from then on, it depends on the same approval as the one you came for.

Step 3: Compare before anyone activates​

Open Configuration Snapshots and compare the draft with the active snapshot. You get a list of what differs, organized by routes, connections and value tables, and for each entry with Added, Changed or Removed.

Everything on the screen is described in Configuration Snapshots in the reference. Here all that counts is how you read it: you are looking for the other changes — your own you know. Everything else in the list is activated along with it.

In the example: the comparison shows exactly one entry — value table "Zahlungsarten Webshop", Changed. So Vogt knows that version 8 contains this change alone, and can let Brandt know with a clear conscience.

If there were two entries and you knew of only one, that would be the moment to ask — now, before activation puts both into operation.

Step 4: Validate and activate​

From here on, the way is the same as for the very first snapshot: validate, then activate. Both are covered step by step under Validate and activate. The only difference is that this time something is running — and Xchange takes care of that, see above. If the validation finds something, Fix the findings of a validation takes you through the checklist.

If you change your mind​

A draft can be discarded, but that too affects it as a whole — everything in it is gone, for good, including the work of someone else.

If it has already been activated and the change was wrong, discarding is the wrong tool anyway — the draft has already become the active snapshot. Then the way is Go back to an earlier snapshot.

What comes next​

See also​