SQLJ Driver Built-In Procedures
Use the SQLJ Driver built-in procedures for one of the following tasks:
- To install, replace, or remove a set of Java™ classes
- To specify a path for Java class resolution for Java classes that are included in a JAR file
- To map or remove the mapping between a user-defined type and the Java type to which it corresponds
SQLJ Driver Built-In Procedures
(1)
|--+-| sqlj.install_JAR |---------+-----------------------------|
| (2) |
+-| sqlj.replace_JAR |---------+
| (3) |
+-| sqlj.remove_JAR |----------+
| (4) |
+-| sqlj.alter_java_path |-----+
| (5) |
+-| sqlj.SetUDTextName |-------+
| (6) |
'-| sqlj.unsetUDTextName |-----'
Note:
- See sqlj.install_jar
- See sqlj.replace_jar
- See sqlj.remove_jar
- See sqlj.alter_java_path
- See sqlj.setUDTextName
- See sqlj.unsetUDTextName
A client application must specify the 'sqli' owner name to invoke these functions from an ANSI-compliant database.
The SQLJ built-in procedures are stored in the sysprocedures system catalog table. They
are grouped under the sqlj schema.
Tip: For any Java static method, the first built-in procedure that you
execute must be the sqlj.install_jar( ) procedure. You must install the JAR file before
you can create a UDR or map a user-defined data type to a Java type. Similarly, you cannot use any of the other SQLJ built-in procedures until you
have used sqlj.install_jar( ).