Change security of adf application on weblogic

hi all,
i am new in weblogic. i set oid in weblogic succesfully. But i couldn't change security of adf application. Is there any documantationof how change security of adf application?

hi frank,
i mean that i set oid in myrealm which is my default security realm. I change order of Authentication Providers. all of the users of oid are in myrealm . However my application does not use this ldap configuration. i couldn't change security of application, and i need help. Before i deploy my 10.1.3 adf application to oc4j and during deployment i can set the security of application but i couldnt see anything like oc4j in weblogic
i configure my oid like below link
http://www.oracle.com/technology/products/jdev/tips/fnimphius/oidconfig/index.html

Similar Messages

Facing error while deploying ADF application on weblogic

We are trying to deploy an ADF Application on weblogic server. We are facing below quoted error (java.lang.ClassNotFoundException: org.apache.myfaces.trinidad.webapp.ResourceServlet) during deployment:
INFO: Completed initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/console'
<Nov 2, 2011 11:32:21 AM IST> <Warning> <J2EE> <BEA-160188> <Unresolved WebApp library references defined in weblogic.xml, of module 'CallTracker_CallTrackerUI_webapp1.war' [Extension-Name: adf.oracle.domain.webapp, exact-match: false], [Extension-Name: jstl, Specification-Version: 1.2, exact-match: false], [Extension-Name: jsf, Specification-Version: 1.2, exact-match: false].>
java.lang.ClassNotFoundException: org.apache.myfaces.trinidad.webapp.ResourceServlet
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at java.lang.ClassLoader.loadClass(ClassLoader.java:321)
at java.lang.ClassLoader.loadClass(ClassLoader.java:266)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
at weblogic.servlet.internal.WebAnnotationProcessorImpl.processServlets(WebAnnotationProcessorImpl.java:225)
at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:209)
at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:105)
at weblogic.application.compiler.WARModule.processAnnotations(WARModule.java:433)
at weblogic.application.compiler.EARModule.processAnnotations(EARModule.java:227)
at weblogic.application.compiler.WARModule.merge(WARModule.java:483)
at weblogic.sip.tools.SipToolsModule.merge(SipToolsModule.java:57)
at weblogic.application.compiler.flow.MergeModuleFlow.compile(MergeModuleFlow.java:23)
at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
at weblogic.application.compiler.FlowDriver$CompilerFlowDriver.compile(FlowDriver.java:96)
at weblogic.application.compiler.ReadOnlyEarMerger.merge(ReadOnlyEarMerger.java:49)
at weblogic.application.compiler.flow.AppMergerFlow.mergeInput(AppMergerFlow.java:88)
at weblogic.application.compiler.flow.AppMergerFlow.compile(AppMergerFlow.java:41)
at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
at weblogic.application.compiler.FlowDriver$CompilerFlowDriver.compile(FlowDriver.java:96)
at weblogic.application.compiler.AppMerge.runBody(AppMerge.java:157)
at weblogic.utils.compiler.Tool.run(Tool.java:158)
at weblogic.utils.compiler.Tool.run(Tool.java:115)
at weblogic.application.compiler.AppMerge.merge(AppMerge.java:169)
at weblogic.deploy.api.internal.utils.AppMerger.merge(AppMerger.java:88)
at weblogic.deploy.api.internal.utils.AppMerger.getMergedApp(AppMerger.java:63)
at weblogic.deploy.api.model.internal.WebLogicDeployableObjectFactoryImpl.createDeployableObject(WebLogicDeployableObjectFactoryImpl.java:181)
at weblogic.deploy.api.model.internal.WebLogicDeployableObjectFactoryImpl.createDeployableObject(WebLogicDeployableObjectFactoryImpl.java:163)
at weblogic.deploy.api.tools.SessionHelper.initialize(SessionHelper.java:727)
Please advise. We are using weblogic 10.3.5 .

Thanks, we have reinstalled the weblogic again , ensuring that Application Development Runtime is installed and we extend our domain with the JRF. So the previous error is resolved. But we are now facing a new error
weblogic.common.ResourceException: java.security.PrivilegedActionException: weblogic.common.ResourceException: java.security.PrivilegedActionException: weblogic.common.ResourceException: No credential mapper entry found for password indirection user=apps for data source XXCT
- Warning Errors were encountered while performing this operation.
Please help.
Regards, Atul

Error deploying adf application to weblogic

hi am deploying my adf application using weblogic but am geting this error
weblogic 10.3.5
jeveloper is 11.1.6.0
[12:14:21 PM] ---- Deployment started. ----
[12:14:21 PM] Target platform is (Weblogic 10.3).
[12:14:22 PM] Retrieving existing application information
[12:14:22 PM] Running dependency analysis...
[12:14:22 PM] Building...
[12:14:32 PM] Deploying profile...
[12:14:33 PM] Wrote Web Application Module to C:\JDeveloper\mywork\Align\ViewController\deploy\Align_ViewController_webapp.war
[12:14:33 PM] Deploying Application...
[12:14:35 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application Align_ViewController_webapp on AdminServer.: [Deployer:149145]Unable to contact 'madimad-b533821'. Deployment is deferred until 'madimad-b533821' becomes available.; nested exception is:
java.rmi.UnknownHostException: Could not discover administration URL for server 'madimad-b533821'.
[12:14:35 PM] [Deployer:149193]Operation 'deploy' on application 'Align_ViewController_webapp' has failed on 'AdminServer'
[12:14:35 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application Align_ViewController_webapp on AdminServer.: Failed to load webapp: 'Align_ViewController_webapp.war'.
[12:14:35 PM] Weblogic Server Exception: weblogic.application.ModuleException: Failed to load webapp: 'Align_ViewController_webapp.war'
[12:14:35 PM] Caused by: java.lang.ClassNotFoundException: oracle.adf.model.servlet.ADFBindingFilter
[12:14:35 PM] See server logs or server console for more details.
[12:14:35 PM] weblogic.application.ModuleException: Failed to load webapp: 'Align_ViewController_webapp.war'
[12:14:35 PM] Deployment cancelled.
[12:14:35 PM] ---- Deployment incomplete ----.
[12:14:35 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)

Hi,
ADF applications that use business components need the weblogic-application.xml deployment
descriptor to be present to be able to work on a WLS.
http://docs.oracle.com/cd/E12839_01/web.1111/b31974/deployment_topics.htm#CHDCICJH
35.4 Creating and Editing Deployment Descriptors
mentions the need of :
<library-ref>
<library-name>adf.oracle.domain</library-name>
</library-ref>
in the weblogic-application.xml
==> please execute the following steps:
1. Wrap the WAR file in an EAR file configured to be deployed to a WebLogic server as follows, so that JDeveloper includes the needed deployment descriptor file:
2.Right-click the project containing the web contents (usually ViewController), and select New -> Deployment Profile. Then select EAR Deployment Profile.
3. Enter the name for the application, and then in the EAR profile properties dialog, in the Application Assembly, include the ViewController project, and in the Platform node, make sure Default Platform is set to WebLogic 10.3. Click OK.
4. In the next dialog box (Project properties), open the node ADF Model, and make sure the checkbox "Contains Data Controls" is checked, and click OK
5. Now to deploy, right click the ViewController project and select Deploy, then the name of the recently created application deployment profile, and then "to EAR file". This will result in a .ear file, deployable from the WLS administration page.
Thanks,
Sharmela

Page naviagation doesn't work after deploy ADF application to Weblogic

After deploy my ADF application (ear) to Weblogic Server, the page navigation doesn't work. When running the ear on weblogic, I got following warnings:
<2010-11-5 下午05时06分01秒 CST> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application HwtOrder is not versioned.>
<2010-11-5 下午05时06分38秒 CST> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=AppApplicationOverviewPage&AppApplicationOverviewPortlethandle=com.bea.console.handles.AppDeploymentHandle%28%22com.bea%3AName%3DHwtOrder%2CType%3DAppDeployment%22%29.>
<2010-11-5 下午05时07分33秒 CST> <Warning> <netuix> <BEA-423420> <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%22DefaultServer%3BDomainLog%22%29.>
I can run the application correctly in jdeveloper 11g environment. I think there is something wrong with deployment. Can anyone help me?

When you target url with .jspx, you are running the page itself, not in the task flow context, so navigation doesn't work.
In the task flow, your page has 'Activity ID' (which is, for example, 'mainPage' for mainPage.jspx) and the navigation is defined for activity IDs, not pages.
Pedja

Migrate an ADF application to weblogic 11g

Hi, I'm trying to migrate a 10g ADF application deployed in OC4J to 11g using the migration tool of JDeveloper.
After some changes in code to adapt to the new api i have an error in libraries while trying to deploy in embeded weblogic.
<30 Ιουν 2010 11:32:50 πμ EEST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1277886764036' for task '1'. Error is: 'java.lang.ClassNotFoundException: oracle.adf.view.faces.event.AttributeChangeEvent'
java.lang.ClassNotFoundException: oracle.adf.view.faces.event.AttributeChangeEvent
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:296)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:269)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:56)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: oracle.adf.view.faces.event.AttributeChangeEvent
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:296)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:269)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:56)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
Truncated. see log file for complete stacktrace
>
Embeded weblogic runs with ADF libraries of 11g why this class cannot be found?
Any comment will be helpfull,
Thanks

