Package Builder/Installer/Manager

Date: April 8, 2011
Presenter: Paul Howard (Engineering)

Objective: Provide a very high-level introduction to the package builder/installer/manager as well as explore the possibility of using this as a deployment tool in place of Multi Server Manager (MSM)
[li]This tool manages idiosyncrasies[/li][li]One of the deficiencies of MSM is the process of deploying slots (Need to deploy slots twice)[/li][li]Cannot be used to move folders or content items, much like the MSM[/li][li]Packaging extension copies the definition, not the jar. Jars have to be moved manually[/li][li]You can create a base package that includes shared fields, shared templates, content types.[/li][li]Packages can be source controlled if multiple developers are working on an environment[/li][li]A given object/element cannot be in more than one package, so modeling of a Package is vital[/li][li]Ability to configure packages[/li][li]New Feature Request: Ability to use this tool for deployment such that you can define community visibility at a granular level by exploding the package[/li][LIST]
[li]PSO can add feature request for this product[/li][/ul]
[li]Upgrading environment requires upgrading packages at the source and then redeploying[/li][li]Next Steps recommended by Paul:[/li][ul]
[li]Read documentation on How to create and deploy packages[/li][/ul]