aspose file tools*
The moose likes Oracle/OAS and the fly likes Deploy works with OC4J standalone, but not OAS console deploy... Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Oracle/OAS
Bookmark "Deploy works with OC4J standalone, but not OAS console deploy..." Watch "Deploy works with OC4J standalone, but not OAS console deploy..." New topic
Author

Deploy works with OC4J standalone, but not OAS console deploy...

Garrett Reinard
Greenhorn

Joined: Dec 10, 2004
Posts: 10
Hello all...

I'm having a problem... I have an application that when built into an ear file can be successfully deployed to OC4J standalone... The app works too...

However, if I give the sys admin my ear file and he uses the admin console for the real OAS instance... while trying to deploy, an error comes back and just says "NullPointerException" with no other information at all...

has anyone encountered this before...

BTW, my standalone instance is on a Win2k machine, the OAS is on Linux, not sure if that matters but thought I'd mention it...

Thanks,
Garrett
Jeanne Boyarsky
author & internet detective
Marshal

Joined: May 26, 2003
Posts: 30957
    
158

Garrett,
I know this problem is mysterious to you too, but you are really unlikely to get an answer without some more specifics.

Some things I can think of that might help expand on the problem:
1) Have you ever sucessfully deployed to the OAS instance?
2) Are there messages in any logs?
3) What is in the ear file? (entity beans, session beans, servlets, ...) Have you ever sucessfully deployed each of those elements before?


[Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Blogging on Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, OCAJP, OCPJP beta, TOGAF part 1 and part 2
Avi Abrami
Ranch Hand

Joined: Oct 11, 2000
Posts: 1135

Garrett,
Oracle <unstated version> Application Server is very different to OC4J <unstated version> stand-alone. What makes you think that EAR creation and deployment is identical on both of them? Maybe you should install "OAS" (as you call it) on your machine and test using that? (It is free for development purposes.)

Good Luck,
Avi.
Garrett Reinard
Greenhorn

Joined: Dec 10, 2004
Posts: 10
Originally posted by Jeanne Boyarsky:
Garrett,
I know this problem is mysterious to you too, but you are really unlikely to get an answer without some more specifics.

Some things I can think of that might help expand on the problem:
1) Have you ever sucessfully deployed to the OAS instance?
2) Are there messages in any logs?
3) What is in the ear file? (entity beans, session beans, servlets, ...) Have you ever sucessfully deployed each of those elements before?


Our sys admin has configured the OAS, and at this point, I believe he may have a deployment or so out on it... My application has never been deployed on the OAS server... It is quite possible that there are OAS config problems... That's what we are trying to figure out... I have three different Ears actually, but we are trying to deploy only one of them for now just to make sure it is working... the one we are trying to deploy right now consists of only session beans and maybe a web app or two...

They have all be successfully deployed and tested on standalone OC4J...

Originally posted by Avi Abrami:
Garrett,
Oracle <unstated version> Application Server is very different to OC4J <unstated version> stand-alone. What makes you think that EAR creation and deployment is identical on both of them? Maybe you should install "OAS" (as you call it) on your machine and test using that? (It is free for development purposes.)

Good Luck,
Avi.


Well, if there are differences what are they? To my knowledge, OAS actually uses an OC4J container under the hood. That is why I believe they are compatible... We are using the method suggested by oracle... develop on standalone, deploy to OAS... They both use identical configuration files and archive build structures...

Just out of curiosity, do you even know what OAS is or have you worked with orion web deployments? Your comments lead me to believe that you aren't familiar with the software I am talking about. "OAS" is Oracle Application Server... That's not what I call it, that is what it is called...

I appreciate the fact that you are trying to help, but if you are not familiar with the software I am asking about, your comments are not really relevant or necessary...


Thanks
-Garrett
Jeanne Boyarsky
author & internet detective
Marshal

Joined: May 26, 2003
Posts: 30957
    
158

