Creating an Application Package:
|1.||Expand the Applications node in the navigation tree, then click on Application Packages - you can see all of existing Application Packages. Out of the box, these are the mSuite packages.|
|2.||Right mouse click on Application Packages in the navigation tree and select New > Create a New Application from the pop-up menu.|
|3.||This launches the Application Package Wizard, click Next on the Welcome page|
|4.||On the General page, enter a name for your Package, enter a Priority - priorities are used for sequencing packages, a lower number get installed before a higher number so you can use this to control dependencies between packages by making sure that dependent packages have a higher priority number than things they depend on. Click Next to continue.|
|5.||Now you have to choose a Version for your application. You can have multiple versions of an application but only one version can be deployed to a particular user/group at any time. Click Next to continue.|
|6.||You now have to choose the type of device this application is applicable to, select the appropriate Device Profile from the available list. Install later instructs the package installer (on the mobile device) to wait until the communications session is complete before installing the package. In general, this is not required. Click Next to continue.|
|7.||Now you must add the components to the package. |
Note: Sis files are only applicable to Symbian devices. Registry values are only applicable to Windows Mobile devices.
To create a package by this method, you need to understand the layout of the application as installed on the device, what folder structure it has, what files are in each folder, what registry values are required and also any certificate requirement. If you do not know this information, use a "snapshot" to create a map of the application for you.
This is where you specify the physical file system components that will be copied to the device.
Right mouse click on File System and choose Add Folder or Add File to import the necessary component(s). When creating a new application, where you start from represents the root directory of the device where the package will be installed.
The first step is to create the folder structure of the Package. Use Add Folder to create a folder structure on the device, you will see the Folder Component Editor.
|1.||Enter a name in the Folder Name field. This will be the folder that is created on the device.|
|2.||If you want this folder and its contents including any contained folder and their contents to be deleted if the package is uninstalled, check Delete on uninstall; otherwise leave that checkbox clear. You should only do this if the folder only belongs to this package.|
|3.||If the folder is going to contain a device setup file (called on installs and uninstalls), check the Installation Directory checkbox.|
|4.||Click OK to close the dialog.|
|5.||Repeat this process to create the entire folder hierarchy of the package when installed on the device.|
Now you need to add the files to the folders:
|1.||Right mouse click the folder that is to contain the file and choose Add File from the pop-up menu.|
|2.||Browse to the file that will be copied to the folder on the device, select it and click Open to display the File Component Editor:|
|3.||If necessary, in the 'File Name' field change the name of the file to appear on the device.|
|4.||If necessary, change the Modified Date by clicking the arrow to the right of the pull-down list and select the desired date. This is used in evaluating whether components have changed in the application so do not change this if you want the package to be capable of repairing itself (if this component is accidentally modified on the device).|
|5.||To apply simple file system attributes to the file, check the relevant check boxes in the File Flags field.|
|6.||Now set the Device Installation Flags fields:|
|•||To specify that the file is not overwritten if it has been modified or updated, check the Mutable checkbox. If this is set, mSuite will not see a modification of this file as being a reason to replace the file with the original file from the package.|
|•||To specify that the file is an installer component, check the Installer checkbox. What does this do?|
|•||To specify that the file is a device setup file (called on installs and uninstalls), check the Device Setup File checkbox. What does this do?|
|•||Key Component marks a file to indicate that, if it is missing, the whole package must be installed. Normally mSuite will just replace a missing component from a package rather than running the installation again. You also have to choose whether to only re-install when this is missing or to re-install if modified or missing.|
|•||If you don't want the file to be redeployed after initial installation, check the Virtual checkbox; if you don't want the file to be sent at all, but need a record of its existence on the device, check both the Virtual and Store comparator at install time check boxes.|
|•||Check Execute file on device if you want mSuite to run this component when the package is installed for the first time.|
|7.||To add another file, repeat steps 1 to 6.|
A sis file is an application installer for Symbian devices,
|1.||Right mouse on Sis File and choose Add Sis File from the pop-up menu.|
|2.||Browse to the file that will be installed on the device, select it and click Open.|
|3.||To add another sis file, repeat steps 1 and 2.|
Define any registry settings for the package.
|1.||Do one of the following:|
|•||To add a registry key to HKEY_CLASSES_ROOT on the device, right-click HKCR|
|•||To add a registry key to HKEY_CURRENT_USER on the device, right-click HKCU|
|•||To add a registry key to HKEY_LOCAL_MACHINE on the device, right-click HKLM|
|2.||From the pop-up menu click Add Registry Key, the Registry Key Component Editor will be displayed|
|3.||Enter a registry key name in the field Registry Key.|
|4.||To specify that the registry key is not overwritten if it has been modified or updated, check the Mutable checkbox.|
|5.||If you want this registry key and sub-keys to be deleted when the package is uninstalled check Delete on uninstall; otherwise leave the checkbox clear.|
|6.||Check Key Component if you want the deletion or modification of this registry key to cause the package to re-install rather than mSuite replacing missing or modified components. If you enable this, choose either Run install if missing or Run install if missing or different.|
|7.||Create the rest of the registry keys by right mouse clicking on a registry key and repeating steps 2 to 6|
Now add any required values to the registry.
To add a value to a registry key, right-click the relevant registry key and select one of the following options:
|1.||In the following Value Editor enter a Value Name and the Value.|
|2.||To specify that the registry key is not overwritten if it has been modified or updated, check the Mutable checkbox.|
|3.||If you want this registry key and its sub-keys to be deleted when the package is uninstalled, check Delete on uninstall; otherwise leave the checkbox clear.|
|4.||Check Key Component if you want the deletion or modification of this registry key to cause the package to re-install rather than mSuite replacing missing or modified components. If you enable this choose either Run install if missing or Run install if missing or different.|
|5.||Repeat step 1 to 4 to add the rest of the registry values.|
Add any certificate(s) that must be deployed with the package.
|1.||Do one of the following:|
|•|| To add a certificate to the Root certificate store on the device, right-click ROOT|
|•|| To add a registry key to User certificate store on the device, right-click USER|
|2.||From the pop-up menu click Add Certificate, a file system browser will be open to allow you to navigate to the certificate that you want to include.|
|3.||Select the certificate and click Open.|
|4.||A Certificate dialog will display a summary of the certificate, review the information and click OK.|
|5.||The certificate is now displayed in the package tree.|
|6.||Repeat steps 1 to 5 to import any other certificates.|
See Deploying Applications