Package Wizard

Export

While importing a package is available by default, Exporting a package is a licensed feature.

Several steps should be followed to export, using the Package Wizard:

First select the Package action. Select ‘Export’.A ‘Working Folder’ needs to be specified before the Package Wizard can act.
Next, the object to be exported must be selected. Select the application you want to export. If you want to export only a Taskset, you can use the selector in the lower right of the window.
Enter the other parameters demanded.For ‘Package File’ you can enter the name under which the package is saved. If applicable, select the repository that is used, using the Operating System selector. An application can be exported independent of operating system. Select ‘Export as Default OS’ to activate this option. The Installer can be added to the package as well.
All necessary information has been collected. The export can be realized.By clicking the ‘Finish’ button the Package Wizard will start creating the package. The Application object and the Taskset are saved in XML-format. All files from the repositories are collected. Then, a compatible ZIP file is created, ready to be imported into another Scense system.
Import The import function consists of several steps as well:
First you select the Package action. Select ‘Import’. For import a ‘Working Folder’ needs to be specified as well.
Then the Package File has to be entered.For (legacy) repository packages, an additional option is to copy application files to the application context location.
The Package Wizard has all information required to import the package. By clicking ‘Finish’ the Package Wizard will start importing the package. First, the package is tested for errors, after that it is unpacked. After unpacking, the Application and/or Taskset is imported and then – in case of Application – also the repository, if applicable. MSI- or VSA-files will be placed in the %InstallScripts% folder. For App-V files this depends on the configuration of the receiving system. This can either be the %InstallScripts% folder, or the content-folder on the App-V server.
In case an application depends on another application, the message on the right is shown at the end of the import session.The administrator can re-establish this dependency manually, using Scense Explorer.

Command Line Packaging

Syntax

ScensePackageCmd makes it possible to import and export packages through a batch-process. The command line syntax is as following:

Application Export:
ScensePackageCmd {/E[xport]}
                 {/P[ackageFile]=<filename>}
                 {/W[orkingFolder]=<folder>}
                 {/S[election]=<objectid>}
                 {/O[peratingSystem]=<operatingsystem>}
                 {/X[tendedInstaller]=<filename>}
                 [/R[epositoryOverwrite]]
                 [/D[efault]]
                 [/V[erbose]]

TaskSet Export:
ScensePackageCmd {/T[askSetExport]}
                 {/P[ackageFile]=<filename>}
                 {/W[orkingFolder]=<folder>}
                 {/S[election]=<objectid>}
                 [/V[erbose]]

Import:
ScensePackageCmd {/I[mport]}
                 {/P[ackageFile]=<filename>}
                 {/W[orkingFolder]=<folder>}
                 [/U[pdateContext]]
                 [/V[erbose]]