This section describes how to deploy applications.
The term application is used in this section to refer to a group of one or more features that must be deployed together to provide some useful capabilities.
The deployment artifacts are plug-ins, fragments, features, and update sites.
Plug-ins contain the code and resources that provide specific functions. Fragments can contain code to extend other plug-ins, but are typically used to provide locale specific information or operating system specific implementations. Plug-ins and fragments are not individually installed into the client runtime, but must be packaged within a feature. A feature is the minimal install artifact. Features include plug-ins and fragments. Features may also include other features. Features can also require other plug-ins and features to be installed.
An update site is a repository of features. Features on an update site may or may not have any relationship one to another. Depending on the methods used for deployment, update sites are optional. To deploy features without adding them to an update site, you can use the following deployment choices:
- Feature distribution using the Client Management server
- Feature distribution using the Portal managed Client
To deploy features that are contained within an update site, you can use the following deployment choices:
- Local update site
- Remote update site
- Local archived update site
- Update site distribution using the Client Management server
To create features and update sites, use the following tasks:
- Creating a feature
- Creating an update site
- Exporting a feature and its plug-ins
Once the feature or update site is created, see Managing the client runtime
for information on deploying the feature or update site.
Parent topic: Assembling and deploying: XPD621