Dynamic media scene7 dam:scene7 Publish Pending in Adobe Experince Manager | Community
Skip to main content
RamMandala
RamMandala
Level 2
September 23, 2022
Solved

Dynamic media scene7 dam:scene7 Publish Pending in Adobe Experince Manager

  • September 23, 2022
  • 4 replies
  • 2947 views

We installed SP8(AEM 6.4.8) on Prod servers. Since then we were not able to update the assets (pdf file) to dynamic media. After troubleshooting we found that assets are getting uploaded to scene7 but their metadata is still showing as uploadStarted instead of Publishcompleted. Because of this, assets are always shown as processing in the card view. Also no other properties e.g. scene7 asset url, file, domain company id etc. And are not getting updated to these asset’s on metadata node. This was working fine earlier without Service Pack 8 Installation. Currently also, it is working fine on those servers in lower environments where we have installed SP8.

 

Can you please help me on this issue. 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by RamMandala

Resolution Description: -

  • We have updated the maintenance jobs(/var/workflow/instances/server0), as workflow instances were not cleaning as part of the maintenance job.                Maintenance Jobs Configuration in (/system/console/configMgr) Adobe Granite Workflow Purge Configuration.
  1. Reducing the number of workflow instances increases the performance of the workflow engine, so we can regularly purge completed or running workflow instances from the repository.
  2. Configure Adobe Granite Workflow Purge Configuration to purge workflow instances according to their age and status. we can also purge workflow instances of all models or of a specific model.
  3. We can also create multiple configurations of the service to purge workflow instances that satisfy different criteria. For example, create a configuration that purges the instances of a particular workflow model when they are running for much longer than the expected time. Create another configuration that purges all completed workflows after a certain number of days to minimize the size of the repository.
  • Modified the order of Scene7 (/conf/global/settings/workflow/models/dam/update_asset/jcr:content/flow/scene7upload) step in Dam Update Asset Workflow (in accordance with the QA environment).

After fixing the issue, we have also tested all the DAM Assets e.g., images (. jpg, Png), pdfs, video (.mp4) upload and they are working fine as expected.

4 replies

D
Adobe Employee
digarg17Adobe Employee
Adobe Employee
September 26, 2022

Hi @rammandala   : what is the size of pdf you tried uploading ?

