Debugging a DataBlade module
Debugging a DataBlade® module
is usually an iterative process, repeated several times until the
code is debugged.
About this task The debugging process has the following general steps:
Procedure Compile the JAR file (if necessary). Install the DataBlade module
shared object and SQL scripts in the $ONEDB_HOME/extend/project directory.
Start your database server while logged on as the informix user.
See the HCL OneDB™
Administrator's Guide
Register the DataBlade module
by using BladeManager (if
necessary).
If you are replacing an existing JAR file, shut down and
restart the database server.
Execute a query that calls the method by using an SQL query
tool such as DB-Access or SQL Editor. See the HCL OneDB DB-Access User's
Guide
Examine the Java™ log
file for errors.
Edit the source code (if necessary). Repeat the procedure, as necessary. Installing a DataBlade module DataBlade module for debugging, create a project directory and copy the necessary files to it. Create the project directory under $ONEDB_HOME/extend . The name of the project directory is what BladeManager uses as the DataBlade module name.Register a DataBlade module DataBlade module the first time you install it and register later if you change the definition of any of your DataBlade module objects in BladeSmith and generate new SQL files. You do not have to reregister your DataBlade module when you only replace its JAR file.Replace a DataBlade module JAR file DataBlade module is loaded onto the HCL OneDB database server, the database server stores it in the database server memory map. Therefore, if you overwrite a JAR file while it is loaded in the database server, you must stop and restart the database server to unload the old JAR file and load the new one.Have feedback? Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.