Running two weblogic server versions

hi all,
i have a requirement wherein i have to run weblog 9.2 and weblogic 8.1 in the same machine. my application deployed in weblogic 9.2 uses dataservice deployed in weblogic 8.1sp5. i have changed the port number of weblogic 8.1 to "8001" from "7001". but still when i start the 9.2 it fails to start saying it is not able to find transport socket...
here is the error.
JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510) ["debugInit.c",L497]
thank you.

Found the problem. The error occurs because I was running another domain which was using the default debug port for JDWP (8453). This port is set in the setDomainEnv.sh file. When I changed this port to 8454 the startup was fine :-)

Similar Messages

How to run two WebLogic server instances on the same machine

The setup is to run server instance A with all EJBs and server instance
B with all servlets.
I edited the weblogic.properties under myserver to include all EJBs and
create server2 under \weblogic parallel to myserver and put a new
weblogic.properties under server2 that has all the servlets aliases.
Is this the right way?
two server ran but I cannot hit the servlet.

The setup is to run server instance A with all EJBs and server instance
B with all servlets.
I edited the weblogic.properties under myserver to include all EJBs and
create server2 under \weblogic parallel to myserver and put a new
weblogic.properties under server2 that has all the servlets aliases.
Is this the right way?
two server ran but I cannot hit the servlet.

How to find out Integrated weblogic server version

