Vous consultez actuellement l'aide de la version:

Assets workflow offloader lets you enable multiple instances of Adobe Experience Manager (AEM) Assets to reduce the processing load on the primary (Leader) instance. The processing load is distributed among the leader instance and the various offloader instances that you add to it. Distributing the processing load of assets increases the efficiency and speed with which AEM Assets processes assets. In addition, it helps allocate dedicated resources to process assets of a particular MIME type. For example, you can allocate a specific node in you topology to process InDesign assets only. 

Configure offloader topology

Use Configuration Manager to add the URL for the leader instance and the host names of offloader instances for connection requests on the Leader instance.

  1. Click/tap the AEM logo, and choose Tools > OperationsWeb Console to open Configuration Manager.

  2. From the Web Console, select Sling > Topology Management.

    chlimage_1
  3. In the Topology Management page, click/tap the Configure Discovery.Oak Service link.

    chlimage_1
  4. In the Discovery Service Configuration page, specify the connector URL for the Leader instance in the Topology Connector URLs field.

    chlimage_1
  5. In the Topology Connector Whitelist field, specify IP address or host names of offloader instances that are allowed to connect with the Leader instance. Click Save.

    chlimage_1
  6. To see the offloader instances connected to the Leader instance, go to Tools > Deployment > Topology and click the Cluster view.

Disable offloading

  1. Click/tap the AEM logo, and choose Tools > Deployment > Offloading. The Offloading Browser page displays topics and the server instances that can consume the topics.

    chlimage_1
  2. Disable the com/adobe/granite/workflow/offloading topic on the leader instances with which users interact to upload or change AEM assets.

    chlimage_1

Configure workflow launchers

Configure workflow launchers to use the DAM Update Asset Offloading workflow on the Leader instance instead of the Dam Update Asset workflow.

  1. Click/tap the AEM logo, and choose, Tools > Workflow > Launchers to open the Workflow Launchers console.

    chlimage_1
  2. Locate the two Launcher configurations with event type Node Created and Node Modified respectively, which run the DAM Update Asset workflow.

  3. For each configuration, select the checkbox before it and click/tap the View Properties icon from the toolbar to display the Launcher Properties dialog.

    chlimage_1
  4. From the Workflow list, choose DAM Update Asset Offloading and click Save.

    chlimage_1
  5. Click/tap the AEM logo, and choose, Tools > Workflow > Models to open the Workflow Models page.

  6. Select the DAM Update Asset Offloading workflow, and click Edit from the toolbar to display its details.

    chlimage_1
  7. Right-click the DAM Workflow Offloading step, and choose Edit from the content menu. Verify the entry in the Job Topic field of the Generic Arguments tab of the configuration dialog.

    chlimage_1

Disable the workflow launchers

Disable the workflow launchers that run the DAM Update Asset workflow on the Leader instance.

  1. Click/tap the AEM logo, and choose, Tools > Workflow > Launchers to open the Workflow Launchers console.

    chlimage_1
  2. Locate the two Launcher configurations with event type Node Created and Node Modified respectively, which run the DAM Update Asset workflow.

  3. For each configuration, select the checkbox before it and click/tap the View Properties icon from the toolbar to display the Launcher Properties dialog.

    chlimage_1
  4. In the Activate section, drag the slider to disable the workflow launcher and click/tap Save to disable it.

    chlimage_1
  5. Upload any asset of type image at the Leader instance. Verify the thumbnails generated and ported back for the asset by the offloader instance.

Ce produit est distribué sous licence Creative Commons Attribution - Pas d’utilisation commerciale - Partage à l’identique 3.0 non transposé  Les publications Twitter™ et Facebook ne sont pas couvertes par les dispositions Creative Commons.

Mentions légales   |   Politique de confidentialité en ligne