You can add these objects to your product in BladePack:
For a DataBlade module, you need the project.bld or project.jar file and the SQL script files. If you have an ActiveX client project, you also need the project.dll file. These files are automatically added to the Files to Install folder when you open a project.prd file.
In addition, consider adding documentation, help, applications, and other files to support your DataBlade module.
If you have an ActiveX client implementation, consider including CLSID (class identifier) and IID (interface identifier) information by including C++ client support library files (see Support Library Files) in the installation package.
If you are packaging an upgrade, you might need to specify files or directories to delete in the old installation.
You might have to specify registry changes for your DataBlade module.
The object appears on the Files/Directories page.
The following sections describe the properties of the objects on the Files/Directories page.
The following table lists properties you define when you add files and directories to install or delete.
You can have multiple operating-system-specific files to install. See Local Paths for Files for Multiple Operating Systems for more information.
The directory in which the file or directory is installed.
See Specifying a Target Directory for more information.
See Assigning to Components for more information on assigning to components.
Options for copying files, including whether the DLL is installed only if it has the same or later date or version than the existing DLL. The default is None.
Whether and how a file can be shared. The default is None.
See File Sharing Options for more information.
Whether the file has an associated icon and information about that icon. The icon appears in the program group. Icons are typically used for applications, read me files, or help files; DataBlade modules do not require icons. The default is no icon.
If you have files that are operating-system-specific, put them in a directory structure that is the same except for one directory, which is named for the operating system. When you add the file to your BladePack project, replace the directory named for the operating system with %OS%.
For example, if you compile your C or C++ DataBlade module on Sun Solaris and Windows, you have two project.bld files, one in each of these directories:
Add the project\src\c\WinNT-i386\project.bld file to the Files to Install folder and then replace WinNT-i386 with %OS%. When you build the BladePack project for Sun Solaris and Windows, BladePack adds the appropriate project.bld file to each project.
For a Java DataBlade module, you have only one version of the project.jar file, which is in the project/src/java directory.
You have the following options in the list for the Directory on target machine field:
The target directory for the DataBlade module files (project.bld and the SQL scripts) should be the extend\project directory under the $INFORMIXDIR directory.
For files in the Files to Install folder, choose one of these file sharing options from the Copy Options page:
You can add entries to the Windows registry for the initialization and configuration of your DataBlade module and its associated programs.
Refer to your Microsoft Developer Studio documentation for information about the registry.
The following table lists the properties you define when adding registry changes.
See Assigning to Components for more information on assigning to components.