Please verify again that you have set your environment properly.
regards

Unable to deploy ADF application to weblogic server

Hi,
We are developing ADF application using jDeveloper 11.1.1.1 and deploying to Weblogic Server 10.3.1. The application is working without any problems on 10.3.1 wblogic platform.
We procured new 64 bit hardware and installed weblogic 10.3.2 and jdeveloper 11.1.1.2 on windows platform. When we are deploying the application developed using jdeveloper 11.1.1.1 on the new platform we are getting the following exception.
An error occurred during activation of changes, please see the log for details.
[J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: adf.oracle.domain, Implementation-Version: 11.1.1.1.0, exact-match: false], [Extension-Name: oracle.jsp.next, exact-match: false].
Can you please provide some suggestions to debug the problem.
Thanks and Regards,
S R Prasad

Hi,
I have tried deploying the application using jdeveloper 11.1.1.2.0, But this time I am getting the following error after commenting the following lines in weblogic-application.xml. I have removed the following lines as I am getting classnot found exception for oracle.adf.share.weblogic.listeners.ADFApplicationLifecycleListener and oracle.mds.lcm.weblogic.WLLifecycleListener.
If I deployed the application on the admin server, The application is working with out any problems. I am having problems only on Managed Server at the time of deployment.
<listener>
<listener-class>oracle.adf.share.weblogic.listeners.ADFApplicationLifecycleListener</listener-class>
</listener>
<listener>
<listener-class>oracle.mds.lcm.weblogic.WLLifecycleListener</listener-class>
</listener>
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:973)
at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAnnotationProcessor.java:966)
Truncated. see log file for complete stacktrace
Caused By: 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:973)
at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAnnotationProcessor.java:966)
Truncated. see log file for complete stacktrace
I installed weblogic with the following steps.
1. Install weblogic 10.3.2 (64 bit)
2. Install jdeveloper (ADF runtime only)
3. Launch configuration wizard.
4. create domain.
5. extend domain with jrf libraries.
5. create managed server
Thanks and Regards,
S R Prasad

Deploying adf application to WebLogic Server Version: 10.3.6.0

