|
<< Click to Display Table of Contents >> RayPack > 7.3 u6 > User Guide > Appendix II: How to Pick the Right Packaging Method Target Definition |
What kind of task does the target package have to achieve? Does the package need to be installed as a real application on a physical machine, will it exist as a virtualized application, or run in a virtual environment? Is it necessary to update or patch an existing application?
RayPack supports the generation of virtualized packages, which only pretend to be a physically installed application, but actually include instructions on how to emulate installation aspects such as environment variables, registry keys, file system resources, and the like.
The appropriate type of application virtualization format depends on the customers infrastructure. If an Application Virtualization Management Server is implemented, the customer might very well request an App-V package, which contains all application streaming instructions and data required to stream the included software via such a management server.
Other scenarios require software to run from an USB stick, or any other portable storage media, without the ability to extract files or settings to the target system. These cases require package formats such as ThinApp, which encapsulate application packages for totally portable usage.
If the basic material has the same format as the target package, it is usually the easiest way to import the package into the PackDesigner, execute the required changes, and export the resulting set of operational instructions. Add MST files to MSI resources, or transfer from one file type to another, for example by importing an MSI file, and exporting it into the App-V format.
However, in some cases it is necessary to leave the original material as is, and just extend it with a transform, for example if an application is to be patched. For MSI files this is the recommended method, especially if the original application is already installed on the target system. It does not make sense to reinstall the whole application, putting existing user data and settings at risk, but fix a certain issue using the repair functionality of MSI based applications. In those scenarios it is the safest way to create an MST file, which contains instructions on how to manipulate the installed application data safely.
Another scenario for MST creation would be the fact, that an MSI file with original resources is available, providing all required options for manipulation directly editable for users during the installation routine. Whatever a user may decide during a manual setup, may be bundled into an MST file by PackTailor. Simply create a new PackTailor project, run through the simulation of the UI sequence, and enjoy the fact that with a decent base MSI, your target MST is potentially only a few clicks away.
Software packages are usually dedicated to one or more specific target environments. The environment definition includes aspects such as operating system, corporate network and security factors, co-existing applications, update schedules, and language settings.
Creating packages with software that represents the client within a client-server application architecture, the required location and authorization data has to be provided to make sure that the installed package can be used straight away without further configuration by the end-user.
Make sure to agree on an exhaustive operational environment definition with the customer in the first place and evaluate the requirements regarding his feasibility before any packaging activity starts. RayPack will offer support with package validation on several levels, including Logo checks for Windows operating systems, ICE validation, and Package Signing. Depending on the required OS coverage, ensure to create a package that passes these validation steps in the context of the targeted systems.
Once knowing what environment to aim for, some target formats, and therefore packaging methods, might turn out to be inapplicable. It does not help at all to prepare an MSI package if the customer runs his IT landscape based on virtualized desktops. On the other hand the availability of virtualization options depends on application requirements, for example regarding prerequisite drivers, which might very well make it impossible to virtualize an application.
Another aspect of deciding for the right packaging method is the desired installation type. If a silent installation is required, but the original software material inevitably requires user input during the installation, PackRecorder has to be used first in order to capture those inputs, and wrap them into a silent package installation procedure. PackTailor might also do the trick, but whenever complex installation routines work with picky launch conditions, system state analysis, custom action based dialog management, and the like, simply tailoring the UI sequence usually does not work out sufficiently well.
Precapturing may also be required if the target installation demands advertised feature installation, and the raw material does not support it. It is possible to extend an MSI file with a transform to achieve advertisement, but in order to integrate it into a legacy setup or a virtualized package requires additional preparations.