How to work with packages (2023)

The packages allow the import and export of the contents of the repository.For example, you can use packages to install a new functionality, transfer content between instances and make a backup copy of repository content.

You can access and/or maintain packages on the following pages:

  • Packaging manager, which he uses to manage the packages in his local AEM instance.

  • Share the package, a centralized server that has publicly available packages as private to your company.Public packages may contain hotes, new features, documentation, etc.

You can transfer packages between the package administrator, the shared package feature and your file system.

What are the packages?

One package is an ZIP file that contains repository content in the form of file system serialization (called "vault" serialization).This provides an easy representation to use and edit files and folders.

Packages include page content and project -related project, selected using filters.

A package also contains safe information, including filter settings and import configuration information.Additional content properties (which are not used for packet extraction) can be included in the package, such as a description, a visual image or an icon;These properties are for the consumer of the content package and only for informative purposes.

To use

The packages represent the current version of the content when the package is built.They do not include previous versions of the AEM content keeps in the repository.

You can perform the following actions in or with packages:

  • Create new packages;Definition of packet configuration and filters as needed
  • Visualization of the package content (before compilation)
  • Build packages
  • See the package information
  • See the package content (after compilation)
  • Modify the definition of existing packages
  • Rebuild existing packages
  • Compensate the packages
  • Download the AEM packages to your file system
  • Carry packages of your file system in your local instance of AEM
  • Validate the package content before installation
  • Perform a dry execution installation
  • Install the packages (AEM does not automatically install the packages after loading)
  • Eliminate packages
  • Download packages, such as Hotfixes, from the shared package library
  • Increases packages for the company's internal section

Package information

A package definition consists of various types of information:

  • Package configuration
  • Package filters
  • Screen Captures
  • Package icons

Package configuration

You can edit a variety of packet settings to define aspects such as package description, related errors, facilities and supplier information.

HePackage configurationThe dialogue is available throughTo editbutton whencreatureoedicióna package and provide three guides for configuration.After making any changes, clickACCORDINGLYTo save them.

How to work with packages (1)

NameThe name of the package.
GroupThe group name to add the package to organize packages.Write the name of a new group or select an existing group.
VersionText to be used for the custom version.
DescriptionA brief description of the package.The marked HTML can be used to format.
ThumbnailThe icon that appears on the package list.Click Examine to select a local file.

How to work with packages (2)

Campo Description Format/example
Name The name of the supplier. AEM GeomeTrixx
Url Supplier URL.
Link Link to the specific package for a supplier page.
  • ADM: Select when the package can only be installed through an account with administrator privileges.
  • Restart: Select when the server is required to restart after the package installation.

Specify how defined access control information is treated in the package when the package is imported:

  • Ignore
  • Replacing
  • Link
  • Clear
  • Micial

The default value isIgnore.

  • Ignore- Preserve ACL in the repository
  • Replacing- Replacing ACL in the repository
  • Link- Merge the two ACL sets
  • Clear- ACLS transparente
  • Micial- Fusion control of access to content with the proportion with the package by adding the access control inputs of directors that are not present in the content

How to work with packages (3)

Tested withThe name and version of the product this package is directed or compatible.To stretch
Errors/problems were correctedA text field that allows you to list the details of the errors resolved with this package.Include each error in a separate line.Bug Summary
Depends onList dependence information that must be respected whenever other packages are necessary to allow the current package to be performed as expected.This field is important when hotels are used.Groupid: Name: Version
ReplacementA list of disabled packages that replace this package.Before installing, make sure this package includes all necessary content from obsolete packages so that the content is not replaced.Groupid: Name: Version

Package filters

The filters identify the nodes of the repository to include in the package.Filter DefinitionSpecifies the following information:

  • HeRoot Roadcontent to include.
  • Standardswhich include or exclude specific nodes below the root route.

Filters may include zero or more rules.When no rule is defined, the package contains all the content of the root route.

You can set one or more filter definitions for a package.You are more than one filter to include multiple root routes.

How to work with packages (4)

The following table describes these rules and provides examples:

Rule type Description Example
include You can set a route or use a regular expression to specify all nodes you want to include.

Including a directory:

  • Include this directoryyAll files and folders in this directory (ie the whole sub -lé)
  • noInclude other files or folders of the specified root route
