Using IBM Tivoli Device Management Server: Create an Eclipse NativeAppBundle

NativeAppBundle -BundleName=<bundle_name>
                   -InputDirectory=<path to your update site>
                  
-InstallDirectory=<temporary_install_directory>
                   -BuildDirectory=<HTTP server document
directory>/bundles
                   -Eclipse=default
                   -BundleVersion=<version>
                   -CleanupAfterInstall=yes
                  -RemoveOnUninstall=no

Notes:

• <bundle_name> is a name for the bundle that will be generated to wrap the Eclipse update site. The bundle name may not contain spaces or periods. Each bundle that you define using the NativeAppBundle tool should use a unique bundle name. For example, if you have created a distribution bundle with a BundleName of MyApp, containing version 1.0.0 of your application, you should use a different BundleName when creating a distribution bundle containing version 2.0.0. This refers only to the BundleName specified as parameters to the NativeAppBundle program, not to the features or plug-ins contained in the update site.
• <path to your update site> is the location of the input update site on the DMS server machine.
• <temporary_install_directory> is the name of a directory that will be used on the client, and is operating system specific. This value may contain a variable reference that will be replaced on the client during bundle installation. The manifest file generated for this bundle uses % as the delimiter surrounding the variable name. The search order for the variable value is the operating system environment, followed by Java System properties.
• If the NativeAppBundle command is being run on a Windows system, escape characters will be needed. For example, to use the value of the environment variable TEMP on the client system, you would need to specify - InstallDirectory=^%^%TEMP^%^%.
• Notice that the variable name is case sensitive, unlike the typical behavior on a Windows systems.
• <HTTP Server document directory> is the destination where the OSGi bundle jar will be written. Since the client will need to access it using either the HTTP or FTP protocol, it is most convenient to generate it directly into a document directory served by a Web or FTP server. An example path would be c:/Program Files/IBM HTTP Server/htdocs/en_US/bundles
• The -Eclipse parameter indicates that the target bundle contains an Eclipse update site for installation into an Eclipse extension framework. Its value defines the Eclipse install site into which the features will be installed. The special value default will install the features into the default install site for WED4WL. Any other value must be an absolute file system path to the eclipse subdirectory of the install site, for example -Eclipse=c:/Program Files/IBM/WED/SalesCenter/eclipse

As an example, the command line

NativeAppBundle -BundleName=MCSC1 -InputDirectory=c:\temp\mcsc 
-installDirectory=^%^%TEMP^%^%\mcsc -BuildDirectory=c:\Program
Files\IBM HTTP Server\htdocs\en_US\bundles 
-Eclipse=default -BundleVersion=1.0.0 -CleanupAfterInstall=yes
-RemoveOnUninstall=no

on successful execution generates the response

SMF bundle: c:\Program Files\IBM HTTP
Server\htdocs\en_US\bundles\MCSC1+1_0_0.jar successfully created