Installing Packages and Disabling Workflow Launchers on Local Instance

How to Work with Packages

https://helpx.adobe.com/experience-manager/6-5/sites/administering/using/package-manager.html

Installing Large Packages on Local Instance

https://edivad.wordpress.com/2013/01/07/installing-big-packages-in-cq5crx/

ONLY FOR LOCAL INSTANCE

Installing large packages is an extremely slow process and is super taxing on the system and browser.  Often, the installs will end up erroring out or bogging down the server. A better way to install large packages:

1.    See Disable/Enable Workflow Launchers section below

2.    Create install folder under crx-quickstart (/path/to/cq/crx-quickstart/install)

3.    Copy package to install folder

4.    The package will automatically install 

5.    Apparently, you cannot delete the packages from the install folder or this will trigger the uninstallation of the package.  I need to verify it.

Disable/Enable Workflow Launchers on Local Instance

https://sourcedcode.com/how-to-enable-or-disable-aem-workflow-launchers

When importing DAM packages, each DAM upload/edit will fire a workflow for the post-processing of metadata and renditions. When installing large packages, the server will likely get bogged down and often the installs fail.  Before installing packages, it’s a great idea to disable the two workflow launchers.  Probably a good idea to reactivate these once you’ve finished installing the packages.

6.    Go to  http://localhost:4502/system/console/components

7.    Using the browser search, search for workflowlauncher to locate these:

com.adobe.granite.workflow.core.launcher.WorkflowLauncherImpl

com.adobe.granite.workflow.core.launcher.WorkflowLauncherListener

8.    Click on the square button to disable the service OR the arrow button to activate the service

9.    If you receive a dialog showing “Request Failed”, just refresh the page and check the status of the services again. The action was still honored, in my experience.