After you specify the user-defined objects, imported objects, and files you want to include in your DataBlade module, use BladeSmith to generate the files you need for compiling a shared object file or dynamic link library, managing a DataBlade module in Informix Dynamic Server, testing object functionality, and creating installation packaging files. These files are described in the following table.
Source code
You use these files to create a shared object or dynamic link library. They include source code files, header files, and makefiles that you compile into a shared object file or dynamic link library.
SQL script
These files contain the SQL statements that support the DataBlade modules in the database system tables. They include prepare scripts that describe the DataBlade module, and object scripts that describe the DataBlade objects.
Test
You use these files to test the positive and negative operation of user-defined routines, opaque data type support routines, and casts.
Packaging
You use these files with BladePack to generate installation files and executables.
The generated source code files contain routine definitions. Overloaded versions of built-in routines, including opaque data types support routines, may not need modification, but user-defined routines need to be edited. The areas of the generated source code that need modification are marked with TO DO: comments. When your C code is complete, you compile the source code files into the shared object file. For instructions, see the DataBlade Developers Kit User's Guide or the tutorial in the on-line DataBlade Developers Kit InfoShelf. BladePack You use BladePack to create an installable DataBlade module package. BladePack uses the packaging project file created by BladeSmith as the basis for the installation package. The packaging file references the SQL scripts, shared object file, and other files required by the DataBlade module. The installation scripts ensure that all DataBlade modules created with the DataBlade Developers Kit can be installed in a similar way. You can perform the following tasks with BladePack:
TO DO:
BladeManager You use BladeManager to register or unregister your DataBlade module in a database and to install or uninstall DataBlade module client files. After you install a DataBlade module on a server, you must register it in every database that uses the module. Registration involves adding the DataBlade SQL scripts to the database system tables and making the DataBlade shared object or dynamic link library available to the server. BladeManager checks for dependencies between DataBlade modules. If you have imported an interface from another DataBlade module, BladeManager registers your DataBlade module only after confirming that the interface is registered in the database. If you are upgrading your DataBlade module, BladeManager automatically unregisters the previous version. You can also unregister any module by using BladeManager. BladeManager does not allow you to unregister a DataBlade module if there is another DataBlade module that depends on it or if any of its objects are used in the database. See the DataBlade Module Installation and Registration Guide for more information.