User`s guide

12
Java in the Database 12-1
12 Java in the Database
This chapter describes BS2000-specific features for Java in the database. This chapter
includes:
■ Installation of a Java Enabled Database
■ Database character sets and Java Encodings
■ Java Demonstration Files
For more information, refer to the Oracle Java documentation set.
12.1 Installation of a Java Enabled Database
When you call $ORAC1120.INSTALL.P.SUPER and set the JAVA parameter to YES, you'll
get a suitable
ORAENV file (with ORACLE_HOME as described earlier), a database sized to
Java requirements and Java installed inside the database.
When you try to enable Java in an existing Oracle database, you can use the Java
related parts of this procedure as an example and modify it according to your needs,
that is, increase dbsize, increase
shared_pool_size , create a large rollback segment,
run
initjvm.sql , and so on. For more information, refer to Oracle Database Java
Developer's Guide.
Where can files related to Java reside and how should they be encoded?
It is not absolutely straightforward where files used by Java have to be stored and how
they should be encoded. In general files can reside in native BS2000 or in the POSIX
file system, but there are exceptions.
The following table gives an overview of the file types, location, default encoding, and
encoding modifications for APIs or statements
Statement or API File type Place
Default
encoding
Encoding
modification
CREATE JAVA CLASS
USING BFILE
.class BS2000 PAM
file or
POSIX
Binary Not applicable
CREATE JAVA
RESOURCE USING
BFILE
.properties BS2000 PAM
file or
POSIX
ascii None, that is,
there is no
means to
change default
encoding)