Register 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).

After you connect to a database, you can register a DataBlade module, as follows:

To display a list of DataBlade modules installed on the database server that are available for registration, enter the following command:
```
show modules
```
Modules that contain client files display the letter c after the module name.
To display a list of DataBlade modules registered in the specified database, enter the following command:
```
list database_name
```
To register a DataBlade module in the specified database, enter the following command:
```
register module_name database_name
```
In the preceding example command, module_name represents the name of the DataBlade module directory. These names typically follow the form of the DataBlade module name followed by the version number.

If BladeManager is not currently connected to the database specified in the register command, it connects to the new database, prepares all available DataBlade modules, and displays a message about the success or failure of the preparation before continuing with registration.

If the registration of a module fails, BladeManager returns the database to its prior state. To see the SQL statements that failed, look at the corresponding log file (see View 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, BladeManager verifies that one of the DataBlade modules that provides the interface required by your module is already registered in the database. If it is, registration continues. If it is not, BladeManager prompts you to register the DataBlade module providing the interface.

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.