Registering the JAR or ZIP File | Java External Stored Procedures | Vantage - Registering the JAR or ZIP File - Analytics Database - Teradata Vantage

SQL External Routine Programming

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-07-11
dita:mapPath
iiv1628111441820.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
B035-1147
lifecycle
latest
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.