HOW TO: Set up your application server to run BC4J

Question

How To set up your application server to run BC4J.
INTRODUCTION
A running BC4J application is actually the combination of:
* Your own application files
* BC4J runtime libraries
In order to successfully run your BC4J application in local mode, the first requirement is
that your application server contains the necessary BC4J libraries.
This How To describes the steps required to ensure that you have a functional
BC4J runtime environment installed on your application server.
Oracle IAS 1.0.2 and Tomcat 3.1 will be used as examples.
THE BC4J RUNTIME LIBRARIES
Whatever application server you deploy to, the following libraries
are required in the following order to be in the classpath.
BC4J Libraries:
xmlparserv2.jar
jdev-rt.zip
jbojdbcpatch.zip
connectionmanager.zip
jbohtml.zip
jboimdomains.zip
ordim817.zip
ordvir817.zip
ordhttp.zip
jbomt.zip
jbodomorcl.zip
jboremote.zip
jndi.jar
jbodatum12.zip
These libraries can be found in <JDEV_HOME>/lib/
INSTALLING THE LIBRARIES ON IAS:
Installing the libraries is simply a matter of copying them to the
application server's filesystem and adding them to the classpath.
IAS's classpath can be modified by editing the file:
<IAS_HOME>\Apache\Jserv\conf\jserv.properties
In this file you'll find the existing pre-installed BC4J libraries which
looks like this:
wrapper.classpath=<IAS_HOME>\Apache\BC4J\lib\ordvir817.zip
wrapper.classpath=<IAS_HOME>\Apache\BC4J\lib\ordim817.zip
etc.
Note! These BC4J libraries correspond to JDeveloper 3.1.1.
In order to run JDev 3.2 based applications you will have to update these libraries
to JDeveloper 3.2 production.
Steps:
1. Copy (or FTP) the JDev 3.2 BC4J libraries from <JDEV_HOME>\lib to a NEW directory on the
appserver's filesystem called:
<IAS_HOME>\Apache\BC4J\newlib
2. Modify the classpath by editing <IAS_HOME>\Apache\Jserv\conf\jserv.properties.
Example: (modified classpath entries)
# New 3.2 BC4J Runtime libraries
wrapper.classpath=<IAS_HOME>\Apache\BC4J\newlib\xmlparserv2.jar
wrapper.classpath=<IAS_HOME>\Apache\BC4J\newlib\jdev-rt.zip
wrapper.classpath=<IAS_HOME>\Apache\BC4J\newlib\jbojdbcpatch.zip
wrapper.classpath=<IAS_HOME>\Apache\BC4J\newlib\connectionmanager.zip
wrapper.classpath=<IAS_HOME>\Apache\BC4J\newlib\jbohtml.zip
wrapper.classpath=<IAS_HOME>\Apache\BC4J\newlib\jboimdomains.zip
wrapper.classpath=<IAS_HOME>\Apache\BC4J\newlib\ordim817.zip
wrapper.classpath=<IAS_HOME>\Apache\BC4J\newlib\ordvir817.zip
wrapper.classpath=<IAS_HOME>\Apache\BC4J\newlib\ordhttp.zip
wrapper.classpath=<IAS_HOME>\Apache\BC4J\newlib\jbomt.zip
wrapper.classpath=<IAS_HOME>\Apache\BC4J\newlib\jbodomorcl.zip
wrapper.classpath=<IAS_HOME>\Apache\BC4J\newlib\jboremote.zip
wrapper.classpath=<IAS_HOME>\Apache\BC4J\newlib\jndi.jar
wrapper.classpath=<IAS_HOME>\Apache\BC4J\newlib\jbodatum12.zip
Note: Make sure to remove or comment out the existing 3.1.1 BC4J library entries!
To see the changes, you must restart IAS and that's it, your IAS will be updated with
the JDev 3.2 BC4J libraries which allow you to run BC4J Data Tags among other
things!
INSTALLING THE LIBRARIES ON TOMCAT
As before, this process involves both the copying of the libraries
and modifying the classpath.
After copying the BC4J libraries to a path accessible from Tomcat,
you can modify Tomcat's classpath by editing it's startup script:
<TOMCAT_HOME>\bin\tomcat.bat (NT)
<TOMCAT_HOME>\bin\tomcat.sh (Unix)
Here is a portion of a modified tomcat.bat (on NT)
rem Add BC4J libraries
set CLASSPATH=%CLASSPATH%;D:\bc4j_lib\xmlparserv2.jar
set CLASSPATH=%CLASSPATH%;D:\bc4j_lib\jdev-rt.zip
set CLASSPATH=%CLASSPATH%;D:\bc4j_lib\jbojdbcpatch.zip
set CLASSPATH=%CLASSPATH%;D:\bc4j_lib\connectionmanager.zip
set CLASSPATH=%CLASSPATH%;D:\bc4j_lib\jbohtml.zip
set CLASSPATH=%CLASSPATH%;D:\bc4j_lib\jboimdomains.zip
set CLASSPATH=%CLASSPATH%;D:\bc4j_lib\or dim817.zip
set CLASSPATH=%CLASSPATH%;D:\bc4j_lib\ordvir817.zip
set CLASSPATH=%CLASSPATH%;D:\bc4j_lib\ordhttp.zip
set CLASSPATH=%CLASSPATH%;D:\bc4j_lib\jbomt.zip
set CLASSPATH=%CLASSPATH%;D:\bc4j_lib\jbodomorcl.zip
set CLASSPATH=%CLASSPATH%;D:\bc4j_lib\jboremote.zip
set CLASSPATH=%CLASSPATH%;D:\bc4j_lib\jndi.jar
set CLASSPATH=%CLASSPATH%;D:\bc4j_lib\jbodatum12.zip
rem Add Oracle JDBC library
set CLASSPATH=%CLASSPATH%;D:\bc4j_lib\classes12.zip
Note: I also added the Oracle JDBC library since Tomcat does not have it.
It is found at:
<JDEV_HOME>\jdbc\lib\oracle8.1.7\classes12.zip
And That's It!
When Tomcat is restarted using this script, the necessary BC4J libraries
will be in the classpath..
A follow up How To:"How To Deploy a BC4J JSP Application on IAS and Tomcat"
will be posted shortly!

