Standalone Weblogic domain for ADF 11.1.2.1

Suppose your team have created a first working version of the ADF application using the latest JDeveloper 11.1.2.1, and now it's the time to deploy it to the QA environment. But before real deployment one should create such QA environment, and in case of ADF 11.1.2.1 the required steps are:
  • Install Oracle Weblogic 10.3.5
  • Install Application Development Runtime 11.1.1.5
  • Follow support.oracle.com note How To Install the ADF Runtime Libraries 11g Release 2 in WebLogic Sever 10.3.5 ? [ID 1328698.1]. For ADF 11.1.2.1.0 you must:
    • install patch 12979653
    • install patch 12917525
    • start WLST from $MW_HOME/oracle_common/common/bin and issue the following command in the offline mode: upgradeADF('<your Domain Path>').  Note that at this moment you do not have the domain yet, so you may be tempted to skip this step at all (as I did the first time).
  • Start Fusion Middleware Configuration Wizard - $MW_HOME/oracle_common/common/bin/config.cmd(sh),  create new Weblogic domain, pick the following products on  "Generate a domain configured automatically to support the following products"  page:
    • Oracle JRF - 11.1.1.0 [oracle_common]
    • Oracle Enterprise Manager - 11.1.1.0 [oracle_common]
I strongly recommend you to install Enterprise Manager (a.k.a. FMW Control) for standalone ADF domains, because it contains a lot of useful features and can help you to deploy/manage ADF applications with ease.
  • Continue domain creation by specifying domain name and location, admin user credentials, start mode and JDK,  admin and managed server settings (by the way it's recommended  to create the managed servers for deploying your ADF apps in QA/Stage/Prod environments), machines and clusters if you need them.

Now you can try to start Administration Server of your new domain, it even changes its state to RUNNING, but Enterprise Manager application (em) fails with the following error in the log:

... <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <a677671586aa9c7f:-32edf730:134cbe5b33b:-8000-0000000000000004> <1326270937527> <BEA-149205> <Failed to initialize the application 'em' due to error java.lang.NoClassDefFoundError: javax/faces/application/ProjectStage.

  javax.faces.application.ProjectStage class is contained in the JSF 2.0 API,  it seems that JSF 2.0 library has not deployed to our domain's AdminServer.  Why? Because you HAVE TO issue WSLT command upgradeADF('<your Domain Path>') even for newly created ADF 11.1.2.1 domain! Stop AdminServer,  issue this WLST command, start AdminServer again and you em will be deployed successfully.  If you're curious like me you can explore what this upgradeADF command is really doing by opening $MW_HOME/oracle_common/common/wlst/adfWLSTCommands.py . Well, it's actually deploying JSF 2.0 library and target it to the AdminServer.

Do not forget, that if you're planning to deploy ADF apps to the Managed Servers of your domain, you should target all ADF-related shared libraries to the corresponding managed servers. The easiest way to do it is to start FMW Control (http://<host>:<admin_server_port>/em), find the Managed Server in the Weblogic domain tree and press the Apply JRF Template button. Managed servers should be restarted after this action.

That's just the basic steps required,  I have not covered ADF Security, MDS configuration, Web Tier setup,  clustering, e.t.c. So I hope to return to these topics later. 

Comments:

What about deploying both ADF 11.1.1.5 apps along side the 11.1.2.1 (As the case of having WebCenter already, and a newer ADF app)

Also what is the steps if the domain already created ?

Thanks

Posted by Amr Gawish on May 18, 2012 at 11:39 PM CEST #

Hi Amr,
it's impossible to have the single domain with Webcenter 11.1.1.5 and ADF 11.1.2.1 simultaneously because of the difference in the JRF versions. The only solution will be to create 2 distinct middleware homes and 2 distinct domains using these MW homes binaries. I have the similar configuration in the ADF 11.1.2.1 - OAM 11.1.1.5 integration scenario described in this post - https://blogs.oracle.com/imc/entry/secured_your_adf_application_time

Posted by Dmitry Nefedkin on May 22, 2012 at 02:00 PM CEST #

Hi Dmitry,
That's what I've ended up doing, and everything worked perfectly.

Thanks

Posted by Amr Gawish on May 22, 2012 at 03:03 PM CEST #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Oracle ECEMEA Partner Hubs Migration Center Team

We share our skills to maximize your revenue!
Our dedicated team of consultants can rapidly and successfully assist you to adopt and implement the latest of Oracle Technology in your solutions.

Stay Connected
partner.imc
@
beehiveonline.oracle-DOT-com
Google+

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
2
3
4
5
6
9
10
11
12
13
14
16
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today