delete You can specify a route or use a regular expression to specify all nodes you want to delete.

Deleting a directory will exclude this directoryyAll files and folders in this directory (ie the whole sub -Tree).


To use

A package can contain several filter definitions so that we from different locations can be easily combined in a package.

Packet filters are defined more often when firstCreate the packagebut they can also be edited later (after which the package must be rebuilt).

Screen Captures

You can attach screenshots to your package to provide a visual representation of how the content is seen;For example, providing new functionality screen captures.

Package icons

You can also attach an icon to your package to provide a quick reference visual representation of what the package contains.It is then shown on the package list and can help it easily identify the Package or Package class.

As a package may contain an icon, the following conventions are used for official packages:

To use

To avoid confusion, use a descriptive icon for your package and do not use one of the official icons.

Official Hotfix Package:

How to work with packages (5)

Official Install of Extensión Paqueto:

Official characteristics packages:

How to work with packages (6)

Packaging manager

The package administrator manages the packages in its local AEM installation.attributed the necessary licensesYou can use the packet administrator for multiple actions, including configuration, construction, download and installation of your packages.The main elements to be configured are:

  • Package configuration
  • Package filters

Necessary permissions to use the package administrator

To give users the right to create, modify, load and install packages, you must provide the appropriate licenses at the following locations:

  • /etc/packages(Complete rights excluding eliminating)
  • The knot that contains the package content

VerAllows the configurationFor instructions on licensing change.

Creating a new package

To create a new package definition:

  1. On the AEM's good -vindas screen, clickpackages(or fromToolsClick console twicepackages).

  2. Then selectPackaging manager.

  3. ClickCreate Package.

    To use

    If your instance has many packages, there may be a folder structure in your place so you can navigate to the required destination folder before creating the new package.

  4. No dialogue:

    How to work with packages (7)


    • Group's name

      The name of the destination group (or folder).Groups should be used to help organize their packages.

      A folder will be created for the group if it does not yet exist.If you leave the name of the group blank, you will create the package on the list of main packages (start packages>).

    • Package name

      The name of your new package.Select a descriptive name to help you easily identify the package content.

      (Video) Project Task Descriptions - Work Packages

    • Version

      A textual field to indicate a version.This will be added to the package name to form the name of the ZIP file.

    ClickACCORDINGLYTo create the package.

  5. List the new package in the appropriate group folder.

    How to work with packages (8)

    Click on the package icon or name to open.

    How to work with packages (9)

    To use

    You can return to this page later if necessary.

  6. ClickTo editTo edit thePackage configuration.

    Here you can add information and/or define certain settings;For example, this includes a description, theicon, related errors and add supplier details.

    ClickACCORDINGLYAfter finishing editing the configuration.

  7. To addScreen Capturesto the package as needed.An instance is available when the package is created, add more if necessary usingPackage screen captureThey companion.

    Add the actual image by twice by clicking to the image component in theScreen CapturesArea, add an image and clickACCORDINGLY.

  8. Define APackage filtersdragging instances fromFilter DefinitionFrom Bureau, click twice to open:

    How to work with packages (10)

    To specify:

    • Root Road
      The content of being packed;This may be the root of a subtree.

    • Standards
      The rules are optional;For simple packet definitions, it is not necessary to specify include or exclude rules.

      If necessary, you can define someoneInclude or exclude rulesTo define exactly the contents of the package.

      Add rules using the+ +symbol, remove alternately the rules using the-symbol.The rules apply according to their order, so that it puts them according to what is necessary using theAboveyBelowbuttons.

    So clickACCORDINGLYTo save the filter.

    To use

    You can use how many filter definitions are needed, although cared for they should ensure that they do not trust conflicts.AdvanceTo confirm what the package content will be.

  9. To confirm what will keep the package you can useAdvanceThis performs a dry execution of the compilation process and lists everything that will be added to the package when it is actually built.

  10. Now you canBuildYour luggage.

    To use

    It is not mandatory to build the package at this time, this can be done later.

Build a package

A package is often built at the same time asCreate the definition of the package, but you can later return to build or rebuild the package.This can be useful if the repository content has changed.

To use