hi i have develope application in adf using jdeveloper 11.1.1.6.0 i have deploy the application to weblogic 10.3.6.0
this is what i have done
1. i have created a new Managed server in my weblogic=under Environment->Servers
2.the state of my new server is shutdown
3.deployment method
-in my jdeveloper i click application->Application properties->Deployment->new->Archive Type->EAR FILE->applicationName->OK
TO deploy from jdeveloper to weblogic server
in my jdeveloper i click application APPLICATION->Deploy->applicationName->Deploy to Application Server-applicationserver i choose the new server i created in my weblogic->weblogic Option->deploy to selected instance->i select the name of the server i created in my weblogic->next->finish
after that the deployment configuration screen pop up than i click deploy then screen MDS CONFIGURATION invalid pop up with message MDS CONFIGURATION information appear invalid metadata Repository not found in target server.deploy anyway then i click yes
i got this meaasge in my deployment log
[08:33:46 AM] Entering Oracle Deployment Plan Editor
[08:38:56 AM] Deploying Application...
[08:38:57 AM] [Deployer:149195]Operation 'deploy' on application 'UAMOrganisation' has been deferred since 'UamOrganisation' is unavailable
[08:38:57 AM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application UAMOrganisation on UamOrganisation.: .
[08:38:57 AM] Application Deployed Successfully.
[08:38:57 AM] Elapsed time for deployment: 5 minutes, 21 seconds
[08:38:57 AM] ---- Deployment finished. ----than i go to my weblogic under deployment there i found my deploy application with a state=new and type=Enterprise application
than i click start->Servircing all request->start application assistance->yes->Start requests have been sent to the selected Deployments.
but now i what to test my application am geting this Internet Explorer cannot display the webpage,do i need to start my Managed server how do i do that,i try to click server start but it does not start how can i start my new created Managed server
the listern port of my new created server is 8003
my problem is am not able to test the application i have deploy
Edited by: adf009 on 2013/01/30 11:26 AM
Edited by: adf009 on 2013/01/30 11:39 AM
Edited by: adf009 on 2013/01/30 11:41 AM
Edited by: adf009 on 2013/01/30 12:33 PM

i did this,am in window 7 64 bit
start startNodeManager.cmd
C:\Oracle\weblogic\wlserver_10.3\server\bin>set CLASSPATH=.;C:\Oracle\weblogic\p
atch_wls1036\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracl
e\weblogic\patch_ocp371\profiles\default\sys_manifest_classpath\weblogic_patch.j
ar;C:\Oracle\MIDDLE~1\JDK160~1\lib\tools.jar;C:\Oracle\weblogic\WLSERV~1.3\serve
r\lib\weblogic_sp.jar;C:\Oracle\weblogic\WLSERV~1.3\server\lib\weblogic.jar;C:\O
racle\weblogic\modules\features\weblogic.server.modules_10.3.6.0.jar;C:\Oracle\w
eblogic\WLSERV~1.3\server\lib\webservices.jar;C:\Oracle\weblogic\modules\ORGAPA~
1.1/lib/ant-all.jar;C:\Oracle\weblogic\modules\NETSFA~1.0_1/lib/ant-contrib.jar;
C:\Oracle\MIDDLE~1\WLSERV~1.1\server\lib\xqrl.jar
C:\Oracle\weblogic\wlserver_10.3\server\bin>if not "" == "" set CLASSPATH=;.;C:\
Oracle\weblogic\patch_wls1036\profiles\default\sys_manifest_classpath\weblogic_p
atch.jar;C:\Oracle\weblogic\patch_ocp371\profiles\default\sys_manifest_classpath
\weblogic_patch.jar;C:\Oracle\MIDDLE~1\JDK160~1\lib\tools.jar;C:\Oracle\weblogic
\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Oracle\weblogic\WLSERV~1.3\server\lib\
weblogic.jar;C:\Oracle\weblogic\modules\features\weblogic.server.modules_10.3.6.
0.jar;C:\Oracle\weblogic\WLSERV~1.3\server\lib\webservices.jar;C:\Oracle\weblogi
c\modules\ORGAPA~1.1/lib/ant-all.jar;C:\Oracle\weblogic\modules\NETSFA~1.0_1/lib
/ant-contrib.jar;C:\Oracle\MIDDLE~1\WLSERV~1.1\server\lib\xqrl.jar
C:\Oracle\weblogic\wlserver_10.3\server\bin>if not "C:\Oracle\MIDDLE~1\WLSERV~1.
1\server\lib\xqrl.jar" == "" set CLASSPATH=.;C:\Oracle\weblogic\patch_wls1036\pr
ofiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\weblogic\patc
h_ocp371\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MI
DDLE~1\JDK160~1\lib\tools.jar;C:\Oracle\weblogic\WLSERV~1.3\server\lib\weblogic_
sp.jar;C:\Oracle\weblogic\WLSERV~1.3\server\lib\weblogic.jar;C:\Oracle\weblogic\
modules\features\weblogic.server.modules_10.3.6.0.jar;C:\Oracle\weblogic\WLSERV~
1.3\server\lib\webservices.jar;C:\Oracle\weblogic\modules\ORGAPA~1.1/lib/ant-all
.jar;C:\Oracle\weblogic\modules\NETSFA~1.0_1/lib/ant-contrib.jar;C:\Oracle\MIDDL
E~1\WLSERV~1.1\server\lib\xqrl.jar;C:\Oracle\MIDDLE~1\WLSERV~1.1\server\lib\xqrl
.jar
C:\Oracle\weblogic\wlserver_10.3\server\bin>cd C:\Oracle\weblogic\WLSERV~1.3\com
mon\NODEMA~1
C:\Oracle\weblogic\WLSERV~1.3\common\NODEMA~1>if not "" == "" if not "" == "" go
to runNMWithListenAddressAndPort
C:\Oracle\weblogic\WLSERV~1.3\common\NODEMA~1>if not "" == "" goto runNMWithList
enAddress
C:\Oracle\weblogic\WLSERV~1.3\common\NODEMA~1>if not "" == "" goto runNMWithList
enPort
C:\Oracle\weblogic\WLSERV~1.3\common\NODEMA~1>"C:\Oracle\MIDDLE~1\JDK160~1\bin\j
ava.exe" -server -Xms32m -Xmx200m -XX:MaxPermSize=128m -XX:+UseSpinning -Dcohere
nce.home=C:\Oracle\weblogic\COHERE~1.7 -Dbea.home=C:\Oracle\weblogic -Dweblogic
.ProductionModeEnabled=true   -da -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.1
-Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.1\server -Dweblogic.home=C:\Oracle\MIDDLE
~1\WLSERV~1.1\server   -Dweblogic.management.discover=true -Dwlw.iterativeDev=f
alse -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false "-Djava.security.pol
icy=C:\Oracle\weblogic\WLSERV~1.3\server\lib\weblogic.policy" "-Dweblogic.nodema
nager.javaHome=C:\Oracle\MIDDLE~1\JDK160~1" weblogic.NodeManager -v
<30 Jan 2013 1:14:37 PM> <INFO> <Loading domains file: C:\Oracle\weblogic\WLSERV
~1.3\common\NODEMA~1\nodemanager.domains>
30 Jan 2013 1:14:37 PM weblogic.nodemanager.server.NMServerConfig initDomainsMap
INFO: Loading domains file: C:\Oracle\weblogic\WLSERV~1.3\common\NODEMA~1\nodema
nager.domains
<30 Jan 2013 1:14:38 PM> <INFO> <Loading identity key store: FileName=C:\Oracle\
MIDDLE~1\WLSERV~1.1\server\lib\DemoIdentity.jks, Type=jks, PassPhraseUsed=true>
30 Jan 2013 1:14:38 PM weblogic.nodemanager.server.SSLConfig loadKeyStoreConfig
INFO: Loading identity key store: FileName=C:\Oracle\MIDDLE~1\WLSERV~1.1\server\
lib\DemoIdentity.jks, Type=jks, PassPhraseUsed=true
<30 Jan 2013 1:14:38 PM> <SEVERE> <Fatal error in node manager server>
weblogic.nodemanager.common.ConfigException: Identity key store file not found:
C:\Oracle\MIDDLE~1\WLSERV~1.1\server\lib\DemoIdentity.jks
        at weblogic.nodemanager.server.SSLConfig.loadKeyStoreConfig(SSLConfig.ja
va:153)
        at weblogic.nodemanager.server.SSLConfig.<init>(SSLConfig.java:102)
        at weblogic.nodemanager.server.NMServer.init(NMServer.java:186)
        at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:148)
        at weblogic.nodemanager.server.NMServer.main(NMServer.java:380)
        at weblogic.NodeManager.main(NodeManager.java:31)
30 Jan 2013 1:14:38 PM weblogic.nodemanager.server.NMServer main
SEVERE: Fatal error in node manager server
weblogic.nodemanager.common.ConfigException: Identity key store file not found:
C:\Oracle\MIDDLE~1\WLSERV~1.1\server\lib\DemoIdentity.jks
        at weblogic.nodemanager.server.SSLConfig.loadKeyStoreConfig(SSLConfig.ja
va:153)
        at weblogic.nodemanager.server.SSLConfig.<init>(SSLConfig.java:102)
        at weblogic.nodemanager.server.NMServer.init(NMServer.java:186)
        at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:148)
        at weblogic.nodemanager.server.NMServer.main(NMServer.java:380)
        at weblogic.NodeManager.main(NodeManager.java:31)
