Administer Azure Connector

Use this information to administer the Azure Connector.


Use this information to upgrade the Azure Connector from a previous version for Tomcat-based deployments only.

  1. Stop the Content Services server.

  2. Navigate to the root directory of your installation.

  3. Use the following command to check for the module you wish to delete:

     java -jar bin/alfresco-mmt.jar list tomcat/webapps/alfresco.war

    This displays a list of the installed modules. Make a note of the module ID of the module you wish to uninstall, for example, org_alfresco_integrations_AzureConnector.

  4. Use the Module Management Tool (MMT) to uninstall the AMP from the repository WAR (alfresco.war). For example:

     java -jar bin/alfresco-mmt.jar uninstall  org_alfresco_integrations_AzureConnector tomcat/webapps/alfresco.war

    For more information, see Using the Module Management Tool (MMT) and Uninstall an AMP file.

  5. Navigate to the amps directory.

  6. Delete any previously installed Azure Connector AMP.

  7. Copy the AMP file you downloaded during installation to the amps directory.

  8. Use the Module Management Tool (MMT) to install the AMP into the repository WAR (alfresco.war).

    For more information, see Using the Module Management Tool (MMT)and Install Alfresco Module Package.

    Note: You must install the Azure Connector AMP using -force.

  9. Check that the configuration is set up correctly for your environment.

    Note: When upgrading from Azure Connector version 1.0, make sure you define the Azure authentication mode and a supported value in your file.

    Note: To upgrade a system that’s never used the file system (i.e. on-premises installation without locally saved binaries), we recommend that you choose a pure Azure content store. See Azure Connector content store subsystems for more details.

  10. Starting from version 1.2, the Azure Connector has the deleted content store disabled by default, since this feature is already present in Microsoft’s Azure Storage services. For details on how to re-enable it, see Azure Connector deleted content store.

  11. Start the server.

Known issues

Use this information to identity known issues and limitations while using Azure Connector.

ReactiveX framework that AzureSDK is based on is not working with Security Manager enabled in Tomcat

This usually results in the following exception:

access: access denied ("java.util.PropertyPermission" "jctools.spsc.max.lookahead.step" "read")
    java.lang.Exception: Stack trace
        at java.base/java.lang.Thread.dumpStack(
        at java.base/
        at java.base/
        at java.base/java.lang.SecurityManager.checkPermission(
        at java.base/java.lang.SecurityManager.checkPropertyAccess(
        at java.base/java.lang.System.getProperty(
        at java.base/java.lang.Integer.getInteger(
        at java.base/java.lang.Integer.getInteger(
        at io.reactivex.internal.queue.SpscArrayQueue.<clinit>(
        at io.reactivex.internal.operators.flowable.FlowableFlatMap$MergeSubscriber.getMainQueue(
        at io.reactivex.internal.operators.flowable.FlowableFlatMap$MergeSubscriber.tryEmitScalar(
        at io.reactivex.internal.operators.flowable.FlowableFlatMap$MergeSubscriber.onNext(
        at io.reactivex.internal.operators.flowable.FlowableMap$MapSubscriber.onNext(
        at java.base/
        at java.base/$
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(
        at java.base/java.util.concurrent.ThreadPoolExecutor$
        at java.base/
        at java.base/
 access: domain that failed ProtectionDomain  null
    <no principals>

See for more.

Edit this page

Suggest an edit on GitHub
This website uses cookies in order to offer you the most relevant information. Please accept cookies for optimal performance. This documentation is subject to the Alfresco documentation terms.