Common pitfalls when deploying from JDeveloper 11g to WebLogic 10.3
By Shay Shmeltzer on Nov 14, 2008
One thing we should probably do in future versions of JDeveloper is work to simplify the deployment steps even further.
Don't get me wrong, we are doing a nice job now with one click packaging and deploy to a remote server - but there are still some pitfalls that people might run into.
At the end of this entry you can see a sample demo showing the basic deployment of an ADF application to a remote WebLogic Server.
The first problem most people run into is that they don't read the manual - there are quite clear instructions for deployment in the Fusion Developer Guide.
Here is a direct link to the deployment chapter.
Here are a couple of things you might run into and how to solve them.
Missing ADF libraries
If you are deploying to a stand-alone WebLogic Server - it won't have the ADF libraries on it by default. Luckily for you it is now very easy to deploy them to the server with the JDeveloper installer. You simply invoke it and choose to install to an existing WebLogic directory, and then uncheck the JDeveloper installation - it will then let you install the ADF libraries.
Then you'll be able to server's configuration wizard to add the ADF libraries to a domain.
Data-sources - and not finding them
When you are building an ADF BC application, or any other Java EE application for that matter, you should take advantage of the data-sources capabilities of your server.
In ADF BC's application module configuration it is quite easy to edit the configuration and replace the connection to be based on a JDBC DataSource instead of direct JDBC connection - once you do that the JDBC data source name will be something like: java:comp/env/jdbc/scottDS (where scott is the name of the DB connection you defined for your application).
After you did this modification, the next step is to go into the WLS admin console and define a data source. The important thing here is to have the JNDI Name be: jdbc/scottDS
This way your JDBC connection will be found.
One more common overlooked thing here is that after you define the data source in WLS you need to give it a target. So click the Targets tab and assign the datasource to the server you are going to deploy to.
One click packing from inside JDeveloper
When you create a regular Fusion application you get two projects a Model one and a ViewController one.
If you right click the ViewController one and choose deploy you'll be able to create a WAR file and directly deploy to WebLogic, but then you might run into an error message which will have this line somewhere in it:
The right way to deploy the complete application is to do it from the application level menu - where you'll find another deploy option - this will create an EAR file that will deploy successfully.
Ran into another gotcha? let me know in the comments and help create a knowledge base for future generation.
Here is a quick demo:
Lynn has a blog entry that walk you through the process of extending the WLS instance with the needed libraries to run ADF (installing the JRF). It also addresses the error some people are running into :
ORA-01005: null password given; logon denied