Java in the Database

Java in the database is supported for remote data access with Component Integration Services.

The following restrictions apply:

Java is supported for remote SAP ASE 12.x and later only.
Java is supported for language events only (no dynamic SQL can be used with remote tables.)

After installing your Java class files on the local server, install the required Java class files on the remote server.

@@textsize – data is returned as a serialized Java object using the image datatype format and then deserialized on the local server. @@textsize must be set large enough to hold the serialized object. If @@textsize is set too small, the object is truncated, and the deserialization fails.
@@stringsize – indicates the amount of character data to be returned from a toString() method. It is similar in behavior to @@textsize, except it applies only the char data returned by the Java Object.toString() method. The default value is 50. The maximum value is 16384. A value of zero means “use the default.” This value can be modified by a set command:
```
set stringsize n
```
where n is an integer value between 0 and 16384. The value immediately displays in the global variable @@stringsize.

Constraints on Java Class Columns
Constraints defined on Java columns of remote tables must be checked on the remote server.
Java Abstract Datatypes (ADTs)
Java Classes in SQL (JCS) is the method of storing and using Java objects within the SAP ASE. Component Integration Services interaction in this implementation is needed to support Java objects and Java functions on remote servers.

Parent topic: Component Integration Services Concepts

Related concepts

Java Class Definitions