C:\Oracle\weblogic\WLSERV~1.3\common\NODEMA~1>goto finish
C:\Oracle\weblogic\WLSERV~1.3\common\NODEMA~1>ENDLOCAL
C:\Oracle\weblogic\wlserver_10.3\server\bin>can i test my application without manged server started
link is http://italianknows.blogspot.com/2011/02/weblogic-1034-ps3-nodemanager-wont.html
Edited by: adf009 on 2013/01/30 1:43 PM
Edited by: adf009 on 2013/01/30 1:56 PM
Edited by: adf009 on 2013/01/30 1:57 PM
Edited by: adf009 on 2013/01/30 2:14 PM
Edited by: adf009 on 2013/01/30 2:15 PM
Edited by: adf009 on 2013/01/30 2:16 PM

How to deal with security when migrating application from weblogic 5.1 to weblogic 6.1?

Dear All,
I have one statement int weblogic 5.1 weblogic.propertis as follow,
weblogic.security.realmClass=com.tbcn.security.realm.TestRealm
but after converting to weblogic 6.1 there are no corresponding statement in
the file config.xml. And when i start the new application, error occured.
what should I do?
The error message is:
<2001/8/27 am 11:33:42> <Notice> <Management> <Loading configuration file
.\config\tbcn\config.xml
<2001/8/27 am 11:33:49> <Emergency> <Server> <Unable to initialize the
server: 'Fatal initializatio
Throwable: java.lang.NullPointerException
java.lang.NullPointerException
at
weblogic.security.SecurityService.initializeRealm(SecurityService.java:261)
at
weblogic.security.SecurityService.initialize(SecurityService.java:115)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:385)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
at weblogic.Server.main(Server.java:35)
'>
The WebLogic Server did not start up properly.
Exception raised: java.lang.NullPointerException
java.lang.NullPointerException
at
weblogic.security.SecurityService.initializeRealm(SecurityService.java:261)
at
weblogic.security.SecurityService.initialize(SecurityService.java:115)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:385)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception

