Hey Ronnie:So, first disclaimer: the only ones allowed to talk pricing specifics are Adobe Sales.  Partners like myself, even if we know pricing, aren't allowed to share it.That being said, the pricing model for AEMaaCS is counted by page view / API call.  When the contract is first signed, you work...

Additionally you should keep your eye peeled for this session at AdaptTo() at the end of October: https://adapt.to/2024/schedule/aem-65-and-java-17 AEM only supported JDK8 up to 6.5, and now only supports JDK8 and JDK11.  Making AEM support JDK17 will likely result in an entirely new version of AEM ...

As @kautuk_sahni mentioned, the only place to get accurate pricing information for your AEMaaCS program is from Adobe Sales via your Customer Success Manager. That being said, by & large, on new implementations, Adobe generally prices AEM as a Cloud Service by aggregate pageview/API call count.  If ...

This looks like an authentication problem with your Scene7 credentials in cloudservices config.  Are you getting this only for a subset of images or all of them?  Have you tried recycling your S7 credentials?

The Content Transfer Tool doesn't require (or care) that your source and destination are in the same org, as that's not at all how they authenticate.   A primary use case for the CTT (and how I've used it in almost every case) is to transfer from an on-prem 6.5 environment to AEM as a Cloud Service,...

Hi Anantha - A few answers to your question.  First of all, I'm sure others have likely advised as much, but you'll definitely want to upgrade this installation as urgently as possible off of AEM 6.0 to AEM 6.5 with the latest service pack.  In addition to being EOL since 2018, AEM 6.0 was also the ...

Hi Mahesh -In order to truly explore this feature, you're going to need a Dynamic Media account to to work with.  Dynamic Media is an entirely separate SKU from AEM or AEM Cloud Service, so it's not available to you unless provisioned by your company.  However, if your company is an Adobe Partner, y...

You want to run the revision GC (i.e. tar compaction) before the Datastore GC.  The Datastore GC depends on the revision GC to know what blobs it can remove that are no longer referenced.  A Datastore GC run by itself (i.e. without any revision GC) won't reclaim anything.  So, let's say you run a fu...

100% seconded on this.  Cache flush for CDN and for Dispatcher tier would absolutely be useful for any environment.  Yes, more-evolved enterprise deployments will have this built into other Jenkins or ADO orchestration that they're using, but having an ad-hoc OOTB flush for CDN and dispatcher would ...

Hey Roberto - In overly-simplistic terms, the Segmentstore contains all of the metadata about each of the nodes in the repository, including the content tree itself, and all of the textual information about each node.  The Datastore is used for larger objects that need to be stored in AEM, which cou...