Before building the package, it may be helpful to obtain a preview of the package content.To clickAdvance.

  1. Open the definition of thePackaging manager(Click on the package icon or name).

  2. ClickBuild.A dialogue requests confirmation that you want to build the package.

    To use

    This is of particular importance when reconstructing a package, as the package content will be replaced.

  3. ClickACCORDINGLY.In will create the package by listing all the content added to the package while doing so.When I am completely confirming the confirmation that the package was built and (when the dialog box closes) updates the information on the package list.


After a package was built, it can be written again if necessary.

Re -approval changes package information -sinChange the contents of the package.Package information is the miniature, description, etc., in other words, everything you can edit with thePackage configurationDialogue (to open this clickTo edit).

An important use case for relocation is when preparing a package for the shared package.For example, you may have an existing package and decide to share it with other people.For this you want to add a miniature and add a package.All its functionality (which can take some time and risks the package no longer identical to the original), can rewrite it and simply add the miniature and description.

  1. Open the definition of thePackaging manager(Click on the package icon or name).

  2. ClickTo editand update thePackage configurationas necessary.ClickACCORDINGLYto save.

  3. ClickCompensate, a dialogue will request confirmation.

See and edit package information

To see the edit information about packet definition:

  1. In the administrator package, navigate to the package you want to see.

  2. Click on the package icon you want to see.This will open the list information on the package page in the package setting:

    How to work with packages (11)

    To use

    You can also edit and perform certain actions in the package of this page.

    The available buttons will depend on whether the package has already been built or not.

    (Video) Work Packages

  3. If the package has already been built, clickSatisfied, a window will open and list all the contents of the package:

See the package content and the test installation

After building a package, you can see the content:

  1. In the administrator package, navigate to the package you want to see.

  2. Click on the package icon you want to see.This will open the list information on the package page in the package setting.

  3. To see the content, clickSatisfied, a window will open and list all the contents of the package:

    How to work with packages (12)

  4. To make a dry execution of the installation, clickTest installationAfter confirming the action, a window will open and list the results as if the installation was performed:

    How to work with packages (13)

Download the package for your file system

This section describes how to download an AEM package to your file system usingPackaging manager.

To use

VerShare the packageFor information on downloading hotfixes, characteristics packages and public packages and your company's internal area sharing.

Of the shared package you can:

  • Download packagesPackage share directly in your local instance of AEM.
    When downloading, the package is imported to your repository, after which you can install it immediately in your local instance using thePackaging manager.The packages include hotes and other shared packages.

  • Download packagesShare the package on your file system.

  1. On the AEM's good -vindas screen, clickpackages, then selectPackaging manager.

  2. Browse to the package you want to download.

    How to work with packages (14)

  3. Click on the link formed by the name of the Zip File (underlined) to the package you want to download;for exampleexport

    AEM downloads the package to your computer (using a standard browser dialog box).

Package load from your file system

A package load allows you to load a package of your file system on the AEM package administrator.

To use

VerPackage load for the internal shared companyTo raise a package for your company's private package sharing area.

To increase a package:

  1. NavigatePackaging manager.Tho for the group folder where you want the package to be loaded.

    How to work with packages (15)

  2. ClickCargo package.

    How to work with packages (16)

    • File

      You can write the file name directly or use theTo browse…Dialog to select the necessary package from your local file system (after selection, clickACCORDINGLY).

    • Strength data increase

      If there is already a package with this name, you can click on this to force the load (and replace the existing package).

    ClickACCORDINGLYso that the new loading package is listed on the package administrator list.

    To use

    So that the content is available for AEM, make sureInstall the package.

Package Validation

Before installing a package, you should check your content.How packages can modify overlapping files in/Formsand/or add, modify and eliminate the LCA, it is usually useful to validate these changes before installing.

Validation options

The validation mechanism can verify the following characteristics of the package:

  • Osgi package imports
  • Overlap
  • ACLs

