cannot start SP slipstream version of AEM in demo-machine

[adobe-marketing-cloud]

cannot start SP slipstream version of AEM in demo-machine

[coatpont]

I'm not familiar with this "custom AEM jar" process - however the demo machine does support the installation of service packs. in the /dist/bin folder, assuming your AEM jar file is something like aem62.jar, then just place the service pack file in the same folder with the -sp suffix (e.g. aem62-sp.zip) and if the demo.servicepack properties is set to true (it's the default value), then AEM will be installed with this service pack upfront (entire instance booting up with the service pack code). Can you review/test and close this issue if it works for you? (this method is the one tested by our QE organization)

[chrismade]

yes, I confirm it is working

for a JAR file like:
cq61-author-4502.jar
the corresponding Service Pack has to be:
cq61-author-4502-sp.zip
both files in dist/bin folder
BTW: for the demo machine I'd rather rename cq61-author-4502.jar to cq61.jar as role and port will be set by properties later by script

and for hotfixes:
a directory dist/hotfixes/all
must be created - containing the files like
cq-6.1.0-hotfix-8651-1.2.zip
cq-6.1.0-hotfix-9113-1.0.zip
etc
"all" contains the hot fixes which belongs to core AEM - whereas there might be also hotfixes for packages (folder has then package name instead of 'all' )

Either I missed that reading the wiki - or it is not there (please copy/paste from here if this is the case)

case can be closed - thanks for support on weekends ;-)