Adding Processed Resources
Since one of the main reasons for using deployment packages is to manage the lifecycles of bundles together with their configurations, permissions and other types of resources, the Deployment Package Editor of mToolkit supports adding, deleting and modifying of different non-bundle artifacts. You can perform such operations in the Resources tab displayed for a Deployment Package Project file by the Deployment Package Editor.
To add a new resource to the deployment package:
- In one of the navigation views, locate and open the Deployment Package Project (.dpp) file to launch the Deployment Package Editor in the editor area.
- Go to the Resources tab of the Deployment Package Editor.
- Add a new entry to the table for each processed resource which will be a part of the desired deployment package:
- Click the New button.
- Specify the following resource properties in the displayed empty row:
- Resource Path - Specify the location of the desired resource by using the Browse (...) button to locate it in the file system, or type the resource file path by hand.
- Name - Specify the location of the added processed resource within the JAR file of the deployment package by typing it in the empty cell of the Name column. The default path name is resources/<resource_name>.<resource_extension>.
- Resource Processor - Type or select from the drop-down list the PID of the Resource Processor service registered to handle this particular resource. The default list of available Resource Processors is configured through the Window > Preferences dialog page.
- Missing - Select the true option of the drop-down list to indicate that the processed resource is logically a part of the generated deployment package, but is not physically included in the deployment package JAR file. Such resources are only mentioned in the Name section of the manifest file of a Fix Package. It is a variety of a deployment package used to quickly upgrade or downgrade an existing deployment package and all processed resources marked as missing should be available in the initial version of this deployment package. The purpose of including such resources in the manifest file of a deployment package is to distinguish between resources that will not be changed and resources that must be removed. The default value is false.
- Custom Headers - Add some additional custom headers by using the Browse (...) button in the Custom Headers column of the processed resource. In the displayed Resource Custom Headers dialog, use the New button to add a new empty row in the table. Then enter the header name in the text field under the Key column and the header value in the text field under the Value column. When ready, click OK. In case you want to remove a custom manifest header, select it from the table in the Resource Custom Headers dialog and use the Remove button.

Figure 1: Adding processed resources to a deployment package.
- Save the Deployment Package Project file to store the changes you have made on the resources included in the deployment package.
Common Errors
When adding a new processed resource to a deployment package, make sure you have entered the PID of the Resource Processor that will handle this resource. Otherwise, an error dialog is displayed to remind you to enter the PID in the Resource Processor column.

Deployment Package Overview
Deployment Package Editor

Creating a Deployment Package Project File
Generating a Deployment Package
Quick Deployment Package Build
Exporting Deployment Package Build Files
Configuring Deployment Package Editor