Dear Satya,
My weblogic propertis file as follow,
# CORE PROPERTIES
# You should set these before you start the WebLogic Server the first time.
# If you need more instructions on individual properties in this
# section, check the same section in the Optional Properties, where
# we've left the long explanations. Or, better yet, go to our
# website and read all about properties, at:
# http://www.weblogic.com/docs51/admindocs/properties.html
# CORE SYSTEM PROPERTIES
# TCP/IP port number at which the WebLogic Server listens for connections
weblogic.system.listenPort=7001
# CORE SECURITY-RELATED PROPERTIES
# Read important information about security at:
# http://www.weblogic.com/docs51/admindocs/properties.html
# REQUIRED: The system password MUST be set in order to start the
# WebLogic Server. This password is case-sensitive, at least 8 characters.
# The username for the privileged user is ALWAYS "system".
# This username and password also includes httpd access (see
# HTTPD properties below).
weblogic.password.system=12345678
# RECOMMEND Set to 'everyone' if HTTPD is enabled
weblogic.allow.execute.weblogic.servlet=everyone
# Set individual ACLs to restrict access to HTTP-related resources,
# such as the Administration servlets.
# To make your own servlets generally available, follow this
# pattern (provide a weblogic.allow.execute) for your packages and
# set ACLs as appropriate.
# CORE SECURITY-RELATED PROPERTIES FOR SSL
# Read important information about SSL at:
# http://www.weblogic.com/docs51/classdocs/API_secure.html
# Enable SSL
# (default if property not defined is false)
weblogic.security.ssl.enable=true
# SSL listen port
weblogic.system.SSLListenPort=7002
# Servlets for SSL
# Authentication servlet for creating tokens for applets
weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationS
ervlet
# Limits number of unclaimed stored tokens
weblogic.security.certificateCacheSize=3
# Capture CA root of client servlet
weblogic.httpd.register.AdminCaptureRootCA=admin.AdminCaptureRootCA
# Certificates for SSL
# Name of acceptable CA roots
# For client authentication change value to a valid .pem file
#weblogic.security.clientRootCA=SecureServerCA.pem
# Server certificates for SSL
weblogic.security.certificate.server=democert.pem
weblogic.security.key.server=demokey.pem
weblogic.security.certificate.authority=ca.pem
# registration for certificate generator servlet
weblogic.httpd.register.Certificate=utils.certificate
weblogic.allow.execute.weblogic.servlet.Certificate=system
# CORE HTTPD ADMINISTRATIVE PROPERTIES
# True permits the HTTPD to run (default)
# Uncomment this property to disable HTTPD
#weblogic.httpd.enable=false
# If authentication is required, add username/password for each user
# who will be included in an ACL, as in this commented-out example:
#weblogic.password.peter=#8gjsL4*
# SYSTEM PROPERTIES
# System properties in this section are set to system defaults
# Performance pack. The shared library must be accessible from your
# PATH (NT) or from your shared library path (UNIX; the name of the
# variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
weblogic.system.nativeIO.enable=true
# Outputs logging information to the console as well as to the log file
weblogic.system.enableConsole=true
# Sets the directory or URL for the WebLogic Admin help pages
# The help pages are shipped in the "docs/adminhelp" directory, in the
# default document root in public_html
weblogic.system.helpPageURL=/weblogic/myserver/public_html/docs51/adminhelp/
# If you prefer to access the most recent help pages, you can do so online
# by commenting out the previous property and uncommenting this one:
#weblogic.system.helpPageURL=http://www.weblogic.com/docs51/adminhelp/
# Properties for tuning the server's performance
# Number of WebLogic Server execute threads.
weblogic.system.executeThreadCount=15
# Other optional system properties
# Limits size of weblogic.log (in K) and versions old log
weblogic.system.maxLogFileSize=1024
# Adjust minimum length of password
weblogic.system.minPasswordLen=8
# UNIX only: If running on port 80 on UNIX, enable the setUID program
#weblogic.system.enableSetUID=false
# UNIX only: Unprivileged user to setUID to after starting up
# WebLogic Server on port 80
#weblogic.system.nonPrivUser=nobody
# CLUSTER-SPECIFIC PROPERTIES
# Cluster-specific properties in this section are set to system defaults.
# CLUSTER USERS: Note that ALL Cluster-specific properties should be set
# in the per-cluster properties file ONLY.
# Time-to-live (number of hops) for the cluster's multicast messages
# (default 1, range 1-255).
#weblogic.cluster.multicastTTL=1
# Sets the load-balancing algorithm to be used between
# replicated services if none is specified. If not specified,
# round-robin is used.
#weblogic.cluster.defaultLoadAlgorithm=round-robin
# SERVER-SPECIFIC CLUSTER PROPERTIES
# Cluster-related properties in this section are set to system defaults.
# CLUSTER USERS: Note that these server-specific cluster-related properties
# should be set in the per-server properties file ONLY.
# Sets the weight of the individual server for the weight-based
load-balancing.
# Range is 0 - 100.
# Larger numbers increase the amount of traffic routed to this server.
#weblogic.system.weight=100
# SYSTEM STARTUP FILES - Examples
# CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
# objects should be registered in the per-server properties file.
# All other startup classes should be registered in the per-cluster
# properties file.
# For more info on writing and using startup file, see the
# Developers Guide "Writing a WebLogic Client application," at
# http://www.weblogic.com/docs51/classdocs/API_t3.html
# Register a startup class by giving it a virtual name and
# supplying its full pathname.
#weblogic.system.startupClass.[virtual_name]=[full_pathname]
# Add arguments for the startup class
#weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
# This example shows the entry for examples/t3client/StartupQuery.java
#weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
#weblogic.system.startupArgs.doquery=\
# query=select * from emp,\
# db=jdbc:weblogic:pool:demoPool
# SYSTEM SHUTDOWN FILES - Examples
# For more info on writing and using shutdown file, see the
# Developers Guide "Writing a WebLogic Client application," at
# http://www.weblogic.com/docs51/classdocs/API_t3.html
# Register a shutdown class by giving it a virtual name and
# supplying its full pathname.
#weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
# Add arguments for the shutdown class
#weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
# This example shows the entry for examples/t3client/ShutdownTest.java
#weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
#weblogic.system.shutdownArgs.ShutdownTest=\
# outfile=c:/temp/shutdown.log
# SECURITY-RELATED PROPERTIES FOR WORKSPACES
# For backward compatibility, the following entries disable Access
# Control on Workspaces
weblogic.allow.read.weblogic.workspace=everyone
weblogic.allow.write.weblogic.workspace=everyone
# JOLT FOR WEBLOGIC PROPERTIES
# These properties configure a BEA Jolt connection pool for use with
# the simpapp and bankapp examples, and register a servlet for use with
# with the simpapp example. The default server address provided here
# points to a public TUXEDO server that is hosted by BEA for use with
# this example.
# Servlet registration for simpapp example:
#weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServle
t
# Pool creation and cleanup
# note this example is set up to work with the public
# demo TUXEDO server available from BEA's website:
#weblogic.system.startupClass.demojoltpoolStart=\
# bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
#weblogic.system.startupArgs.demojoltpoolStart=\
# poolname=demojoltpool,\
# appaddrlist=//beademo1.beasys.com:8000,\
# failoverlist=//beademo1.beasys.com:8000,\
# minpoolsize=1,\
# maxpoolsize=3
#weblogic.system.shutdownClass.demojoltpoolStop=\
# bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
#weblogic.system.shutdownArgs.demojoltpoolStop=\
# poolname=demojoltpool
# WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
# The registrations enable a BEA IIOP connection pool and
# register servlets for use with the simpapp and university examples.
# Configure for your environment and uncomment to use.
# Uncommenting these properties requires WebLogic Enterprise Connectivity
# and an operating WebLogic Enterprise Server.
# Servlet registration for simpapp servlet example
#weblogic.httpd.register.SimpappServlet=\
# examples.wlec.servlets.simpapp.SimpappServlet
#weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
# Servlet registration for simpapp EJB example
# (You'll need to add the wlec_ejb_simpapp.jar to the
# weblogic.ejb.deploy property in this file.)
#weblogic.httpd.register.ejbSimpappServlet=\
# examples.wlec.ejb.simpapp.ejbSimpappServlet
#weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
# Pool creation and cleanup for the simpapp example
#weblogic.CORBA.connectionPool.simplepool=\
# appaddrlist=//wlehost:2468,\
# failoverlist=//wlehost:2468,\
# minpoolsize=2,\
# maxpoolsize=3,\
# username=wleuser,\
# userrole=developer,\
# domainname=simpapp
# Servlet registration for university Servlet example:
#weblogic.httpd.register.UniversityServlet=\
# examples.wlec.servlets.university.UniversityServlet
#weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
# Pool creation and cleanup for the University example:
#weblogic.CORBA.connectionPool.Univpool=\
# appaddrlist=//wlehost:2498,\
# failoverlist=//wlehost:2498,\
# minpoolsize=2,\
# maxpoolsize=3,\
# username=wleuser,\
# userrole=developer,\
# apppassword=wlepassword,\
# domainname=university
# WEBLOGIC FILE PROPERTIES
# Maps a volume name to a path, for client file read/write
#weblogic.io.fileSystem.[volumeName]=[fullPathName]
# WEBLOGIC JMS DEMO PROPERTIES
# CLUSTER USERS: Note that ALL JMS deployment should be done in the
# per-cluster properties file ONLY.
# You set up a JDBC connection pool if you want persistent messages
# (including durable subscriptions). To use JMS and EJBs in the same
# transaction, both must use the same JDBC connection pool. Uncomment
# the following property to use the default JDBC connection pool
# 'demo', which is defined in the Demo connection pool section of this file.
#weblogic.jms.connectionPool=demoPool
# The JMS Webshare example demonstrates how the ClientID for a
# durable subscriber is configured in the connection factory:
#weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
#weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
#weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
#weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
# The JMS trader example shows how to use JMS with an EJB. In addition
# to uncommenting the following properties, you must also set up and
# deploy the EJB example examples.ejb.basic.statelessSession.Trader in
# ejb_basic_statelessSession.jar to try out this JMS example:
#weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
#weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
#weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
#weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
# Registers the underlying servlet
#weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
# These properties are used with the ServerReceive JMS example,
# which demonstrates how to establish a JMS message consumer
# in a startup class:
#weblogic.system.startupClass.serverReceive=\
# examples.jms.startup.ServerReceive
#weblogic.system.startupArgs.serverReceive=\
# connectionFactory=javax.jms.TopicConnectionFactory,\
# topic=javax.jms.exampleTopic
# These properties are used with the PoolReceive JMS example,
# which demonstrates how to establish a pool of JMS message consumers
# in a startup class:
#weblogic.system.startupClass.poolReceive=\
# examples.jms.startup.PoolReceive
#weblogic.system.startupArgs.poolReceive=\
# connectionFactory=javax.jms.TopicConnectionFactory,\
# topic=javax.jms.exampleTopic
#weblogic.allow.create.weblogic.jms.ServerSessionPool=everyone
# WEBLOGIC RMI DEMO PROPERTIES
# CLUSTER USERS: Note that pinned RMI objects should be registered
# in the per-server properties file ONLY. All other RMI startup
# classes should be registered in the per-cluster properties file.
# Remote classes registered at startup after the pattern:
#weblogic.system.startupClass.[virtualName]=[fullPackageName]
# These examples can be compiled to see RMI in action. Uncomment to use:
#weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
#weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
#weblogic.system.startupClass.stock=examples.rmi.stock.StockServer
# WEBLOGIC EJB DEMO PROPERTIES
# CLUSTER USERS: Note that ALL EJB deployment should be done in the
# per-cluster properties file ONLY.
# See WebLogic Demo Connection Pool below for a connection pool
# to use with these examples.
# Deploys EJBeans. Uncomment the appropriate lines below and
# modify DBMS-related info and paths to match your particular installation:
# TBCN EJB PROPERTIES
weblogic.ejb.deploy=\
C:/weblogic/myserver/AccountSB.jar, \
C:/weblogic/myserver/AddressEntryDet.jar, \
C:/weblogic/myserver/AddressEntry.jar, \
C:/weblogic/myserver/Affiliate.jar, \
C:/weblogic/myserver/ContactPerson.jar, \
C:/weblogic/myserver/ContactSB.jar, \
C:/weblogic/myserver/Factory.jar, \
C:/weblogic/myserver/FactorySups.jar, \
c:/weblogic/myserver/LoginUsers.jar, \
c:/weblogic/myserver/Member.jar, \
c:/weblogic/myserver/MemberQuotaUsage.jar,\
c:/weblogic/myserver/MemberToCategory.jar,\
c:/weblogic/myserver/Organization.jar, \
c:/weblogic/myserver/Person.jar, \
c:/weblogic/myserver/QuotaType.jar,\
c:/weblogic/myserver/Registration.jar, \
c:/weblogic/myserver/TempAccounts.jar, \
c:/weblogic/myserver/TempDomain.jar, \
c:/weblogic/myserver/UserAccount.jar, \
c:/weblogic/myserver/UserRole.jar, \
c:/weblogic/myserver/BuyerProducts.jar, \
c:/weblogic/myserver/Catalog.jar, \
c:/weblogic/myserver/Categories.jar, \
c:/weblogic/myserver/CategoryToCategory.jar, \
c:/weblogic/myserver/CountryToCategory.jar, \
c:/weblogic/myserver/InvitedMember.jar, \
c:/weblogic/myserver/ProductOrigin.jar, \
c:/weblogic/myserver/ProductOtherFee.jar,\
c:/weblogic/myserver/ProductSups.jar, \
c:/weblogic/myserver/Products.jar,\
c:/weblogic/myserver/ProductToCategory.jar, \
c:/weblogic/myserver/SecondaryQcEntry.jar, \
c:/weblogic/myserver/CodeClass.jar,\
c:/weblogic/myserver/ConfirmationSB.jar, \
c:/weblogic/myserver/PurchasedPackage.jar,\
c:/weblogic/myserver/RejectReasonCode.jar, \
c:/weblogic/myserver/ServiceOrder.jar,\
c:/weblogic/myserver/ServiceOrderLog.jar,\
c:/weblogic/myserver/ServiceOrderState.jar,\
c:/weblogic/myserver/ServiceOrderType.jar,\
c:/weblogic/myserver/ServicePackageDetails.jar, \
c:/weblogic/myserver/ServicePackage.jar, \
c:/weblogic/myserver/ServicePayment.jar, \
c:/weblogic/myserver/ServiceReqSB.jar, \
c:/weblogic/myserver/TAM.jar, \
c:/weblogic/myserver/SubscriptionEB.jar, \
c:/weblogic/myserver/PostingCategoryEB.jar, \
c:/weblogic/myserver/PostingBrowsedEB.jar, \
c:/weblogic/myserver/PostingInfoEB.jar, \
c:/weblogic/myserver/TransactionLogEB.jar, \
c:/weblogic/myserver/PostingSB.jar
#weblogic.ejb.deploy=\
# d:/weblogic/myserver/ejb_basic_beanManaged.jar, \
# d:/weblogic/myserver/ejb_basic_containerManaged.jar, \
# d:/weblogic/myserver/ejb_basic_statefulSession.jar, \
# d:/weblogic/myserver/ejb_basic_statelessSession.jar, \
# d:/weblogic/myserver/ejb_extensions_finderEnumeration.jar, \
# d:/weblogic/myserver/ejb_extensions_readMostly.jar, \
# d:/weblogic/myserver/ejb_subclass.jar, \
# d:/weblogic/myserver/jolt_ejb_bankapp.jar
# Servlet used by the EJB basic beanManaged example
# Uncomment to use:
weblogic.httpd.register.beanManaged=\
examples.ejb.basic.beanManaged.Servlet
# Add a list of users (set the password with
weblogic.password.[username]=XXX)
# to set an ACL for this servlet:
#weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
#weblogic.password.user1=user1Password
#weblogic.password.user2=user2Password
# WEBLOGIC XML DEMO PROPERTIES
# These properties are required to run the XML examples.
# Uncomment to use.
# CLUSTER USERS: Note that ALL servlets should be set up
# in the per-cluster properties file ONLY.
#weblogic.httpd.register.StockServlet=examples.xml.http.StockServlet
# BizTalk example properties
#weblogic.jms.queue.tradeIncoming=biztalk.jms.tradeIncoming
#weblogic.jms.queue.tradeError=biztalk.jms.tradeError
#weblogic.httpd.register.BizTalkServer=examples.xml.biztalk.BizHttpProtocolA
dapter
#weblogic.httpd.initArgs.BizTalkServer=bizQueue=biztalk.jms.tradeIncoming
# WEBLOGIC ZAC DEMO PROPERTIES
# These registrations enable the ZAC Publish Wizard.
weblogic.zac.enable=true
# Set the publish root for a WebLogic Server. Edit and
# uncomment to use.
#weblogic.zac.publishRoot=d:/weblogic/zac
# Set an ACL for each package you publish. The [name] is
# the "Package name" you assign in the ZAC Publish Wizard.
# Publish a package, edit this property, and uncomment to use.
#weblogic.allow.read.weblogic.zac.[name]=[user list]
#weblogic.allow.write.weblogic.zac.[name]=system
# HTTPD ADMINISTRATIVE PROPERTIES
# Enables logging of HTTPD info in common log format and
# sets the log file name (default is "access.log" in "myserver")
weblogic.httpd.enableLogFile=true
weblogic.httpd.logFileName=access.log
# Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
weblogic.httpd.enableEvents=false
# Enables HTTP sessions
weblogic.httpd.session.enable=true
# Sets an optional cookie name. The default name is "WebLogicSession".
# Prior to version 4.0, the default was "TengahSession". To make
# this backward compatible with cookies generated from previous
# installations, you should set this property to "TengahSession".
# Uncomment this line and set this to any string of your choice,
# or comment out this property to use the default.
#weblogic.httpd.session.cookie.name=WebLogicSession
# MIME types
weblogic.httpd.mimeType.text/html=html,htm
weblogic.httpd.mimeType.image/gif=gif
weblogic.httpd.mimeType.image/jpeg=jpeg,jpg
weblogic.httpd.mimeType.application/pdf=pdf
weblogic.httpd.mimeType.application/zip=zip
weblogic.httpd.mimeType.application/x-java-vm=class
weblogic.httpd.mimeType.application/x-java-archive=jar
weblogic.httpd.mimeType.application/x-java-serialized-object=ser
weblogic.httpd.mimeType.application/octet-stream=exe
weblogic.httpd.mimeType.text/vnd.wap.wml=wml
weblogic.httpd.mimeType.text/vnd.wap.wmlscript=wmls
weblogic.httpd.mimeType.application/vnd.wap.wmlc=wmlc
weblogic.httpd.mimeType.application/vnd.wap.wmlscriptc=wmlsc
weblogic.httpd.mimeType.image/vnd.wap.wbmp=wbmp
# In seconds, the keep-alive for HTTP and HTTPS requests
weblogic.httpd.http.keepAliveSecs=60
weblogic.httpd.https.keepAliveSecs=120
# WEBLOGIC JDBC DRIVER PROPERTIES
# Enables JDBC driver logging and sets the file name for the log
# The weblogic.jdbc.logFile is placed in the per-server
# directory (default is "myserver")
weblogic.jdbc.enableLogFile=false
weblogic.jdbc.logFileName=jdbc.log
# WEBLOGIC JDBC CONNECTION POOL MANAGEMENT
# CLUSTER USERS: Note that ALL JDBC connection pools should be set up
# in the per-cluster properties file ONLY.
# For creating JDBC connection pools. This example shows a connection
# pool called "oraclePool" that allows 3 T3Users "guest," "joe," and "jill"
# to use 4 JDBC connections (with a potential for up to 10 connections,
# incremented by two at a time, with a delay of 1 second between each
# attempt to connect to the database), to an Oracle database server called
# "DEMO." If more than 4 connections are opened, after 15 minutes, unused
# connections are dropped from the pool until only 4 connections remain
open.
# Every 10 minutes, any unused connections in the pool are tested and
# refreshed if they are not viable.
#weblogic.jdbc.connectionPool.oraclePool=\
# url=jdbc:weblogic:oracle,\
# driver=weblogic.jdbc.oci.Driver,\
# loginDelaySecs=1,\
# initialCapacity=4,\
# maxCapacity=10,\
# capacityIncrement=2,\
# allowShrinking=true,\
# shrinkPeriodMins=15,\
# refreshMinutes=10,\
# testTable=dual,\
# props=user=SCOTT;password=tiger;server=DEMO
# Get more details on each argument for this property in the
# Administrators Guide on setting properties at:
# http://www.weblogic.com/docs51/admindocs/properties.html
# Set up ACLs for this connection pool with the following:
weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=everyone
# guest,joe,jill
#weblogic.allow.reset.weblogic.jdbc.connectionPool.oraclePool=\
# joe,jill
#weblogic.allow.shrink.weblogic.jdbc.connectionPool.oraclePool=\
# joe,jill
# This property is an ACL that specifies the users who can
# create dynamic connection pools:
#weblogic.jdbc.connectionPoolcreate.admin=joe,jill
# Read more about setting up and using connection pools in the
# developers guide for WebLogic JDBC at:
# http://www.weblogic.com/docs51/classdocs/API_jdbct3.html#T5a
# TBCN JDBC CONNECTION POOL MANAGEMENT
weblogic.jdbc.connectionPool.oraclePool=\
url=jdbc:oracle:thin:@202.109.102.151:1521:tbcn,\
driver=oracle.jdbc.driver.OracleDriver,\
loginDelaySecs=1,\
initialCapacity=2,\
maxCapacity=10,\
capacityIncrement=2,\
allowShrinking=true,\
shrinkPeriodMins=15,\
refreshMinutes=10,\
testTable=dual,\
props=user=tbcn;password=ca91768
weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=everyone
weblogic.jdbc.TXDataSource.oracleDataSource=oraclePool
weblogic.jdbc.DataSource.oracleReadOnlyDataSource=oraclePool
# WEBLOGIC DEMO CONNECTION POOL PROPERTIES
# CLUSTER USERS: Note that ALL JDBC connection pools should be set up
# in the per-cluster properties file ONLY.
# This connection pool uses the sample Cloudscape database shipped
# with WebLogic. Used by the EJBean, JHTML, JSP and JMS examples.
# Uncomment to use:
#weblogic.jdbc.connectionPool.demoPool=\
# url=jdbc:cloudscape:demo,\
# driver=COM.cloudscape.core.JDBCDriver,\
# initialCapacity=1,\
# maxCapacity=2,\
# capacityIncrement=1,\
# props=user=none;password=none;server=none
# Add a TXDataSource for the connection pool:
#weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.demoPool=demoPool
# Add an ACL for the connection pool:
#weblogic.allow.reserve.weblogic.jdbc.connectionPool.demoPool=everyone
# WEBLOGIC HTTP SERVLET PROPERTIES
# CLUSTER USERS: Note that ALL servlets should be set up
# in the per-cluster properties file ONLY.
# WebLogic offers different types of servlets for various uses.
# Classpath servlet registration
# The ClasspathServlet is used to serve classes from
# the system CLASSPATH. It is used by applets to load
# classes they depend upon, and is registered against
# the virtual name 'classes' here by default. This means
# you should set your applet codebase to "/classes".
# You can register multiple virtual names for this servlet.
# Note that it can also be used to serve other
# resources/files from the system CLASSPATH.
# Don't confuse the ClasspathServlet with the ServletServlet. The
# ClasspathServlet is used for serving classes for client-side Java only.
# The ServletServlet is used to invoke unregistered servlets.
# See the Administrators Guide "Setting up WebLogic as an HTTP server"
# http://www.weblogic.com/docs51/admindocs/http.html#classfile for more
info.
weblogic.httpd.register.classes=weblogic.servlet.ClasspathServlet
# We also set an open ACL for everyone to call the ClasspathServlet
# so that applets work without requiring further changes.
weblogic.allow.execute.weblogic.servlet.classes=everyone
# File servlet registration
# FileServlet searches below the documentRoot for the requested file
# and serves it if found. If the requested file is a directory,
# FileServlet will append the defaultFilename to the requested path
# and serve that file if found.
weblogic.httpd.register.file=weblogic.servlet.FileServlet
weblogic.httpd.initArgs.file=defaultFilename=index.html
weblogic.httpd.indexFiles=zh_TW/index.htm
# ServerSideInclude servlet registration
# SSIServlet searches below the documentRoot for the
# requested .shtml file and serves it if found.
weblogic.httpd.register.*.shtml=weblogic.servlet.ServerSideIncludeServlet
# Example URL: http://localhost:7001/portside/welcome.shtml
# for the file /weblogic/myserver/public_html/portside/welcome.shtml
# PageCompileServlet (used by JHTML)
# See the information below under WebLogic JHTML
# JSPServlet (used by JSP)
# See the information below under WebLogic JSP
# ServletServlet registration
# Allows unregistered servlets in the servlet classpath (see Servlet
# reload properties below) to be r