These options are detailed below.

  • Validate Osgi packages

    What is verified

    This validation inspects the package for all Jar (Osgi packages) files, extract yourmanifest.xml(containing the version of dependencies on which the OSGI package is based) and checks the instance exports that AEM said that the dependencies with the correct versions.

    How it is informed

    Any version dependence that cannot satisfy the AEM instance is listed in theActivity registrationof the package administrator.

    Error states

    If the units are not satisfied, OSGI will be grouped in the package with these units will not start.This results in the implementation of the broken application, as anything that trusts the Osgi package not started will not work correctly.

    Error resolution

    To resolve errors due to Osgi's dissatisfied packages, the dependency version in the packet with dissatisfied imports must be adjusted.

  • Validate overlays

    What is verified

    This validation determines whether the package being installed contains a file that is already overlapping in the destination instance.

    For example, given an existing overlap in/apps/sling/servlet/errorhandler/404.jsp, a package that contains/libs/sling/servlet/errorhandler/404.jsp, for the existing file to change in/libs/sling/servlet/errorhandler/404.jsp.

    (Video) Systems at Work

    How it is informed

    Any of this type is described in theActivity registrationof the package administrator.

    Error states

    A state of error means that the package is trying to implement a file that is already overlapping;Therefore, the changes in the package will be nullified (and therefore "hidden") by overlap and will not come into force.

    Error resolution

    To solve this problem, the surface of the overlap file in/FormsYou must review the changes in the overlapping file in/Libsand incorporate changes as needed in the overlap (/Forms) and place the superfified file re -.

    To use

    Remember that the validation mechanism cannot be reconciled if the superimposed content has been incorporated correctly into the overlap file.Therefore, this validation will continue to inform about conflicts even after the necessary changes.

  • Validate ACLS

    What is verified

    This validation checks what permission is being added, how they will be treated (mix/replace) and if current licenses will be affected.

    How it is informed

    Licenses are described inActivity registrationof the package administrator.

    Error states

    Explicit errors cannot be provided.Validation simply indicates whether new ACL permissions will be added or affect the package installation.

    Error resolution

    Using the information provided by validation, the affected nodes can be checked in the Crxde and the ACL can be adjusted in the package as needed.


    As a recommended practice, it is recommended that packages do not affect ACLs provided by AEM as this can lead to unexpected product behavior.


Package validation can be done in two different ways:

  • Through the user interface of the package administrator
  • Through the HTTP publication app, as in Curl

To use

Validation should always occur after package loading, but before installing it.

Package validation through the package administrator

  1. Open the package administrator inhttps: // <ver>: <tem>/crx/packmgr

  2. Select the package from the list and selectAdvanceimplantable header and thenValidateNo menu Drop -Rapno.

    To use

    This should be done after charging the content package, but before installing the package.

  3. In the modal dialog box that appears, use the check boxes to select the validation types and start validation by clickingValidateHealthy, clickCancel.

  4. The validations chosen are executed/executed.The results are shown in the record of packaging administrator activities.

Validation packages by posting http posting

The publication application assumes the following form.

https: // <dost>: <sot> /crx/packmgr/service.jsp?cmd=validate&type=osgipackageImports.overlays,acls

To use

HetypeThe parameter can be any confused list separated by a coma consisting of:

  • OsgipackageImports
  • overlap
  • ACLs

The value oftypepredeterminedOsgipackageImportsIf you do not pass.

Following is an example of using CRO to perform a package validation.

  1. If the curl is used, perform a statement similar to the following:

    Curl -v -x post -User Admin: admin -f file=@/users/someguy/desktop/ 'http: // localhost: 4502/crx/packmgr/servicio.jsp?cmd = validate & type = osgipackageImports, superposicionas, ACLs '
  2. The requested validation is performed and the answer is sent as a JSON object.

To use

The response to a post -validation HTTP app will be a JSON object with validation results.

Package Installation

After sending a package, you must install the content.To have the contents of the package installed and functional, both must be:

  • loaded in AEM (alsoLoaded from your file systemoDownloaded from the shared package)

  • installed


Installing a package can replace or eliminate the existing content.Only one package increases if you are sure that you do not eliminate or replace the necessary content.

To see the content or impact of a package, you can:

  • Run a package test installation without modifying any of the contents:
    Open the package (click on the package icon or name) and clickTest installation.

  • See a package content list:
    Open the package and clickSatisfied.

    (Video) Project Management Concept #14: Work Packages v Activities

To use

Immediately before installing your package, an instant package is created to contain the content that will be replaced.

This instantaneous reinstall will be/when you uninstall your package.


If you are installing digital assets, you should:

  • First, disable the work of work.
    Use the Osgi console component menu option to

  • So when the installation is completed, the reactive workfloucher.

