It is running on 64-bit environment for both instances. Without
offloading setup, renditions could be processed successfully using
single instance. In offloading setup, I notice that the rendition was
already generated in offloading instance, but could not replicate back
to the author. There seems to have no protocol choice in the replication
agent settings page - it is always HTTP. HTTP method and headers are
configurable thru.There is pretty much disk space left in the temp
folder. Both instan...
Both author and offloading instances had configured sizeLimit attribute
to >2GB (in
and the upload was successful. However when running DAM Update Asset
Offloading workflow there was an error message in author instance.And
the Offloading Reverse Replication Agent started to keep throwingI have
seen the Offloading Reverse Replication Agent is using HTTP GET which I
believe there is another 2GB limit...
MC Stuff wrote... Hi, Can you send latest har after the change? As an
workaround you can add a rewrite rule to add index.html for route access
request. Thanks, This is a har after adding 'DefaultType text/html' to
httpd.conf. pls rename to .zip and unzip. Thank you.
Thanks MC Staff. Had tried the following suggestions but have no luck.
1/ Clear cache directory.2/ Add 'DefaultType text/html' to
httpd.confStill looking into it. Strange thing is that if I put a path
after the hostname in the URL it would work. If anyone has more
suggestion do let me know. I am attaching my httpd.conf here.
When using a dispatcher with an author server, and login from
http://localhost, browsers (chrome & IE) will keep reloading after
pressing the Sign In button.If I login from http://localhost/index.html
or http://localhost/projects.html there is no such issue. Also Safari
has no such issue as well with the path absent.The dispatcher
configuration follows to the sample in the bottom of this page
https://docs.adobe.com/docs/en/dispatcher.html Anyone may have idea?
MC Stuff wrote... Hi terenceleung, Trust store store under
/etc/truststore where as keystore under
/home/users/system/dam/dynamic-media-replication/keystore. You have
following options. 1) Create the config on each envirnoments. OR 2) Want
to use package, include /etc/key also part of package and needs system
restart. OR 3) Part of your build create the configs using curl. Thanks,
Thank you MC Stuff. Including /etc/key in the package (option 2) works
for me. So this should be the crx location st...
Had a private key added to the keystore of a system user
(dynamic-media-replication). Would like to know the crx path(s) that
store the truststore password and private keys inside?I want to include
it in a content package for backup/restore. Exporting with the crx
locaton /home/users/system/dam/dynamic-media-replication/keystore and
restore with it in vanilla AEM is not helping. AEM version:
6.1.0.SP2-CFP7, Feature Pack NPR-8956 The private key was added
according to the steps