Problem with links in deployed ADF application to Weblogic Server 11g

Hi everyone !
I have a query here, firstly, I have created an ADF application using Jdeveloper 11g and have successfully deployed (EAR file) onto the weblogic server.
However, after testing out the application, the linking within the application does not seem to work. Whenever I click on a link or button, the page refreshes but the result is not displayed.
What could have cause the problem?
Thanks
Gavin

Are the ADF runtime libraries installed into the WebLogic server?

Problem while deploying the ADF application in weblogic 10.3

Hi,
We did the application using ADF and EJB3.0 in JDeveloper11g relese and this application is working fine when i run in the JDeveloper release. When i try to deploy the same application in weblogic 10.3(Which I downloded and installed) i am getting following error.
shared library "adf.oracle.domain" could not be found.
Can any one tell me, what the problem is?
Thanking you,
NIRANJAN REDDY.

person with many names,
You need to configure the WLS domain for ADF.
http://download.oracle.com/docs/cd/E12839_01/install.1111/e13666/toc.htm#wls_adf
John

From RFC 2068 Error while testing ADF Application in Weblogic Server

Hi All,
Created an ADF application and Deployed this application to Weblogic server.
I am getting the below error After deploy into weblogic server while running the application
I am able to run this application well in JDeveloper using the IntegratedWebLogicServer.
The Application is successfully deployed to the Web Logic server.
While creating the domain, I have extended the Oracle JRF classes.
Error
Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
JDeveloper Version : 11.1.1.3.0
Weblogic Version : 10.3.3.0
Thanks
Satish

