Best Way to Uninstall a AMP Module

[cgonzalez]

Hi,

I have developed a amp module than extends Alfresco, it works fine,but now i want to uninstall it. How can i do that?

If have readed that there's no good way to do that.

Any tip?

[pmonks]

By default the MMT tool will create a backup of the original alfresco.war file in the same directory as the original (eg. ${TOMCAT_HOME}/webapps).  To revert, simply:

• shutdown Alfresco


• rename or move the modified alfresco.war file


• copy or rename the backed up file to "alfresco.war"


• delete the ${TOMCAT_HOME}/webapps/alfresco directory


• delete the ${TOMCAT_HOME}/temp directory


• delete the ${TOMCAT_HOME}/work directory


• restart Alfresco

Cheers,
Peter

[cgonzalez]

Thanks for your reply


If i do that when i start alfresco again i get the next log message.

A previously-installed module 'mymodule' (version 1.0) is not present in your distribution.

[lvs]

Hi,

I think this is a warning message and it should not have consequences on the behaviour of your alfresco

Regards
Laura

[jpfi]

Hi,
if your module only consists of some UI-extension or something like that, you can treat this message as an info. But if your module includes some custom content models AFAIK browsing nodes which uses this content model will lead to errors /error messages.
Cheers,
Jan

[cgonzalez]

So there's no way to uninstall completely an amp module and i always will receive that WARNING?.

Thanks

[invostar]

So there's no way to uninstall completely an amp module and i always will receive that WARNING?.

Thanks

Does anyone have an answer to this question?  Trying to resolve an issue with an amp that seems to have broken our alfresco installation and would like to "roll back" all changes.  Using the backup war alone doesn't seem to fix it and there are still references to that amp in alf_data.

[sacco]

So there's no way to uninstall completely an amp module and i always will receive that WARNING?.

No, as far as I know that's not possible.  When you uninstall (ideally before) a module
you should really also hunt down and delete all content items whose type is defined by that module,
including purging them from the deleted items store, as they can cause the system integrity problems
if the model definition is missing, and it is likely to be impossible to remove them afterwards
(due to inbuilt integrity checks).  In my experience such problems can become serious, even fatal,
for the repository, even though nothing may obviously break at first.

Although the new dynamic configuration facilities may allow flexibility during development,
Alfresco really does not seem to be well adapted (yet!) for applications which may change and
evolve organically over their lifetime after deployment.  In particular, there are (as far as I have seen)
very few tools available for low level maintenance and repair/manipulation of the repository, and those
that exist can be very fragile, e.g. the Node Browser will usually be unable to display anything at all if
it encounters something odd or broken in the repository, though it may be able to display the parent
and even nodes below the problem (i.e. the node can be traversed), which makes it of rather limited
usefulness for diagnosis.

[sharifu]

has this been updated now?

[kaynezhang]

The quickest way is to move module property file and spring configuration file which is located in classpath*:alfresco/module/youmoduleid/*  out of alfresco classpath to other place.

Doing this will give you a warning like "A previously-installed module *** (version **) is not present in your distribution",But alfresco will operate normally.
If you want to suppressing warnings  you can do it  by deleting nodes in path /{http://www.alfresco.org/model/system/1.0}system-registry/{http://www.alfresco.org/system/modules/1.0... that related to the module