Yes, this is one of the way.mvn clean install -PautoInstallPackage -Daem.host=test-author.dev.com -Daem.port=4502 -Daem.author.user=admin -Daem.author.password=admin 

Sometimes it does not work as it suppose to. Instead of caching/excluding configured components, it just returns the entire page. Lets say you configured a component with specific TTL then the expected behavior should be: SDI should intercept the request and send the configured component headers to ...

This is just a one time activity and why do you want to add maintenance overhead via code?

Agree. It's better to create a support ticket and guess this is a bug.

This is just a notification since Java 8 removed the MaxPermSize and this is expected and should work fine. Also, were you able to login to the AEM server after startup? Your server was starting successfully but throwing that warning since its removed since Java 8.

The article briefly talks about installing the AEM server first and this is straight forward before configuring it as a service as well in one of its section. What version of Java are you using and the AEM version?

That seems to be a custom one. The better way would be creating a ticket with Adobe. Have you followed below to disable request access?https://experienceleague.adobe.com/docs/experience-manager-brand-portal/using/admin-tools/access-configurations-brand-portal.html?lang=en#allow-users-to-request-acce...

The SP7 have some issues and Adobe don't recommend to install this but if you need to then you'll have to install a hotfix on top of SP7. I would suggest go for SP8.Thanks,Singaiah

My below articles will give you an overview of the setup: Installing AEM:https://chintalapudi4.medium.com/installing-aem-as-a-service-linux-centos-7-x-7d879259747d Setting up Dispatcher: Try using docker for easy setup but you'll get an idea from this article if you want to setup dispatcher by itsel...

Okay. Try to fix those open issues causing the slowness and it will help you on the long run on the maintenance side as well as improving App One performance. To start with, you can deploy both the code bases to all four publishers and route the App Two traffic to Pub 3 and 4 and App One traffic to ...