JDeveloper Integrated WLS Language

Hi,
I'm using JDeveloper/ADF 11.1.1.1.0 on Vista (Installed in German). There are some applications, such as Jdeveloper that I use in english. JDeveloper installs and runs in English fine, but the integrated WLS server that it sets up in my profile dir picks up my German environment. The WLS error messages (and many of the components in the deployed app) therefore are in German. Is there any way (other than changing my system environment, which I don't want to do) to tell the Integrated WLS to run in English?
Thanks in advance.
Barry
Edited by: cafelatte on Aug 18, 2009 4:37 PM

Shame it's not a config option somewhere in JDev, but that worked, thank you :-)
Edit: just for anyone else, I needed to edit:
C:\Users\<my-user-name>\AppData\Roaming\JDeveloper\system11.1.1.1.33.54.07\DefaultDomain\bin\setDomainEnv.cmd
and added
-Duser.language=en
to the end of the properties declaration, like so:
set JAVA_PROPERTIES=-Dplatform.home=%WL_HOME% -Dwls.home=%WLS_HOME% -Dweblogic.home=%WLS_HOME% -Duser.language=en
Edited by: cafelatte on Aug 19, 2009 2:19 PM

Similar Messages

JDeveloper Integrated WLS startup error preventing local tests

Hello,
I'm getting the following error while trying to start the IWLS:
Messages:*
[Starting Server Instance IntegratedWebLogicServer]
#### Server Instance IntegratedWebLogicServer could not be started: Server Instance was terminated.
Running: IntegratedWebLogicServer*
*** Using port 7101 ***
C:\Users\jpatters\AppData\Roaming\JDeveloper\system11.1.1.5.37.60.13\DefaultDomain\bin\startWebLogic.cmd
[waiting for the server to complete its initialization...]
\QuickTime\QTSystem\QTJava.zip was unexpected at this time.
Process exited.
Any idea how to fix this?
Thx,
S

Check your environment for variables. If you have a CLASSPATH variable. If yes, check if you find the QTJava.zip on it. Remove it and start again.
Timo

Problem using integrated WLS in jDeveloper 11.1.2.1.0

Hey there,
I got a problem using the integrated WLS from the jDeveloper 11.1.2.1.0.
After trying to deploy an ADF Web Application on the integrated WLS, I get the following log message:
LOG
+[Waiting for the domain to finish building...]+
+[11:26:04 AM] Creating Integrated Weblogic domain...+
+[11:28:13 AM] Extending Integrated Weblogic domain...+
+[11:30:06 AM] Integrated Weblogic domain processing completed successfully.+
*** Using HTTP port 7101 ***
*** Using SSL port 7102 ***
+/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/bin/startWebLogic.sh+
+[waiting for the server to complete its initialization...]+
+.+
+.+
JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m
+.+
WLS Start Mode=Development
+.+
CLASSPATH=/home/robin/bin/wls/oracle_common/modules/oracle.jdbc_11.1.1/ojdbc6dms.jar:/home/robin/bin/wls/patch_wls1211/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/robin/bin/wls/patch_oepe100/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/robin/bin/wls/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/robin/bin/wls/jdk160_29/lib/tools.jar:/home/robin/bin/wls/wlserver_12.1/server/lib/weblogic_sp.jar:/home/robin/bin/wls/wlserver_12.1/server/lib/weblogic.jar:/home/robin/bin/wls/modules/features/weblogic.server.modules_12.1.1.0.jar:/home/robin/bin/wls/wlserver_12.1/server/lib/webservices.jar:/home/robin/bin/wls/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/home/robin/bin/wls/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/home/robin/bin/wls/oracle_common/modules/oracle.jrf_11.1.1/jrf.jar:/home/robin/bin/wls/wlserver_12.1/common/derby/lib/derbyclient.jar:/home/robin/bin/wls/wlserver_12.1/server/lib/xqrl.jar
+.+
PATH=/home/robin/bin/wls/wlserver_12.1/server/bin:/home/robin/bin/wls/modules/org.apache.ant_1.7.1/bin:/home/robin/bin/wls/jdk160_29/jre/bin:/home/robin/bin/wls/jdk160_29/bin:/usr/local/bin:/usr/bin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.5.3:/usr/games/bin
+.+
+* To start WebLogic Server, use a username and   *+
+* password assigned to an admin-level user. For *+
+* server administration, use the WebLogic Server *+
+* console at http://hostname:port/console        *+
starting weblogic with Java version:
java version "1.6.0_29"
Java(TM) SE Runtime Environment (build 1.6.0_29-b11)
Java HotSpot(TM) Client VM (build 20.4-b02, mixed mode)
Starting WLS with line:
+/home/robin/bin/wls/jdk160_29/bin/java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=DefaultServer -Djava.security.policy=/home/robin/bin/wls/wlserver_12.1/server/lib/weblogic.policy -Djavax.net.ssl.trustStore=/tmp/trustStore7618453572230021232.jks -Dhttp.proxyHost=emea-proxy.uk.oracle.com -Dhttp.proxyPort=80 -Dhttp.nonProxyHosts=localhost|localhost.localdomain|127.0.0.1|::1|MUELLER-BADY-GENTOO|MUELLER-BADY-GENTOO -Dhttps.proxyHost=emea-proxy.uk.oracle.com -Dhttps.proxyPort=80 -Doracle.jdeveloper.adrs=true -Dweblogic.nodemanager.ServiceEnabled=true -Xverify:none -Djava.endorsed.dirs=/home/robin/bin/wls/jdk160_29/jre/lib/endorsed:/home/robin/bin/wls/wlserver_12.1/endorsed -da -Dplatform.home=/home/robin/bin/wls/wlserver_12.1 -Dwls.home=/home/robin/bin/wls/wlserver_12.1/server -Dweblogic.home=/home/robin/bin/wls/wlserver_12.1/server -Djps.app.credential.overwrite.allowed=true -Dcommon.components.home=/home/robin/bin/wls/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain -Djrockit.optfile=/home/robin/bin/wls/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.server.config.dir=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/config/fmwconfig/servers/DefaultServer -Doracle.domain.config.dir=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/config/fmwconfig -Digf.arisidbeans.carmlloc=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/config/fmwconfig/carml -Digf.arisidstack.home=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/config/fmwconfig/arisidprovider -Doracle.security.jps.config=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/config/fmwconfig/jps-config.xml -Doracle.deployed.app.dir=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/servers/DefaultServer/tmp/_WL_user -Doracle.deployed.app.ext=/- -Dweblogic.alternateTypesDirectory=/home/robin/bin/wls/oracle_common/modules/oracle.ossoiap_11.1.1,/home/robin/bin/wls/oracle_common/modules/oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dwsm.repository.path=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/oracle/store/gmds -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/home/robin/bin/wls/patch_wls1211/profiles/default/sysext_manifest_classpath:/home/robin/bin/wls/patch_oepe100/profiles/default/sysext_manifest_classpath:/home/robin/bin/wls/patch_ocp371/profiles/default/sysext_manifest_classpath weblogic.Server+
+<Feb 10, 2012 11:30:09 AM CET> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>+
+<Feb 10, 2012 11:30:10 AM CET> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>+
+<Feb 10, 2012 11:30:11 AM CET> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 20.4-b02 from Sun Microsystems Inc..>+
+<Feb 10, 2012 11:30:12 AM CET> <Info> <Management> <BEA-141107> <Version: WebLogic Server 12.1.1.0 Wed Dec 7 08:40:57 PST 2011 1445491 >+
+<Feb 10, 2012 11:30:15 AM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING.>+
+<Feb 10, 2012 11:30:15 AM CET> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool.>+
+<Feb 10, 2012 11:30:15 AM CET> <Notice> <Log Management> <BEA-170019> <The server log file /home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/servers/DefaultServer/logs/DefaultServer.log is opened. All server side log events will be written to this file.>+
Feb 10, 2012 11:30:24 AM oracle.security.jps.internal.keystore.file.FileKeyStoreManager saveKeyStore
WARNING: Failed to save farm keystore. Reason {0}
Feb 10, 2012 11:30:24 AM oracle.security.jps.internal.keystore.file.FileKeyStoreManager createKeyStore
WARNING: Failed to save farm keystore. Reason {0}
oracle.security.jps.service.keystore.KeyStoreServiceException: JPS-06513: Failed to save farm keystore. Reason
+     at oracle.security.jps.internal.keystore.file.FileKeyStoreManager.createKeyStore(FileKeyStoreManager.java:309)+
+     at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.doInit(FileKeyStoreServiceImpl.java:95)+
+     at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<init>(FileKeyStoreServiceImpl.java:73)+
+     at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<init>(FileKeyStoreServiceImpl.java:63)+
+     at oracle.security.jps.internal.keystore.KeyStoreProvider.getInstance(KeyStoreProvider.java:157)+
+     at oracle.security.jps.internal.keystore.KeyStoreProvider.getInstance(KeyStoreProvider.java:64)+
+     at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.findServiceInstance(ContextFactoryImpl.java:139)+
+     at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:170)+
+     at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:191)+
+     at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:132)+
+     at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:127)+
+     at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:850)+
+     at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:844)+
+     at java.security.AccessController.doPrivileged(Native Method)+
+     at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:844)+
+     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:291)+
+     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:284)+
+     at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:270)+
+     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)+
+     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)+
+     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)+
+     at java.lang.reflect.Constructor.newInstance(Constructor.java:513)+
+     at java.lang.Class.newInstance0(Class.java:355)+
+     at java.lang.Class.newInstance(Class.java:308)+
+     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1343)+
+     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1022)+
+     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)+
+     at weblogic.security.SecurityService.start(SecurityService.java:148)+
+     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)+
+     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)+
+     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)+
+<Feb 10, 2012 11:30:24 AM CET> <Error> <Security> <BEA-090892> <The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider>+
+<Feb 10, 2012 11:30:24 AM CET> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider+
+weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider+
+     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1402)+
+     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1022)+
+     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)+
+     at weblogic.security.SecurityService.start(SecurityService.java:148)+
+     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)+
+     Truncated. see log file for complete stacktrace+
+Caused By: oracle.security.jps.JpsRuntimeException: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider+
+     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:293)+
+     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:284)+
+     at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:270)+
+     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)+
+     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)+
+     Truncated. see log file for complete stacktrace+
+Caused By: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider+
+     at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:899)+
+     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:291)+
+     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:284)+
+     at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:270)+
+     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)+
+     Truncated. see log file for complete stacktrace+
+Caused By: java.security.PrivilegedActionException: oracle.security.jps.JpsException: [PolicyUtil] Unable to obtain default JPS Context!+
+     at java.security.AccessController.doPrivileged(Native Method)+
+     at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:844)+
+     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:291)+
+     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:284)+
+     at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:270)+
+     Truncated. see log file for complete stacktrace+
+Caused By: oracle.security.jps.JpsException: [PolicyUtil] Unable to obtain default JPS Context!+
+     at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:860)+
+     at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:844)+
+     at java.security.AccessController.doPrivileged(Native Method)+
+     at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:844)+
+     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:291)+
+     Truncated. see log file for complete stacktrace+
Caused By: oracle.security.jps.service.keystore.KeyStoreServiceException: JPS-06513: Failed to save farm keystore. Reason
+     at oracle.security.jps.internal.keystore.file.FileKeyStoreManager.createKeyStore(FileKeyStoreManager.java:309)+
+     at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.doInit(FileKeyStoreServiceImpl.java:95)+
+     at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<init>(FileKeyStoreServiceImpl.java:73)+
+     at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<init>(FileKeyStoreServiceImpl.java:63)+
+     at oracle.security.jps.internal.keystore.KeyStoreProvider.getInstance(KeyStoreProvider.java:157)+
+     Truncated. see log file for complete stacktrace+
+>+
+<Feb 10, 2012 11:30:24 AM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED.>+
+<Feb 10, 2012 11:30:24 AM CET> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down.>+
+<Feb 10, 2012 11:30:24 AM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN.>+
Process exited.
*/LOG*
After that, I tried setting permissions for the cwallet.sso file to ugo+rwx, but this leads to the same problems as mentioned above.
My second try was to setup an external WLS 12c, but it seems to be not yet possible to connect to a WLS 12c from within jDeveloper.
Do you have any ideas ?
Thank you in advance for your help.
Regards,
Robin