HI John,
In The web.xml i added /faces/TestPG
This is URL in Weblogic Server
http://10.146.2.232:7001/TestDeployee-ViewController-context-root/faces/TestPG
Thanks
Sathish

Identify the end url of ADF application in Weblogic console

Hi All,
Is there a way to identify the end url of an ADF application deployed in the Weblogic server (v10.3.6) from the Weblogic console screen?
Request you to please share the steps.
Best Regards,
Ankit Gupta

No, the only thing you can do is to setup a welcome file in your web.xml. This file or files then cna be accessed through the testing tab of an application from the admin console.
Timo

How to deply ADF application on weblogic 10.3

Hello Team,
Here i created one aplpication using jdevloper 11.1.1.1.0
I have Model Part & View Controller How can i deploy aaplication on weblogic. I aslo follow the steps which are defines in the *"Fusion Developer’s Guide for Oracle Application Development Framework"* but still i am facing the problem in deployment i.e. deployment incomplete.....
1) first i created the dataSourse on weblogic
2) then i gave the dataSourse path to the Application Module
3) then i created the WAR file in viewController
4) then i create the EAR file
then i deplying application to weblogic....
Is i am going in right direction?

yes i tryed but still i uable to deploy the application....
now m facing this error....
"The task cannot be processed further until the current edit session is activated. When this occurs, task processing will continue. The user can exit the deployer tool without affecting the task."