hi experts,
am using jdev11.1.1.5.0
i h'd big doubt ;)
how to find out Integrated weblogic server version
i think am using weblogic10.1.3. but am not sure?
so how can i found out.
this my log. but i dont see any info about version.
*** Using port 7101 ***
"C:\Documents and Settings\Administrator\Application Data\JDeveloper\system11.1.1.5.37.60.13\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\ORACLE~1\modules\oracle.jdbc_11.1.1\ojdbc6dms.jar;C:\Oracle\MIDDLE~1\patch_wls1035\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.5.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
PATH=C:\Oracle\MIDDLE~1\patch_wls1035\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:\DevSuiteHome_1\jdk\jre\bin\classic;C:\DevSuiteHome_1\jdk\jre\bin;C:\DevSuiteHome_1\jdk\jre\bin\client;C:\DevSuiteHome_1\jlib;C:\DevSuiteHome_1\bin;C:\DevSuiteHome_1\jre\1.4.2\bin\client;C:\DevSuiteHome_1\jre\1.4.2\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;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_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b50)
Java HotSpot(TM) Client VM (build 19.1-b02, 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\Middleware\wlserver_10.3\server\lib\DemoTrust.jks -Duser.timezone="+05:30" -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 -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 -Ddomain.home=C:\DOCUME~1\ADMINI~1\APPLIC~1\JDEVEL~1\SYSTEM~1.13\DEFAUL~1 -Djrockit.optfile=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=C:\DOCUME~1\ADMINI~1\APPLIC~1\JDEVEL~1\SYSTEM~1.13\DEFAUL~1\config\FMWCON~1\servers\DefaultServer -Doracle.domain.config.dir=C:\DOCUME~1\ADMINI~1\APPLIC~1\JDEVEL~1\SYSTEM~1.13\DEFAUL~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=C:\DOCUME~1\ADMINI~1\APPLIC~1\JDEVEL~1\SYSTEM~1.13\DEFAUL~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\DOCUME~1\ADMINI~1\APPLIC~1\JDEVEL~1\SYSTEM~1.13\DEFAUL~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=C:\DOCUME~1\ADMINI~1\APPLIC~1\JDEVEL~1\SYSTEM~1.13\DEFAUL~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=C:\DOCUME~1\ADMINI~1\APPLIC~1\JDEVEL~1\SYSTEM~1.13\DEFAUL~1\servers\DefaultServer\tmp\_WL_user -Doracle.deployed.app.ext=\- -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 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dwsm.repository.path=C:\DOCUME~1\ADMINI~1\APPLIC~1\JDEVEL~1\SYSTEM~1.13\DEFAUL~1\oracle\store\gmds   -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1035\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sysext_manifest_classpath weblogic.Server
<Feb 17, 2012 5:50:39 AM GMT> <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 17, 2012 5:50:39 AM GMT> <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 17, 2012 5:50:39 AM GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 19.1-b02 from Sun Microsystems Inc.>
<Feb 17, 2012 5:50:40 AM GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<Feb 17, 2012 5:50:42 AM GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Feb 17, 2012 5:50:42 AM GMT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Feb 17, 2012 5:50:42 AM GMT> <Notice> <LoggingService> <BEA-320400> <The log file C:\Documents and Settings\Administrator\Application Data\JDeveloper\system11.1.1.5.37.60.13\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.>
<Feb 17, 2012 5:50:42 AM GMT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Documents and Settings\Administrator\Application Data\JDeveloper\system11.1.1.5.37.60.13\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log00220. Log messages will continue to be logged in C:\Documents and Settings\Administrator\Application Data\JDeveloper\system11.1.1.5.37.60.13\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log.>
<Feb 17, 2012 5:50:42 AM GMT> <Notice> <Log Management> <BEA-170019> <The server log file C:\Documents and Settings\Administrator\Application Data\JDeveloper\system11.1.1.5.37.60.13\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log is opened. All server side log events will be written to this file.>
<Feb 17, 2012 5:50:48 AM GMT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Feb 17, 2012 5:50:50 AM GMT> <Notice> <LoggingService> <BEA-320400> <The log file C:\Documents and Settings\Administrator\Application Data\JDeveloper\system11.1.1.5.37.60.13\DefaultDomain\servers\DefaultServer\logs\access.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Feb 17, 2012 5:50:50 AM GMT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Documents and Settings\Administrator\Application Data\JDeveloper\system11.1.1.5.37.60.13\DefaultDomain\servers\DefaultServer\logs\access.log00102. Log messages will continue to be logged in C:\Documents and Settings\Administrator\Application Data\JDeveloper\system11.1.1.5.37.60.13\DefaultDomain\servers\DefaultServer\logs\access.log.>
<Feb 17, 2012 5:50:56 AM GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Feb 17, 2012 5:50:56 AM GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<MessageLocalizationHelper> <getLocalizedMessage> The resource for bundle "oracle.jrf.i18n.MBeanMessageBundle" with key "oracle.jrf.JRFServiceMBean.checkIfJRFAppliedOnMutipleTargets" cannot be found.
<Feb 17, 2012 5:51:02 AM GMT> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application GeneralLedger is not versioned.>
<Feb 17, 2012 5:51:07 AM GMT> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application Rapppdf is not versioned.>
<Feb 17, 2012 5:51:27 AM GMT> <Notice> <LoggingService> <BEA-320400> <The log file C:\Documents and Settings\Administrator\Application Data\JDeveloper\system11.1.1.5.37.60.13\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.>
<Feb 17, 2012 5:51:27 AM GMT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Documents and Settings\Administrator\Application Data\JDeveloper\system11.1.1.5.37.60.13\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log00208. Log messages will continue to be logged in C:\Documents and Settings\Administrator\Application Data\JDeveloper\system11.1.1.5.37.60.13\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log.>
<Feb 17, 2012 5:51:27 AM GMT> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<Feb 17, 2012 5:51:27 AM GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Feb 17, 2012 5:51:27 AM GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<Feb 17, 2012 5:51:27 AM GMT> <Warning> <Server> <BEA-002611> <Hostname "rmsys0061", maps to multiple IP addresses: 192.168.0.161, 192.168.2.161>
<Feb 17, 2012 5:51:27 AM GMT> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on 127.0.0.1:7101 for protocols iiop, t3, ldap, snmp, http.>
<Feb 17, 2012 5:51:27 AM GMT> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 192.168.2.161:7101 for protocols iiop, t3, ldap, snmp, http.>
<Feb 17, 2012 5:51:27 AM GMT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.0.161:7101 for protocols iiop, t3, ldap, snmp, http.>
<Feb 17, 2012 5:51:27 AM GMT> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "DefaultServer" for domain "DefaultDomain" running in Development Mode>
<Feb 17, 2012 5:51:27 AM GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Feb 17, 2012 5:51:27 AM GMT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
IntegratedWebLogicServer startup time: 51640 ms.
IntegratedWebLogicServer started.
[Running application frmtesting on Server Instance IntegratedWebLogicServer...]
[11:21:30 AM] ---- Deployment started. ----
[11:21:30 AM] Target platform is (Weblogic 10.3).
[11:21:31 AM] Retrieving existing application information
[11:21:31 AM] Running dependency analysis...
[11:21:31 AM] Deploying 2 profiles...
[11:21:32 AM] Wrote Web Application Module to C:\Documents and Settings\Administrator\Application Data\JDeveloper\system11.1.1.5.37.60.13\o.j2ee\drs\frmtesting\ViewControllerWebApp.war
[11:21:32 AM] Wrote Enterprise Application Module to C:\Documents and Settings\Administrator\Application Data\JDeveloper\system11.1.1.5.37.60.13\o.j2ee\drs\frmtesting
[11:21:32 AM] Deploying Application...
<Feb 17, 2012 5:51:33 AM GMT> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application frmtesting is not versioned.>
[11:21:40 AM] Application Deployed Successfully.
[11:21:40 AM] The following URL context root(s) were defined and can be used as a starting point to test your application:
[11:21:40 AM] http://192.168.0.161:7101/frmtesting-ViewController-context-root
[11:21:40 AM] Elapsed time for deployment: 11 seconds
[11:21:40 AM] ---- Deployment finished. ----
Run startup time: 10812 ms.
[Application frmtesting deployed to Server Instance IntegratedWebLogicServer]
Target URL -- http://127.0.0.1:7101/frmtesting-ViewController-context-root/faces/untitled6.jspxhttp://127.0.0.1:7101/console/login/LoginForm.jsp. it stated as weblogicserver 11g admin console
At the botton(copy right section) 10.3.5.0

Hi,
There is one more method,i know
Set the JAVA_HOME and PATH
then execute the
$WL_HOME\wlserver_10.3\server\bin>setWLSEnv.cmd
Go to directory which contains weblogic.jar ($WL_HOME\server\lib) and run below command
$WL_HOME\wlserver_10.3\server\lib>java -cp weblogic.jar weblogic.version
WebLogic Server 10.3.4.0 Fri Dec 17 20:47:33 PST 2010 1384255
Hope this will be helpful,
Regards
Fabian

Error when deploying application in wiblogic WebLogic Server Version: 10.3.

hi when doing deployment in my WebLogic Server Version: 10.3.6.0 am geitng this error
weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: adf.oracle.domain, exact-match: false], [Extension-Name: oracle.jsp.next, exact-match: false], [Extension-Name: oracle.webcenter.framework, Specification-Version: 11.1.1, exact-match: false], [Extension-Name: oracle.webcenter.skin, Specification-Version: 11.1.1, exact-match: false].
how can i install this libraires in weblogic i have install this in jdeveloper by help->check updatesEdited by: adf009 on 2013/01/29 11:47 AM

