DataBlade Module Installation and Registration Guide

DataBlade Module Installation and Registration Guide
Chapter 2: Registering with the BladeManager Graphical User

Home Contents Index Master Index New Book

Managing DataBlade Modules

To manage DataBlade modules, use the Databases page, as shown in Figure 2-1.


	Figure 2-1 Databases Page

Managing DataBlade modules consists of tasks as described in the following subsections:

Connecting to a Database

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 to register DataBlade modules. See the INFORMIX-Universal Server Administrator's Guide for more information on permissions.

Important: For best results with BladeManager, run it while logged on as the default user, as recognized by the Informix server. If you need to log on to the Informix server after logging on to your host computer, you are not the default user. If necessary, specify the user name and password you want to use for a particular database server using the Setnet32 utility, then restart BladeManager.

To connect to a database

1. To see a list of available database servers, in the Databases list box on the Databases page, click the expander button next to the network and database server icons.

2. Click the name of the database to which you want to connect.

If you select a database server or database that requires a user name or password other than the default, BladeManager displays a login window that allows you to specify a user name and password.

3. If the User Login dialog box appears, type a user name and password that have the required permissions for the database.

After you connect, BladeManager displays the registered and available DataBlade modules for that database.

The first time BladeManager connects to a database, BladeManager prepares the installed DataBlade modules for registration and generates a log file. During the preparation, BladeManager gathers the DataBlade module information that appears on the BladeManager pages. If the preparation of a DataBlade module fails, the DataBlade module does not appear in the Available list box. Check the log file for information about preparation failures (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.

To register a DataBlade module

1. On the Databases page, select the database in which you want to register a DataBlade module (see Figure 2-1).

2. In the Available list box, select the DataBlade module you want to register.

3. Click Add to move the DataBlade module from the Available list box to the Registered list box.

4. Click Apply to register the DataBlade module in the database.

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 is a contract 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 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 prompts you to register a 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.

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.

If your DataBlade module depends on an interface provided by another DataBlade module, BladeManager displays the Modules with Missing Interface dialog box after you click Apply to register the DataBlade module.

To register a DataBlade module with the necessary interface, select one of the DataBlade modules listed in the Modules with Missing Interface dialog box and click OK.

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".

Important: You cannot use the following procedure to upgrade or downgrade some versions of DataBlade modules. For instructions on which versions can be upgraded or downgraded, see the release notes for the DataBlade module.

To upgrade a DataBlade module

1. On the Databases page, select the database in which you want to upgrade a DataBlade module (see Figure 2-1).

2. In the Available list box, select the DataBlade module you want to upgrade.

3. Click Add to move the DataBlade module from the Available list box to the Registered list box.

4. Click Apply to upgrade the DataBlade module in the database.

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.

To downgrade a DataBlade module, use the above procedure to replace the DataBlade module with an earlier version.

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".

Important: BladeManager does not unregister a DataBlade module that provides a required interface for DataBlade modules or database objects.

To unregister a DataBlade module

1. On the Databases page, select the database from which you want to unregister a DataBlade module (see Figure 2-1).

2. In the Registered list box, select the DataBlade module you want to unregister.

3. Click Remove to move the DataBlade module from the Registered list box to the Available list box.

4. Click Apply to unregister the selected DataBlade module in the database.

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.

DataBlade Module Installation and Registration Guide, version 3.6
Copyright © 1998, Informix Software, Inc. All rights reserved.