Registering the JAR or ZIP File | Java External Stored Procedures | Vantage - Registering the JAR or ZIP File - Advanced SQL Engine - Teradata Database

SQL External Routine Programming

Product
Advanced SQL Engine
Teradata Database
Release Number
17.05
17.00
Published
June 2020
Language
English (United States)
Last Update
2021-01-24
dita:mapPath
qwr1571437338192.ditamap
dita:ditavalPath
lze1555437562152.ditaval
dita:id
B035-1147
lifecycle
previous
Product Category
Teradata Vantage™

After you write and test the Java source code for an external stored procedure, you place the resulting class or classes in an archive (JAR or ZIP) file.

Next, you call the SQLJ.INSTALL_JAR external stored procedure to register the archive file and its classes with the database, specifying an SQL identifier for the archive file. The SQL identifier that you specify is the same name that you use later in the EXTERNAL NAME clause of the CREATE PROCEDURE or REPLACE PROCEDURE statement to define the external stored procedure.

For example, consider a JAR file called reports.jar on a Windows client in the directory C:\java_xsp.

The following statements register the JAR file with the JXSP database and create an SQL identifier called Report_JAR for the JAR file:

DATABASE JXSP;
CALL SQLJ.INSTALL_JAR('CJ?C:\java_xsp\reports.jar', 'Report_JAR', 0);

For details on how to register the archive file for a Java external stored procedure, see Registering and Distributing JAR and ZIP Files for Java External Routines.