Managing DataBlade Modules
Managing DataBlade modules includes the tasks described in the following subsections:
Connection Information
After you install a DataBlade module in a database server, you register the DataBlade module in each database in which you want to use that module. To register a DataBlade module in a database, you must first connect to a database.
You need connect and resource permissions to connect to the database and register DataBlade modules. See the INFORMIX-Universal Server Administrator's Guide for more information on permissions.
Before BladeManager can connect to a database, your Informix environment must be properly configured on the computer running the database server, and on the client computer.
This section describes:
Connecting to Informix Dynamic Server
When you start BladeManager, it uses default values for your user name, password, and database server unless you explicitly issue commands to change them.
The default user name and password are defined as your operating system login and password. The default database server is defined as the value of the INFORMIXSERVER environment variable. For information on setting these values, see INFORMIX-Universal Server Administrator's Guide. 
The default values for user name, password, and database server are listed in the Setnet32 utility. The default database server is defined as the value of the INFORMIXSERVER environment variable. For information on setting these values, see Informix Client Products Installation Guide for Microsoft Windows Environments.
You can change your connection to an Informix database server:
At the password prompt, enter the password. The user name and password are not validated until you attempt to connect to a database.
Connecting to Databases
BladeManager commands to register, unregister, list registered, and show available DataBlade modules operate on a specific database.
After you start BladeManager, you can connect to a database:
The first time BladeManager connects to a database, it prepares the installed DataBlade modules for registration and generates a log file. If BladeManager fails to connect to a database or preparation fails, look at the appropriate log file (see "Viewing Log Files"), and see Appendix A, "Troubleshooting Registration Problems," for possible solutions.
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.
After you connect to a database, you can register a DataBlade module:
Modules that contain client files display the letter c after the module name.
module is the name of the DataBlade module directory in 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 state prior to the attempted registration. To see the SQL statements that failed to execute, look at the corresponding log file (see "Viewing Log Files"), and see Appendix A, "Troubleshooting Registration Problems," for possible solutions.
Some DataBlade modules depend on one or more interfaces. An interface defines dependencies between DataBlade modules: the DataBlade module requiring the interface is dependent on the functionality of the DataBlade modules providing that 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.
BladeManager first registers the DataBlade module providing the interface, then registers the original module. If there are no DataBlade modules that provide the needed interface installed on your database server, you cannot register the original module.
Upgrading a DataBlade Module
To upgrade a DataBlade module, use BladeManager to register a new version of the module: this unregisters the old version. For more information on what happens during registration, see "Registering a DataBlade Module".
To upgrade or downgrade a DataBlade module, enter the following command:
module is the name of the DataBlade module directory in the form of the DataBlade module name followed by the version number. BladeManager warns you that you are upgrading or downgrading a DataBlade module.
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 upgrade of a module fails, BladeManager returns the database to its state prior to the attempted upgrade. To see the SQL statements that failed to execute, look at the corresponding log file (see "Viewing Log Files"), and see Appendix A, "Troubleshooting Registration Problems," for possible solutions.
Unregistering a DataBlade Module
When BladeManager unregisters a DataBlade module, it removes each element of the DataBlade module from the database using SQL DROP statements. For more information on what happens during registration, see "Registering a DataBlade Module".
To unregister a DataBlade module, enter the following command:
module is the name of the DataBlade module directory in the form of the DataBlade module name followed by the version number. If BladeManager is not currently connected to the database specified in the unregister 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 the unregister command.
If the unregistration of a module fails, BladeManager returns the database to its state prior to the attempted unregistration. To see the SQL statements that failed to execute, look at the corresponding log file (see "Viewing Log Files"), and see Appendix A, "Troubleshooting Registration Problems," for possible solutions.
|
