Having trouble with JBOExceptions during deployment of your ADF application on AS 10.1.3? americas cup win 2682133k1

Having trouble with JBOExceptions during deployment of your ADF application on AS 10.1.3?

August 11, 2006 DBA Oracle, Oracle, Oracle WebLogic Server 1 Comment

or How to deploy into an application-specific OCJ4-container on Oracle AS 10.1.3 without JBOExecption during deployment when your application uses ADF   Lately our developers were working on an application which uses ADF and requested an Oracle AS 10.1.3 J2EE implementation as webserver for the deployment of this Java application.
The webserver was quickly and effortlessly installed and the ear-file was soon ready to install. A deadline was lurking for the acceptance testing by the client and up to now everthing went smoothly until …the deployment.

During development everthing was run against an OC4J-standalone implementation where the ADFinstaller was run via JDeveloper 10.1.3. Now the deployment failed constantly with a nagging and unexplainable JBOException at the end. Even after having run the ADFinstaller!

What went wrong?

We had created a second OC4J-container for the application so we don’t install into the home-container. Nowhere, nor in the install guide of the ADFruntime installer, nor in the install guide of the AS is mentioned that the ADFruntime-installer is just for the container it was originally installed in, namely “home”.

All the other OC4J-containers which can be added are (initially) not able to use the ADFruntime-jars because the new container does not know they exist. Searching Metalink for “JBOException” does not result in any articles which mention problems of AS 10.1.3 with ADF, especially not in combination with non-home installed applications. By pure chance I snuffed though the Knowledge Base Article Overview for Application Servers and stumbled across DOC_ID 371937.1 “How to Configure a 2:nd OC4J Instance for ADF use Within Oracle Application Server 10.1.3”.

Basically, what you have to do is repeat all entries which the ADF-installer inserts into the server.xml and application.xml files of the home-container in the acording xml-files for each OC4J-container under the application server which are destined to run ADF-based applications. Just cut them out of the article and plug them into the server and application.xml onder {OH}/j2ee/(but check your paths first if your AS install is not default). Then, restart your midtier instance.
Having done that,the ADF-containing ear-file deploys without the JBOException.

Related Posts

About The Author

Karin Kriebisch

Karin is an experienced, broadly orientated Oracle consultant (senior DBA consultant (OCP)) and is specializing in Oracle Database Security (Oracle Implementation Specialist Security 11g). Karin uses to work in divers enterprise environments like pension fonds, banks or pharmaceuticals, where ITIL and Service Management software products (e.g. Assyst, Remedy, Jira, GLPI) play a big role. She is regularly working for custumers in development projects and migrations, so her experience lead her to pay special attention in the areas of maintenance and (database)infrastructure. Her knowledge embraces multiple operating systems like OpenVMS, Linux, HP-UX and of course Windows, and she is comfortable with Oracle Database versions starting with Oracle 7 up to 12c and virtualization environments like vmWare and Oracle Virtualbox. Add to this her ability of scripting (for Windows commandline and Powershell, *nix shells) and her knowlegde of Oracle applicatieservers (incl. WebLogic) to her portfolio and it makes her a technical allround Oracle specialist. Karin is very customer and service orientated and always strives to reach her goals. She has a very sharp analytical mind and a keen eye for the details in the big picture. Karin is a senior DBA at AMIS b.v. for more than 15 years and she still likes the changing environments she is able to work in and meeting new and interesting people all the time.

One Response

  1. Jacco Landlust August 13, 2006

    When you think about this, you know you should have expected this behaviour. A seperate container means a seperate virtual machine. Therefore a different classpath exists. ADF is “just” another library, so it should be container specific instead of globally availlable.

    B.T.W. did you have fun deploying the .ear file? Also deploying on a cluster without multicast is loads of fun 😉