Disabling WorkflowLance ensures that the asset importer's picture does not manipulate (unintentionally) assets when installing.

  1. In the administrator package, navigate to the package you want to install.

    EinstallThe button is shown next to the packages that have not yet been installed.

    To use

    Alternatively, you can open the package by clicking your icon to access theinstallbutton there.

  2. ClickinstallTo start the installation.A dialog box will request confirmation and list all changes made.When finished, clickFenceNo dialogue.

    WordInstalledIt appears next to the package after it is installed.

File system based on loading and installation

There is an alternative way to load and install packages in your instance.In your file system, you have aCRX-CickstartFolder along with your bottle andlicense.propitiesFileinstalllowCRX-Cickstart.So you will have something like this:<aem_home>/crx-quickstart/install

In this installation, folder, you can directly add your packages.They will be loaded and automatically installed in their instance.When ready, you can see the packages in the package administrator.

If your instance is running, adding a package toinstallThe folder will directly start the load and installation in the instance.If your instance is not being executed, the packages it puts in theinstallThe folder will be installed at the beginning in the alphabetical order.

To use

You can also do this before starting the instance for the first time.To do this, you need to create theCRX-CickstartManually, create theinstallFolder underneath and place your packages there.So when you first start your instance, the packages will be installed in the alphabetical order.

Non -stalian packages

AEM allows you to uninstall the packages.This action reverses the contents of the repository that is affected to the instantaneous made immediately before the package installation.

To use

After installation, an instant package is created that contains the content that will be replaced.

This package will reinstall when the package uninstall.

  1. In the administrator package, navigate to the package you want to uninstall.
  2. Click the package icon of the package you want to uninstall.
  3. ClickUninstallTo eliminate the contents of this repository package.A dialog box will request confirmation and list all changes made.When finished, clickFenceNo dialogue.

Eliminate packages

To delete a package package: Package Administrator:

To use

The package files/nodes arenoeliminated

  1. NoToolsconsole, expand thepackagesFolder to show your package on the right panel.

  2. Click on the package you want to delete to highlight and then:

    • ClickDeleteNo Menu gives ferramentas bar.
    • Right -click and selectDelete.

    How to work with packages (17)

  3. AEM requests confirmation that you want to remove the package.ACCORDINGLYTo confirm the elimination.


If this package has already been installed, then theinstalledsatisfiednobe eliminated.

Package replication

Replicates the content of a package to install it in the publication instance:

  1. NoPackaging managerBrowse to the package you want to replicate.

  2. Click the icon or name of the package you want to replicate to expand it.

  3. NoAdvanceDROP -Redondo in the toolbar, selectReplicate.

The shared package was a centralized server available to the public to share content packages.

Was replaced bySoftware distribution.

Software Distribution

Software DistributionIt is the new user interface designed to simplify research and download AEM packages.

For more information, take a look atSoftware distribution documentation.


Currently, AEM Package Manager cannot be used with software distribution.Decorate your packages for your local album. features

(Video) Relocation Packages - Part 1

Automated incorporationAutomatic Form FillDirected contentAsset CollectionsIntegrated GraphicsVersion History


1. VIBL #10, WBS & Work Packages
(Jeffrey Andrew Pulliam)
2. Pricing Freelance Packages (Work Session!)
(Latasha James)
(Dariel Guerrero)
4. Computer Packages
(Mcomps Network)
5. Introduction to R Packages
6. How Amazon's Super-Complex Shipping System Works
(Wendover Productions)
Top Articles
Latest Posts
Article information

Author: Terence Hammes MD

Last Updated: 12/11/2022

Views: 6437

Rating: 4.9 / 5 (69 voted)

Reviews: 92% of readers found this page helpful

Author information

Name: Terence Hammes MD

Birthday: 1992-04-11

Address: Suite 408 9446 Mercy Mews, West Roxie, CT 04904

Phone: +50312511349175

Job: Product Consulting Liaison

Hobby: Jogging, Motor sports, Nordic skating, Jigsaw puzzles, Bird watching, Nordic skating, Sculpting

Introduction: My name is Terence Hammes MD, I am a inexpensive, energetic, jolly, faithful, cheerful, proud, rich person who loves writing and wants to share my knowledge and understanding with you.