After debugging the WLS Initialisation with jdb, I recognized that there was some trouble with dependent libraries.
In the end, I solved my problem by using another OS (Ubuntu 11.10) for development. There, the WLS works out of the box, even with 64-Bit libraries.
Thank you for your help.
Regards,
Robin

Installing SOA Suite on the integrated WLS in JDeveloper

Hi,
I'm wondering if it's possible to install SOA suite on the integrated WebLogic provided with JDeveloper?
If it is not possible, what is the recommended way for provisioning for development? Is it to install a full-blown WebLogic & SOA Suite on each developers' machine?

Hi Mark,
No, it is not possible to install SOA on the integrated WLS in JDeveloper. There are some technical issues preventing it now but we would like to get this working in the future.
So yes, you can install the full WLS + SOA on your own machine for development. After you install, go into WLS and turn off whatever you are not using to shrink the footprint (e.g., you don't need both soa composer and bpm composer, you don't need both worklist and workspace).
Heidi.

Re: Error Starting In Integrated WLS 11.1.1.3

I was creating a pick list while some internal IDE Level appeared.
I ignored & was doing my job but it started continuously to appear.
I thought this as IntegratedWLS domain problem & removed the instance from local directory.
But again Integrated WLS is giving error in creating domian. Jdev 11.1.1.3.
Please note, from few days these warning were coming in Log Window
CreateFileandSetSecurity failed with FALSE (Expected on FAT Partitions) GLE: 3
CreateFileandSetSecurity failed with TRUE (not expected) GLE: 3Error Log File-
Log File:      C:\Users\ral\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60\o.j2ee.adrs\CreateDefaultDomain.log
Label:         JDEVADF_11.1.1.3.PS2_GENERIC_100408.2356.5660
Product Home: C:\Oracle\Middleware11g\jdeveloper\jdev\
Domain:        C:\Users\ral\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60\DefaultDomain
"C:\Oracle\Middleware11g\oracle_common\common\bin\wlst.cmd" "C:\Users\ral\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60\o.j2ee.adrs\CreateDefaultDomain.py"
Process started
wlst > CreateFileandSetSecurity failed with FALSE (Expected on FAT Partitions) GLE: 3
wlst > CreateFileandSetSecurity failed with TRUE (not expected) GLE: 3
wlst >
wlst > CLASSPATH=C:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\JDK160~1\lib\tools.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;C:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules_10.3.3.0.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.1/lib/ant-all.jar;C:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.jrf_11.1.1/jrf-api.jar;C:\Oracle\MIDDLE~1\ORACLE~1/common/wlst/resources/jrf-wlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.odl_11.1.1/ojdl.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.odl_11.1.1/ojdl2.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.dms_11.1.1/dms.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.dconfig-infra_11.1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.fabriccommon_11.1.1/fabric-common.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.xdk_11.1.0/xmlparserv2.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.xdk_11.1.0/xml.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.wsm.common_11.1.1/wsm-pmlib.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.wsm.common_11.1.1/wsm-policy-core.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.wsm.common_11.1.1/wsm-secpol.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.wsm.common_11.1.1/wsm-dependencies.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.wsm.policies_11.1.1/wsm-seed-policies.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.webservices_11.1.1/orawsdl.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.webservices_11.1.1/mdds.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.webservices_11.1.1/ws_confmbeans.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/org.apache.commons.digester_1.8.jar;C:\Oracle\MIDDLE~1\ORACLE~1/../modules/javax.xml.bind_2.1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1/../modules/javax.activation_1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1/../modules/javax.xml.stream_1.1.1.0.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.http_client_11.1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.jmx_11.1.1/jmxframework.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.jmx_11.1.1/jmxspi.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.adf.dconfigbeans_11.1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.adf.share.ca_11.1.1/adf-share-base.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.adf.share.ca_11.1.1/adf-share-ca.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.adf.share_11.1.1/adflogginghandler.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.adf.share_11.1.1/adfsharembean.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.adf.share_11.1.1/commons-el.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.adf.share_11.1.1/jsp-el-api.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.adf.share_11.1.1/oracle-el.jar;C:\Oracle\MIDDLE~1\ORACLE~1/common/wlst/resources/auditwlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1/common/wlst/resources/sslconfigwlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1/common/wlst/resources/oamap_help.jar;C:\Oracle\MIDDLE~1\ORACLE~1/common/wlst/resources/ossoiap_help.jar;C:\Oracle\MIDDLE~1\ORACLE~1/common/wlst/resources/jps-wlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.auditprovider_11.1.1/jps-wls-auditprovider.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.jps_11.1.1/jps-manifest.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.jps_11.1.1/jps-mbeans.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.jps_11.1.1/jps-upgrade.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.jps_11.1.1/jps-patching.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\lib\ADF-SH~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\lib\mdswlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\AUDITW~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\jps-wlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\jrf-wlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\OAMAP_~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\OAMAUT~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\ossoiap.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\OSSOIA~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\SSLCON~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\wsm-wlst.jar
wlst >
wlst > PATH=C:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\native;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\native;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\bin;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.1\bin;C:\Oracle\MIDDLE~1\JDK160~1\jre\bin;C:\Oracle\MIDDLE~1\JDK160~1\bin;;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32\oci920_8
wlst >
wlst > Your environment has been set.
wlst >
wlst > CLASSPATH=C:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\JDK160~1\lib\tools.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;C:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules_10.3.3.0.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.1/lib/ant-all.jar;C:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.jrf_11.1.1/jrf-api.jar;C:\Oracle\MIDDLE~1\ORACLE~1/common/wlst/resources/jrf-wlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.odl_11.1.1/ojdl.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.odl_11.1.1/ojdl2.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.dms_11.1.1/dms.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.dconfig-infra_11.1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.fabriccommon_11.1.1/fabric-common.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.xdk_11.1.0/xmlparserv2.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.xdk_11.1.0/xml.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.wsm.common_11.1.1/wsm-pmlib.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.wsm.common_11.1.1/wsm-policy-core.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.wsm.common_11.1.1/wsm-secpol.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.wsm.common_11.1.1/wsm-dependencies.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.wsm.policies_11.1.1/wsm-seed-policies.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.webservices_11.1.1/orawsdl.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.webservices_11.1.1/mdds.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.webservices_11.1.1/ws_confmbeans.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/org.apache.commons.digester_1.8.jar;C:\Oracle\MIDDLE~1\ORACLE~1/../modules/javax.xml.bind_2.1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1/../modules/javax.activation_1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1/../modules/javax.xml.stream_1.1.1.0.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.http_client_11.1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.jmx_11.1.1/jmxframework.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.jmx_11.1.1/jmxspi.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.adf.dconfigbeans_11.1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.adf.share.ca_11.1.1/adf-share-base.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.adf.share.ca_11.1.1/adf-share-ca.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.adf.share_11.1.1/adflogginghandler.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.adf.share_11.1.1/adfsharembean.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.adf.share_11.1.1/commons-el.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.adf.share_11.1.1/jsp-el-api.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.adf.share_11.1.1/oracle-el.jar;C:\Oracle\MIDDLE~1\ORACLE~1/common/wlst/resources/auditwlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1/common/wlst/resources/sslconfigwlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1/common/wlst/resources/oamap_help.jar;C:\Oracle\MIDDLE~1\ORACLE~1/common/wlst/resources/ossoiap_help.jar;C:\Oracle\MIDDLE~1\ORACLE~1/common/wlst/resources/jps-wlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.auditprovider_11.1.1/jps-wls-auditprovider.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.jps_11.1.1/jps-manifest.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.jps_11.1.1/jps-mbeans.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.jps_11.1.1/jps-upgrade.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.jps_11.1.1/jps-patching.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\lib\ADF-SH~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\lib\mdswlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\AUDITW~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\jps-wlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\jrf-wlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\OAMAP_~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\OAMAUT~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\ossoiap.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\OSSOIA~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\SSLCON~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\wsm-wlst.jar;C:\Oracle\MIDDLE~1\utils\config\10.3\config-launch.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\derby\lib\derbynet.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\derby\lib\derbyclient.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\derby\lib\derbytools.jar;;
wlst > CreateFileandSetSecurity failed with FALSE (Expected on FAT Partitions) GLE: 3
wlst > CreateFileandSetSecurity failed with TRUE (not expected) GLE: 3
wlst >
wlst > Initializing WebLogic Scripting Tool (WLST) ...
wlst >
wlst > Welcome to WebLogic Server Administration Scripting Shell
wlst >
wlst > Type help() for help on available commands
wlst >
wlst > Failed to get environment, getEnv command (set) did not print environment as key=value lines.
wlst > Output=CreateFileandSetSecurity failed with FALSE (Expected on FAT Partitions) GLE: 3
wlst > CreateFileandSetSecurity failed with TRUE (not expected) GLE: 3
wlst > ADRS_DOMAIN_PASSWORD=weblogic1
wlst > ANT_CONTRIB=C:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1
wlst > ANT_HOME=C:\Oracle\MIDDLE~1\modules\ORGAPA~1.1
wlst > BEA_HOME=C:\Oracle\MIDDLE~1
wlst > CLASSPATH=C:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\JDK160~1\lib\tools.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;C:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules_10.3.3.0.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.1/lib/ant-all.jar;C:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.jrf_11.1.1/jrf-api.jar;C:\Oracle\MIDDLE~1\ORACLE~1/common/wlst/resources/jrf-wlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.odl_11.1.1/ojdl.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.odl_11.1.1/ojdl2.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.dms_11.1.1/dms.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.dconfig-infra_11.1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.fabriccommon_11.1.1/fabric-common.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.xdk_11.1.0/xmlparserv2.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.xdk_11.1.0/xml.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.wsm.common_11.1.1/wsm-pmlib.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.wsm.common_11.1.1/wsm-policy-core.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.wsm.common_11.1.1/wsm-secpol.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.wsm.common_11.1.1/wsm-dependencies.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.wsm.policies_11.1.1/wsm-seed-policies.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.webservices_11.1.1/orawsdl.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.webservices_11.1.1/mdds.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.webservices_11.1.1/ws_confmbeans.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/org.apache.commons.digester_1.8.jar;C:\Oracle\MIDDLE~1\ORACLE~1/../modules/javax.xml.bind_2.1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1/../modules/javax.activation_1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1/../modules/javax.xml.stream_1.1.1.0.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.http_client_11.1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.jmx_11.1.1/jmxframework.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.jmx_11.1.1/jmxspi.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.adf.dconfigbeans_11.1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.adf.share.ca_11.1.1/adf-share-base.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.adf.share.ca_11.1.1/adf-share-ca.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.adf.share_11.1.1/adflogginghandler.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.adf.share_11.1.1/adfsharembean.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.adf.share_11.1.1/commons-el.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.adf.share_11.1.1/jsp-el-api.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.adf.share_11.1.1/oracle-el.jar;C:\Oracle\MIDDLE~1\ORACLE~1/common/wlst/resources/auditwlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1/common/wlst/resources/sslconfigwlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1/common/wlst/resources/oamap_help.jar;C:\Oracle\MIDDLE~1\ORACLE~1/common/wlst/resources/ossoiap_help.jar;C:\Oracle\MIDDLE~1\ORACLE~1/common/wlst/resources/jps-wlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.auditprovider_11.1.1/jps-wls-auditprovider.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.jps_11.1.1/jps-manifest.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.jps_11.1.1/jps-mbeans.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.jps_11.1.1/jps-upgrade.jar;C:\Oracle\MIDDLE~1\ORACLE~1/modules/oracle.jps_11.1.1/jps-patching.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\lib\ADF-SH~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\lib\mdswlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\AUDITW~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\jps-wlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\jrf-wlst.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\OAMAP_~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\OAMAUT~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\ossoiap.jar;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\OSSOIA~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\SSLCON~1.JAR;C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\wsm-wlst.jar;C:\Oracle\MIDDLE~1\utils\config\10.3\config-launch.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\derby\lib\derbynet.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\derby\lib\derbyclient.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\derby\lib\derbytools.jar;;
wlst > COMMON_COMPONENTS_HOME=C:\Oracle\MIDDLE~1\ORACLE~1
wlst > COMMON_WLST_HOME=C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst
wlst > COMSPEC=C:\Windows\system32\cmd.exe
wlst > CURRENT_HOME=C:\Oracle\MIDDLE~1\ORACLE~1
wlst > DELEGATE_ORACLE_HOME=C:\Oracle\MIDDLE~1\ORACLE~1
wlst > DERBY_CLASSPATH=C:\Oracle\MIDDLE~1\WLSERV~1.3\common\derby\lib\derbynet.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\derby\lib\derbyclient.jar
wlst > DERBY_CLIENT_CLASSPATH=C:\Oracle\MIDDLE~1\WLSERV~1.3\common\derby\lib\derbyclient.jar
wlst > DERBY_HOME=C:\Oracle\MIDDLE~1\WLSERV~1.3\common\derby
wlst > DERBY_OPTS="-Dderby.system.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\common\derby\demo\databases"
wlst > DERBY_SYSTEM_HOME=C:\Oracle\MIDDLE~1\WLSERV~1.3\common\derby\demo\databases
wlst > DERBY_TOOLS=C:\Oracle\MIDDLE~1\WLSERV~1.3\common\derby\lib\derbytools.jar
wlst > FEATURES_DIR=C:\Oracle\MIDDLE~1\modules\features
wlst > FMWCONFIG_CLASSPATH=C:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\JDK160~1\lib\tools.jar;C:\Oracle\MIDDLE~1\utils\config\10.3\config-launch.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;C:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules_10.3.3.0.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.1/lib/ant-all.jar;C:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar
wlst > FMWLAUNCH_CLASSPATH=C:\Oracle\MIDDLE~1\utils\config\10.3\config-launch.jar
wlst > JAVA_HOME=C:\Oracle\MIDDLE~1\JDK160~1
wlst > JAVA_OPTIONS= -Xverify:none
wlst > JAVA_USE_64BIT=false
wlst > JAVA_VENDOR=Sun
wlst > JAVA_VM=-client
wlst > JDEV1111_PATCH_CLASSPATH=C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sys_manifest_classpath\weblogic_patch.jar
wlst > JDEV1111_PATCH_EXT_DIR=C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sysext_manifest_classpath
wlst > JDEV1111_PATCH_LIBPATH=C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\native
wlst > JDEV1111_PATCH_PATH=C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\native
wlst > JVM_ARGS=-Dprod.props.file="C:\Oracle\MIDDLE~1\WLSERV~1.3\.product.properties" -Dweblogic.wlstHome=C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst; -DORACLE_HOME=C:\Oracle\MIDDLE~1\ORACLE~1 -DCOMMON_COMPONENTS_HOME=C:\Oracle\MIDDLE~1\ORACLE~1 -Xms32m -Xmx200m -XX:MaxPermSize=128m -XX:+UseSpinning
wlst > MEM_ARGS=-Xms32m -Xmx200m -XX:MaxPermSize=128m -XX:+UseSpinning
wlst > MODULES_DIR=C:\Oracle\MIDDLE~1\modules
wlst > MW_HOME=C:\Oracle\MIDDLE~1
wlst > ORACLE_HOME=C:\Oracle\MIDDLE~1\ORACLE~1
wlst > PATCH_CLASSPATH=C:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sys_manifest_classpath\weblogic_patch.jar
wlst > PATCH_LIBPATH=C:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\native;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\native
wlst > PATCH_PATH=C:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\native;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\native
wlst > PATH=C:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\native;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\native;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\bin;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.1\bin;C:\Oracle\MIDDLE~1\JDK160~1\jre\bin;C:\Oracle\MIDDLE~1\JDK160~1\bin;;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32\oci920_8
wlst > PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.JS;.WS;.MSC
wlst > PROMPT=$P$G
wlst > SCRIPTPATH=C:\Oracle\MIDDLE~1\ORACLE~1\common\bin\
wlst > TEMP=C:\Users\ral\AppData\Local\Temp
wlst > TMP=C:\Users\ral\AppData\Local\Temp
wlst > WEBLOGIC_CLASSPATH=C:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\JDK160~1\lib\tools.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;C:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules_10.3.3.0.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.1/lib/ant-all.jar;C:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar
wlst > WEBLOGIC_EXTENSION_DIRS=C:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sysext_manifest_classpath
wlst > WLS1033_PATCH_CLASSPATH=C:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\sys_manifest_classpath\weblogic_patch.jar
wlst > WLS1033_PATCH_EXT_DIR=C:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\sysext_manifest_classpath
wlst > WLS1033_PATCH_LIBPATH=C:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\native
wlst > WLS1033_PATCH_PATH=C:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\native
wlst > WLST_HOME=C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst;
wlst > WLST_PROPERTIES=-Dweblogic.wlstHome=C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst; -DORACLE_HOME=C:\Oracle\MIDDLE~1\ORACLE~1 -DCOMMON_COMPONENTS_HOME=C:\Oracle\MIDDLE~1\ORACLE~1
wlst > WLST_SCRIPT=C:\Oracle\MIDDLE~1\WLSERV~1.3\common\bin\wlst.cmd
wlst > WLS_VER=10.3
wlst > WL_HOME=C:\Oracle\MIDDLE~1\WLSERV~1.3
wlst > WL_USE_AMD64DLL=false
wlst > WL_USE_IA64DLL=false
wlst > WL_USE_X86DLL=true
wlst > Error: ADRS_DOMAIN_PASSWORD environment variable not set.
wlst >
wlst >
wlst > Exiting WebLogic Scripting Tool.
wlst >
Elapsed time: 8137 ms

