It is recommended that all classes and JAR files that are being used with Java in the database be installed in the database.
When you store the classes and JAR files within the database, the database can be easily moved to a different computer or
operating system. Another benefit of installing classes and JAR files into the database is that the database server's class
loader can fetch the classes and resources from the database, allowing each connection that is using Java in the database
to have its own instance of these classes and its own copy of static variables within these classes.
However, when a class or JAR file must be loaded by the system class loader, it can be specified with the java_class_path
database option or the -cp dbeng12/dbsrv12 server option. Both options add classes and JAR files to the classpath that the
database server builds for launching the Java VM. The java_class_path database option is useful when the server is running
multiple databases and each database has a different set of JARs and directories that need to be loaded by the system class
loader. The -cp database server option is useful when all databases on the server require the same classes or JAR files.