Install with zip - Install with zip - Alfresco - Alfresco Transform Service - Alfresco/Alfresco-Transform-Service/4.1/Alfresco-Transform-Service/Install/Install-with-zip - 4.1 - 4.1

In this directory you’ll see the following content including three runnable JAR files, with x.x.x in the names being their version numbers:

• alfresco-shared-file-store-controller-x.x.x.jar
• alfresco-transform-core-aio-boot-x.x.x.jar
• alfresco-transform-router-x.x.x.jar
• README.md
• IPTC Content Model
  • Needs to be bootstrapped into Alfresco Content Services for IPTC Metadata extraction to work, unless you are using Alfresco Content Services version 7.1.0+. See Supported Platforms for more information.

For example, run the following command from the ActiveMQ installation directory:

 bin/activemq start

For more information on installing and configuring ActiveMQ, see the Configure ActiveMQ section in the Alfresco Content Services documentation.

Check the output to ensure that it starts successfully.

Make a note of the TCP URL, with example format tcp://server:port, where server is the host name of the server where ActiveMQ is installed. This is used in later steps.

Content Services uses ActiveMQ for message queuing with various products, including the Transform Service.

 java -DfileStorePath="/path/to/your/AlfrescoFileStore" \
      -Dscheduler.contract.path="/path/to/tempdir/scheduler.json" \
      -jar alfresco-shared-file-store-controller-x.x.x.jar

Check the output to ensure that it starts successfully.

By default, files are stored in fileStorePath=/tmp/Alfresco. This can be modified using the fileStorePath parameter as shown in the above example.

The SFS allows components such as the repository, and the Transform Service to share a common place to store and retrieve files, for example, to enable transforms from an input source file to an output target file.

 java -DPDFRENDERER_EXE="<alfresco-pdf-renderer_installation_dir>/alfresco-pdf-renderer" \
      -DLIBREOFFICE_HOME="<libreoffice_installation_dir>" \
      -DIMAGEMAGICK_ROOT="<imagemagick_installation_dir>" \
      -DIMAGEMAGICK_DYN="<imagemagick_installation_dir>/lib" \
      -DIMAGEMAGICK_EXE="<imagemagick_installation_dir>/bin/convert" \
      -DACTIVEMQ_URL="failover:(tcp://<server>:61616)?timeout=3000" \
      -DFILE_STORE_URL="http://<server>:8099/alfresco/api/-default-/private/sfs/versions/1/file" \
      -jar alfresco-transform-core-aio-boot-x.x.x.jar

For example:

 java -DPDFRENDERER_EXE="/usr/local/acs74/alfresco-pdf-renderer/alfresco-pdf-renderer" \
      -DLIBREOFFICE_HOME="/usr/local/acs74/libreoffice" \
      -DIMAGEMAGICK_ROOT="/usr/local/acs74/imagemagick" \
      -DIMAGEMAGICK_DYN="/usr/local/acs74/imagemagick" \
      -DIMAGEMAGICK_EXE="/usr/local/acs74/imagemagick/convert" \
      -DIMAGEMAGICK_CODERS="/usr/local/acs74/imagemagick/modules-Q16HDRI/coders" \
      -DIMAGEMAGICK_CONFIG="/usr/local/acs74/imagemagick/config-Q16HDRI" \
      -DACTIVEMQ_URL="failover:(tcp://localhost:61616)?timeout=3000" \
      -DFILE_STORE_URL="http://localhost:8099/alfresco/api/-default-/private/sfs/versions/1/file" \
      -jar /usr/local/acs74/bin/alfresco-transform-core-aio-boot-x.x.x.jar

Check the output to ensure that it starts successfully.

The all-in-one core T-Engine combines the five T-Engines (i.e. LibreOffice, ImageMagick, Alfresco PDF Renderer, Tika, and Misc) into one single engine. All functionality that’s available in the five T-Engines is available in the all-in-one core T-Engine. The command-line options provide the paths to the installation locations and the URL of the messaging broker.

 java -DCORE_AIO_QUEUE="org.alfresco.transform.engine.aio.acs" \
      -DCORE_AIO_URL="http://localhost:8090" \
      -DACTIVEMQ_URL="failover:(tcp://localhost:61616)?timeout=3000" \
      -DFILE_STORE_URL="http://localhost:8099/alfresco/api/-default-/private/sfs/versions/1/file" \
      -jar alfresco-transform-router-x.x.x.jar

Check the output to ensure that it starts successfully.

The Transform Router allows simple (single-step) and pipeline (multi-step) transforms that are passed to the Transform Engines. The command-line options provide the router with the required data for T-Engines, queuing, and file-store URL.

 # ActiveMQ properties:
 messaging.broker.url=failover:(tcp://server:61616)?timeout=3000
 messaging.broker.username=$MQUSER
 messaging.broker.password=$MQPASS

 # Shared File Store properties:
 sfs.url=http://localhost:8099
 sfs.endpoint=${sfs.url}/alfresco/api/-default-/private/sfs/versions/1

 # Transform Router properties:
 transform.service.enabled=true
 transform.service.url=http://<Transform Service host>:8095/

 # Transform Core properties:
 localTransform.core-aio.url=http://<Transform Service host>:8090/

This overrides the default properties provided by Content Services.

Files should also be available in the specified path for the alfresco-shared-file-store. However, these files will only temporarily appear in the Shared File Store until explicitly deleted by the repository and/or expired and cleaned up.