Looks like your configuration is messed up big.
Try this:
1) stop jdev
2) rename the folder C:\Users\ral\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60 to C:\Users\ral\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60_corrupt
3) start jdev and answer no if you are asked if you like to migrate this will create a fresh configuration
4) test your app with the new created configuration
If this works you have two possible ways to go on:
a) leave everything as is but keep in mind that any changes to jdev properties like style changes are gone
b) again start by 1), but this time migrate your settings from the renamed system folder C:\Users\ral\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60_corrupt
I only use b) if I have many settings changes from the default settings. Sometimes you migrate the error back in this way and have to use ea) anyway.
Timo

How to install Enterprise Manager to JDeveloper integrated Weblogic domain

I have installed JDeveloper 11g and as you know it also installs an embedded Weblogic and creates a Weblogic domain. This domain by default has the console application but does not have the em application. How can I add em to my integrated Weblogic?

Sturla,
I can give you the quick steps for installing EM into the WLS container integrated with JDev:
1). Download from OTN two pieces of software from the Fusion Middleware 11g (use the "For Deployment" software, click "See All"): the Application Development Runtime, and (under Additional Required Software) the Repository Creation Utility (RCU).
2). Unzip the RCU and run bin/rcu.bat or bin/rcu (windows/*nix). Create the MDS repository in an Oracle DB using this utility.
3). Install the application development runtime into the same home you installed JDeveloper.
4). Run the configuration wizard - on Windows its in the start menu / Oracle Fusion Middleware 11.1.1.1.0 / Weblogic Server 11gR1 / Tools. Find it yourself on *nix ;)
5). Choose to extend a domain
6). Pick your DefaultDomain directory for the integrated WLS
7). Tick the checkbox to add enterprise manager
8). Supply the database connection information for the DB in which you created the repository in step 2.
Ta-da!
The EM will be accessible via http://hostname:7001/em, username/password=weblogic/weblogic1. I will caution you about generically installing into the integrated domain - it makes your WLS take noticeably longer to start up...
Best,
John

Integrated WLS version 10.3.3.0

I just downloaded JDeveloper 11g Release 1, and I am trying to run a sample Struts 1 application, MailReader.
I started the integrated WLS, and surfed to http://localhost:7101/console.
I was presented with the login page, and I cannot log in.
I have tried weblogic/weblogic, weblogic/weblogic1, weblogic/welcome, weblogic/welcome1
Any other I should try?

weblogic/weblogic1 worked, but I had to stop/start the server

Works fine with Integrated WLS, NPE when deployed

I have an application that runs fine on my Integrated WLS.
But, when I deploy it to our production environment, I get a Null Point Exception.
        DCBindingContainer bc =
            (DCBindingContainer)BindingContext.getCurrent().getCurrentBindingsEntry();
        DCIteratorBinding sItr = bc.findIteratorBinding("Empmaster1Iterator");
        Row currentRow = sItr.getCurrentRow();
        String fName = (String)currentRow.getAttribute("FirstName");Curiously, the NPE occurs on the VERY first retrieval of data from the database (the same database I am using in Integrated WLS).
The NPE occurs on the last line in the above code snippet.
Can anyone point me in the correct direction to troubleshoot this?
JDeveloper:
Studio Edition Version 11.1.1.6.0
Weblogic 10.3
production environ:
WebLogic Server Version: 10.3.6.0
Thanks,
Arie

Arie,
as you got a NPE at
String fName = (String)currentRow.getAttribute("FirstName");means that at the time you run this code there is no current row defined for the 'Empmaster1Iterator'.
The question now is why don't you have a current row?
One reason can be that the iterator simply doesn't have a row. With the information provided we can only guess. However, you should check if you get a row before using the row. If you get null you have to decide what to do,
Timo

Cant start integrated wls on windows 7

I have a new machine with Windows 7 on it. We were successfully developing with jdev 11.1.1.2.0 on our old xp machines. I ran the jdev installer for 11.1.1.2.0 and things seemed to install just fine. However, when I try to Start the integrated wls for the very first time, I get the following in the console:
[Waiting for the domain to finish building...]
[02:32:29 PM] Creating Integrated Weblogic domain...
[02:33:29 PM] Extending Integrated Weblogic domain...
[02:33:57 PM] Integrated Weblogic domain processing completed successfully.
*** Using port 7101 ***
C:\Users\jmindrup\AppData\Roaming\JDeveloper\system11.1.1.2.36.55.36\DefaultDomain\bin\startWebLogic.cmd
[waiting for the server to complete its initialization...]
\Java\jre6\lib\ext\QTJava.zip was unexpected at this time.
Process exited.
Does anyone have any ideas of why I cannot start the integrated wls on my windows 7 machine? Thanks.

Well, we haven't have any problems running WebLogic in Windows 7, so I don't think the problem has to do excusively with Windows 7.
On the other hand, there is no 'QTJava.zip' in \Java\jre6\lib\ext\ by default. What is that? Can't you put it somewhere else?

Reconfigure Integrated WLS from jdev

Hi I´ve deleted the integrated wls configuration from jdev from a msitake now I whant to retrieve and configure it back but I cant...
Can you help me?
Jdeveloper is 11.1.1.3 release 1
when I try to run I got this error
+[Waiting for the domain to finish building...]+
+[03:57:25 PM] Creating Integrated Weblogic domain...+
The Server Instance cannot be started because the Integrated Weblogic domain was not built successfully.
+[03:57:25 PM] ERROR: An error occurred while building the default domain.+
Please see this log file for more details:
Edited by: José Carlos on 25/05/2010 12:03

Thanks for reply nick but my OS (windows 7) doesnt have JDEV_USER_HOME variable set. Where can i change it?
COuldnt start yet, i already deleted directory but my jdev cant recreate internal wls...
[05:09:41 PM] Creating Integrated Weblogic domain...
The Server Instance cannot be started because the Integrated Weblogic domain was not built successfully.
[05:09:41 PM] ERROR: An error occurred while building the default domain.
Please see this log file for more details:
C:\Users\carlos.barros\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60\o.j2ee.adrs\CreateDefaultDomain.log
Log File: C:\Users\carlos.barros\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60\o.j2ee.adrs\CreateDefaultDomain.log
Label: JDEVADF_11.1.1.3.PS2_GENERIC_100408.2356.5660
Product Home: C:\Oracle\Middleware11\jdeveloper\jdev\
Domain: C:\Users\carlos.barros\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60\DefaultDomain
"C:\Oracle\Middleware11\oracle_common\common\bin\wlst.cmd" "C:\Users\carlos.barros\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60\o.j2ee.adrs\CreateDefaultDomain.py"
Process started
wlst > O sistema nÆo pode encontrar o caminho especificado.
Elapsed time: 102 ms
Edited by: José Carlos on 25/05/2010 13:10
Edited by: José Carlos on 25/05/2010 13:19

Integrated WLS or standalone for development?

I am wondering... What are the benefits of a IWLS instead of a standalone WLS for development? IS their a difference in instance, memory usage,... ?
The only thing i can think of is that you can test your application by right clicking and press run... You don't need to deploy first and when you stop the application, it gets undeployed.
To me, that's not important because i'm working 90% of my time with ADF portlets so in order to test them, i need to deploy it instead of run it. Isn't it better to use a standalone server for this?
Are their any benefits from it?

To Add more:
I am not sure if you can beat the benefits of Integrated WLS when it comes to quick development:
- Not every developer has to know much about WLS. Deployment to standalone server can be complicated and time consuming depending upon the size, dependency of your project. [I should mention you can also deploy to standalone wls from JDeveloper]
- Its quick and fast
- isolated and doesn't effect any other developer/team.
- In my Org, not every developer has excess to deployment on standalone servers.
- Helps developers from getting involved in may deployment related issues.
But there are some benefits of standalone server too:
- deployment to standalone is always different than deploying to IWLS. With IWLS some times you may not know lot
about the dependencies of your project and face issues when handing code to QA/Prod.
- As said, better control on dependencies.
- Look-n-Feel , behavior may differ, so standalone is always close to QA/Production.
Amit

Integrated wls doesn't start

Hi,
I'm using JDev 11.1.1.3.
I was working normally but suddenly the integrated wls doesn't start anymore.
When I start the server, the log stops here
<Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
Although the log says "RUNNING", the server is not running. If I test, through the server properties, all tests fail, except the HTTP.
I tried to delete the cache folder and re-install the middleware... the problem remains.
Thanks.

Hi,
bellow follows the entire log.
I can't launch the console... the log shows this message "<Logger><error> ServletContainerAdapter manager not initialized correctly."
*** Using port 7101 ***
D:\JDevCache\system11.1.1.3.37.56.60\DefaultDomain\bin\startWebLogic.cmd
[waiting for the server to complete its initialization...]
JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m
WLS Start Mode=Development
CLASSPATH=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\ext\jdbc\oracle\11g\ojdbc6dms.jar;C:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\JDK160~1\lib\tools.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;C:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules_10.3.3.0.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.1/lib/ant-all.jar;C:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrf.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\derby\lib\derbyclient.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\xqrl.jar;.;C:\Program Files\Java\jre6\lib\ext\QTJava.zip
PATH=C:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\native;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\native;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\bin;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.1\bin;C:\Oracle\MIDDLE~1\JDK160~1\jre\bin;C:\Oracle\MIDDLE~1\JDK160~1\bin;C:\oraclexe\app\oracle\product\10.2.0\server\bin;D:\ORACLE\PRODUCT\10.2.0\CLIENT_3\BIN;D:\ORACLE\PRODUCT\10.2.0\CLIENT_2;C:\Windows\SYSTEM32;C:\Windows;C:\Windows\SYSTEM32\WBEM;C:\Windows\SYSTEM32\WINDOWSPOWERSHELL\V1.0\;C:\PROGRAM FILES\TORTOISESVN\BIN;C:\Oracle\Middleware\jdeveloper\jdev\bin;C:\Oracle\Middleware\jdeveloper\ant\bin;C:\Oracle\Middleware\jdk160_14_R27.6.5-32\bin;C:\Program Files\QuickTime\QTSystem\;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32\oci920_8
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
starting weblogic with Java version:
java version "1.6.0_18"
Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
Java HotSpot(TM) Client VM (build 16.0-b13, mixed mode)
Starting WLS with line:
C:\Oracle\MIDDLE~1\JDK160~1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=DefaultServer -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Djavax.net.ssl.trustStore=C:\Oracle\Middleware3\wlserver_10.3\server\lib\DemoTrust.jks -Dhttp.proxyHost=proxy.link.pt -Dhttp.proxyPort=3128 "-Dhttp.nonProxyHosts=*.msdev.pt|*.linkcom.pt|*sgps*|*sonae*|*mch*|172.20.*.*|*.nvsd.local|192.168.*.*|194.117.36.*|*.aitec.pt|*.link.pt|localhost|localhost.localdomain|127.0.0.1|::1|pwpmedeiros.aitec.pt|pwpmedeiros" -Dhttps.proxyHost=proxy.link.pt -Dhttps.proxyPort=3128 "-Dhttps.nonProxyHosts=*.msdev.pt|*.linkcom.pt|*sgps*|*sonae*|*mch*|172.20.*.*|*.nvsd.local|192.168.*.*|194.117.36.*|*.aitec.pt|*.link.pt|localhost|localhost.localdomain|127.0.0.1|::1|pwpmedeiros.aitec.pt|pwpmedeiros" -Dweblogic.nodemanager.ServiceEnabled=true -Xverify:none -da -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Djps.app.credential.overwrite.allowed=true -Ddomain.home=D:\JDEVCA~1\SYSTEM~1.60\DEFAUL~1 -Dcommon.components.home=C:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.domain.config.dir=D:\JDEVCA~1\SYSTEM~1.60\DEFAUL~1\config\FMWCON~1 -Doracle.server.config.dir=D:\JDEVCA~1\SYSTEM~1.60\DEFAUL~1\config\FMWCON~1\servers\DefaultServer -Doracle.security.jps.config=D:\JDEVCA~1\SYSTEM~1.60\DEFAUL~1\config\fmwconfig\jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=D:\JDEVCA~1\SYSTEM~1.60\DEFAUL~1\config\FMWCON~1\carml -Digf.arisidstack.home=D:\JDEVCA~1\SYSTEM~1.60\DEFAUL~1\config\FMWCON~1\arisidprovider -Dweblogic.alternateTypesDirectory=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Dwsm.repository.path=D:\JDEVCA~1\SYSTEM~1.60\DEFAUL~1\oracle\store\gmds -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sysext_manifest_classpath weblogic.Server
<30/Ago/2011 18H01m BST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 16.0-b13 from Sun Microsystems Inc.>
<30/Ago/2011 18H01m BST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 >
<30/Ago/2011 18H01m BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<30/Ago/2011 18H01m BST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<30/Ago/2011 18H01m BST> <Notice> <LoggingService> <BEA-320400> <The log file D:\JDevCache\system11.1.1.3.37.56.60\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<30/Ago/2011 18H01m BST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to D:\JDevCache\system11.1.1.3.37.56.60\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log00004. Log messages will continue to be logged in D:\JDevCache\system11.1.1.3.37.56.60\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log.>
<30/Ago/2011 18H01m BST> <Notice> <Log Management> <BEA-170019> <The server log file D:\JDevCache\system11.1.1.3.37.56.60\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log is opened. All server side log events will be written to this file.>
<30/Ago/2011 18H01m BST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<30/Ago/2011 18H01m BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<30/Ago/2011 18H01m BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<30/Ago/2011 18H01m BST> <Notice> <LoggingService> <BEA-320400> <The log file D:\JDevCache\system11.1.1.3.37.56.60\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<30/Ago/2011 18H01m BST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to D:\JDevCache\system11.1.1.3.37.56.60\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log00004. Log messages will continue to be logged in D:\JDevCache\system11.1.1.3.37.56.60\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log.>
<30/Ago/2011 18H01m BST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<30/Ago/2011 18H01m BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<30/Ago/2011 18H01m BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<30/Ago/2011 18H01m BST> <Notice> <Server> <BEA-002613> <Channel "Default[13]" is now listening on 0:0:0:0:0:0:0:1:7101 for protocols iiop, t3, ldap, snmp, http.>
<30/Ago/2011 18H01m BST> <Notice> <Server> <BEA-002613> <Channel "Default[12]" is now listening on 127.0.0.1:7101 for protocols iiop, t3, ldap, snmp, http.>
<30/Ago/2011 18H01m BST> <Notice> <Server> <BEA-002613> <Channel "Default[6]" is now listening on fe80:0:0:0:289b:22c3:bcf6:2bce:7101 for protocols iiop, t3, ldap, snmp, http.>
<30/Ago/2011 18H01m BST> <Warning> <Server> <BEA-002611> <Hostname "pwpmedeiros.aitec.pt", maps to multiple IP addresses: 169.254.251.192, 192.168.59.64, 192.168.181.1, 192.168.159.1, fe80:0:0:0:8935:43d7:b990:fbc0%17, fe80:0:0:0:289b:22c3:bcf6:2bce%18, fe80:0:0:0:e437:fbfb:c9ee:9352%19>
<30/Ago/2011 18H01m BST> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on 192.168.59.64:7101 for protocols iiop, t3, ldap, snmp, http.>
<30/Ago/2011 18H01m BST> <Notice> <Server> <BEA-002613> <Channel "Default[10]" is now listening on fe80:0:0:0:0:100:7f:fffe:7101 for protocols iiop, t3, ldap, snmp, http.>
<30/Ago/2011 18H01m BST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.159.1:7101 for protocols iiop, t3, ldap, snmp, http.>
<30/Ago/2011 18H01m BST> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 192.168.181.1:7101 for protocols iiop, t3, ldap, snmp, http.>
<30/Ago/2011 18H01m BST> <Notice> <Server> <BEA-002613> <Channel "Default[9]" is now listening on fe80:0:0:0:0:5efe:c0a8:b501:7101 for protocols iiop, t3, ldap, snmp, http.>
<30/Ago/2011 18H01m BST> <Notice> <Server> <BEA-002613> <Channel "Default[5]" is now listening on fe80:0:0:0:e437:fbfb:c9ee:9352:7101 for protocols iiop, t3, ldap, snmp, http.>
<30/Ago/2011 18H01m BST> <Notice> <Server> <BEA-002613> <Channel "Default[7]" is now listening on 169.254.251.192:7101 for protocols iiop, t3, ldap, snmp, http.>
<30/Ago/2011 18H01m BST> <Notice> <Server> <BEA-002613> <Channel "Default[8]" is now listening on fe80:0:0:0:8935:43d7:b990:fbc0:7101 for protocols iiop, t3, ldap, snmp, http.>
<30/Ago/2011 18H01m BST> <Notice> <Server> <BEA-002613> <Channel "Default[11]" is now listening on fe80:0:0:0:f102:6891:b891:3efd:7101 for protocols iiop, t3, ldap, snmp, http.>
<30/Ago/2011 18H01m BST> <Notice> <Server> <BEA-002613> <Channel "Default[4]" is now listening on fe80:0:0:0:0:5efe:a9fe:fbc0:7101 for protocols iiop, t3, ldap, snmp, http.>
<30/Ago/2011 18H01m BST> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on fe80:0:0:0:0:5efe:c0a8:3b40:7101 for protocols iiop, t3, ldap, snmp, http.>
<30/Ago/2011 18H01m BST> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "DefaultServer" for domain "DefaultDomain" running in Development Mode>
<30/Ago/2011 18H01m BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<30/Ago/2011 18H01m BST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>

Integrated WLS fails to start

Recently I have found out that I cannot get to start the integrated wls in debug mode. When I choose "Debug server instance" the IDE initiates the server start, everything goes pretty well, the Debugging log tab shows the proccess (unless the startup time seems to be suspiciously long) but it all eventually ends with the message "#### Server Instance DefaultServer could not be started: Server Instance was terminated" in the Messages tab.
After that I cannot run an app, because as soon as I do this, the server scripts try to shut the server down and deployment fails. I have noticed that this message shows up because of the longer server start, in my case it's about 120 000ms. The "Run server instance" goes ok since the server starts in 30 000ms.
I guess that there's some timeout monitoring mechanism in the IDE or somewhere in the scripts. Is there any way to increase this timeout parameter? I tried to reinstall the JDev - the same problem occurs. Longer before, the debug mode started well in may be 50 000ms, and the timeout case didn't happen. Oh, I have to mention - when windows running in the Safe mode the debug starts really well, about 30 000ms and I don't see any termination message.
Edited by: euggie on Oct 25, 2009 1:57 AM

Hi, Arun!
There's no exception at all. I've just reinstalled the JDev 1.1.1.1.0.2 and it is clean install, and the situation is the same.
Here's the Debugging log tab:
C:\Oracle\Middleware111102\jdeveloper\system\system11.1.1.0.31.52.05\DefaultDomain\bin\startWebLogic.cmd
[waiting for the server to complete its initialization...]
JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=48m -XX:MaxPermSize=192m
WLS Start Mode=Development
CLASSPATH=;C:\Oracle\MIDDLE~1\patch_wls1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_cie660\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\JDK160~1\lib\tools.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;C:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules_10.3.0.0.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.5/lib/ant-all.jar;C:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;C:\Oracle\Middleware111102\jdeveloper\modules\features\adf.share_11.1.1.jar;;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\eval\pointbase\lib\pbclient57.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\xqrl.jar;;
PATH=C:\Oracle\MIDDLE~1\patch_wls1030\profiles\default\native;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\native;C:\Oracle\MIDDLE~1\patch_cie660\profiles\default\native;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\bin;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.5\bin;C:\Oracle\MIDDLE~1\JDK160~1\jre\bin;C:\Oracle\MIDDLE~1\JDK160~1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\QuickTime\QTSystem\;C:\Program Files\ATI Technologies\ATI.ACE\Core-Static;C:\lib\jaxb-ri-20071219\bin;C:\Program Files\SecureCRT\;C:\Program Files\TortoiseSVN\bin;C:\Program Files\Common Files\Adobe\AGL;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32\oci920_8
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
starting weblogic with Java version:
java version "1.6.0_05"
Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode)
Starting WLS with line:
C:\Oracle\MIDDLE~1\JDK160~1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=48m -XX:MaxPermSize=192m -agentlib:jdwp=transport=dt_socket,server=y,address=1337 -Xverify:none -da -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Ddomain.home=C:\Oracle\MIDDLE~1\JDEVEL~1\system\SYSTEM~1.05\DEFAUL~1 -Doracle.home=C:\Oracle\Middleware111102\jdeveloper -Doracle.security.jps.config=C:\Oracle\MIDDLE~1\JDEVEL~1\system\SYSTEM~1.05\DEFAUL~1\config\oracle\jps-config.xml -Doracle.dms.context=OFF -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1030\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_cie660\profiles\default\sysext_manifest_classpath -Dweblogic.Name=DefaultServer -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy weblogic.Server
Listening for transport dt_socket at address: 1337
Debugger connected to local process.
<25.10.2009 13:18:16 MSK> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
C:\Oracle\Middleware111102\patch_wls1030\profiles\default\sysext_manifest_classpath\weblogic_ext_patch.jar;C:\Oracle\Middleware111102\wlserver_10.3\L10N\beehive_ja.jar;C:\Oracle\Middleware111102\wlserver_10.3\L10N\beehive_ko.jar;C:\Oracle\Middleware111102\wlserver_10.3\L10N\beehive_zh_CN.jar;C:\Oracle\Middleware111102\wlserver_10.3\L10N\beehive_zh_TW.jar;C:\Oracle\Middleware111102\wlserver_10.3\L10N\p13n_wls_ja.jar;C:\Oracle\Middleware111102\wlserver_10.3\L10N\p13n_wls_ko.jar;C:\Oracle\Middleware111102\wlserver_10.3\L10N\p13n_wls_zh_CN.jar;C:\Oracle\Middleware111102\wlserver_10.3\L10N\p13n_wls_zh_TW.jar;C:\Oracle\Middleware111102\wlserver_10.3\L10N\testclient_ja.jar;C:\Oracle\Middleware111102\wlserver_10.3\L10N\testclient_ko.jar;C:\Oracle\Middleware111102\wlserver_10.3\L10N\testclient_zh_CN.jar;C:\Oracle\Middleware111102\wlserver_10.3\L10N\testclient_zh_TW.jar;C:\Oracle\Middleware111102\wlserver_10.3\L10N\tuxedocontrol_ja.jar;C:\Oracle\Middleware111102\wlserver_10.3\L10N\tuxedocontrol_ko.jar;C:\Oracle\Middleware111102\wlserver_10.3\L10N\tuxedocontrol_zh_CN.jar;C:\Oracle\Middleware111102\wlserver_10.3\L10N\tuxedocontrol_zh_TW.jar;C:\Oracle\Middleware111102\wlserver_10.3\L10N\workshop_ja.jar;C:\Oracle\Middleware111102\wlserver_10.3\L10N\workshop_ko.jar;C:\Oracle\Middleware111102\wlserver_10.3\L10N\workshop_zh_CN.jar;C:\Oracle\Middleware111102\wlserver_10.3\L10N\workshop_zh_TW.jar>
<25.10.2009 13:18:20 MSK> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 10.0-b19 from Sun Microsystems Inc.>
<25.10.2009 13:18:23 MSK> <Info> <Management> <BEA-141107> <Version: WebLogic Server Temporary Patch for CR380042 Thu Sep 11 13:33:40 PDT 2008
WebLogic Server Temporary Patch for 7372756 Fri Sep 12 17:05:44 EDT 2008
WebLogic Server Temporary Patch for CR381265 Wed Oct 08 10:15:58 PDT 2008
WebLogic Server Temporary Patch for CR380913 Wed Oct 15 13:24:22 PDT 2008
WebLogic Server Temporary Patch for CR382965 Fri Nov 21 15:51:48 PST 2008
WebLogic Server Temporary Patch for CR383260 Thu Nov 20 12:58:15 PST 2008
WebLogic Server Temporary Patch for CR383202 Fri Nov 21 09:58:15 PST 2008
WebLogic Server 10.3 Mon Aug 18 22:39:18 EDT 2008 1142987 >
<25.10.2009 13:18:37 MSK> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<25.10.2009 13:18:37 MSK> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<25.10.2009 13:18:41 MSK> <Notice> <Log Management> <BEA-170019> <The server log file C:\Oracle\Middleware111102\jdeveloper\system\system11.1.1.0.31.52.05\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log is opened. All server side log events will be written to this file.>
<25.10.2009 13:19:56 MSK> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
DefaultServer startup time: 122687 ms.
DefaultServer started.
<25.10.2009 13:20:36 MSK> <Warning> <Deployer> <BEA-149617> <Non-critical internal application uddi was not deployed. Error: [Deployer:149158]No application files exist at 'C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\uddi.war'.>
<25.10.2009 13:20:36 MSK> <Warning> <Deployer> <BEA-149617> <Non-critical internal application uddiexplorer was not deployed. Error: [Deployer:149158]No application files exist at 'C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\uddiexplorer.war'.>
<25.10.2009 13:20:49 MSK> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<25.10.2009 13:20:49 MSK> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<25.10.2009 13:20:57 MSK> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<25.10.2009 13:20:58 MSK> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<25.10.2009 13:20:58 MSK> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<25.10.2009 13:20:59 MSK> <Warning> <Server> <BEA-002611> <Hostname "eug-desk", maps to multiple IP addresses: 192.168.161.1, 192.168.129.1, 192.168.1.36, 127.0.0.1>
<25.10.2009 13:20:59 MSK> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on 192.168.1.36:7101 for protocols iiop, t3, ldap, snmp, http.>
<25.10.2009 13:20:59 MSK> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on 127.0.0.1:7101 for protocols iiop, t3, ldap, snmp, http.>
<25.10.2009 13:20:59 MSK> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 192.168.129.1:7101 for protocols iiop, t3, ldap, snmp, http.>
<25.10.2009 13:20:59 MSK> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.161.1:7101 for protocols iiop, t3, ldap, snmp, http.>
<25.10.2009 13:20:59 MSK> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "DefaultServer" for domain "DefaultDomain" running in Development Mode>
<25.10.2009 13:20:59 MSK> <Warning> <Server> <BEA-002611> <Hostname "localhost", maps to multiple IP addresses: 192.168.161.1, 192.168.129.1, 192.168.1.36, 127.0.0.1>
<25.10.2009 13:20:59 MSK> <Warning> <Server> <BEA-002611> <Hostname "EUG-DESK", maps to multiple IP addresses: 192.168.161.1, 192.168.129.1, 192.168.1.36, 127.0.0.1>
<25.10.2009 13:20:59 MSK> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<25.10.2009 13:20:59 MSK> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
And here's the Messages tab:
[Starting Server Instance DefaultServer]
#### Server Instance DefaultServer could not be started: Server Instance was terminated.

JDevejoper 11.1.1.1.0 Integrated WLS Server Console not coming up

Hi,
I just downloaded the new JDeveloper 11.1.1.1.0
http://localhost:7101 shows the welcome page but
http://localhost:7101/em The page cannot be found.
Is there any other setting involved.
Thanks

Hi,
Can you tell me what is the default username and password for the integrated wls console: http://localhost:7101/console
I tried like for the previous weblogic/weblogic but it seams isn't working.
Thank you.

Multi datasource faliover problem - JDeveloper integrated Weblogic 10.3.5

Hi all,
I have a problem with JDeveloper integrated weblogic (version 10.3.5) fail over to second datasource in multi data source (2 generic datasources) configuration environment.
My test goes like this:
1. I have two databases running on separate servers.
2. both data sources are up & running OK.
3. JDeveloper integrated weblogic configured with multi datasource, using algorithm failover, and failover callback class.
4. weblogic started and adf application running using first datasource in list.
5. if I unplug network cable or shut down first database, weblogic won't fail over to second datasource and still trying to use the first one.
Failover callback class:
package failover;
public class ConnectionPoolFailoverCallback implements weblogic.jdbc.extensions.ConnectionPoolFailoverCallback {
     static {
          System.out.println("------------------------------------------------------------");
          System.out.println("\n\n\tConnectionPoolFailoverCallback class initiated...\n\n\t");
          System.out.println("------------------------------------------------------------");
     public int allowPoolFailover(String currPool, String nextPool, int opcode) {
          System.out.println("Current Pool - " + currPool);
          System.out.println("Next Pool - " + nextPool);
          System.out.println("Operation Code - " + opcode);
          System.out.println("------------------------------------------------------------");
          if (opcode == OPCODE_CURR_POOL_DEAD) {
               System.out.println("\n\n\tConnectionPoolFailoverCallback     return OK.");
               return OK;
          } else {
               System.out.println("\n\n\tConnectionPoolFailoverCallback     return DONOT_FAILOVER.");
               return DONOT_FAILOVER;
}{code}
*Problem:* When I unplug network cable or shutdown first database, method allowPoolFailover returns OK, but weblogic won't switch to second datasource entering allowPoolFailover method again and again.
+Note:+ weblogic integrated in JDeveloper is running u development mode.
Did I miss something in configuration or something else?
Any help is appreciated.
Thanks in advance,
Alexandar

Hi Alexandar,
Have you made any progress with this? We seem to have bumped into this issue as well. Connection requests are consistently routed to the disabled pool (it appears as disabled in the WLS console, but we can see the counters increasing steadily), the callback handler is called and returns OK, and the connection request is ultimately serviced by the active pool. So while the application still successfully handles requests, there's obviously an underlying problem in obtaining the connection.
Thanks,
Sebastien

JDeveloper Integrated WLS Language

Similar Messages

Maybe you are looking for