Put your short description here; used for first paragraph and abstract.
Native Application Bundles must be started before they can deploy the native files they contain. In previous releases of Lotus® Expeditor, the Device Management Server (DMS) could send a "bundle start" task after the Native Application Bundle (NAB) was deployed to a client. The Expeditor Client Manager (XCM) can not perform the same task. Therefore, an install handler must be added to the Native Application feature in order to start the NAB.
To deploy a native application to a device, perform the following procedure:
- Copy NABinstaller_1.0.0.jar from <Client DVD>\\utils and extract the install_conf.properties file from the /config folder inside the JAR.
- Edit install_conf.properties and change the NAB-Bundle-SymbolicName value to be the symbolic name of your Native Application Bundle.
- Return the changed install_conf.properties file back to the /config folder inside the NABinstaller_1.0.0.jar.
- In the IDE, import the NAB as a plug-in project.
- Create a feature project that includes the NAB plug-in project. For more information, see Creating a feature.
- Copy the NABinstaller_1.0.0.jar to the root of the feature project.
- Open the feature.xml file using the Feature Manifest Editor.
- Select the Build tab.
- Ensure that NABinstaller_1.0.0.jar is included in the Binary Build field.
- Select the Installation tab.
- Enter NABHandlerImpl as the Handler class and NABinstaller_1.0.0.jar as the Library attribute.
- Save the feature.xml file.
- Create an Update Site containing the Native Application feature.
- Deploy the feature using an XCM feature distribution job.
Parent topic: Managing with a Client Management server: XPD622