Export a package to bundle one or more MBOs and package options in the selected package to create a new instance of a deployment archive. Typically, export is used to move the package contents onto another Unwired Server, however you can only import packages to the same domain as it was exported from.
Note: It is a requirement to create domains in the same order in both the export and import server environment to ensure that an internal ID assigned to the domain in both environment matches. You can verify the internal ID assigned to a domain by looking at the prefix used in the package folder in the exported zip.
- In the left navigation pane, expand the Packages folder.
- In the right administration pane, check the box adjacent to the name of the package and click Export.
The Export Package dialog appears.
- Check the appropriate export package options from the list: Include
synchronization tracing, Include package logging,,Include role mappings, and Include device notification templates (for RBS packages only).
These selections determine which package settings are retained for the new instance of the package. The current security configuration for the package is automatically applied to the exported package.
- Click Next.
- Select the file system target for the exported contents and click OK.
Note: Ensure that you do not hide file type extension when you name the export package; otherwise, when the *.zip extension becomes invisible, which adversely affects the outcome of the export process.
A status message on the General tab indicates the success or failure of the export transaction. If successful a ZIP file is created in the location you specified. You can then use this file to import the package.
Next
Deliver the file to the appropriate person or deploy the exported package on the appropriate server.