Closed zipkid closed 7 years ago
Because Adobe doesn't provide the package definition, I can't provide a standard approach for using that approach for installation. There are too many variables that individual organizations may use to create packages. This doesn't preclude the use of a package definition approach, you just have to add both to the node's manifest.
The installer resource provider won't execute the unpack command; but will take over ownership of the start and start environment scripts. The source file doesn't have to actually exist, just has to be defined. Here's the example on how to set that up in a manifest.
package { 'aem':
ensure => installed,
}
aem::instance { 'aem' :
source => '/path/to/non-existing.jar',
require => Package['aem']
}
Add param to allow installing OS package of AEM compared to unpacking the jar file.