INFORMIX
DataBlade Developers Kit User's Guide
Chapter 10: Using BladePack
Home Contents Index Master Index New Book

BladePack Overview

BladePack produces installation packages for installing products on UNIX and Microsoft Windows platforms. BladePack can create a simple directory tree containing files to be installed or an installation that includes an interactive user interface.

On UNIX platforms, an interactive installation includes install and uninstall shell scripts. On Windows, an interactive installation includes Setup and Uninstall programs created with InstallShield.

Important: You must have an InstallShield Professional license to create an InstallShield installation for Windows NT. Specify the directory where InstallShield is installed during the DataBlade Developers Kit installation or, after installation, modify the IShieldDir environment variable.
The files in an installation package can be divided into separate components, subcomponents, and shared components. You must define at least one component for an installation package. You can designate the components to include in typical and compact installations. You can also allow users to customize their installation by choosing the components they want to install.

For example, in addition to the required shared object file and SQL scripts, a DataBlade module can include example files and on-line help files. You can place these additional files into separate components that are included in a typical installation but excluded from a compact installation.

BladePack organizes information into projects. Each project is controlled by a product file (project.prd), which contains entries for the component file (project.cmp), bill of materials file (project.bom), and string file (project.str). If you are packaging a DataBlade module created by BladeSmith, the Generate Packaging option creates these files in the install directory. The following table describes these files.

Package File Description

project.bom

A bill of materials file. This file contains an entry for each file to be installed. The entry includes the path to the source file and the path where the file will be installed.

project.cmp

Lists the main components and subcomponents in the installation package.

project.str

Defines character strings used in the installation.

project.prd

The main product file that you open with BladePack. This file lists other files that define the installation package. Initially, this file contains entries for the .bom, .cmp, and .str files. Add Read Me files using BladePack.

Important: Do not edit the generated installation package files. Instead, use BladeSmith to update the installation package files after you have added or removed DataBlade module objects in the project file.
When you build an installation package, you can include several BladePack projects. For example, you can include DataBlade modules that facilitate similar financial calculations into a single installation package.

If you include standard items in each of your installations, create a separate project for these items and include this project in every installation. For example, you can put registry changes required by all DataBlade modules in a standard project file. Include these changes in a component that is always installed.

BladePack On-Line Help

BladePack on-line help provides overview and detailed reference information for BladePack.

The "About BladePack" section contains topics that provide an overview of BladePack and installation packages.

The "BladePack Interface" section describes BladePack menus, project view pages, item view pages, dialog boxes, and the Build Installation wizard.

The "BladePack Procedures" section contains instructions for working with projects, establishing the content of the installation package, organizing components, and setting up the installation package interface.

BladePack Windows

The BladePack project window is divided into two panes. The project view pane displays the overall structure of the installation package. The project view contains tabbed views of the contents of the installation package arranged in hierarchical trees.

The item view pane contains detailed information about the object selected in the project view. You use the project view to add objects to the installation package and to organize the structure of the installation package. You use the item view to enter details about objects in the installation package. Figure 10-1 shows a BladePack project window.

Figure 10-1
BladePack Project Window

Project View

The project view pane has three tabbed pages: Files/Directories, Components, and Customization.

Each page in the project view presents a hierarchical tree of the contents of the package. To expand or collapse a folder, click the expander button next to the folder or double-click the folder.

Files/Directories Page
When you click the Files/Directories tab in the project view, BladePack displays files and directories to install, and files and directories to remove. BladePack also displays registry changes for Windows installations.

The Files to Install, Files to Delete, Directories to Install, and Directories to Delete folders are organized as trees that match the directories on the target computer for the installation.

The Registry Changes folder contains entries for the Windows registry.

Components Page
The Components page displays the component organization of the installation package. An installation package can have components, subcomponents, and shared components. You can create a component, subcomponent, or shared component and then drag files and directories into it. Subcomponents and shared components are subordinate to components. Shared components are useful for files that are included in more than one component.

You can organize the installation package into components to make it possible for the customer who installs the package to select portions of the DataBlade module in the Select Components to Install screen. For example, if your DataBlade module includes examples, you can create a component of the DataBlade module called Examples and then create subcomponents for each example. Then customers can choose which examples to install with the DataBlade module. Shared components do not appear in the Select Components to Install screen; they are installed if the component to which they belong is installed.

However, you can also ship your DataBlade module as a single component that contains all of the files. You do not have to organize your installation package into subcomponents and shared components.

Customization Page
The Customization page displays information that can be customized for the installation package.

The Custom DLL Routine, Custom DLL Dialog, and Custom Program folders contain custom routines, dialog boxes, and executable programs for InstallShield installations on Windows platforms and executable programs to run from within interactive installations on Windows or UNIX platforms. You control when routines execute by specifying the execution sequence.

Tip: To add dialog boxes and routines to your installation package, create them using Microsoft Visual C++ and then add them to a dynamic link library (DLL). For examples, see the directory $INFORMIXDIR\dbdk\setup\example.
The Readme Files folder contains files that you want to place unpacked on the first diskette of an InstallShield installation.

The Support Files folder contains a list of files that are available during the installation, but are not installed with the product.

Item View

The item view pane displays one or more tabbed pages, depending on the object you select in the project view.

If you select a folder in the project view, the first tab in the item view contains a list of the folder contents.

If you select an object, such as a file, in the project view, the first tab in the item view displays details about the object. The information displayed and the names of the tabs depend on the type of object you are viewing. Some objects have other tabs, containing supporting information for that object.

Much of the information in the item view is editable. For example, if you add a component, you type its name in the name field that appears in the item view. Editable fields have a white background. Fields that cannot be edited have a gray background.




DataBlade Developers Kit User's Guide, version 3.6
Copyright © 1998, Informix Software, Inc. All rights reserved.