Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Look up keyword
0Activity
0 of .
Results for:
No results containing your search query
P. 1
Chapter 1

Chapter 1

Views: 1|Likes:
Published by $!v@

More info:

Published by: $!v@ on Apr 07, 2011
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as DOCX, PDF, TXT or read online from Scribd
Visibility:Private
See more
See less

01/02/2013

pdf

text

original

 
Chapter 1 : INTRODUCTION TO APPLICATION RE-PACKAGING1.1 WHAT IS REPACKAGING?
Repackaging refers to the recreation of an application¶s installation by capturing thedifferences in a computer before and after the application is installed. These changes are thencombined into an installation ³package´ which may then be applied to another computer toenforce those same changes- resulting in an installation of the application.
 
The single reason for creating such an installation package is to automate the installation so that the graphicalinteractive installation process may be avoided. 
1.2 NEED FOR REPACKAGING AND ITS BENEFITS(a) Application Deployment:
I
n an organization consisting of N-terminals, it is required that the standards should beMaintained at Hardware layer, Software layer in the User terminals. Possibly, the terminalsmight be located in different locations. But, they are connected to the same network and thenetwork can be managed from one end-point.So,
I
n order to maintain the standards at software layer, the administrator of the network installsthe required applications from one-point into all the User terminals. This process is calledApplication Deployment. This process ensures that all the Users of a network are using the sameset of applications of same versions.
(b) Application Management by Operating System (Self-Repair):
Earlier, there was a difficulty in managing the application. That is, whenever some of files or registry entries related to an application gets deleted by mistake or gets corrupted theapplication does not function properly.
I
t is the user responsibility to contact the Administrator &Un-install the application and again installs the same application.
 
I
n order to eliminate the Application Management Responsibility at the User/Administrator Level, an Operating System Service is created which takes care of 
I
nstalling the application,repairing the application when it gets corrupted and Uninstalling the application.
Note:
The Operating System Service is called ³Windows
I
nstaller´ which was first developed for Windows 2000 Operating System.
(c) Upgrading the application:
I
t is often required that installed applications should be upgraded for the latest versions.
I
tis so cumbersome that manually UN-installing the older version and installing the newer versionof the application.Once Again the responsibility is handed over to the operating system. Here, when an attempt ismade to install the newer version of an application, the Operating System Service first uninstallsthe older version of an application and installs the newer version of an application.
(d) Application Advertisement ± (On-Demand Installation):
General Say, to make the Product popular. An Effective Advertisement Strategy shouldbe applied. That is, when the Main product or application is given to a customer theadvertisement about the Sub-Products can be given. So that the customer get to know about thesub-products.
I
f the customer is interested in those sub-products he can request for thoseproducts. This feature is also called as
³Advertisement Installation or On-DemandInstallation´.
 (e) Application Patch:
Sometimes it is required that some additional files, registry entries, or configuration filesshould be set to the existing installed application. i.e. patching up the application with therequired data
I
nstead of creating the newer version of installation package.
 
Note:
Patches can be interpreted as Operating System Service Packs
.
 
(f) Central Point of Reference:
I
t is required that a central point of reference for application installation should be set.This is because whenever the application, which has been installed gets corrupted and needs tobe repaired. So, the corrupted application gets repaired from the same location from where it hasbeen installed.
(g) File Versioning Maintenance:
Earlier, there was a drawback in setup installers. Say, there is a DLL of latest version andsetup installer contains the same DLL of older version. When the setup is installed, it willoverwrite the DLL of latest version with the DLL of older version without performing any typeof pre-check of versions.Therefore, this drawback can be overcome in MS
I
 
I
nstallers, where the file versions aremaintained. That is, if there is already a file of latest version, it will be preserved during MS
I
 installation.
1.3 PACKAGING VS RE-PACKAGING
When you purchase a software application to install it onto a computer you will need to executesomething like setup.exe. Setup.exe is an installation routine, a program that puts all of the filesand registry keys in the right places so that everything works correctly. This is in essence a
Package
. However the setup routine can sometimes be very complex and open to user error especially when thousands of repeat installations are required in a corporate environment.
I
n such environments reliability and repeatability are crucial. This is where applicationrepackaging comes into its own. An experienced application packager can take a vendor application and re-write the setup routine to the specific requirements of the client. Ensuring botha reliable and accurate installation every time. The package can then be deployed silently, if desired, via your chosen deployment mechanism to all of your target workstations or users.
I
t¶s avery rapid and accurate.

Activity (0)

You've already reviewed this. Edit your review.
No activity yet

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->