Registering a DataBlade module

When BladeManager registers a DataBlade module, it executes a set of SQL statements to register each database object in the module. Registration is equivalent to creating database objects individually with the SQL CREATE statement.

You must have resource permissions on the database to register a DataBlade module in it. Additionally, if the server is configured so that the EXTEND role is needed to add UDRs and UDTs, then you must be granted the EXTEND role by a DBSA (typically, user informix).

To register a DataBlade module:

On the Databases page, select the database in which you want to register a module.
In the Available list box, select the module you want to register.
Click Add.
Click Apply.

If registration fails, BladeManager returns the database to its prior state. To see the SQL statements that failed, look at the corresponding log file (see Viewing log files) and see Troubleshooting registration problems, for possible solutions.

Some DataBlade modules depend on one or more interfaces. An interface is like a contract between DataBlade modules: the DataBlade module that requires the interface depends on the functionality of the DataBlade module that provides the interface.

When you register a DataBlade module with an interface dependency, BladeManager verifies that one of the DataBlade modules that provides that interface is registered in the database. If it is, registration continues. If it is not, BladeManager displays the Modules with Missing Interface dialog box; select one of the DataBlade modules and click OK.

Important: BladeManager does not verify the integrity of the DataBlade modules that provide a required interface; BladeManager does not check for the presence of the required database objects.