topic Re: Share site ACP import using AMP in Alfresco Archive

Share site ACP import using AMP

jayesh_prajapat — Fri, 19 Oct 2012 11:59:05 GMT

Hello All,I have created share site 'TEST' from Alfresco GUI. I created ACP file of share site from Alfresco DM using export option in ' Company Home > Sites > TEST> location. I selected "include this space" option during export process to include 'TEST' folder as well in ACP file.I created

Re: Share site ACP import using AMP

afaust — Sat, 20 Oct 2012 12:57:57 GMT

Hello,

each module component (as identified by its ID) is only executed once by default. The execution is logged in the database and prevents any further execution, unless you configure the module to execute EACH TIME the repository is started.

Regards
Axel

Re: Share site ACP import using AMP

saket_saraf — Tue, 17 Sep 2013 10:41:12 GMT

Hi,

Continue with the same if i have new updates for the same module how will i update in the repository.
Where it stores the versions. Because i tried following settings but did not work


                       <property name="sinceVersion" value="2.0.0" />
                     <property name="appliesFromVersion" value="2.0.0" />
                       <property name="executeOnceOnly" value="false" />

            ‍‍‍‍‍‍

Regards,
Saket S.

Re: Share site ACP import using AMP

dcorneanu — Mon, 07 Apr 2014 12:28:15 GMT

If you have a look at the code in
org.alfresco.repo.module.ModuleComponentHelper.executeComponent(String, VersionNumber, ModuleComponent, Set<ModuleComponent>)
I think you can conclude that the registry key is not using the version of the module at all. Thus, a module component once executed will never run again until you change it's name or you delete the appropriate key from the registry.

<java>RegistryKey executionDateKey = new RegistryKey(
ModuleComponentHelper.URI_MODULES_1_0,
REGISTRY_PATH_MODULES, moduleId, REGISTRY_PATH_COMPONENTS, name, REGISTRY_PROPERTY_EXECUTION_DATE);</java>

Furthermore, I see no use for <strong>sinceVersion</strong> and <strong>appliesFromVersion</strong> in solving this kind of problems.

However, I too am interested in what are the best options for implementing an upgrade path from one version of a module to a newer one?
Say I have this scenario:
<ul>
<li>Amp Version 1.0 : creates some users and groups</li>
<li>Amp Version 2.0 : needs to add some of the users to some of the groups (already created and imported by the previous version)</li>
<li>Amp Version 3.0 : needs to import some documents into the repository</li>
</ul>

How can I make sure that a client that has version 2.0 already installed, when upgrading to version 3.0 will get the extra documents into the repository and a client that has no version installed, when installing 3.0 will get everything properly imported in the repository ?

Any advice would be highly appreciated.

Best regards,
Dan.