is the issue only with large size pdf assets  or is it with all mimetypes (jpegs/png's) and all sizes?

I would recommend checking your workflow instances and logs and see for any issues . You can check and compare OOTB scene7 instance workflow models and see all hander advances are checked.

Try uploading same pdf on all lower/higher instance and see if issue is with the asset or with DM configuration.

    RamMandala
    RamMandalaAuthor
    Level 2
    September 26, 2022

    Thank you @digarg17 for reply.

     

    We are uploaded 100KB to 5 MB pdf files not huge files. This issue for only PDF files not for images.

    we tested same files in lower environments like dev, test, pre-prod it is working fine. but issue in prod.

     

     

      RamMandala
      RamMandalaAuthor
      Level 2
      September 26, 2022

      I found in error log below error.

       

      26.09.2022 13:34:48.219*ERROR* [194.50.160.200 [166419208823404] GET /mnt/overlay/dam/gui/coral/content/commons/sidepanels/renditions.html/content/dam/project/downloads/Santabd.pdf HTTP/1.1] com.day.cq.dam.s7dam.common.smartcrop.DMSmartCropResource Unable to read property!
      javax.jcr.PathNotFoundException: jcr:content/metadata/dam:scene7File not found on /content/dam/project/downloads/Santabd.pdf
      at org.apache.jackrabbit.oak.jcr.session.NodeImpl$11.perform(NodeImpl.java:636) [org.apache.jackrabbit.oak-jcr:1.8.20]
      at org.apache.jackrabbit.oak.jcr.session.NodeImpl$11.perform(NodeImpl.java:629) [org.apache.jackrabbit.oak-jcr:1.8.20]
      at org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.perform(SessionDelegate.java:207) [org.apache.jackrabbit.oak-jcr:1.8.20]
      at org.apache.jackrabbit.oak.jcr.session.ItemImpl.perform(ItemImpl.java:112) [org.apache.jackrabbit.oak-jcr:1.8.20]
      at org.apache.jackrabbit.oak.jcr.session.NodeImpl.getProperty(NodeImpl.java:629) [org.apache.jackrabbit.oak-jcr:1.8.20]
      at com.day.cq.dam.s7dam.common.smartcrop.DMSmartCropResource.readProperty(DMSmartCropResource.java:88) [com.day.cq.dam.cq-dam-s7dam:5.11.188]
      at com.day.cq.dam.s7dam.common.smartcrop.DMSmartCropResource.getFileName(DMSmartCropResource.java:62) [com.day.cq.dam.cq-dam-s7dam:5.11.188]
      at com.day.cq.dam.s7dam.common.smartcrop.DMSmartCropResource.isValid(DMSmartCropResource.java:73) [com.day.cq.dam.cq-dam-s7dam:5.11.188]
      at com.day.cq.dam.s7dam.common.datasource.SmartCropDataSource.colate(SmartCropDataSource.java:148) [com.day.cq.dam.cq-dam-s7dam:5.11.188]
      at com.day.cq.dam.s7dam.common.datasource.SmartCropDataSource.<init>(SmartCropDataSource.java:69) [com.day.cq.dam.cq-dam-s7dam:5.11.188]
      at com.day.cq.dam.s7dam.common.servlets.SmartCropDataSourceServlet.doGet(SmartCropDataSourceServlet.java:97) [com.day.cq.dam.cq-dam-s7dam:5.11.188]

        diksha_mishra
        Community Advisor
        diksha_mishraCommunity Advisor
        Community Advisor
        September 26, 2022

        @rammandala In order to enable the PDF upload to Dynamic Media for AEM, please got to this path in CRXDE:

        /conf/global/settings/cloudconfigs/dmscene7/jcr:content/mimeTypes/application_pdf

        Enabled=true

        Save All

        Note: PDF isn't allowed to be served via DM. I recommend opening a support ticket with Adobe and getting a confirmation.

         

          D
          Adobe Employee
          digarg17Adobe Employee
          Adobe Employee
          September 26, 2022

          @rammandala @diksha_mishra  : For me PDF upload to DM works seamlessly without making any explicit change in crxde. (testing on 6.5)

          https://github.com/AdobeDocs/experience-manager-64.en/blob/main/help/assets/assets-formats.md

          Configuration in crxde : 

          Enabled = true

          pdfprocess=Rasterize&resolution=150&colorspace=Auto&pdfbrochure=true&keywords=true&links=true

          Can you find the uploaded pdf in DM , use search and see if PDFis in DM.If exists in DM,  is It

          published and the Dynamic url's generated in DM like below?

          what do you see in workflow instances status in AEM?

          Any errors in AEM logs?

          Can you also recheck scene7 configuration and make sure you are uploading in correct folder.

           

            RamMandala
            RamMandalaAuthor
            Level 2
            September 26, 2022

            26.09.2022 13:34:48.219*ERROR* [194.50.160.200 [166419208823404] GET /mnt/overlay/dam/gui/coral/content/commons/sidepanels/renditions.html/content/dam/project/downloads/Santabd.pdf HTTP/1.1] com.day.cq.dam.s7dam.common.smartcrop.DMSmartCropResource Unable to read property!
            javax.jcr.PathNotFoundException: jcr:content/metadata/dam:scene7File not found on /content/dam/project/downloads/Santabd.pdf
            at org.apache.jackrabbit.oak.jcr.session.NodeImpl$11.perform(NodeImpl.java:636) [org.apache.jackrabbit.oak-jcr:1.8.20]
            at org.apache.jackrabbit.oak.jcr.session.NodeImpl$11.perform(NodeImpl.java:629) [org.apache.jackrabbit.oak-jcr:1.8.20]
            at org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.perform(SessionDelegate.java:207) [org.apache.jackrabbit.oak-jcr:1.8.20]
            at org.apache.jackrabbit.oak.jcr.session.ItemImpl.perform(ItemImpl.java:112) [org.apache.jackrabbit.oak-jcr:1.8.20]
            at org.apache.jackrabbit.oak.jcr.session.NodeImpl.getProperty(NodeImpl.java:629) [org.apache.jackrabbit.oak-jcr:1.8.20]
            at com.day.cq.dam.s7dam.common.smartcrop.DMSmartCropResource.readProperty(DMSmartCropResource.java:88) [com.day.cq.dam.cq-dam-s7dam:5.11.188]
            at com.day.cq.dam.s7dam.common.smartcrop.DMSmartCropResource.getFileName(DMSmartCropResource.java:62) [com.day.cq.dam.cq-dam-s7dam:5.11.188]
            at com.day.cq.dam.s7dam.common.smartcrop.DMSmartCropResource.isValid(DMSmartCropResource.java:73) [com.day.cq.dam.cq-dam-s7dam:5.11.188]
            at com.day.cq.dam.s7dam.common.datasource.SmartCropDataSource.colate(SmartCropDataSource.java:148) [com.day.cq.dam.cq-dam-s7dam:5.11.188]
            at com.day.cq.dam.s7dam.common.datasource.SmartCropDataSource.<init>(SmartCropDataSource.java:69) [com.day.cq.dam.cq-dam-s7dam:5.11.188]
            at com.day.cq.dam.s7dam.common.servlets.SmartCropDataSourceServlet.doGet(SmartCropDataSourceServlet.java:97) [com.day.cq.dam.cq-dam-s7dam:5.11.188]
            at org.apache.sling.api.servlets.SlingSafeMethodsServlet.mayService(SlingSafeMethodsServlet.java:266) [org.apache.sling.api:2.20.0]

              RamMandala
              RamMandalaAuthor
              Level 2
              October 13, 2022

              Can you please help me any one still having issue. not resolved this issue.

                RamMandala
                RamMandalaAuthorAccepted solution
                Level 2
                October 17, 2022

                Resolution Description: -

                • We have updated the maintenance jobs(/var/workflow/instances/server0), as workflow instances were not cleaning as part of the maintenance job.                Maintenance Jobs Configuration in (/system/console/configMgr) Adobe Granite Workflow Purge Configuration.
                1. Reducing the number of workflow instances increases the performance of the workflow engine, so we can regularly purge completed or running workflow instances from the repository.
                2. Configure Adobe Granite Workflow Purge Configuration to purge workflow instances according to their age and status. we can also purge workflow instances of all models or of a specific model.
                3. We can also create multiple configurations of the service to purge workflow instances that satisfy different criteria. For example, create a configuration that purges the instances of a particular workflow model when they are running for much longer than the expected time. Create another configuration that purges all completed workflows after a certain number of days to minimize the size of the repository.
                • Modified the order of Scene7 (/conf/global/settings/workflow/models/dam/update_asset/jcr:content/flow/scene7upload) step in Dam Update Asset Workflow (in accordance with the QA environment).

                After fixing the issue, we have also tested all the DAM Assets e.g., images (. jpg, Png), pdfs, video (.mp4) upload and they are working fine as expected.

                  Terms & ConditionsAccessibility statement

                  Loading footer...