Contrary to my comment last May, I've got some more up-to-date info that
AEM Communities has no plans for support in AEM as a Cloud Service (see:
What’s the Future of AEM Communities? – OpsInventor). So, if you're
looking to do communities, your only bets are to either (a) design your
own bespoke solution or (b) stay on the on-premise AEM 6.5 for the time
being. @Arun_Patidar @Nirmal_Jose
Hi Marc - I'm just coming back to this here, as I haven't had luck with
getting any other answers from Adobe. What I'm referring to here with my
question is not using Solr as an AEM index, but using Solr as part of
the MSRP arrangement, which (to my understanding) doesn't offer the same
design constraints as you mentioned in your answer. Do you know what the
current recommended version for Solr in an MSRP architecture is?
Hey Peter - thanks for the comment. Unfortunately I don't get plugin
stats / caching metrics, as this implementation is still on ye olde Solr
5.5, as that was what Adobe recommended and they've still not updated
their official recommendation on what Solr version to use for MSRP. I'm
asking again to see if they've changed their tune and can officially
recommend Solr 8 yet.
I am looking for help from anyone who has run AEM Communities, on how to
best optimize for performance. An AEM Communities site I am supporting,
backed by MongoDB & SolrCloud (MSRP) is running into severe performance
constraints. The performance constraints stem from the sheer number of
calls our blog pages are making back to Solr, and I've not found any
good way as yet to optimize such. The site primarily uses Communities
for blog post likes, comments and comment likes, on which the
out-of-the-...
@pegr69 as far as I know, this is not configurable. This was
intentionally removed in AEM 6.5.5 along with PackageShare.
http://www.jetteroheller.com/package-share-discontinued-on-aem-6-5-5-0-aem-6-5-sp5/
Thanks for this - but this quotes the same documentation as above, which
I'm suspecting is out of date. OpenOffice 4.1.2 came out over 5 years
ago, and there have been multiple releases of LibreOffice since then
which provide speed & stability enhancements. I'm just trying to find
out if there are any reasons why these would not be supported in AEM
Forms.
@Arun_Patidar from everything I've heard so far, it's still absolutely
the plan to provide AEM Communities support on AEM as a Cloud Service -
/eventually/. Just like Forms, Screens, Commerce, InDesign Server, etc,
it's got a lot of work to do in order to make it work containerized in
the new infra. But it's not being discontinued.
@Abi-sr It is absolutely possible to have your AEM Assets instance
hosted on a private cloud, on-premise, or at AWS. The version you'd be
deploying on this would not be the "AEM as a Cloud Service" version, but
would be the latest version of self-hosted AEM which at this time is AEM
6.5.4. I wrote a post here which gives some pros & cons for running AEM
on-premise, which absolutely still can be done and most people still do.
http://www.jetteroheller.com/aem-as-a-cloud-service-tech-qa-and-should-...
An AEM 6.5 Assets environment I am working with presently uses the PDF
Generator service to convert PowerPoint files (pptx) from PPTX -> PDF
for downloads as well as text extraction & indexing. It is currently
running into various performance problems, and the version of
soffice.bin that it's running is potentially to blame as it is currently
running LibreOffice 4.3.2 on the server, a version that was release in
the spring of 2015. However, in Adobe docs
(https://docs.adobe.com/content/help/en/e...