Solution:
open the weblogic server console, in home page--> click the Deployments-->Select the adf.oracle.domain-->select target tab-->Click Lock & Edit-->
select the servers (admin and managed Server) and save.--> click Activate All changes.
Redeploy the application.

Is WebLogic Server Version 10.3.3.0 equal to 10.3

My WebLogic Server Version is 10.3.3.0 and I want to apply Patch 10215257, but the patch is only for WLS 10.3, 10.3.2.0, 10.3.4, and 10.3.5.
And I can not find Weblogic Doc web link for 10.3.3.0.
Is WebLogic Server Version 10.3.3.0 equal to 10.3

Hi ,
Application Server versions
WebLogic Server 12c Release 2 (12.1.2) - July 11, 2013
WebLogic Server 12c Release 1 (12.1.1) - Dec 1, 2011
WebLogic Server 11gR1 PS5 (10.3.6) - February 26, 2012
WebLogic Server 11gR1 PS4 (10.3.5) - May 16, 2011
WebLogic Server 11gR1 PS3 (10.3.4) - January 15, 2011
WebLogic Server 11gR1 PS2 (10.3.3) - April 2010
WebLogic Server 11gR1 PS1 (10.3.2) - November 2009
WebLogic Server 11g (10.3.1) - July 2009
WebLogic Server 10.3 - August 2008
WebLogic Server 10.0 - March 2007
Regards

How can I tell my current Weblogic server version and Service pack

Hello,
I was wondering how can I tell what my current
weblogic server version is and what service pack
it is at.
Thanks.

use 'java weblogic.version'
ensure weblogic.jar is in the classpath

Find my WebLogic Server version ?

Iam very new to Oracle..I wsh to install the Oracle11g Forms & reports.... as I know, to install the Oracle11g Forms & reports I need to install the weblogic server....
My clarifications are following....
01). I have a desktop pc with higher configuration...Is it possible to install ?
02). If it's possible means, I downloaded for forms & Reports installation file ..... win_11.1.2.1.0_32_disk1 file
But does anybody can provide me the appropriate Weblogic Server version for that?.....
Thanks

Hi,
It will depend on the OS version, JDK version used. Also might differ based on system is 32-bit or 64-bit.
For Oracle 11g forms & reports (11.1.2.1.0) on Windows 7 with 32-bit, Oracle weblogic server 10.3.6+ will work.
Refer to - http://www.oracle.com/technetwork/developer-tools/forms/oracle-forms-111210certmatrix-1886127.xls for the correct version.
## rank answer if found useful ###
Thanks,
Ranjan

