This step is also demoed with this video :

(ongoing...)

Step 6e : Synchronization process with several servers

As seen in srep 6c, a server must declared and activated to enable the capitalization & synchronization process :

It is possible to declared several addresses :

In this context 6e, MTX_Server1 and MTX_Server2 have been declared :

Fundamentally, due to the traceability feature, there is no need of several addresses, but some modules may be stored at different adresses

• • for confidentiality reasons

  • for localisation reasons

Here is a scenario that one can get with two addresses. Suppose that a User works on module FB_LatAcc_vU2 :

On Monday, User decides to capitalize its version on Server #1 in version v000d000 (Server #1 is already activated in this context) :

Now, change the active server from Server #1 to Server #2 :

And try to capitalize FB_LatAcc_vU2 on Server #2 :

As the origin version FB_LatAcc_v000d000 of vU2 is not found on Server #2 and to maintain traceability, it is not possible to proceed :

To recover the traceability, origin version has to exist on Server #2, which is achievable by synchronization process (step 6d) :

Now, the origin version v000d000 of vU2 exists on the server Server #2,

capitalization of vU2 to v001d000 on Server #2 is allowed :

Note that if is not possible to capitalize vU2 on Server #1 because its origin version v002d000 does not exist on Server #1,

if necessary, version v002d000 has to be copied via synchronization process to Server #1.

Moreover, the traceability does not check only the name of the version.

To illusrate this, suppose that meanwhile, an other contributor has capitalized v001d000 on Server #1 :

(to set this particular context, click here).

Origin version v001d000 does exist but it's not the true origin version v001d000.

Though version is equal, if you try to capitalize vU2 on Server #1, traceability process will check that this is not the expected version :

To summarize, traceability process requires only one thing : the true origin version must exist on the server.

Published with MATLAB® R2013a