This chapter describes BS2000-specific features for Java in the database. This chapter includes:
See Also:
Oracle Java documentation set for more informationWhen you call $ORACINST.INSTALL.P.SUPER
and set the JAVA
parameter to YES
, you get a database that meets the Java requirements.
When you 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. For example, you can increase dbsize
, shared_pool_size
, create a large rollback segment, run initjvm.sql
, and so on.
See Also:
Oracle Database Java Developer’s Guide for more informationWhere can files related to Java reside and how should they be encoded?
It is not absolutely straightforward where files used by Java must be stored and how they should be encoded. In general, files can reside either in the native BS2000 or in the POSIX file system. However, 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 |
---|---|---|---|---|
|
.class |
BS2000 PAM file or POSIX |
Binary |
Not applicable |
|
.properties |
BS2000 PAM file or POSIX |
ascii |
None, that is, there is no means to change the default encoding. |
|
.java, .sqlj |
BS2000 PAM file or POSIX |
DB charset |
None, that is, there is no means to change the default encoding. |
|
.sql |
Part of statement |
Session character set specified in |
|
|
*, .jar, .zip |
POSIX |
DB charset |
Option encoding in loadjava call |
|
* |
POSIX |
DB charset |
Depends on the classes used |
You can create BS2000 PAM files in ASCII by transferring files with the File Transfer Protocol (FTP) from an ASCII platform to BS2000 in binary mode.
The distinction between a native BS2000 file name and a POSIX file name is made by the preceding slash ('/'). As a consequence, no relative path names are allowed for POSIX file names.
However, there is an exception: when used within dbms_java.loadjava
, relative path names are preceded by the value of ORACLE_HOME
in ORAENV
file.
As far as I/O is concerned, the Oracle JAVAVM uses the database character set as the system property file.encoding
. Therefore, the following Oracle Database on Fujitsu BS2000/OSD database character sets have been added to the list of supported Java encodings:
WE8BS2000 WE8BS2000E EE8BS2000 CE8BS2000 CL8BS2000 WE8BS2000L5
These encodings are not known to any other Java implementation.
The system property file.encoding
, however, does not apply to Java property files. Property files always use the encoding 8859_1. The system property file.encoding
is used when compiling a source file. You can change this default by either using the following procedure or by setting the encoding option of the procedure dbms_java.loadjava
:
dbms_java.set_compiler_option('','encoding',...)
See Also:
Oracle Database SQLJ Developer’s Guide for more details about property filesA simple Java demonstration program running in the server is shipped under:
$ORACINST.JAVAVM.DEMO.HELLO.SQL
An example with database connection using the server-side internal driver is shipped under:
$ORACINST.JAVAVM.DEMO.EMPLOYEE.JAVA $ORACINST.JAVAVM.DEMO.CREATE.SQL $ORACINST.JAVAVM.DEMO.RUN.SQL