Welcome to the BEA WebLogic Server Version 6.0 Beta Program!

Welcome to the BEA WebLogic Server Version 6.0 Beta Program!
We are very excited about this beta program and appreciate your
participation. In the past, our public betas have been very well received
by our developer community. So, we have once again organized a public beta
program to enable everyone to preview our latest release.
We do ask that you follow a few guidelines:
-- There will be no voice, e-mail, or fax support for this beta through the
technical support organization. All questions, bug reports, or comments on
the beta program should be directed to to the WebLogic beta newsgroups at
news://newsgroups.bea.com. These newsgroups are:
weblogic.developer.interest.60beta.transaction
weblogic.support.install.60beta
weblogic.developer.interest.60beta.ejb
weblogic.developer.interest.60beta.clustering
weblogic.developer.interest.60beta.security
weblogic.developer.interest.60beta.jdbc
weblogic.developer.interest.60beta.jms
weblogic.developer.interest.60beta.performance
weblogic.developer.interest.60beta.misc
weblogic.developer.interest.60beta.servlet
weblogic.developer.interest.60beta.jsp
weblogic.developer.interest.60beta.tools
weblogic.developer.interest.60beta.rmi-iiop
weblogic.developer.interest.60beta.management
weblogic.developer.interest.60beta.management.console
weblogic.developer.interest.60beta.management.general_and_jmx
weblogic.developer.interest.60beta.internationalization
weblogic.developer.interest.60beta.xml
weblogic.developer.interest.60beta.jndi
weblogic.developer.interest.60beta.documentation
weblogic.developer.interest.60beta.javamail
-- Please remember that this release is currently beta code. This means that
it should not be put into production deployments until the final release
occurs.
-- It is very likely that this release will contain bugs and errors. This is
the nature of beta code. Please the patient with us as we do our best to fix
any problems that we find. We will do our absolute best to make sure that
your issues are addressed as soon as possible.
-- Please do not post any issues relevant to the beta on the standard
newsgroups also available at news://newsgroups.bea.com.
-- Please use the newsgroup for all communication and do not contact any BEA
employees directly. They have been instructed to direct you to comment only
via the newsgroup.
-- Please review previous posts in the newsgroups before posting. If you
locate a bug or need to ask a question, it is very likely that it will have
been asked before.
-- Please do not post on the newsgroup using hostile or profane language.
Inappropriate posts will be removed and offenders will be blocked from the
beta program.
Thank you again for your support and participation. We very much appreciate
all that you will be doing to make this release of the BEA WebLogic Server
as great as possible.
Michael Girdley
BEA Systems Inc

Welcome to the BEA WebLogic Server Version 6.0 Beta Program!
We are very excited about this beta program and appreciate your
participation. In the past, our public betas have been very well received
by our developer community. So, we have once again organized a public beta
program to enable everyone to preview our latest release.
We do ask that you follow a few guidelines:
-- There will be no voice, e-mail, or fax support for this beta through the
technical support organization. All questions, bug reports, or comments on
the beta program should be directed to to the WebLogic beta newsgroups at
news://newsgroups.bea.com. These newsgroups are:
weblogic.developer.interest.60beta.transaction
weblogic.support.install.60beta
weblogic.developer.interest.60beta.ejb
weblogic.developer.interest.60beta.clustering
weblogic.developer.interest.60beta.security
weblogic.developer.interest.60beta.jdbc
weblogic.developer.interest.60beta.jms
weblogic.developer.interest.60beta.performance
weblogic.developer.interest.60beta.misc
weblogic.developer.interest.60beta.servlet
weblogic.developer.interest.60beta.jsp
weblogic.developer.interest.60beta.tools
weblogic.developer.interest.60beta.rmi-iiop
weblogic.developer.interest.60beta.management
weblogic.developer.interest.60beta.management.console
weblogic.developer.interest.60beta.management.general_and_jmx
weblogic.developer.interest.60beta.internationalization
weblogic.developer.interest.60beta.xml
weblogic.developer.interest.60beta.jndi
weblogic.developer.interest.60beta.documentation
weblogic.developer.interest.60beta.javamail
-- Please remember that this release is currently beta code. This means that
it should not be put into production deployments until the final release
occurs.
-- It is very likely that this release will contain bugs and errors. This is
the nature of beta code. Please the patient with us as we do our best to fix
any problems that we find. We will do our absolute best to make sure that
your issues are addressed as soon as possible.
-- Please do not post any issues relevant to the beta on the standard
newsgroups also available at news://newsgroups.bea.com.
-- Please use the newsgroup for all communication and do not contact any BEA
employees directly. They have been instructed to direct you to comment only
via the newsgroup.
-- Please review previous posts in the newsgroups before posting. If you
locate a bug or need to ask a question, it is very likely that it will have
been asked before.
-- Please do not post on the newsgroup using hostile or profane language.
Inappropriate posts will be removed and offenders will be blocked from the
beta program.
Thank you again for your support and participation. We very much appreciate
all that you will be doing to make this release of the BEA WebLogic Server
as great as possible.
Michael Girdley
BEA Systems Inc

