AEM Publish Package Manager

Hi @nsvsrk,

Working with a brand new AEM Publish instance and trying to install some packages using the same Package Manager URL as Author - just changing the port to match Publish.

Here’s what you are observing and looking for some clarity:

Issue 1: No Packages Visible in Package Manager on Publish

Yes, this can be expected on a fresh Publish install - but there’s also a very common gotcha here:

Are you logged in as an admin?

Unlike Author, the Publish instance doesn’t auto-login, and if you're not authenticated (or logged in as an insufficiently privileged user), the Package Manager may appear empty — or you won’t even have permissions to upload/install packages.

What to do:

• Go to: http://localhost:4503/libs/granite/core/content/login.html

• Then enter the admin credentials (default: admin / admin, unless changed).

• After login, go back to the Package Manager URL: http://localhost:4503/crx/packmgr/index.jsp

• Once logged in, you should be able to upload and view packages — assuming none have been installed yet.

Issue 2: Error: “The tree does not exist” when installing package

This typically means your package is trying to install content/code to a path that doesn’t yet exist in the repository — or relies on something not available yet.

What to Check:

• Open the package and look at the filter.xml (in META-INF/vault/).

• Check if your filters reference paths like /content/mysite, /apps/myproject, etc.

• Ensure any required parent structures or templates/components are already deployed on Publish before pushing content.

Example:

If your package includes pages under /content/mysite, but the corresponding site structure or templates under /apps haven’t been installed yet - it will fail.