AgileApps Support Wiki Pre Release

Difference between revisions of "Distribute and Install a Package"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
 
(7 intermediate revisions by the same user not shown)
Line 2: Line 2:


The ZIP file option provides the ability to move packages across different installations of the {{enterprisebrand}}.  
The ZIP file option provides the ability to move packages across different installations of the {{enterprisebrand}}.  
{{TenantCapability | Install Package from File | Off| On| }}


;Examples:
;Examples:
Line 15: Line 13:
#:[[image:package.gif|none|thumb]]
#:[[image:package.gif|none|thumb]]
#:The Package Revision Details section indicates the number of package revisions, and will automatically update when you publish new versions
#:The Package Revision Details section indicates the number of package revisions, and will automatically update when you publish new versions
#Click the [Publish] button to create the package
#Click '''[Publish]''' to create the package


;Considerations:
;Considerations:
Line 23: Line 21:


===Install a Package from a .zip file===
===Install a Package from a .zip file===
 
{{:Install a Package from a .zip File}}
To Install a Package from a .zip file:
#Click '''[[File:GearIcon.png]] > Administration > Account Management > Packages'''
#Click the '''[Subscribe from File]''' button
#Select the name of the .zip file
:The package is installed
 
:During installation, these actions are taken by the {{enterprisebrand}}:
:*A list of available package items is displayed
:*Validation is performed (check that Objects, Classes, Pages, Functions have unique names)
:**If any fields have been added to the packaged object, the customer_id is post-fixed to the internal field name to maintain uniqueness
:**Validation will also be done for classes, pages and resources before installing


===Alternate Package Distribution Methods===
===Alternate Package Distribution Methods===
A package can also be distributed in these ways:
A package can also be distributed in these ways:
* [[Publish]] the package and submit it to the [[Service Provider]] for distribution in the [[Catalog]].
:* Publish the package and submit it to the [[Service Provider]] for distribution in the [[Catalog]].
* Post the URL to the web or put it into an email, so users can subscribe to it directly.
:* Post the URL to the web or put it into an email, so users can subscribe to it directly.
:''Learn more:'' [[Publish a Package]]

Latest revision as of 21:10, 15 January 2015

Packages can be deployed as a compressed .ZIP file, a feature available to Service Providers.

The ZIP file option provides the ability to move packages across different installations of the AgileApps Cloud platform.

Examples
  • Move from the Development instance to the QA instance for testing
  • Move packages from the QA instance to the production instance
  • Download the package as a zip file and archive it

Create a Package as a .ZIP file

To create a Package as a downloadable .ZIP file:

  1. Click the [Download Package] button to create a compressed .zip file
    Package.gif
    The Package Revision Details section indicates the number of package revisions, and will automatically update when you publish new versions
  2. Click [Publish] to create the package
Considerations
  • This file can be distributed by ftp or as digital media, loaded directly to a user's desktop
  • When uncompressed, the application is installed to that user's account
  • This file may be very large, and unsuitable for emailing

Install a Package from a .zip file

Lock-tiny.gif

To Install a Package from a .zip file:

  1. Click GearIcon.png > Administration > Account Management > Packages
  2. Click the [Subscribe from File] button
  3. Select the name of the .zip file
The package is installed
During installation, these actions are taken by the AgileApps Cloud platform:
  • A list of available package items is displayed
  • Validation is performed (check that Objects, Classes, Pages, Functions have unique names)
    • If any fields have been added to the packaged object, the customer_id is post-fixed to the internal field name to maintain uniqueness
    • Validation will also be done for classes, pages and resources before installing

Alternate Package Distribution Methods

A package can also be distributed in these ways:

  • Publish the package and submit it to the Service Provider for distribution in the Catalog.
  • Post the URL to the web or put it into an email, so users can subscribe to it directly.
Learn more: Publish a Package