To Enable ADF Logging on Standalone WLS

Hi All,
I have read the following article to enable ADF loggin in my code and testing using JDeveloper:
http://blogs.oracle.com/groundside/entry/adventures_in_adf_logging_part
However, now I want to know how can I test it on a standalone server. How to enable fine level trace for my application code on a stanalone(or production) server incase to debug any issue.
Could you please tell me the steps for this.
Thanks,
Lalit.

If you have the EM (Enterprise Manager) installed on your stand alone WLS (which you should) you can select the managed server your app is running on, select the 'Log Configuration' menu and you should see almost the same representation an in jdev.
Timo

Similar Messages

Problem while deploying ADF application to standalone WLS server

Hi,
I am facing a problem while deploying ADF application to standalone WLS Server.
Following is the error message that I am getting.
[07:24:03 PM] ---- Deployment started. ----
[07:24:03 PM] Target platform is (Weblogic 10.3).
[07:24:07 PM] Retrieving existing application information
[07:24:08 PM] Running dependency analysis...
[07:24:08 PM] Building...
[07:24:13 PM] Deploying 2 profiles...
[07:24:14 PM] Wrote Web Application Module to D:\WorkSpace3\DashboardUi\deploy\Dashboard.war
[07:24:14 PM] Wrote Enterprise Application Module to D:\WorkSpace3\deploy\Dashboard.ear
[07:24:14 PM] Deploying Application...
[07:24:22 PM] [Deployer:149191]Operation 'deploy' on application 'Dashboard' is initializing on 'msDevServer1'
[07:24:27 PM] [Deployer:149193]Operation 'deploy' on application 'Dashboard' has failed on 'msDevServer1'
[07:24:27 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application Dashboard on msDevServer1.: .
[07:24:27 PM] Weblogic Server Exception: weblogic.application.ModuleException:
[07:24:27 PM] Caused by: weblogic.common.ResourceException: DataSource DashboardDb already exists
[07:24:27 PM] See server logs or server console for more details.
[07:24:27 PM] weblogic.application.ModuleException:
[07:24:27 PM] #### Deployment incomplete. ####
[07:24:27 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)Any suggestion how to fix this.
Thanks
Ajay

I logged into console and browsed to 'Home >Summary of JDBC Data Sources' but not able to locate DashboardDb. Please let me know where to find DashboardDB on wls console.
Also, please let me know how to configure the app to not to auto-deploy JDBC data sources

Task-flow ADF security on Standalone WLS

Hi,
Jdev 11g
I have into the main adfc-config.xml 3 links one to a jspx and 2 links to 2 different bounded task flows.
I applied ADF security depends on Roles to the three links, one on the jspx itself (on the pagedef) and 2 to the Task-flow.
All is working perfectly on the embedded WLS.
When deploying the application to a standalone WLS and applying the security migration as explained (system-jazn-data.xml verified and security is migrated) I have only the jspx working and for the 2 task-flows I have an Authorization check failed exception.
I always think that it is a migration problem but seems not because the jspx is working depends on the right Role.
Any idea what can cause this and why the ADF security is working only on jspx page and not on the task-flow after deploying to a standalone WLS?
Thanks
Jamil
<May 27, 2009 12:22:20 PM AST> <Error> <HTTP> <BEA-101017> <[weblogic.servlet.in
ternal.WebAppServletContext@197171f - appName: 'TasdeeqEAR', name: 'TasdeeqApp',
context-path: '/TasdeeqApp', spec-version: '2.5', request: weblogic.servlet.int
ernal.ServletRequestImpl@31dbd4[
GET /TasdeeqApp/faces/home?_adf.ctrl-state=1028508221_19 HTTP/1.1
Accept: */*
Accept-Language: en-US,ar-SA;q=0.5
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; Trident/4.0; SLCC
1; .NET CLR 2.0.50727; Media Center PC 5.0; InfoPath.2; .NET CLR 3.5.21022; .NET
CLR 3.5.30729; .NET CLR 3.0.30618; Tablet PC 2.0; FDM)
Accept-Encoding: gzip, deflate
Connection: Keep-Alive
Cookie: JSESSIONID=9Z7tKdGCD0BSvt2GnDfLrkhZJ62rhMPpGLmXtGctDT2YGTQcl2VJ!-1394634
041
]] Root cause of ServletException.
oracle.adf.controller.security.AuthorizationException: ADFC-0619: Authorization
check failed: '/WEB-INF/registrar-task-flow.xml#registrar-task-flow' 'VIEW'.
at oracle.adf.controller.internal.security.AuthorizationEnforcer.handleF
ailure(AuthorizationEnforcer.java:145)
at oracle.adf.controller.internal.security.AuthorizationEnforcer.checkPe
rmission(AuthorizationEnforcer.java:80)
at oracle.adf.controller.internal.security.AuthorizationEnforcer.checkRe
ad(AuthorizationEnforcer.java:314)
at oracle.adf.controller.internal.metadata.MetadataService.getTaskFlowDe
finition(MetadataService.java:204)
at oracle.adfinternal.controller.activity.TaskFlowCallActivityLogic.find
TaskFlowDefinition(TaskFlowCallActivityLogic.java:931)
Truncated. see log file for complete stacktrace
>

Hi Frank,
I copied the <jazn-policy> section from the jazn-data.xml to system-jazn-data.xml and it is working
So as expected something wrong with the migration...I will check what
Thanks
Jamil

Logging Standards and ADF Application Log File on Standalone WLS

Hi Experts,
I am using JDev - 11.1.1.5.0 and WLS - 10.3
Is ADF Logger the standard logger to be used in an ADF Application? If Yes, how to configure it?
During development I simply used "System.out.println" for log messages and I was able to see the log messages in the Integrated WLS Console in JDeveloper. Now, I am moving to deployment on Standalone WLS. Please let me know how to configure the logger to log these messages to some log file to be accessed from standalone WLS.
Thanks
Rathnam

Start with this 5 part series http://blogs.oracle.com/groundside/entry/adventures_in_adf_logging_part
http://blogs.oracle.com/groundside/entry/adventures_in_adf_logging_part1
http://blogs.oracle.com/groundside/entry/adventures_in_adf_logging_part2
http://blogs.oracle.com/groundside/entry/adventures_in_adf_logging_part3
http://blogs.oracle.com/groundside/entry/adventures_in_adf_logging_part4
For the UI
http://blogs.oracle.com/jdevotnharvest/entry/using_adf_logger_with_groovy
and For some more advanced usage
http://tompeez.wordpress.com/2011/09/23/adflogger-using-a-custom-formatter-class-to-print-log-messages/
Timo

ADF application deployment to standalone WLS

Hello everyone,
I developed a small ADF app within JDeveloper (JDev 11g Rel 1-- 11.1.1.3.0) and have been deploying it onto the Integrated WLS with JDev.
I'm now trying to deploy it onto a standalone WLS domain on another machine. This WLS is of the latest release. I packaged my app into an EAR file, added the deployment descriptors, etc.
Within the WLS admin console, when I try to start the deployment (i.e. activate changes) for this EAR, I get this error after activation:
[J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: adf.oracle.domain, exact-match: false].
I understand it's a problem with not recognizing adf.oracle.domain, but JDev's help documents (Section 36.3.3) say to ensure that my weblogic-application.xml file has a reference to adf.oracle.domain.
If anyone has any comments about this error and how to fix it, that would be much appreciated.
Also, if there is a more appropriate forum to ask this in, please let me know.
Thanks so much,
Janelle

Janelle,
Did you create the ADF domain in the WLS server? Also, you can directly deploy from JDeveloper once you have the appropriate deployment descriptors.
Check this 3 articles
http://radalcove.com/blog/?p=34
http://radalcove.com/blog/?p=16
http://radalcove.com/blog/?p=48
Juan C

JDeveloper 12c & Standalone WLS w/ADF Runtime 12.1.2

My question is related to setting up WLS with ADF...
Has anyone tried setting up WLS 12.1.2 with ADF Runtime 12.1.2? I cannot seem to successfully deploy a simple ADF 12c app against the new standalone WLS container.
First, I installed WLS 12.1.2 (no coherence) followed by ADF Runtime 12.1.2.
When creating a new domain, I setup the domain with default option (nothing checked-EM,JRF,etc..)
Upon deploying a simple app with a page, I receive the following error:
[02:32:43 PM] [Deployer:149193]Operation "deploy" on application "ADF12cTest" has failed on "AdminServer".
[02:32:43 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application ADF12cTest on AdminServer.: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: adf.oracle.domain, exact-match: false].
[02:32:43 PM] weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: adf.oracle.domain, exact-match: false]
[02:32:43 PM] Deployment cancelled.
[02:32:43 PM] ---- Deployment incomplete ----.
[02:32:43 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
However, if I check off EM,JRF. I am asked to create a DB connection!
http://i.imgur.com/fPPaw7t.jpg
I am not interested in using Coherence at the moment, is there an option to just setup a standalone WLS 12c server with ADF 12.1.2 runtime?
Also, does the "Coherence" option imply that ADF Runtime will be included in the domain libs?

Shay, that was the doc I was following, seems like I might have to go another direction now that Brian has confirmed the additional JRF requirements associated with wls 12c. I'm not going to start using technology which I do not understand or have a need yet...so paddling backwards with some wishful thinking, I attempted to run the ADF 12c infrastructure installer against a wls 10.3.6 setup, which results in:
http://i.imgur.com/u3dv5Km.jpg
That pretty much dashes my hopes for an easy install...so moving on.
JDev/ADF 12c is certified for wls 10.3.5+, are there any documentation on how to upgrade ADF Runtime 11.1.2 on WLS 10.3.6 to ADF 12c (perhaps via OPatch)?

Failure deploying FOD app to standalone WLS

I consistently get the following message when trying to run the Fusion Order Demo application on a standalone WLS
<BEA-101371> <There was a failure when processing annotations for application C:\JDev_projects\FOD_11\StoreFrontModule\StorefrontUI\deploy\StoreFrontWebApp.war. Please make sure that the annotations are valid. The error is oracle.adf.library.webapp.ResourceServlet>
I performed a "clean all" then used the delivered deployment descriptor to build the war.
From the standalone WLS I accessed the Admin Console and tried to install the war.
I saw an earlier post about this, but not sure it was resolved for this reason (Re: Problem in running the Fusion Store Front demo..)
Has anyone else encountered this and have a solution?

Hi Lynn,
I rebuilt all projects under the StoreFronModule workspace.
I can run the app just fine when deployed to the integrated WLS, but still not when I generate an EAR and deploy on and stand-alone.
The connection.xml looks good. Here it is with some of the urls x'ed out.
<?xml version = '1.0' encoding = 'UTF-8'?>
<References xmlns="http://xmlns.oracle.com/adf/jndi">
<Reference name="FOD" className="oracle.jdeveloper.db.adapter.DatabaseProvider" credentialStoreKey="FOD" xmlns="">
<Factory className="oracle.jdeveloper.db.adapter.DatabaseProviderFactory"/>
<RefAddresses>
<StringRefAddr addrType="subtype">
<Contents>oraJDBC</Contents>
</StringRefAddr>
<StringRefAddr addrType="user">
<Contents>FUSIONOD</Contents>
</StringRefAddr>
<StringRefAddr addrType="hostname">
<Contents>xxxx.xx.xxxx.xxxx.edu</Contents>
</StringRefAddr>
<StringRefAddr addrType="port">
<Contents>1711</Contents>
</StringRefAddr>
<SecureRefAddr addrType="password"/>
<StringRefAddr addrType="serviceName">
<Contents>xxxx.xxxx.xxxx.edu</Contents>
</StringRefAddr>
<StringRefAddr addrType="DeployPassword">
<Contents>true</Contents>
</StringRefAddr>
<StringRefAddr addrType="oraDriverType">
<Contents>thin</Contents>
</StringRefAddr>
</RefAddresses>
</Reference>
</References>
Here is the full listing of entries in the AdminServer-diagnostic.log for the intial startup of the app:
[2008-11-07T09:15:35.796-06:00] [AdminServer] [NOTIFICATION] [J2EE JMX-46010] [oracle.as.jmx.framework.PortableMBeanFactory] [tid: 11] [APP: FODDS] [arg: class oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl] JMX Portable Framework initialized with platform SPI "class oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl"
[2008-11-07T09:16:08.187-06:00] [AdminServer] [ERROR] [] [javax.enterprise.resource.webcontainer.jsf.application] [tid: 11] [APP: StoreFrontModule] JSF1030: The specified InjectionProvider implementation 'com.bea.faces.WeblogicInjectionProvider' cannot be loaded.
[2008-11-07T09:18:31.880-06:00] [AdminServer] [ERROR] [] [javax.enterprise.resource.webcontainer.jsf.application] [tid: 12] [APP: StoreFrontModule] JSF1030: The specified InjectionProvider implementation 'com.bea.faces.WeblogicInjectionProvider' cannot be loaded.
[2008-11-07T09:19:07.459-06:00] [AdminServer] [ERROR] [] [javax.enterprise.resource.webcontainer.jsf.application] [tid: 15] [APP: StoreFrontModule] JSF1030: The specified InjectionProvider implementation 'com.bea.faces.WeblogicInjectionProvider' cannot be loaded.
[2008-11-07T09:20:33.571-06:00] [AdminServer] [WARNING] [ADFC-54008] [oracle.adfinternal.controller.faces.lifecycle.JSFLifecycleImpl] [tid: 12] [APP: StoreFrontModule] [arg: oracle.adfinternal.controller.application.model.JSFDataBindingLifecycleContextBuilder] ADFc: Replacing the ADF Page Lifecycle implementation with 'oracle.adfinternal.controller.application.model.JSFDataBindingLifecycleContextBuilder'.
[2008-11-07T09:20:34.118-06:00] [AdminServer] [NOTIFICATION] [ADFC-60001] [oracle.adfinternal.controller.util.model.AdfmInterface] [tid: 12] [APP: StoreFrontModule] ADFc: BindingContext is not present, not using ADFm APIs for DataControlFrames.
[2008-11-07T09:20:34.337-06:00] [AdminServer] [NOTIFICATION] [ADFC-50009] [oracle.adfinternal.controller.metadata.provider.MdsMetadataResourceProvider] [tid: 12] [APP: StoreFrontModule] ADFc: Controller caching of MDS metadata resources ENABLED.
[2008-11-07T09:20:34.696-06:00] [AdminServer] [NOTIFICATION] [ADFC-52039] [oracle.adf.controller.internal.metadata.MetadataService] [tid: 12] [APP: StoreFrontModule] [arg: /WEB-INF/adfc-config.xml] ADFc: Loading bootstrap metadata from '/WEB-INF/adfc-config.xml'.
[2008-11-07T09:20:53.962-06:00] [AdminServer] [NOTIFICATION] [ADFC-52039] [oracle.adf.controller.internal.metadata.MetadataService] [tid: 11] [APP: StoreFrontModule] [arg: /WEB-INF/adfc-config.xml] ADFc: Loading bootstrap metadata from '/WEB-INF/adfc-config.xml'.
[2008-11-07T09:20:54.806-06:00] [AdminServer] [WARNING] [] [oracle.adf.share.security] [tid: 11] [APP: StoreFrontModule] Unable to locate the credential for key FOD in C:\weblogic\user_projects\domains\base_domain\config\oracle.
[2008-11-07T09:20:54.806-06:00] [AdminServer] [WARNING] [] [oracle.adf.share.jndi.ReferenceStoreHelper] [tid: 11] [APP: StoreFrontModule] Incomplete connection information
[2008-11-07T09:21:05.713-06:00] [AdminServer] [WARNING] [] [oracle.adfinternal.view.faces.renderkit.rich.NavigationPaneRenderer] [tid: 11] [APP: StoreFrontModule] Warning: There are no items to render for this level
I hope this gives you more info to diagnose the deployment problem. Thank you.

Standalone WLS server instance deployment failure - missing ADFLogger

I was hoping somebody could help me please with issues of installing ADF JDev 11g apps to separate WLS server instances (ie. not Admin Server) and the ADFLogger class.
I've successfully configured a separate standalone WLS, installed the ADF Runtime Libraries and deployed/run an ADF JDev 11g app to the server under the default AdminServer.
We encountered one issue with deployment regarding the ADFApplicationLifecycleListener class which is addessed in the following forum post with the documented workaround of removing ADFApplicationLifecycleListener from the weblogic-application.xml file: Standalone WLS deployment failure - incorrect weblogic-application.xml
Next we want to deploy to a separate server instance/machine on the standalone WLS (we have the eventual requirement of deploying our apps to a WLS cluster, so we're experimenting with configuring separate WLS server instances+machines).
I've created via the Admin Server a new separate server instance (say ADFServer) on a separate WLS machine (say ADFMachine) within my standalone WLS. I've configured the separate WLS server instance to run on a different port from the default Admin Server port. In addition for the 3 deployed libraries jsf, jstl and oracle.adf.domain, via selecting them in the Admin Console under Deployments, then the Target tab, I've also "targetted" (read: deployed) these 3 libraries to the new server instance so they reside both on the Admin Server and ADFServer.
However when I redeploy my original application via JDeveloper's Application Menu -> Deploy option, on deployment to the ADFServer directly I receive the exception at the bottom of this post. The relevant error message:
java.lang.NoClassDefFoundError: oracle/adf/share/logging/ADFLogger
This class is included in numerous ADF Runtime Libraries, and I would expect that once I targetted the oracle.adf.domain library for both Admin Server and ADFServer, the relevant ADFLogger class should be available (and given the fact I've run the application successfully on the standalone WLS under the Admin Server, it proves the library is available).
The missing ADFLogger library seems to be a reoccuring theme for application server deployments, in particular OC4J. This is the first time I've seen it broached for WLS when using the ADF Runtime Libraries and haven't found much assistance via the OTN forums, Google searches etc.
Does anybody know what I've configured incorrectly on my standalone WLS such that the ADFLogger is not configured for the separate WLS server instance? (I suspect I'll have to try the WLS forum too, but lets start here).
Any help appreciated.
Thanks & regards,
CM.
(Complete stack trace)
Failure occurred in the execution of deployment request with ID '1229647798124' for task '2'. Error is: 'java.lang.NoClassDefFoundError: oracle/adf/share/logging/ADFLogger' java.lang.NoClassDefFoundError: oracle/adf/share/logging/ADFLogger at java.lang.Class.getDeclaredFields0(Native Method) at java.lang.Class.privateGetDeclaredFields(Class.java:2291) at java.lang.Class.getDeclaredFields(Class.java:1743) at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAnnotationProcessor.java:965) at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAnnotationProcessor.java:958) at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.processJ2eeAnnotations(BaseJ2eeAnnotationProcessor.java:97) at weblogic.j2ee.dd.xml.J2eeAnnotationProcessor.processJ2eeAnnotations(J2eeAnnotationProcessor.java:37) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processFilters(WebAnnotationProcessorImpl.java:241) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:212) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:107) at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1287) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:412) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:456) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:414) at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:910) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:388) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:44) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:616) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:198) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:725) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:160) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) java.lang.NoClassDefFoundError: oracle/adf/share/logging/ADFLogger at java.lang.Class.getDeclaredFields0(Native Method) at java.lang.Class.privateGetDeclaredFields(Class.java:2291) at java.lang.Class.getDeclaredFields(Class.java:1743) at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAnnotationProcessor.java:965) at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAnnotationProcessor.java:958) at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.processJ2eeAnnotations(BaseJ2eeAnnotationProcessor.java:97) at weblogic.j2ee.dd.xml.J2eeAnnotationProcessor.processJ2eeAnnotations(J2eeAnnotationProcessor.java:37) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processFilters(WebAnnotationProcessorImpl.java:241) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:212) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:107) at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1287) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:412) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:456) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:414) at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:910) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:388) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:44) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:616) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:198) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:725) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:160) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

I do start it by commandline since I only have the AdminServer, and no other nodes. Below is my startWeblogic.sh and setDomainEnv.sh scripts under medrec/bin directory. I don't see any modifications to them for ADF. Also, after extending the domain, the oracle.adf.domain library shows up in my deployments page and is pointing to "/ u01/ app/ oracle/ product/ wls/ jdeveloper/ modules/ oracle. adf. model_11. 1. 1/ adf. oracle. domain. ear". It seems like the extending step is missing a step to give access to all the libraries?
STARTWEBLOGIC.SH:
#!/bin/sh
# WARNING: This file is created by the Configuration Wizard.
# Any changes to this script may be lost when adding extensions to this configuration.
# --- Start Functions ---
stopAll()
     # We separate the stop commands into a function so we are able to use the trap command in Unix (calling a function) to stop these services
     if [ "X${ALREADY_STOPPED}" != "X" ] ; then
          exit
     fi
     # STOP POINTBASE (only if we started it)
     if [ "${POINTBASE_FLAG}" = "true" ] ; then
          echo "Stopping PointBase server..."
          ${WL_HOME}/common/bin/stopPointBase.sh -port=${POINTBASE_PORT} -name=${POINTBASE_DBNAME} >"${DOMAIN_HOME}/pointbaseShutdown.log" 2>&1
          echo "PointBase server stopped."
     fi
     ALREADY_STOPPED="true"
     # Restore IP configuration the node manager starts IP Migration
     if [ "${SERVER_IP}" != "" ] ; then
          ${WL_HOME}/common/bin/wlsifconfig.sh -removeif "${IFNAME}" "${SERVER_IP}"
     fi
# --- End Functions ---
# This script is used to start WebLogic Server for this domain.
# To create your own start script for your domain, you can initialize the
# environment by calling @USERDOMAINHOME/setDomainEnv.
# setDomainEnv initializes or calls commEnv to initialize the following variables:
# BEA_HOME - The BEA home directory of your WebLogic installation.
# JAVA_HOME - Location of the version of Java used to start WebLogic
# Server.
# JAVA_VENDOR - Vendor of the JVM (i.e. BEA, HP, IBM, Sun, etc.)
# PATH - JDK and WebLogic directories are added to system path.
# WEBLOGIC_CLASSPATH
# - Classpath needed to start WebLogic Server.
# PATCH_CLASSPATH - Classpath used for patches
# PATCH_LIBPATH - Library path used for patches
# PATCH_PATH - Path used for patches
# WEBLOGIC_EXTENSION_DIRS - Extension dirs for WebLogic classpath patch
# JAVA_VM - The java arg specifying the VM to run. (i.e.
# - server, -hotspot, etc.)
# USER_MEM_ARGS - The variable to override the standard memory arguments
# passed to java.
# PRODUCTION_MODE - The variable that determines whether Weblogic Server is started in production mode.
# POINTBASE_HOME - Point Base home directory.
# POINTBASE_CLASSPATH
# - Classpath needed to start PointBase.
# Other variables used in this script include:
# SERVER_NAME - Name of the weblogic server.
# JAVA_OPTIONS - Java command-line options for running the server. (These
# will be tagged on to the end of the JAVA_VM and
# MEM_ARGS)
# For additional information, refer to the WebLogic Server Administration
# Console Online Help(http://e-docs.bea.com/wls/docs103/ConsoleHelp/startstop.html).
# Call setDomainEnv here.
DOMAIN_HOME="/u01/app/oracle/product/wls/wlserver_10.3/samples/domains/medrec"
. ${DOMAIN_HOME}/bin/setDomainEnv.sh $*
SAVE_JAVA_OPTIONS="${JAVA_OPTIONS}"
SAVE_CLASSPATH="${CLASSPATH}"
# Start PointBase
PB_DEBUG_LEVEL="3"
if [ "${POINTBASE_FLAG}" = "true" ] ; then
     ${WL_HOME}/common/bin/startPointBase.sh -port=${POINTBASE_PORT} -debug=${PB_DEBUG_LEVEL} -console=false -background=true -ini=${DOMAIN_HOME}/pointbase.ini >"${DOMAIN_HOME}/pointbase.log" 2>&1
fi
JAVA_OPTIONS="${SAVE_JAVA_OPTIONS}"
SAVE_JAVA_OPTIONS=""
CLASSPATH="${SAVE_CLASSPATH}"
SAVE_CLASSPATH=""
trap 'stopAll' 1 2 3 15
if [ "${PRODUCTION_MODE}" = "true" ] ; then
     WLS_DISPLAY_MODE="Production"
else
     WLS_DISPLAY_MODE="Development"
fi
if [ "${WLS_USER}" != "" ] ; then
     JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.management.username=${WLS_USER}"
fi
if [ "${WLS_PW}" != "" ] ; then
     JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.management.password=${WLS_PW}"
fi
CLASSPATH="${CLASSPATH}${CLASSPATHSEP}${MEDREC_WEBLOGIC_CLASSPATH}"
echo "."
echo "."
echo "JAVA Memory arguments: ${MEM_ARGS}"
echo "."
echo "WLS Start Mode=${WLS_DISPLAY_MODE}"
echo "."
echo "CLASSPATH=${CLASSPATH}"
echo "."
echo "PATH=${PATH}"
echo "."
echo "***************************************************"
echo "* To start WebLogic Server, use a username and *"
echo "* password assigned to an admin-level user. For *"
echo "* server administration, use the WebLogic Server *"
echo "* console at http://hostname:port/console *"
echo "***************************************************"
# Set up IP Migration related variables.
# Set interface name.
if [ "${Interface}" != "" ] ; then
     IFNAME="${Interface}"
else
     IFNAME=""
fi
# Set IP Mask.
if [ "${NetMask}" != "" ] ; then
     IPMASK="${NetMask}"
else
     IPMASK=""
fi
# Perform IP Migration if SERVER_IP is set by node manager.
if [ "${SERVER_IP}" != "" ] ; then
     ${WL_HOME}/common/bin/wlsifconfig.sh -addif "${IFNAME}" "${SERVER_IP}" "${IPMASK}"
fi
# START WEBLOGIC
echo "starting weblogic with Java version:"
${JAVA_HOME}/bin/java ${JAVA_VM} -version
if [ "${WLS_REDIRECT_LOG}" = "" ] ; then
     echo "Starting WLS with line:"
     echo "${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} ${JAVA_OPTIONS} -Dweblogic.Name=${SERVER_NAME} -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${PROXY_SETTINGS} ${SERVER_CLASS}"
     ${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} ${JAVA_OPTIONS} -Dweblogic.Name=${SERVER_NAME} -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${PROXY_SETTINGS} ${SERVER_CLASS}
else
     echo "Redirecting output from WLS window to ${WLS_REDIRECT_LOG}"
     ${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} ${JAVA_OPTIONS} -Dweblogic.Name=${SERVER_NAME} -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${PROXY_SETTINGS} ${SERVER_CLASS} >"${WLS_REDIRECT_LOG}" 2>&1
fi
stopAll
popd
# Exit this script only if we have been told to exit.
if [ "${doExitFlag}" = "true" ] ; then
     exit
fi
SETDOMAINENV.SH:
#!/bin/sh
# WARNING: This file is created by the Configuration Wizard.
# Any changes to this script may be lost when adding extensions to this configuration.
# --- Start Functions ---
BP=100
SP=$BP
pushd()
     if [ -z "$1" ]
     then
          return
     fi
     SP=`expr $SP - 1`
     eval _stack$SP=`pwd`
     cd $1
     return
popd()
     if [ $SP -eq $BP ]
     then
          return
     fi
     eval cd \${_stack$SP}
     SP=`expr $SP + 1`
     return
# --- End Functions ---
# This script is used to setup the needed environment to be able to start Weblogic Server in this domain.
# This script initializes the following variables before calling commEnv to set other variables:
# WL_HOME - The BEA home directory of your WebLogic installation.
# JAVA_VM - The desired Java VM to use. You can set this environment variable before calling
# this script to switch between Sun or BEA or just have the default be set.
# JAVA_HOME - Location of the version of Java used to start WebLogic
# Server. Depends directly on which JAVA_VM value is set by default or by the environment.
# USER_MEM_ARGS - The variable to override the standard memory arguments
# passed to java.
# PRODUCTION_MODE - The variable that determines whether Weblogic Server is started in production mode.
# DOMAIN_PRODUCTION_MODE
# - The variable that determines whether the workshop related settings like the debugger,
# testconsole or iterativedev should be enabled. ONLY settable using the
# command-line parameter named production
# NOTE: Specifying the production command-line param will force
# the server to start in production mode.
# Other variables used in this script include:
# SERVER_NAME - Name of the weblogic server.
# JAVA_OPTIONS - Java command-line options for running the server. (These
# will be tagged on to the end of the JAVA_VM and
# MEM_ARGS)
# For additional information, refer to the WebLogic Server Administration
# Console Online Help(http://e-docs.bea.com/wls/docs103/ConsoleHelp/startstop.html).
ORACLE_HOME="/u01/app/oracle/product/wls/jdeveloper"
export ORACLE_HOME
WL_HOME="/u01/app/oracle/product/wls/wlserver_10.3"
export WL_HOME
BEA_JAVA_HOME="/u01/app/oracle/product/wls/jrockit_160_05"
export BEA_JAVA_HOME
SUN_JAVA_HOME="/u01/app/oracle/product/wls/jdk160_05"
export SUN_JAVA_HOME
if [ "${JAVA_VENDOR}" = "BEA" ] ; then
     JAVA_HOME="${BEA_JAVA_HOME}"
     export JAVA_HOME
else
     if [ "${JAVA_VENDOR}" = "Sun" ] ; then
          JAVA_HOME="${SUN_JAVA_HOME}"
          export JAVA_HOME
     else
          JAVA_VENDOR="BEA"
          export JAVA_VENDOR
          JAVA_HOME="/u01/app/oracle/product/wls/jrockit_160_05"
          export JAVA_HOME
     fi
fi
# We need to reset the value of JAVA_HOME to get it shortened AND
# we can not shorten it above because immediate variable expansion will blank it
JAVA_HOME="${JAVA_HOME}"
export JAVA_HOME
SAMPLES_HOME="${WL_HOME}/samples"
export SAMPLES_HOME
DOMAIN_HOME="/u01/app/oracle/product/wls/wlserver_10.3/samples/domains/medrec"
export DOMAIN_HOME
LONG_DOMAIN_HOME="/u01/app/oracle/product/wls/wlserver_10.3/samples/domains/medrec"
export LONG_DOMAIN_HOME
if [ "${DEBUG_PORT}" = "" ] ; then
     DEBUG_PORT="8453"
     export DEBUG_PORT
fi
if [ "${SERVER_NAME}" = "" ] ; then
     SERVER_NAME="MedRecServer"
     export SERVER_NAME
fi
POINTBASE_FLAG="true"
export POINTBASE_FLAG
POINTBASE_PORT="9082"
export POINTBASE_PORT
POINTBASE_DBNAME="medrec"
export POINTBASE_DBNAME
enableHotswapFlag=""
export enableHotswapFlag
PRODUCTION_MODE=""
export PRODUCTION_MODE
doExitFlag="false"
export doExitFlag
verboseLoggingFlag="false"
export verboseLoggingFlag
while [ $# -gt 0 ]
do
     case $1 in
     nodebug)
          debugFlag="false"
          export debugFlag
     production)
          DOMAIN_PRODUCTION_MODE="true"
          export DOMAIN_PRODUCTION_MODE
     notestconsole)
          testConsoleFlag="false"
          export testConsoleFlag
     noiterativedev)
          iterativeDevFlag="false"
          export iterativeDevFlag
     noLogErrorsToConsole)
          logErrorsToConsoleFlag="false"
          export logErrorsToConsoleFlag
     nopointbase)
          POINTBASE_FLAG="false"
          export POINTBASE_FLAG
     doExit)
          doExitFlag="true"
          export doExitFlag
     noExit)
          doExitFlag="false"
          export doExitFlag
     verbose)
          verboseLoggingFlag="true"
          export verboseLoggingFlag
     enableHotswap)
          enableHotswapFlag="-javaagent:${WL_HOME}/server/lib/diagnostics-agent.jar"
          export enableHotswapFlag
          PROXY_SETTINGS="${PROXY_SETTINGS} $1"
          export PROXY_SETTINGS
     esac
     shift
done
MEM_DEV_ARGS=""
export MEM_DEV_ARGS
if [ "${DOMAIN_PRODUCTION_MODE}" = "true" ] ; then
     PRODUCTION_MODE="${DOMAIN_PRODUCTION_MODE}"
     export PRODUCTION_MODE
fi
if [ "${PRODUCTION_MODE}" = "true" ] ; then
     debugFlag="false"
     export debugFlag
     testConsoleFlag="false"
     export testConsoleFlag
     iterativeDevFlag="false"
     export iterativeDevFlag
fi
# If you want to override the default Patch Classpath, Library Path and Path for this domain,
# Please uncomment the following lines and add a valid value for the environment variables
# set PATCH_CLASSPATH=[myPatchClasspath] (windows)
# set PATCH_LIBPATH=[myPatchLibpath] (windows)
# set PATCH_PATH=[myPatchPath] (windows)
# PATCH_CLASSPATH=[myPatchClasspath] (unix)
# PATCH_LIBPATH=[myPatchLibpath] (unix)
# PATCH_PATH=[myPatchPath] (unix)
. ${WL_HOME}/common/bin/commEnv.sh
WLS_HOME="${WL_HOME}/server"
export WLS_HOME
MEM_ARGS="-Xms256m -Xmx512m"
export MEM_ARGS
MEM_PERM_SIZE="-XX:PermSize=48m"
export MEM_PERM_SIZE
MEM_MAX_PERM_SIZE="-XX:MaxPermSize=128m"
export MEM_MAX_PERM_SIZE
if [ "${JAVA_VENDOR}" = "Sun" ] ; then
     if [ "${PRODUCTION_MODE}" = "" ] ; then
          MEM_DEV_ARGS="-XX:CompileThreshold=8000 ${MEM_PERM_SIZE} "
          export MEM_DEV_ARGS
     fi
fi
# Had to have a separate test here BECAUSE of immediate variable expansion on windows
if [ "${JAVA_VENDOR}" = "Sun" ] ; then
     MEM_ARGS="${MEM_ARGS} ${MEM_DEV_ARGS} ${MEM_MAX_PERM_SIZE}"
     export MEM_ARGS
fi
if [ "${JAVA_VENDOR}" = "HP" ] ; then
     MEM_ARGS="${MEM_ARGS} ${MEM_MAX_PERM_SIZE}"
     export MEM_ARGS
fi
# IF USER_MEM_ARGS the environment variable is set, use it to override ALL MEM_ARGS values
if [ "${USER_MEM_ARGS}" != "" ] ; then
     MEM_ARGS="${USER_MEM_ARGS}"
     export MEM_ARGS
fi
JAVA_PROPERTIES="-Dplatform.home=${WL_HOME} -Dwls.home=${WLS_HOME} -Dweblogic.home=${WLS_HOME} "
export JAVA_PROPERTIES
# To use Java Authorization Contract for Containers (JACC) in this domain,
# please uncomment the following section. If there are multiple machines in
# your domain, be sure to edit the setDomainEnv in the associated domain on
# each machine.
# -Djava.security.manager
# -Djava.security.policy=location of weblogic.policy
# -Djavax.security.jacc.policy.provider=weblogic.security.jacc.simpleprovider.SimpleJACCPolicy
# -Djavax.security.jacc.PolicyConfigurationFactory.provider=weblogic.security.jacc.simpleprovider.PolicyConfigurationFactoryImpl
# -Dweblogic.security.jacc.RoleMapperFactory.provider=weblogic.security.jacc.simpleprovider.RoleMapperFactoryImpl
EXTRA_JAVA_PROPERTIES="-Ddomain.home=${DOMAIN_HOME} -Doracle.home=${ORACLE_HOME} -Doracle.security.jps.config=${DOMAIN_HOME}/config/oracle/jps-config.xml -Doracle.dms.context=OFF -Djava.protocol.handler.pkgs=oracle.mds.net.protocol ${EXTRA_JAVA_PROPERTIES}"
export EXTRA_JAVA_PROPERTIES
JAVA_PROPERTIES="${JAVA_PROPERTIES} ${EXTRA_JAVA_PROPERTIES}"
export JAVA_PROPERTIES
ARDIR="${WL_HOME}/server/lib"
export ARDIR
pushd ${LONG_DOMAIN_HOME}
# Clustering support (edit for your cluster!)
if [ "${ADMIN_URL}" = "" ] ; then
     # The then part of this block is telling us we are either starting an admin server OR we are non-clustered
     CLUSTER_PROPERTIES="-Dweblogic.management.discover=true"
     export CLUSTER_PROPERTIES
else
     CLUSTER_PROPERTIES="-Dweblogic.management.discover=false -Dweblogic.management.server=${ADMIN_URL}"
     export CLUSTER_PROPERTIES
fi
LOG4J_CONFIG_FILE="/u01/app/oracle/product/wls/wlserver_10.3/samples/domains/medrec/log4j.properties"
export LOG4J_CONFIG_FILE
if [ "${LOG4J_CONFIG_FILE}" != "" ] ; then
     JAVA_PROPERTIES="${JAVA_PROPERTIES} -Dlog4j.configuration=file:${LOG4J_CONFIG_FILE}"
     export JAVA_PROPERTIES
fi
JAVA_PROPERTIES="${JAVA_PROPERTIES} ${CLUSTER_PROPERTIES}"
export JAVA_PROPERTIES
# Clear the pre_classpath here in case an application template wants to set it before the larger pre_classpath is invoked below
PRE_CLASSPATH=""
export PRE_CLASSPATH
PRE_CLASSPATH=""
export PRE_CLASSPATH
JAVA_DEBUG=""
export JAVA_DEBUG
if [ "${debugFlag}" = "true" ] ; then
     JAVA_DEBUG="-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=${DEBUG_PORT},server=y,suspend=n -Djava.compiler=NONE"
     export JAVA_DEBUG
     JAVA_OPTIONS="${JAVA_OPTIONS} ${enableHotswapFlag} -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole..."
     export JAVA_OPTIONS
else
     JAVA_OPTIONS="${JAVA_OPTIONS} ${enableHotswapFlag} -da"
     export JAVA_OPTIONS
fi
if [ ! -d ${JAVA_HOME}/lib ] ; then
     echo "The JRE was not found in directory ${JAVA_HOME}. (JAVA_HOME)"
     echo "Please edit your environment and set the JAVA_HOME"
     echo "variable to point to the root directory of your Java installation."
     popd
     read _val
     exit
fi
if [ "${POINTBASE_FLAG}" = "true" ] ; then
     DATABASE_CLASSPATH="${POINTBASE_CLASSPATH}"
     export DATABASE_CLASSPATH
else
     DATABASE_CLASSPATH="${POINTBASE_CLIENT_CLASSPATH}"
     export DATABASE_CLASSPATH
fi
POST_CLASSPATH=""
export POST_CLASSPATH
POST_CLASSPATH="${ORACLE_HOME}/modules/features/adf.share_11.1.1.jar${CLASSPATHSEP}${POST_CLASSPATH}"
export POST_CLASSPATH
POST_CLASSPATH=""
export POST_CLASSPATH
POST_CLASSPATH="${POST_CLASSPATH}${CLASSPATHSEP}${DATABASE_CLASSPATH}${CLASSPATHSEP}${ARDIR}/xqrl.jar"
export POST_CLASSPATH
# PROFILING SUPPORT
JAVA_PROFILE=""
export JAVA_PROFILE
SERVER_CLASS="weblogic.Server"
export SERVER_CLASS
JAVA_PROPERTIES="${JAVA_PROPERTIES} ${WLP_JAVA_PROPERTIES}"
export JAVA_PROPERTIES
JAVA_OPTIONS="${JAVA_OPTIONS} ${JAVA_PROPERTIES} -Dwlw.iterativeDev=${iterativeDevFlag} -Dwlw.testConsole=${testConsoleFlag} -Dwlw.logErrorsToConsole=${logErrorsToConsoleFlag}"
export JAVA_OPTIONS
# -- Setup properties so that we can save stdout and stderr to files
if [ "${WLS_STDOUT_LOG}" != "" ] ; then
     echo "Logging WLS stdout to ${WLS_STDOUT_LOG}"
     JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.Stdout=${WLS_STDOUT_LOG}"
     export JAVA_OPTIONS
fi
if [ "${WLS_STDERR_LOG}" != "" ] ; then
     echo "Logging WLS stderr to ${WLS_STDERR_LOG}"
     JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.Stderr=${WLS_STDERR_LOG}"
     export JAVA_OPTIONS
fi
# ADD EXTENSIONS TO CLASSPATHS
if [ "${EXT_PRE_CLASSPATH}" != "" ] ; then
     PRE_CLASSPATH="${EXT_PRE_CLASSPATH}${CLASSPATHSEP}${PRE_CLASSPATH}"
     export PRE_CLASSPATH
fi
if [ "${EXT_POST_CLASSPATH}" != "" ] ; then
     POST_CLASSPATH="${POST_CLASSPATH}${CLASSPATHSEP}${EXT_POST_CLASSPATH}"
     export POST_CLASSPATH
fi
if [ "${WEBLOGIC_EXTENSION_DIRS}" != "" ] ; then
     JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.ext.dirs=${WEBLOGIC_EXTENSION_DIRS}"
     export JAVA_OPTIONS
fi
JAVA_OPTIONS="${JAVA_OPTIONS}"
export JAVA_OPTIONS
# SET THE CLASSPATH
CLASSPATH="${PRE_CLASSPATH}${CLASSPATHSEP}${WEBLOGIC_CLASSPATH}${CLASSPATHSEP}${POST_CLASSPATH}${CLASSPATHSEP}${WLP_POST_CLASSPATH}"
export CLASSPATH
JAVA_VM="${JAVA_VM} ${JAVA_DEBUG} ${JAVA_PROFILE}"
export JAVA_VM

D8B3 - Standalone WLS memory leaks

I have a standalone WLS with FMWTOOLS_MAIN.D8B3_GENERIC_100218.1734.D08B03
Created with wlsconfig.sh
observing the following message in the log very frequently..almost for every request or so..
[2010-05-12T07:58:10.548-06:00] [AdminServer] [WARNING] [] [oracle.adf.share.ADFContext] [tid: Timer-18] [userId: SCMOPERATIONS] [ecid: 0000IYClSEJAPPB5JZd9if1BuLjB0000mq,1:21250] [APP: EarFscmAnalytics] Automatically initializing a DefaultContext for getCurrent.[[
Caller should ensure that a DefaultContext is proper for this use.
Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
This message may be avoided by performing initADFContext before using getCurrent().
Any idea on what this means? How to fix it?
Thanks, -Ram

Did you get a resolution for this? I am seeing the same issue. Thx.

Standalone WLS broken after unsuccessfull deployment

Hi OTN,
We've got a standalone WLS 10.3 on RedHat 5 (VM on Windows 2008) with ADF runtime installed.
This server was used for development of ADF applications from one computer for a certain time.
Few days ago my colleague tried to deploy his simple ADF app to the server. There were no exceptions during deployment but a browser couldn't reach the application.
After that I found that WLS didn't respond and stopped it with Ctrl+C from the console.
I got sonm exceptions (listed lower).
Now the server doesn't start. When I call start script I see normal messages and the last of them is
"Server state changed to STARTING". Nothing happenes after. When I interrupt the process with Ctrl+C I see the exceptions listed below.
How could I restore WLS back to work?
Thanks.
<09.08.2010 10:38:04 MSD> <Notice> <WebLogicServer> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now> <09.08.2010 10:38:04 MSD> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>>
<09.08.2010 10:38:04 MSD> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<09.08.2010 10:38:04 MSD> <Warning> <Management> <BEA-141198> <The undeployment of ReliableWseeSAFAgent failed.
weblogic.management.UndeploymentException: Deployment weblogic.management.configuration.SAFAgentMBeanImpl@8ee0d8d6([miit2]/SAFAgents[ReliableWseeSAFAgent]) was never prepared
at weblogic.management.utils.GenericManagedService.deactivateDeployment(GenericManagedService.java:257)
at weblogic.management.utils.GenericServiceManager.deactivateDeployment(GenericServiceManager.java:141)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:636)
at weblogic.management.internal.DeploymentHandlerHome.deactivateCurrentDeployments(DeploymentHandlerHome.java:562)
at weblogic.management.internal.DeploymentHandlerHome.deactivateCurrentDeployments(DeploymentHandlerHome.java:518)
Truncated. see log file for complete stacktrace
>
<09.08.2010 10:38:04 MSD> <Warning> <Management> <BEA-141198> <The undeployment of WseeFileStoreAdminServer failed.
weblogic.management.UndeploymentException: Deployment weblogic.management.configuration.FileStoreMBeanImpl@dff3f0c7([miit2]/FileStores[WseeFileStoreAdminServer]) was never prepared
at weblogic.management.utils.GenericManagedService.deactivateDeployment(GenericManagedService.java:257)
at weblogic.management.utils.GenericServiceManager.deactivateDeployment(GenericServiceManager.java:141)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:636)
at weblogic.management.internal.DeploymentHandlerHome.deactivateCurrentDeployments(DeploymentHandlerHome.java:562)
at weblogic.management.internal.DeploymentHandlerHome.deactivateCurrentDeployments(DeploymentHandlerHome.java:518)
Truncated. see log file for complete stacktrace
>
<09.08.2010 10:38:04 MSD> <Warning> <Management> <BEA-141198> <The undeployment of ReliableWseeSAFAgent failed.
weblogic.management.UndeploymentException: Deployment weblogic.management.configuration.SAFAgentMBeanImpl@8ee0d8d6([miit2]/SAFAgents[ReliableWseeSAFAgent]) was never prepared
at weblogic.management.utils.GenericManagedService.unprepareDeployment(GenericManagedService.java:285)
at weblogic.management.utils.GenericServiceManager.unprepareDeployment(GenericServiceManager.java:151)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:640)
at weblogic.management.internal.DeploymentHandlerHome.unprepareCurrentDeployments(DeploymentHandlerHome.java:597)
at weblogic.management.internal.DeploymentHandlerHome.unprepareCurrentDeployments(DeploymentHandlerHome.java:574)
Truncated. see log file for complete stacktrace
>
<09.08.2010 10:38:04 MSD> <Warning> <Management> <BEA-141198> <The undeployment of WseeFileStoreAdminServer failed.
weblogic.management.UndeploymentException: Deployment weblogic.management.configuration.FileStoreMBeanImpl@dff3f0c7([miit2]/FileStores[WseeFileStoreAdminServer]) was never prepared
at weblogic.management.utils.GenericManagedService.unprepareDeployment(GenericManagedService.java:285)
at weblogic.management.utils.GenericServiceManager.unprepareDeployment(GenericServiceManager.java:151)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:640)
at weblogic.management.internal.DeploymentHandlerHome.unprepareCurrentDeployments(DeploymentHandlerHome.java:597)
at weblogic.management.internal.DeploymentHandlerHome.unprepareCurrentDeployments(DeploymentHandlerHome.java:574)
Truncated. see log file for complete stacktrace
>

Janelle,
Did you create the ADF domain in the WLS server? Also, you can directly deploy from JDeveloper once you have the appropriate deployment descriptors.
Check this 3 articles
http://radalcove.com/blog/?p=34
http://radalcove.com/blog/?p=16
http://radalcove.com/blog/?p=48
Juan C

Deploy to Standalone WLS 10.3.5 java.lang.ClassNotFoundException:

Hi there, I am having a problem with my upgraded application and upgraded WLS server.
I am really hoping that someone can help me out here.... I simply can't get it to deploy.
Basically I had no deployment issues ever, with 11.1.1.4 and WLS 10.3.4 with deployments. I have since upgraded my JDEV application to 11.1.2 and also our standalone WLS server to 10.3.5. I believe that all post patches (upgrade ADF and the Sherman patch) have been applied. I can see the JSF 2.0 library under deployments and these are correctly targeted.
When I attempt to deploy now, the following error message is recieved:
[08:30:46 AM] [Deployer:149191]Operation 'deploy' on application 'HROpenView_application1' is initializing on 'wls_adf1'
[08:31:02 AM] Weblogic Server Exception: weblogic.application.ModuleException: Failed to load webapp: 'CEL'
[08:31:02 AM] Caused by: java.lang.ClassNotFoundException: org.apache.myfaces.trinidad.webapp.TrinidadConverterELTag
[08:31:02 AM] See server logs or server console for more details.
[08:31:02 AM] weblogic.application.ModuleException: Failed to load webapp: 'CEL'
[08:31:02 AM] Deployment cancelled.
[08:31:02 AM] ---- Deployment incomplete ----.
[08:31:02 AM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
I have read the following note:
when deplying ear file in weblogic getting this error
However this seems to be relevant to someone trying to deploye on weblogic 10.3.4. Is there something specific here that I can be looking at? It works fine on the integrated server.
I have checked my project libraries, and ADF Faces runtime 11 and Trinidad Faces Runtime 11 are both included and ticked. Is there something on the server that I need to be looking for? Does anyone know what the deployment library name is?
Cheers,
Simon
Edited by: Simo on Oct 20, 2011 2:11 PM

Simon,
your test application should be simple but not blank. If you're using BC in your other application, you should add a table (EO) and a VO. A minimal UI e. g. the vo as table on a jsf page should be enough.
If this works on the stand alone wls know that the server is running OK.
The em or enterprise manager is an application to manage one or more wls serves our cluster of serves. This em is part of the installation. When You instal the adf runtime in a server, our extend an on, you should see a check box to install the em in the server. This its am option, you don't need to do this, but my experience is that if em runs OK, the adf runtime installation is OK.
If the em its installed, you should see an application named em on the server. If this app is in running state OK you can it with the same url you use to start the admin console, only you write em instead of condole at three end of the url.
Timo

ADF 11g - Deployed app (WLS 10.3) fall into endless loop

My application runs just fine in the embedded WLS in JDeveloper 11. But when deployed to standalone WLS, the application is suddenly fall into endless redirect loop.
I tried to put out any filter that might cause the problem, including JpsFilter to no result.
The console output when a request came in is as shown in http://pastebin.com/f60edd84d . The last line of the log is when firefox detected an endless redirect loop and decided to halt.
Server log shows repeated entry of:
Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=DiagnosticsViewDomainLogTablePage&DiagnosticsViewDomainLogTablePortlethandle=com.bea.console.handles.LogDispatchHandle%28%22AdminServer%3BDomainLog%22%29
What could be the problem?
Thanks.
Rgds,
Rudi Adianto

I wanted to mention, when it occurs while rendering the page (as can be seen from the stack traces) that its occurring when rendering a tag. Here is one of the tags in my JSP page, specifically one where I think it could be hanging. Does anyone see anything fishy? This tag is an Oracle ADF tag and the "param" variable is a local loop variable. I jus recently added the " || !financialBean.profitAssistant.paDataEditable" part but I don't know if thats the cause of the problem. This does not occur everytime, it just seems like when there is a good amount of load on the system.
<af:inputText simple="true"
     id=         "tlInputTextParam"
     value=      "#{param.textValue}"
     rendered=   "#{param.rendered}"
     disabled=   "#{param.disabled || !financialBean.profitAssistant.paDataEditable}"
     styleClass= "#{param.styleClass}"
     inlineStyle="#{param.style}"
     columns=    "#{param.componentSize}"
     onchange=   "#{param.onChangeJS}"
     onclick=    "#{param.onClickJS}"
     onkeydown= "#{param.onKeyDownJS}"
     onfocus=    "#{param.onFocusJS}"
     onblur=     "#{param.onBlurJS}"
     onmouseover="try{this.title='#{param.description}';#{param.onMouseOverValueJS}}catch(e){}"
     />

Infinite loop/afrLoop when deploying ADF application to standalone weblogic

Working with Oracle ADF / JDeveloper 11.1.2.2
I have enabled ADF security in my application and am using JAAS combined with Oracle EBS users and roles to provide security to the application. Testing on my local integrated weblogic server works fine.
When deploying my Oracle ADF application to a standalone Weblogic server through an EAR file, requesting a JSF page causes the server to go into an infinite loop on both IE and firefox.
GET /test-app/faces/login.jsf HTTP/1.1     200
GET /test-app/faces/login.jsf?_afrLoop=346001033248597&_afrWindowMode=0&Adf-Window-Id=w0 HTTP/1.1     302
GET /test-app/adfAuthentication HTTP/1.1     302
GET /test-app/faces/login.jsf HTTP/1.1     200
GET /test-app/faces/login.jsf?_afrLoop=346001340281597&_afrWindowMode=0&Adf-Window-Id=w0 HTTP/1.1     302
GET /test-app/adfAuthentication HTTP/1.1     302
GET /test-app/faces/login.jsf;jsessionid=syWvP1nMY1L87BySh2JbTd1tb4SY0HzDw6T3LvLctvkbMWKmqqJv!1800986117 HTTP/1.1     200
GET /test-app/adfAuthentication HTTP/1.1
Reviewing some of the suggestions from the forum and from the link below, I have tried fixing the issue through updates to my web.xml - but am still having the same issue.
https://blogs.oracle.com/jdevotnharvest/entry/solving_jdeveloper_11gr2_issue_with
Updated web.xml:
<security-constraint>
<web-resource-collection>
<web-resource-name>Allowed ADF Resources</web-resource-name>
<url-pattern>/adf/*</url-pattern>
<url-pattern>/afr/*</url-pattern>
<url-pattern>/bi/*</url-pattern>
<url-pattern>/servlet/GraphServlet/*</url-pattern>
<url-pattern>/servlet/GaugeServlet/*</url-pattern>
<url-pattern>/mapproxy/*</url-pattern>
<url-pattern>/adflib/</url-pattern>
</web-resource-collection>
<web-resource-collection>
<web-resource-name>allPages</web-resource-name>
<url-pattern>/*</url-pattern>
</web-resource-collection>
<web-resource-collection>
<web-resource-name>adfAuthentication</web-resource-name>
<url-pattern>/adfAuthentication</url-pattern>
</web-resource-collection>
<auth-constraint>
<role-name>valid-users</role-name>
</auth-constraint>
</security-constraint>
<login-config>
<auth-method>FORM</auth-method>
<form-login-config>
<form-login-page>/faces/login.jsf</form-login-page>
<form-error-page>/faces/login-error.jsf</form-error-page>
</form-login-config>
</login-config>
<security-role>
<role-name>valid-users</role-name>
</security-role>
weblogic.xml
<security-role-assignment>
<role-name>valid-users</role-name>
<principal-name>users</principal-name>
</security-role-assignment>
I know other users have experienced similar issues - but I am having trouble debugging or troubleshooting why this is happening.
Any suggestions on how to further troubleshoot or resolve this issue would be appreciated!
Dan

I was able to resolve the login page looping issue.
The issue is related to the login page being a JSF page based on a page template.
When I created the JSF login page as a page template - the template contains a binding:
<af:pageTemplate viewId="/test-template.jsf" value="#{bindings.ptb1}" id="pt1">
When I deploy my application to the test weblogic server, the anonymous-role grants are not being respected. So even though I grant view access to the login JSF page to anonymous-role -- it appears that weblogic is trying to request a login for any page with a pageDef (including the login page). By re-creating the login page with no pageDef (a JSF page that does not use a page template) -- the login page is displayed (rather than entering into a loop).
There is still a seperate issue with the anonymous-role grant not working as I would expect it to work that I will need to troubleshoot further.

Looking for clarification on ADF 12.1.2 WLS support

What versions of WLS supports ADF 12.1.2? If there is support for 11g, are there any documentation on how to install the ADF 12 Runtime?
Oracle JDeveloper 12c Support</title><meta name="Title" content="Oracle JDeveloper 12c Support&q…
Application Servers
The following table shows application servers supported by JDeveloper and ADF. Application Server support for JDeveloper is provided for connecting and deploying directly to the server as well as debugging. For ADF, it refers to servers that ADF applications can be deployed to.
Application Server
JDeveloper
ADF
Oracle Fusion Middleware (WLS)
10.3.5+, 12.1.2
12.1.2
GlassFish
3.1+
3.1 (ADF Essentials)
WebSphere
8.x
JBoss
5
Tomcat
7
Oracle Cloud
13.1

I'm not hearing any oracle responses, thus I can only assume what Timo said is the closest to that fact.
Here is what I know about what a production ready standalone WLS 12c with ADF Runtime 12.1.2 entails:
-a domain running on WLS 12.1.2 needs JRF & Coherence to be installed in order to run ADF 12.1.2 https://forums.oracle.com/thread/2559381
-JRF & Coherence on WLS 12.1.2 needs a RCU database repository JDeveloper 12c & Standalone WLS w/ADF Runtime 12.1.2
-WLS 12.1.2 is only certified to run on Oracle DB 11.1.0.7+ http://www.oracle.com/technetwork/middleware/ias/downloads/wls-1211x-certmatrix-1395408.xls
Does that sound about right?
I hope I'm wrong and someone can guide me to easier setup. It seems that getting a standalone WLS server to run ADF has gotten harder with every new release!
I can get a standalone WLS 10.3.5 up with ADF 11.1.2.4 in ~3mins
http://www.youtube.com/watch?v=TG6wqrFVY00
WLS 10.3.6 with ADF 11.1.2.4 requires 2 additional console applied patches ontop of the 11.1.1.6 runtime installer. (Corrected from false version of 11.1.1.7)
WLS 12.1.2 with ADF 12.1.2 - I have not attempted but it seems to be even more involved than the previous.

Application Logging in Standalone weblogic - quick questions

Hi
In JDeveloper, we could write our application logging to logs for debugging and viewable from JDeveloper.
When we deploy to Standalone weblogic server, we cant find our logging.
Of the 3 loggers (Msg Catalog, nonCatalog, Commons log API),
Which logging mechanism is the best practice used logging for development environment ? Does it print to AdminServer.log ? If not, how can we accomplish that printing app log to AdminServer.log ?
Which logging mechanism is the best practice used logging for production environment ? Does it print to AdminServer.log ? If not, how can we accomplish that printing app log to AdminServer.log ?
Thanks

hi,
people commonly Log4J for their logging,Like Commons Logging, SLF4J, or the default Java Logging API. But if you're working with Oracle's Application Development Framework, there is another option as well: ADF Logging.
ADF Logging is a logging mechanism, embedded in the ADF framework. It wraps the Java Logging API, but throws in a few extra methods and some JDeveloper and (Weblogic) Enterprise Manager features.
the following one demo video from oracle site its very useful.
http://download.oracle.com/otn_hosted_doc/jdeveloper/11gdemos/ADF_Insider_Essentials/debug_part1/debug_part1.html
regards
siva

To Enable ADF Logging on Standalone WLS

Similar Messages

Maybe you are looking for