.net pdf 417

.net pdf 417

.net pdf 417

.net pdf 417

.net pdf 417

.net pdf 417,

.net pdf 417,

.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,

.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,

Repackaged application (.msi) files These files are used to repackage appli cations that do not have a native Windows Installer package. Although repackaged Windows Installer packages work the same as native Windows Installer packages, a repackaged Windows Installer package contains a single product with all the components and applications associated with that product installed as a sin gle feature. A native Windows Installer package contains a single product with many features that can be individually installed as separate features.

10

Customizing Windows Installer Packages You can customize Windows Installer packages by using modifications, also called transforms. The Windows Installer package format provides for customization by allowing you to transform the original package using authoring and repackaging tools. Some applications also provide wiz ards or templates that permit a user to create modifications. For example, Microsoft Office XP supplies a Customization Wizard that builds modifi cations. Using the Office XP Customization Wizard, you can create a modification that allows you to manage the configuration of Office XP that is deployed to users. A mod ification might be designed to accommodate Microsoft Word as a key feature, installing it during the first installation. Less popular features, such as revision support or docu ment translators, could install on first usage, and other features, such as clip art, might not install at all. You might have another modification that provides all of the features of Word and does not install Microsoft PowerPoint. In addition, you can make modifi cations to customize the installation of a Windows Installer package at the time of assignment or publication. The exact mix of which features to install and when to install them varies based on the audience for the application and how they use the software. You can use the following file types to modify an existing Windows Installer package:

unwrap() and getDelegate()

Patch (.msp) files These files are used to update an existing .msi file for software patches, service packs, and some software update files, including bug fixes. An .msp file provides instructions about applying the updated files and registry keys in the software patch, service pack, or software update.

implementing and administering desktop operating systems and network operating system in environments that have the following characteristics:

Note You cannot deploy .mst or .msp files alone. They must modify an existing Windows Installer package.

At least 250 supported users Three or more physical locations Typical network services such as messaging, database, file and print, proxy server or firewall, Internet and intranet, remote access, and client computer management Three or more domain controllers Connectivity needs that include connecting branch offices and individual users in remote locations to the corporate network, and connecting corporate networks to the Internet

The unwrap() method allows you to obtain a reference to the underlying persistence provider object that implements the EntityManager interface. Most vendors will have API extensions to the EntityManager interface that can be executed by obtaining and typecasting this delegate object to a provider s proprietary interface. In theory, you should be able to write vendor-independent code, but in practice, most vendors provide a lot of extensions to Java Persistence that you may want to take advantage of in your applications. The getDelegate() method was provided in JPA1; for now, it s recommended that users call unwrap().

You can also deploy software using the Software Installation extension by using an application file. Application files are text files that contain instructions about how to

In addition, you should have experience designing a network infrastructure. Many design exercises are paper-based; however, to understand the technical capabil ities that a design can incorporate, you should have some hands-on experience with products. Where specific hands-on instruction is given, you must have at least two computers configured as specified in the Getting Started section at the beginning of this book.

12-7

publish an application, taken from an existing setup program (Setup.exe or Install.exe). Application files use the .zap extension. Use .zap files when you can t justify develop ing a native Windows Installer package or repackaging the application to create a repackaged Windows Installer package. A .zap file does not support the features of Windows Installer. When you deploy an application by using a .zap file, the applica tion is installed by using its original Setup.exe or Install.exe program. The software can only be published and users can only select it by using Add Or Remove Programs in Control Panel. It is recommended that you use .msi files to deploy software with Group Policy whenever possible.