There isn't a great deal of need for this on UNIX since the blademgr command line utility is distributed as part of IDS in the bin directory - though having said that it would be handy to be able to perform as many administrative functions as possible remotely via SQL.
On Windows there is no command line blademgr utility; the only option is to install the DBDK (DataBlade Developer's Kit) and use the GUI Blade Manager utility in order to register a blade with a database. That seems like a lot of effort to go to just to register a blade, especially since IDS 11.10 comes with some new bundled blades like Binary UDT, Basic Text Search and Node.
There is an alternative to calling blademgr, and that is to call the underlying SYSBldPrepare() and SYSBldRegister() SQL functions to register a blade manually. As far as I know this method was first published externally by Jochen Platzer in this comp.databases.informix thread in 2004:
datablade registration in ANSI database
For example here is how I would register the Binary UDT datablade with a database called "mydb":
- DATABASE mydb;EXECUTE FUNCTION SYSBldPrepare('ifxmngr', 'sysblderrorlog'); EXECUTE FUNCTION SYSBldRegister('binaryudt.1.0','sysblderrorlog');
Now suppose I wanted to automate this process on Windows and create a batch file that registers an arbitrary blade to a database. Something like this would work for simple blades (i.e. blades that do not depend on other blades):
echo EXECUTE FUNCTION SYSBldPrepare('ifxmngr', 'sysblderrorlog'); ^ EXECUTE FUNCTION SYSBldRegister('%2','sysblderrorlog') | dbaccess %1
So to register the Binary UDT blade to a database "mydb" using this batch file you would call: bladereg mydb binaryudt.1.0.
See Jochen's original post for instructions on manually registering blades that depend on other blades (like the Excalibur Text Blade for example). In summary, each dependent blade should be registered with SYSBldRegister in the correct order.
Is this method a supported way of registering a blade? Well, since it is not officially documented (AFAIK), it could change at some point, so if you have trouble with it, it would be advisable to try reproducing the problem with blademgr first.