Running the MMT - Alfresco Content Services - 23.4 - 23.4 - Ready - Alfresco - external

Alfresco Content Services

Platform
Alfresco
Product
Alfresco Content Services
Release
23.4
License

Run the following command:

java -jar alfresco-mmt.jar [args]

It is compatible with WAR files v 2.0 and above.

Note that in some cases you must run $ALF_HOME/scripts/setenv.sh before this command, and to set $ALF_HOME and $CATALINA_HOME (as used in $ALF_HOME/bin/apply_amps.sh) is also recommended. $ALF_HOME is the installation directory. $CATALINA_HOME is the Tomcat installation directory.

MMT Commands

The MMT has a number of commands. Details of these are outlined as follows:

  • install

      usage: install <AMPFileLocation> <WARFileLocation> [options]
            
      valid options:
              
          -verbose   : enable verbose output
          -directory : indicates that the amp file location specified is a directory.
            All amp files found in the directory and its sub directories are installed.
          -force     : forces installation of AMP regardless of currently installed module version
          -preview   : previews installation of AMP without modifying WAR file
          -nobackup  : indicates that no backup should be made of the WAR
    

    This installs the files found in the AMP file into the alfresco.war, updating it if an older version is already installed. If the module represented by the AMP is already installed and the installing AMP is of a higher release version, then the files relating to the older version will be removed from the WAR and replaced with the newer files.

    It is the responsibility of the module developer to provide the appropriate module components to bootstrap or patch any data as required when updated WAR is run.

    If the installing module version is less than or equal to the version already installed in the WAR then installation will be aborted unless the -force option is specified. In this case the installing AMP will always replace the currently installed version. This option is especially useful when developing an AMP.

    Before an AMP is installed into a WAR a copy of the original WAR is taken and placed in the same directory. Specifying the -nobackup option prevents this from occurring.

    Example:

      java -jar alfresco-mmt-2.1.0.jar install /root/alfresco-recordsmanagement-2.1.0.amp /usr/jboss-4.0.3SP1/server/default/deploy/alfresco.war 
    
  • list

       usage: list <warFile>
    

    Lists the details about all the modules currently installed in the WAR file specified. The output is directed to the console.

  • uninstall

    usage: uninstall <moduleId> <warFile>