Garrett,
If you are stuck, I would try simplifying the deployment. For example, try to just deploy one session bean. This will help isolate the component causing the problem. App servers typically deploy each component at a time (internally. I realize you deploy the whole ear.)

Avi does have a point about installing OAS locally. Then you can figure out if it is Windows vs Linux problem or something else. It is also much easier to troubleshoot if you can deploy yourself, without having to wait on someone else.

Note: I haven't used OAS on a real project. I've used other app servers though and the same troubleshooting tips apply.
Avi Abrami
Ranch Hand

Joined: Oct 11, 2000
Posts: 1135

Garrett,
Just to set the record straight:

http://www.oracle.com/technology/community/oracle_ace/ace1.html

Good Luck,
Avi.
Avi Abrami
Ranch Hand

Joined: Oct 11, 2000
Posts: 1135

Garrett,
Oracle Corporation like to rename their products, frequently. Originally it was called OAS (Oracle Application Server). It was a heap of rubbish and Oracle dumped it. Then they came out with iAS (Internet Application Server) -- also a waste of time and also, subsequently dumped.

Then came a special license agreement with OrionServer, and the new rpoduct was called "Oracle 9iAS".

Now I see that the latest name is (indeed) "Oracle Application Server 10g". I was under the (wrong) impression that it was called "Oracle 10gAS" -- hence my statements regarding the product name.

Nonetheless, OAS and OC4J are different, and just because Oracle recommends developing on OC4J and deploying to OAS, doesn't mean it's the best thing to do.

Originally Oracle's EJB container was embedded in the database, and although Oracle's marketing hype said that it was better to use their embedded EJB container (than some other third-party one), Oracle's EJB container just didn't cut it. (Why do you think they got the source code for "OrionServer" and created OC4J?)

Good Luck,
Avi.
Garrett Reinard
Greenhorn

Joined: Dec 10, 2004
Posts: 10
Thanks for the clarification...

-Garrett
Robert Hayes
Ranch Hand

Joined: Oct 24, 2004
Posts: 116
I have worked with both 9i and 10g Oracle App Servers. What you may find interesting is that even with JDeveloper (Oracle's Java IDE), I had nothing but problems trying to deploy applications to the 9iAS.

Once my client switched to 10gAS, all those problems disappeared. So I highly recommend you start talking version #s...

Although, yes, you always want to "develop where you deploy", you SHOULD be able to -- for the most part -- develop on a standalone OC4J and deploy to OAS. I have done it with 2 apps now which used the embedded OC4J server in JDeveloper.

What you should check is the "redirected output/errors" log file on the app server. It contains info about deployments...
Garrett Reinard
Greenhorn

Joined: Dec 10, 2004
Posts: 10
Just as an update, in case you guys encounter this or find someone encountering this in the future...

The solution to the problem was in the application.xml file... (not the orion-application.xml file)

when defining the web modules in the app, I had left out the "<context-root>" element as a child of the "<web" element... I just had a "<web-uri>" element by itself... with the standalone deployment, the context root, etc, was specified in the call to the admin.jar... when using the enterprise manager console with OAS, it actually parses that file and expects that you have defined "<context-root>" as a sub element for each of your web modules... My thoughts are that the only reason they are doing this is to prepopulate the binding textfields, which seems kind of annoying, but none-the-less, that is the fix for my particular problem...


Something to note also, is that all the log files were pretty useless for this problem... I searched through them all on numerous occassions after attempting new deployments... nothing showed up... the only way I figured it out was by deploying a couple other apps we had... one worked, and after digging through it all for a while, I figured out that the only difference in the descriptors was that "<context-root>" element... changed that and bingo...


Thanks all for the help...

-Garrett
Robert Hayes
Ranch Hand

Joined: Oct 24, 2004
Posts: 116
Garrett,

What version of OAS are you using?
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Deploy works with OC4J standalone, but not OAS console deploy...