Answer 1

I copied the following files in jserv classpath
bc4jct.jar
bc4jctejb.jar
bc4jdomorcl.jar
bc4jhtml.jar
bc4jimdomains.jar
bc4jmt.jar
bc4jmtejb.jar
bc4juixtags.jar
collections.jar
datatags.jar
jdev-cm.jar
regexp.jar
share.jar
uix2.jar
cabo.war
classes12.jar
nls_charset12.jar
ordim.jar
ordhttp.jar
runtime12.jar
jdev-rt.jar
xmlparserv2.jar
bc4j_jclient_common.jar
webapp.war
I got this list from Jdev 9031 on-line help
I also copied the new DataTags.tld file to /webapp directory
When i run my jsp page i get this error..
java.lang.NoClassDefFoundError: java/util/TimerTask
     at oracle.jbo.http.HttpContainer.findSessionCookie(HttpContainer.java:693)
     at oracle.jbo.html.jsp.datatags.ApplicationModuleTag.doStartTag(ApplicationModuleTag.java:148)
     at jspapp.odrjsp__html._menu._jspService(Compiled Code)
     at oracle.jsp.runtime.HttpJsp.service(HttpJsp.java:119)
     at oracle.jsp.app.JspApplication.dispatchRequest(Compiled Code)
     at oracle.jsp.JspServlet.doDispatch(Compiled Code)
     at oracle.jsp.JspServlet.internalService(Compiled Code)
     at oracle.jsp.JspServlet.service(Compiled Code)
     at javax.servlet.http.HttpServlet.service(Compiled Code)
     at oracle.portal.provider.v1.http.JspRenderer.renderBody(JspRenderer.java:116)
     at oracle.portal.provider.v1.RenderManager.render(RenderManager.java:164)
     at oracle.portal.provider.v1.http.ServletProviderResponse.showPortlet(Compiled Code)
     at oracle.portal.provider.v1.http.HttpProvider.dispatchProviderAction(Compiled Code)
     at oracle.portal.provider.v1.http.HttpProvider.service(Compiled Code)
     at javax.servlet.http.HttpServlet.service(Compiled Code)
     at org.apache.jserv.JServConnection.processRequest(Compiled Code)
     at org.apache.jserv.JServConnection.run(Compiled Code)
     at java.lang.Thread.run(Compiled Code)
In the JDK 1.3 APi docs, i found that TimerTask was introduced only in JDK 1.3
Does this mean that BC4J (in jdev 9031) will only work
with JDK 1.3 or later?
Thanks for your time.
Harish