Stuck thread in adf application with weblogic

hi every body
I am working in JDev 11.1.1.4 and weblogic 10.3.4
when I deploy my Application in my production weblogic
after some time (it does not constant it is variable) I got warnning on the server
when I check the server I got some stuck thread
any idea or notes how can I know what is the reason of these stuck threads?
is there any objects have thread unsafe issue, resource contention or race condition in ADF?
BR,
Alaa

actully I do that guys
but what I get does not have any related to my application
even those http request does not request the same page
this is the stuck thread when I dump
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=61 idx=0xe8 tid=13369 prio=1 alive, waiting, native_blocked, daemon
-- Waiting for notification on: oracle/adfinternal/controller/util/RequestLock@0x88e06b58[fat lock]
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
at jrockit/vm/Locks.wait(Locks.java:1973)[inlined]
at java/lang/Object.wait(Object.java:485)[inlined]
at oracle/adfinternal/controller/util/RequestLock.lock(RequestLock.java:42)[inlined]
at oracle/adfinternal/controller/state/RootViewPortContextImpl.lockViewPortRequestLock(RootViewPortContextImpl.java:604)[optimized]
^-- Lock released while waiting: oracle/adfinternal/controller/util/RequestLock@0x88e06b58[fat lock]
at oracle/adfinternal/controller/state/ControllerState.initializeRequest(ControllerState.java:833)[inlined]
at oracle/adfinternal/controller/state/ControllerState.initializeRequest(ControllerState.java:754)[inlined]
at oracle/adfinternal/controller/application/AdfcConfigurator.beginRequest(AdfcConfigurator.java:50)[optimized]
at org/apache/myfaces/trinidadinternal/config/GlobalConfiguratorImpl._startConfiguratorServiceRequest(GlobalConfiguratorImpl.java:562)[inlined]
at org/apache/myfaces/trinidadinternal/config/GlobalConfiguratorImpl.beginRequest(GlobalConfiguratorImpl.java:212)[optimized]
at org/apache/myfaces/trinidadinternal/webapp/TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:155)[optimized]
at org/apache/myfaces/trinidad/webapp/TrinidadFilter.doFilter(TrinidadFilter.java:92)[optimized]
at weblogic/servlet/internal/FilterChainImpl.doFilter(FilterChainImpl.java:56)[optimized]
at oracle/adf/library/webapp/LibraryFilter.doFilter(LibraryFilter.java:175)[optimized]
at weblogic/servlet/internal/FilterChainImpl.doFilter(FilterChainImpl.java:56)[optimized]
at oracle/security/jps/ee/http/JpsAbsFilter$1.run(JpsAbsFilter.java:111)[optimized]
at jrockit/vm/AccessController.doPrivileged(AccessController.java:254)[inlined]
at oracle/security/jps/util/JpsSubject.doAsPrivileged(JpsSubject.java:313)[inlined]
at oracle/security/jps/ee/util/JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)[inlined]
at oracle/security/jps/ee/http/JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)[inlined]
at oracle/security/jps/ee/http/JpsAbsFilter.doFilter(JpsAbsFilter.java:161)[optimized]
at oracle/security/jps/ee/http/JpsFilter.doFilter(JpsFilter.java:71)[optimized]
at weblogic/servlet/internal/FilterChainImpl.doFilter(FilterChainImpl.java:56)[optimized]
at oracle/dms/servlet/DMSServletFilter.doFilter(DMSServletFilter.java:136)[optimized]
at weblogic/servlet/internal/FilterChainImpl.doFilter(FilterChainImpl.java:56)[optimized]
at weblogic/servlet/internal/RequestEventsFilter.doFilter(RequestEventsFilter.java:27)[optimized]
at weblogic/servlet/internal/FilterChainImpl.doFilter(FilterChainImpl.java:56)[inlined]
at weblogic/servlet/internal/WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)[inlined]
at weblogic/servlet/internal/WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)[optimized]
at weblogic/security/acl/internal/AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)[optimized]
at weblogic/security/service/SecurityManager.runAs(SecurityManager.java:120)[inlined]
at weblogic/servlet/internal/WebAppServletContext.securedExecute(WebAppServletContext.java:2277)[inlined]
at weblogic/servlet/internal/WebAppServletContext.execute(WebAppServletContext.java:2183)[optimized]
at weblogic/servlet/internal/ServletRequestImpl.run(ServletRequestImpl.java:1454)[optimized]
at weblogic/work/ExecuteThread.execute(ExecuteThread.java:207)[optimized]
at weblogic/work/ExecuteThread.run(ExecuteThread.java:176)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
any another ideas?
BR,
Alaa

Deploy Jdeveloper 11.1.2 ADF Application on weblogic 10.3.5 ???

I don't want to install ADR on my weblogic. how to create ear file having all the required adf jar and war files in it?
what is recommended installing ADR on production weblogic server or having ear file containing required war and jar files and why?

Then how would we deploy jdeveloper 11.1.2 application on jBoss?You wouldn't, at least if you want a supported configuration. Right now, WLS and IBM WebSphere are the only ones supported, and yes, you do install the ADR on WebSphere. If you want to try to get it working on JBoss, you can fuss around with JAR files in the classpath, but it's not going to be supported.
John

Change security of adf application on weblogic

Similar Messages

Maybe you are looking for