Is it possible to run EJB ( Weblogic server 7.0) on win XP professional

Hi,
i am using win XP Professional platform. Is it possible to run EJB (WEBLOGIC SERVER 7.0) on this platform. IF not what are the other plug in needed to run WEBLOGIC SERVER on WIN XP Prof ?.

Yes, though currently BEA hasn't certified it for XP.

How to terminate the "process" running in weblogic server by servlet

hi all !!
i have executed a external command from servlet but i am not getting the output untill i logoff the weblogic server.
now i want to kill the process running in my server by servlet code.how could i do this? here is my code ,it is executing the command but not giving output untill i logoff the server.
                 Runtime rt = Runtime.getRuntime();
                 Process proc = rt.exec("var.bat");
                 proc.wait(60);
                 proc.destroy();Thanks and Regards
Allwyn

hey !
anybody is here?????

Weblogic Server version with ADF runtime

Expert,
May I know which the latest version of Weblogic Server can support ADF runtime? Thanks!
Rgds!

No, there is no support for 12c jet. You have to wait for this till next year. There will be at least one more 11.1.1.x and 11.1.2.x version before we get 12c with ADF support.
I'll try to keep the list up to date (which it is right now).
Timo

Signed Applet running in weblogic server

Hi ,
Im a newbie with applet. Can anyone help me to clarify below question.
1. I have signed applet compile with jdk 1.4.2. It its running fine with JRE 1.4 and 1.4.2. However i need to upgrade the applet so that it can support JRE 1.6. Can anyone guide me regarding this issue as the applet will close if i running in jre 1.6. I got the below exception
java.io.FilePermission<<allFiles>> execute.
2. As i know, If i compiled the applet again, i need to signed the ja againr. I tried once and got below exception
ClassNotFoundException. can anyone give any idea how resolved this problem. Fyi, im using weblogic server 8.1
Thanks.
Regards

Normally, a 1.4 compiled and signed applet should work just fine under 1.6. No need to recompile and resign.
This is in theory and in my practice with my applets. Since you do have problems, please post here (copy and paste, don't paraphrase) full stack traces of the errors and relevant code where the error occurs.

XServe Running Tiger, not Server Version?

Can we install the standard (non-server) version of Tiger on an XServe? We use to render video and run video at concerts and are having lots of render crashes under Final Cut as well as some tasks apparantly running in the background which is making full screen live video playback glitch every second or so. Running the same tasks on a tower is fine so we thought it might be OSX Server. Suggestions?
Ron
http://www.MotionLoops.com

I'm with William here.
Running Mac OS X client on an XServe certainly isn't supported, but that means you can't turn to Apple for help if something breaks.
There's absolutely nothing in Mac OS X client that says "oh, I'm running on an XServe so I'd better stop right now", and there's nothing in the hardware that says it has to run Mac OS X Server - heck, you can install Linux on an XServe if you really want to, just don't expect Apple to help you afterwards.
You will lose the server-specific features, admin tools, etc., etc., but other than that there is no reason why you can't run Mac OS X client.

What's the recommended way to run a WebLogic Server in the background?

I'm new to WebLogic Server and I've been looking at the documentation. There's instructions for starting and stopping servers on Linux but they all seem to rely on foreground processes. What's the correct way to run these processes in the background in a production environment? Is it just by using nohup somewhere in a script /etc/init.d/ or is there some other way I should be running it?

Meatwad,
Of course, running the WLS processes using nohup would place the process in the background. However, the recommended way to run the WLS servers on a production system would be to configure node manager and use this. This places the servers as a background process but also provides some additional functionality, that would be useful - for instance, allowing starting and stopping via the admin console and the ability to auto restart failed or stuck servers.
For more information, please consult the documentation.
http://docs.oracle.com/cd/E17904_01/web.1111/e13740/starting_nodemgr.htm

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

Running two weblogic server versions

Similar Messages

Maybe you are looking for