Uploaded assets Not Available from Dynamic Media Scene7 delivery
This KB article provides the points to check when an asset uploaded into AEM and expected to be available from the DMS7 delivery servers is not available.
Description description
Description : There are quite a few reasons why an asset uploaded into AEM and expected to be available from DMS7 deivery is in fact not. This KB article goes over them to help debug and address the concern.
Resolution resolution
The first few points are to debug when the image is not being replicated to DMS7. This can be verified by logging into DMC and searching for the image.
DMC UI can be downloaded here: https://docs.adobe.com/content/help/en/dynamic-media-classic/using/new-ui-2020.html
- There is no DynamicMedia CloudConfiguration
In AEM - hammer - Cloud Services - Dynamic Media Configuration, there should be a DynamicMedia configuration under the global tab. If it is not there, that would be the first reason why no sync is hapening. Some customers have project specific DMS7 config, per the documentation this is not recommended.
- The DynamicMedia CloudConfiguration is setup with the setting “sync all content” unchecked.
In AEM - hammer - Cloud Services - Dynamic Media Configuration, there should be a DynamicMedia configuration under the global tab. When editing it, there is a checkbox “sync all content”. If checked, all AEM content supported by DM will be synced to the DMS7 backoffice. If unchecked, there is an option per folder to sync or refrain from syncing to DMS7. If a folder is configured not to sync, that would be the reason why the assets in the folder don’t make it to DMS7.
- The password for the DMS7 login might have been changed or expired.
In AEM - hammer - Cloud Services - Dynamic Media Configuration, there should be a DynamicMedia configuration under the global tab. When editing it, there is a field “email” with the DMS7 login used for the sync. The owner of that email address might have changed the password, or the password might have expired. It is recommended to make use of a user-independent login and set the password to never expire (30000 days or so) to prevent this concern.
The next points are to debug further when the asset in question is replicated to DMS7, but not available from DMS7 delivery
- Asset was not activated
In AEM - hammer - Cloud Services - Dynamic Media Configuration, there should be a DynamicMedia configuration under the global tab. When editing it, there is a setting: “Publish assets”. hen this setting is set to “Upon activation” or “Selective Publish”, then an activation/publish to DynamicMedia needs to be performed in order to flip the publish flag at te DMS7 end. In the DMC UI you can verify whether the asset in question has a green tick. If not, the publishing action was not received. You can search in the DM splunk and there should be an entry with setAssetPublishState with the assethandle of the asset in question. If this is not there, then it was not sent from AEM, and issue might need to be further investigated at AEM side.
- Asset was activated, but remains unavailable
It could be the replication from AEM to DMS7 went well and the AEM Asset metadata indicates everything went successfully, but asset is still not available using DMS7 URL. if this is the case, have a look at the job logs in IPS for the asset. It could be one or the other action to publish the asset from DMS7 backoffice to delivery was not successful. This could be a job log entry that looks like:
yyyy-mm-dd hhss AssetName Unable to push ‘./company/AssetName’ to the server load balanced CS Live IS
This would indicate the writing of the catralog server entry to the catalog server was not successful. This entry forms the reference between the asset name and the physical location of the asset payload. This entry missing means the asset cannot be found. The DMS7 backoffice runs a validate job to fix any such entries every 24 hrs, but until it runs, the asset will remain unavailable. Customer can reprocess the asset in AEM to fix.