Browse Prior Art Database

Dynamic Setup Bootstrapper

IP.com Disclosure Number: IPCOM000179838D
Published in the IP.com Journal: Volume 9 Issue 3A (2009-03-16)
Included in the Prior Art Database: 2009-Mar-16
Document File: 2 page(s) / 121K

Publishing Venue

Siemens

Related People

Juergen Carstens: CONTACT

Abstract

Most installation developments need a bootstrapper which installs applications and prerequisite components. Currently, a bootstrapper can be developed as follows: 1) A setup script, which is a very limited solution that combines the setup components without providing a GUI (Graphical User Interface). Each package needs a different bootstrapper. 2) A predefined bootstrapper, which is an application with a fixed GUI that suppresses the GUIs of the sub-setups. This is a good solution if all the product packages have a common base or platform and the packages will be installed as part of this platform. However, it is hard to generalize such a solution to a wider spectrum without reprogramming it. 3) A general bootstrapper, which is an application with a minimal GUI that performs the setups using the setups own GUI. These solutions, however, do not provide flexible usability and design. A disadvantage of solution 1 and 2 is also that they need high development and maintenance efforts. A disadvantage of solution 1 and 3 is further that it is hard to integrate special 3rd party products for them.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 54% of the total text.

Page 1 of 2

Dynamic Setup Bootstrapper

Idea: Zreiq Hisham, DE-Nuremberg

Most installation developments need a bootstrapper which installs applications and prerequisite

components. Currently, a bootstrapper can be developed as follows:
1) A setup script, which is a very limited solution that combines the setup components without

providing a GUI (Graphical User Interface). Each package needs a different bootstrapper.
2) A predefined bootstrapper, which is an application with a fixed GUI that suppresses the GUIs

of the sub-setups. This is a good solution if all the product packages have a common base or

platform and the packages will be installed as part of this platform. However, it is hard to

generalize such a solution to a wider spectrum without reprogramming it.
3) A general bootstrapper, which is an application with a minimal GUI that performs the setups

using the setups own GUI.

These solutions, however, do not provide flexible usability and design. A disadvantage of solution 1

and 2 is also that they need high development and maintenance efforts. A disadvantage of solution 1

and 3 is further that it is hard to integrate special 3rd party products for them.

As a novel solution a dynamic bootstrapper is proposed that adapts itself to the setup packages and

replaces the GUI of the products in the package with preconfigured dialogs. The user defines the GUI

and the needed information for the GUIs, e.g. setup features, in XML (eXtensible Markup Language)

files which get the same ID (Identification Number) as the dialogs that they replace. During the

installation, the MSI (Microsoft Windows Installer) original dialog is suppressed and a dynamic dialog

is displayed using the description from the XML file. The XML file provides only the logical information

that needs to be displayed. The style and design are defined in the bootstrapper. Thus, a...