Install T-Engine using Docker Compose - Install T-Engine using Docker Compose - Alfresco - Alfresco Outlook Integration - Alfresco/Alfresco-Outlook-Integration/2.8/Alfresco-Outlook-Integration/Alfresco-Outlook-Integration/Install-Outlook-Integration/Install-Transform-Engine/Install-T-Engine-using-Docker-Compose - 2.8

Alfresco Outlook Integration

Platform
Alfresco
Product
Alfresco Outlook Integration
Release
2.8
ft:lastPublication
2026-05-06T19:24:43.034734
ft:locale
en-US
ArchiveStatus
Archived

To deploy the Outlook Integration T-Engine with the Transform Service, you'll need to update your Docker Compose file to include the Outlook T-Engine.

Note

While Docker Compose is often used for production deployments, the Docker Compose file provided is recommended for development and test environments only. Customers are expected to adapt this file to their own requirements, if they intend to use Docker Compose to deploy a production environment.

  1. Add Outlook Integration T-Engine container to your docker-compose.yaml file:

    transform-outlook:
        image: quay.io/alfresco/transform-outlook:1.0.0
        mem_limit: 2g
        environment:
            JAVA_OPTS: " -Xms256m -Xmx512m"
            ACTIVEMQ_URL: "nio://activemq:61616"
            ACTIVEMQ_USER: "admin"
            ACTIVEMQ_PASSWORD: "admin"
            FILE_STORE_URL: "http://shared-file-store:8099/alfresco/api/-default-/private/sfs/versions/1/file"
        ports:
            - 8091:8090
        links:
            - activemq
    
  2. Add the following JAVA_OPTS property to the alfresco container:

    -DlocalTransform.transform-outlook.url=http://transform-outlook:8090/
    
  3. If you're using Content Services 6.2.2 (i.e. not 7.x), you'll need to set the following properties in your Docker Compose file:

    -Dlegacy.transform.service.enabled=false
    -Dlocal.transform.service.enabled=true
    

    Note

    If these settings are missing for Content Services 6.2.2, the transformation of MSG and EML files to PDFs won't work. You can ignore these settings for Content Services 7, as they're already set by default.

See the Content Services documentation - T-Engine configuration for more details. For further development, see Content Transformers and Renditions Extension Points.