The application migration weblogic 8.1 to weblogic 10.0 - Urgent

Similar Questions

• Build failed while credentials of the application migration, to standaloneWLS.

  I use jdeveloper 11g update 2 and Weblogic10.3
  
  I am migrating the credentials and policies for Standalone WebLogic.
  I'm following the link:
  
  http://www.Oracle.com/technology/products/jdev/tips/Muench/credmig111100/index.html
  
  
  3.2 step migration request credentials to Standalone WebLogic:
  
  When I'm trying to run the command:
  $ ant-Dapp-credstore=APPWORKSPACEDIR/src/META-INF/cwallet.sso
  
  I am confronted with error:
  
  
  
  BUILD FAILED
  F:\WLSoracle2\user_projects\domains\base_domain\migration\build.XML:48: Lee
  pay error has occurred during execution of this line:
  F:\WLSoracle2\user_projects\domains\base_domain\migration\build.XML:53: * file
  App-cedstore = APPWORKSPACEDIR/SRC/META-INF/cwallet. SSO does not exist!
  
  
  Here I don't know that the APPWORKSPACEDIR is referring to that.
  
  Here, I use the file build.xml and jps - config.xml as shown in the link above.
  
  Please if any one face the same error during deployment, please tell me the solution.how can I remove this error.
  
  
  Sanchez

  Sanchez,

  APPWORKSPACEDIR is the directory of your *.jws file is located in, so it the main folder of the application.

  Timo

• error when refresh/create database during the application migration

  Hello
  
  version 9.3.1 to 9.3.1 (migration)
  
  (1) application created in the target
  (2) CSSImport made
  (3) restoration planning scheme
  (4) resistant with shared services is
  (5) alternative var created at the server level
  
  After you create and update I met with error
  
  "
  Step 42 43: [Wrkforce] financial rate of filling.
  "com.hyperion.planning.olap.EssbaseException: BUDGET (1100027).
  
  However, I have increased already Netdelay and NETRETRYCOUNT 10000
  
  any help.

  No need, if anything happens that we are here to sort them :)

  BT don't forger to mark messages as correct or useful if you think they are.

  Bbye GN

• When I start the integration of weblogic 10.3

  When I launched wli server admin:
  
  < 12 August 2012 02:15:18 BRT > < error > < hats > < BEA-149231 > < cannot create the activation state to true for the application "Worklist_Console".
  weblogic.application.ModuleException: Exception by activating the module: EJBModule (p13n_ejb.jar)
  
  
  Unable to deploy EJB: p13n_ejb.jar TrackedAnonymous:
  
  [EJB:010127] Detected incorrect data source type. The data source with the JNDI name "weblogic.jdbc.jts.commercePool", specified in the deployment descriptor of RDBMS for the EJB "TrackedAnonymous" does not support global transactions. The EJB container requires a data source that supports global transactions to be specified for transactions to manage properly.
  
  
  at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
  at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
  to weblogic.application.internal.flow.DeploymentCallbackFlow$ 2.next(DeploymentCallbackFlow.java:411)
  at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
  at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:74)
  at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:66)
  to weblogic.application.internal.BaseDeployment$ 2.next(BaseDeployment.java:635)
  at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
  at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
  at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
  at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
  at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
  at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
  at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
  to weblogic.management.deploy.internal.DeploymentAdapter$ 1.doActivate(DeploymentAdapter.java:51)
  at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196)
  to weblogic.management.deploy.internal.AppTransition$ 2.transitionApp(AppTransition.java:30)
  at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
  at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
  at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
  at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
  at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
  at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
  to weblogic.work.SelfTuningWorkManagerImpl$ WorkAdapterImpl.run (SelfTuningWorkManagerImpl.java:516)
  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
  at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
  [EJB:010127] Detected incorrect data source type. The data source with the JNDI name "weblogic.jdbc.jts.commercePool", specified in the deployment descriptor of RDBMS for the EJB "TrackedAnonymous" does not support global transactions. The EJB container requires a data source that supports global transactions to be specified for transactions to manage properly.
  at weblogic.ejb.container.cmp.rdbms.RDBMSPersistenceManager.verifyTXDataSource(RDBMSPersistenceManager.java:4275)
  at weblogic.ejb.container.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:255)
  at weblogic.ejb.container.manager.BaseEntityManager.setupPM(BaseEntityManager.java:300)
  at weblogic.ejb.container.manager.BaseEntityManager.setup(BaseEntityManager.java:249)
  at weblogic.ejb.container.manager.DBManager.setup(DBManager.java:172)
  at weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1166)
  at weblogic.ejb.container.deployer.EntityBeanInfoImpl.activate(EntityBeanInfoImpl.java:238)
  at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1237)
  at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:476)
  at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
  to weblogic.application.internal.flow.DeploymentCallbackFlow$ 2.next(DeploymentCallbackFlow.java:411)
  at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
  at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:74)
  at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:66)
  to weblogic.application.internal.BaseDeployment$ 2.next(BaseDeployment.java:635)
  at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
  at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
  at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
  at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
  at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
  at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
  at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
  to weblogic.management.deploy.internal.DeploymentAdapter$ 1.doActivate(DeploymentAdapter.java:51)
  at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196)
  to weblogic.management.deploy.internal.AppTransition$ 2.transitionApp(AppTransition.java:30)
  at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
  at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
  at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
  at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
  at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
  at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
  to weblogic.work.SelfTuningWorkManagerImpl$ WorkAdapterImpl.run (SelfTuningWorkManagerImpl.java:516)
  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
  at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
  >
  
  What can I do to fix this?

  Hi Alex,

  Console open weblogic, go to Services > Data Sources and search for your "weblogic.jdbc.jts.commercePool" on the JNDI name column jndi.

  Click the data source and go to the Transaction tab - you have to check the Supports Global transactions

  See you soon,.
  Vlad

• Deploying the application to the stand-alone WebLogic problem

  Hello!
  I have a problem with the stand-alone WebLogic Server applications.
  We migrated to JDeveloper 11.1.1.5 to 11.1.2.1. I followed the instructions on this page: https://blogs.oracle.com/imc/entry/standalone_weblogic_domain_for_adf to deploy our application of ADF on AdminServer. Everything worked OK.
  
  Then I followed the instructions on this page: http://docs.oracle.com/cd/E21043_01/web.1111/e13813/custom_jrf.htm to apply with our "ADF_server" the server JRF managed and got this:
  WLS: / offline > applyJRF ('ADF_server', ' / Oracle/Middleware/user_projects/domains/our_domain ')
  Read the/Oracle/Middleware/user_projects/domains/our_domain area of applyJRF
  Copy the configuration files JRF/Oracle/Middleware/oracle_common/modules/Oracle/Middleware/user_projects/domains/our_domain/config/fmwconfig/servers/ADF_server
  Components JRF target to "ADF_server".
  Update changes JRF to/Oracle/Middleware/user_projects/domains/our_domain field in offline mode
  It's probably OK?
  
  When I try to deploy a problem occurs on a managed server 'ADF_server':
  * [10: 55:08] Weblogic Server Exception: weblogic.application.ModuleException: could not load the webapp: "ADFMainApplication-ViewController-context-root."
  * [10: 55:08] caused by: weblogic.management.DeploymentException: error: unresolved Webapp library makes reference to ' [ServletContext@1542360219[app:ADFMainApplication_Project1_ADFMainApplication module: root ADFMainApplication-ViewController-context-path: / ADFMainApplication-ViewController-context-root spec-version: 2.5] ", defined in weblogic.xml [Extension name: jsf Specification-Version: 2, exact match: false] *.
  * [10: 55:08] see the server logs or the console of the server for more details.*
  * [10: 55:08] weblogic.application.ModuleException: failed to load the webapp: "ADFMainApplication-ViewController-context-root."
  * [10: 55:08] deployment cancelled.*
  * [10: 55:08] - incomplete deployment. *
  * [10: 55:08] remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer). *
  
  What should I do to run the managed server? Help, please.
  Best regards, Marko

  You did to be sure that the 11.1.1.5.0 adf runtime has been installed on the managed server before installing Upgrade patches to 11.1.2.1.0?

  If this isn't the case, it is the problem. The new runtime environment is installed automatically if the olny one has been set up correctly, my personal conclusion from my tests. If you want to learn more about this check http://tompeez.wordpress.com/2011/06/25/upgrading-wls-10-3-5-with-adf-runtime-11-1-2-0-0-sherman-patch/ and http://tompeez.wordpress.com/2011/06/29/follow-up-upgrading-wls-10-3-5-with-adf-runtime-11-1-2-0-0-sherman-patch/.

  You can make the threethings:
  1. Open Enterprise Manager, select your managed server and hope you see a message like "JRF aply to this managed server" (don't remember the exact wording). To do this, and libraries must configure OK.
  2. open the administration console and select the necessary shared libraries and add your manages the target server. Problem is that you don't know what libs are needed. If you don't mind target libraries to the managed server. Not sure if this causes problems later.
  3 write information on the managed server as port, domain names machine name. Remove the server managed the installation of WLS. It must be very sad that you upgrade and which should be no application or shared library of your one deployed on the managed server. After removal of the old successful server closes wls and start it again (just for security). Now, create a new managed server with all names, ports, and other information like the old using the quick start tool.

  I prefer the 3 method, this one worked for me all the time.

  Timo

• where the application is stored in the weblogic file after deployment?

  Hello, I am beginner of WebLogic Server12C.

  I deployed a project of console gui war. However, I can't find where the expansion.

  I can find. "" appmergengen folder "and"_WL_user folder"in the tmp folder.

  They exploded Archive Directory. However, they are in the tmp folder.

  So could you tell me where the application is stored in the weblogic file after deployment?

  I find no specific document of the oralce site documents.

  The application that you deploy to weblogic may be placed under a folder tmp only under appropriate weblogic server instance i.e. Managed server / Server Admin

  It will be cached in the exploded only form and not in WAR or archived form.

  Hope that clarifies!

  Thank you

  Vijaya

• Problem server standard weblogic that does not detect the application of ADF data side

  Hi all

  I use the jdev11.1.1.7.0 version.

  I have deployed an adf on oracle weblogic server application. When to test a page server-side it dispalyed but with blank fields. When I try to insert the data, it shows an error like "lines cannot be created in the entity xxxx.eo (name of the entity with path mentioned on Jdeveloper). This same code is deployed in the weblogic server local and works very well.

  For DB connection: I created a JNDI connection and used on the configuration of the application module. DB connections are tested. they work very well on the server side.

  Could someone help on why the error comes from the side server.

  Thanks in advance,

  Suresh.

  Hi all

  Thanks are for all of your support.

  Problem is solved. It is may not be bounce oracle weblogic server.  After the rebound of the server, the database data is displayed in pages.

  Thank you

  Suresh.

• Error during the deployment of ADF application on weblogic Server integrated in JDEV - [SPI: J2EE deployment 260010]

  Hello Experts,

  I received the following message when I tried to deploy a sample application on the weblogic Server integrated into my JDEV ADF.  Can someone help me with this error message?

  < 27 March 2015 21:30:09 CEST > < opinion > < WebLogicServer > < BEA-000360 > < server started operation >

  IntegratedWebLogicServer start time: 33630 ms.

  IntegratedWebLogicServer has begun.

  [Running the application on Server Instance IntegratedWebLogicServer SavedSearches...]

  [15:30:11]-deployment began.  ----

  [15:30:11] the target platform's (Weblogic 10.3).

  [15:30:18] # incomplete deployment.  ####

  [15:30:18] [SPI: J2EE deployment 260010] unable to connect to ' t3s: / / localhost:7102' as a user, "weblogic. Error returned: null

  [15:30:18] [SPI: J2EE deployment 260010] unable to connect to ' t3s: / / localhost:7102' as a user, "weblogic. Error returned: null

  [15:30:18] [SPI: J2EE deployment 260010] unable to connect to ' t3s: / / localhost:7102' as a user, "weblogic. Error returned: null

  [15:30:18] t3s: / / localhost:7102: Destination unreachable; nested exception is:

  java.net.ConnectException: Connection refused: connect. No router available at destination

  [15:30:18] Destination unreachable; nested exception is:

  java.net.ConnectException: Connection refused: connect. No router available at destination

  # Cannot run application SavedSearches due to the deployment on IntegratedWebLogicServer error.

  [SavedSearches application stopped and cancelled Server Instance IntegratedWebLogicServer]

  Thank you

  David Selvaraj

  Can user, you please tell us your exact Jdev version?

  The error message tells you that the server has been started, but is not available under the localhost:7102 of access

  The port doesn't look good for me. The built-in Server normally uses port 7101. You can check which port you configured for the server?

  You can check this on the "application server" tab and select the built-in server, right-click, and select Properties. In the dialog box, you see the configuration.

  Timo

• What configuration is required to start the application of P6, if deployed manually in weblogic?

  
  Hello

  I had faced a number of question time but did not have a solution yet.

  If I create the weblogic domain and deploy p6 web application manually and start the application, it becomes active.

  But when I tried to open it dosen't work. (I had faced this a lot of time problem)

  If I deploy the web application to p6 P6 itself create the new domain weblogic or existing user, installing it deployed and works perfectly well.

  I think that if we deploy P6 manually, you must configure something in weblogic.

  Can you please help.

  You can see the configuration guide for P6 EPPM manual for appropriate versions. Link below is 8.3. This will tell you the requirements for manual deployment.

  http://docs.Oracle.com/CD/E40266_01/English/Install_and_Config/Admin_PDF_Library/p6_and_weblogic_config_guide.PDF

  Thank you
  Sachin Gupta

• WebLogic error when starting the application

  Hello

  My JDev: 11.1.2.3.0.

  I get debug log console WebLogic error, but the application runs successfully.

  < 9 October 2013 08:36:45 AST > < error > < JMX > < BEA-149500 > < exception occurred during the recording of the signal no MBean.

  java.lang.IllegalArgumentException: recorded several instances with the same object name : com.bea:ServerRuntime = DefaultServer, Name = QICIntranet, Type = ApplicationRuntime new:weblogic.j2ee.J2EEApplicationRuntimeMBeanImpl@13acdcd existing weblogic.j2ee.J2EEApplicationRuntimeMBeanImpl@465d15

  at weblogic.management.jmx.ObjectNameManagerBase.registerObject(ObjectNameManagerBase.java:168)

  at weblogic.management.mbeanservers.internal.WLSObjectNameManager.lookupObjectName(WLSObjectNameManager.java:131)

  at weblogic.management.jmx.modelmbean.WLSModelMBeanFactory.registerWLSModelMBean(WLSModelMBeanFactory.java:87)

  to weblogic.management.mbeanservers.internal.RuntimeMBeanAgent$ 1.registered(RuntimeMBeanAgent.java:104)

  at weblogic.management.provider.core.RegistrationManagerBase.invokeRegistrationHandlers(RegistrationManagerBase.java:180)

  Truncated. check the log file full stacktrace

  >

  CurrentVersion = 1.5.0.0

  < 9 October 2013 08:36:46 AST > < error > < JMX > < BEA-149500 > < exception occurred during the recording of the signal no MBean.

  java.lang.IllegalArgumentException: recorded several instances with the same objectName: com.bea:ServerRuntime = DefaultServer, Name = default, ApplicationRuntime = QICIntranet, Type = WorkManagerRuntime new:weblogic.work.WorkManagerRuntimeMBeanImpl@1bd397b existing weblogic.work.WorkManagerRuntimeMBeanImpl@1c8c168

  at weblogic.management.jmx.ObjectNameManagerBase.registerObject(ObjectNameManagerBase.java:168)

  at weblogic.management.mbeanservers.internal.WLSObjectNameManager.lookupObjectName(WLSObjectNameManager.java:131)

  at weblogic.management.jmx.modelmbean.WLSModelMBeanFactory.registerWLSModelMBean(WLSModelMBeanFactory.java:87)

  to weblogic.management.mbeanservers.internal.RuntimeMBeanAgent$ 1.registered(RuntimeMBeanAgent.java:104)

  at weblogic.management.provider.core.RegistrationManagerBase.invokeRegistrationHandlers(RegistrationManagerBase.java:180)

  Truncated. check the log file full stacktrace

  >

  < 9 October 2013 08:36:46 AST > < error > < JMX > < BEA-149500 > < exception occurred during the recording of the signal no MBean.

  java.lang.IllegalArgumentException: recorded several instances with the same objectName: com.bea:ServerRuntime=DefaultServer,Name=default@QICIntranet@null,WorkManagerRuntime=default,ApplicationRuntime=QICIntranet,Type=RequestClassRuntime new:weblogic.work.RequestClassRuntimeMBeanImpl@178170e existing weblogic.work.RequestClassRuntimeMBeanImpl@111b59c

  at weblogic.management.jmx.ObjectNameManagerBase.registerObject(ObjectNameManagerBase.java:168)

  at weblogic.management.mbeanservers.internal.WLSObjectNameManager.lookupObjectName(WLSObjectNameManager.java:131)

  at weblogic.management.jmx.modelmbean.WLSModelMBeanFactory.registerWLSModelMBean(WLSModelMBeanFactory.java:87)

  to weblogic.management.mbeanservers.internal.RuntimeMBeanAgent$ 1.registered(RuntimeMBeanAgent.java:104)

  at weblogic.management.provider.core.RegistrationManagerBase.invokeRegistrationHandlers(RegistrationManagerBase.java:180)

  Truncated. check the log file full stacktrace

  >

  < FeatureUtils > < _resolveFeatures > Ignoring feature-dependency on the function "AdfDvtCommon".  There is no such feature.

  < FeatureUtils > < _resolveFeatures > Ignoring feature-dependency on the function "AdfDvtCommon".  There is no such feature.

  < FeatureUtils > < _resolveFeatures > Ignoring feature-dependency on the function "DvtDiagram".  There is no such feature.

  Thank you

  Hello, Derek.

  It is very similar to the present case:

  https://forums.Oracle.com/thread/2290229

  I hope this helps you.

  RFH.

• Please help me on the jdeveloper to weblogic application deployment

  At the beginning I just thought after developing an adf application then just deploy as an .ear file and deploy it in the weblogic console and everything will be ok. But actually I had a lot of problems. Then I had a tutorial for it and I do what he says step by step, but some new problems occurred. This is the tutorial I mentioned: [how-to: ADF Deployment Guide | http://www.oracle.com/webfolder/technetwork/jdeveloper/howto/11114/managedserver/wlsadfms.htm]
  
  Now, could someone tell how did deploy your adf application?
  
  Here are the errors I got.
  
  It's the packege of installation and the operating system I use:
  1. 6.3_x64 + jdeveloper11123.jar(include wls10.3.5) + adr centOS (the package name is ofm_appdev_generic_11.1.1.6.0_disk1_1of1.zip) [and earlier, I used a solaris11 of oracle vm and install jdeveloper11.1.2.3, the same probem occurred as CentOS.]
  2 Win7_x64 + jdeveoper11123.exe(include wls10.3.5) + adr mentioned above
  
  Here are the problems I get:
  in case 1, after that I installed the jdeveloper (using the sun jdk 1.7), the weblogic seems to be fine but I na not configure a domain. But after I opened a
  request (which I get from the oracle jdeveloper tutorial demo, which works well in my Win7 env) and I run it, the integrated weblogic can not get
  has started. First in the console it says identifier jrocket - is not recognized, then I edit the setDomainEnv.sh and the startWebLogic.sh file in the
  integrated wls area (that of the Director of .jdeveloper) to assign to the variable JAVA_VM - server. After that another problem emerged: when the
  WLS goes to the 'start-up' status, it is blocked and I turn to System Monitor shows only a thread of java using more than 1 GB of memory in my system
  and occupy 150% of my cpu (it's a dual-core computer). I wait about 5 minutes, when an error came up said "PermSize is too small".so I change the
  setDomainEnv.sh file to set the PermSize be 1024 m and MaxPermSize to 2048. (the name of the variable is something like that, maybe not the)
  exactly on time. "I think you can understand that one is). But the problem is still there.
  
  then in 2 cases in the first place the jdev and integrated wls works fine, but when I deploy an application that works well in one ear of the file, and then deploy it to a
  WLS (10.3.5) autonomous it never Works.the dumb mistake is something libraries of reference/dependencies was not found. Then I tried again a server connection to
  the autonomous wls and I got the tutorial [how_to_deploy_adf | http://www.oracle.com/webfolder/technetwork/jdeveloper/howto/11114/managedserver/wlsadfms.html], as the tutorial says I my standalone patch
  WLS with adr and everything is fine, no error reported. Then I tried the new server in the new slot machine the adminserver management and apply the
  the ADF model in him will overload / console em. But after I restarted the new server (by the console, and then by file stop + startweblogic.bat) the server is running
  the application in the new server is just 'not available '. I tried for three times in three computer, two of them are running win7, it runs Windows XP.
  
  I don't know what the problem is and I'm quite a beginner on this subject. Someone help me please. Thank you very much!
  
  respect, Neo.

  Neo,
  There are a few problems. First of all, jdev comes with its own jdk provided in the product (jdk 1.6_x). The next thing is that if you use JDev 11.1.2.3.0 to build an application you must use a wls 10.3.5 and 10.3.6 where you need to install the appropriate on runtime. In your case, you first install adf runtime 11.1.1.6.0 and then you need to install two patches that update the adf to 11.1.2.3.0 life. These husks are only available through support.oracle.com, which means that you need a support contract to get.
  More information you can find in my blog http://tompeez.wordpress.com/2011/09/14/jdeveloper-versions-vs-weblogic-server-versions/
  The rest of your problems disappear once you have installed the adf right on your server runtime.

  Timo

• Error during the deployment of business applications on weblogic 11 g 1 (10.3.3)

  Hi people,
  
  I got an error when starting a (ALRuleBean) .ear file.
  
  weblogic.management.ManagementException: [Deployer: 149188] there is no app named 'ALRuleBean' for the start of the operation. Operation cannot be performed until the server is restarted.
  
  Please help me.

  Hello

  Probably, you did some changes and you try to start the application.

  You can try to reboot the servers where the application was taken for target and start the server.

  Provide us with the sign of the full stack of the server logs, which will help us to know how challenging question is, if possible.

  Nice day!!

  ~ Ashish

• Unable to start the web application in weblogic server 11g R1 RBACx

  Hi friends,
  I have an error when starting Oracle Identity Analitycs 11 g R1, can someone help me solve the problem
  
  Server Weblogic Server logs at the start of the application of web rbacx.war:
  # < 7 April 2011 11:57:37 AM GMT - 05:00 > < WARNING > < HTTP > < vkpeoplesoft000 > < RbacxAdmin > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1302195457218 > < BEA-101162 > < org.springframework.web.util.Log4jConfigListener listener has not defined by the user: java.lang.IllegalStateException: failed to set web app system root property when the WAR file is not developed.
  
  java.lang.IllegalStateException: failed to set web app system root property when WAR file is not developed
  
  at org.springframework.web.util.WebUtils.setWebAppRootSystemProperty(WebUtils.java:139)
  
  at org.springframework.web.util.Log4jWebConfigurer.initLogging(Log4jWebConfigurer.java:118)
  
  at org.springframework.web.util.Log4jConfigListener.contextInitialized(Log4jConfigListener.java:47)
  
  to weblogic.servlet.internal.EventsManager$ FireContextListenerAction.run (EventsManager.java:481)
  
  at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
  
  at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
  
  at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
  
  at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1863)
  
  at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
  
  at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
  
  at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
  
  to weblogic.application.internal.flow.ModuleStateDriver$ 3.next(ModuleStateDriver.java:425)
  
  at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
  
  at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
  
  at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
  
  at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
  
  to weblogic.application.internal.flow.ModuleStateDriver$ 3.next(ModuleStateDriver.java:425)
  
  at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
  
  at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
  
  at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
  
  to weblogic.application.internal.BaseDeployment$ 2.next(BaseDeployment.java:1267)
  
  at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
  
  at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
  
  at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
  
  at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
  
  at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
  
  at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
  
  at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
  
  to weblogic.management.deploy.internal.DeploymentAdapter$ 1.doActivate(DeploymentAdapter.java:51)
  
  at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
  
  to weblogic.management.deploy.internal.AppTransition$ 2.transitionApp(AppTransition.java:30)
  
  at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
  
  at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
  
  at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
  
  at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
  
  at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
  
  at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
  
  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
  
  at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
  
  # < 7 April 2011 11:57:37 AM GMT - 05:00 > < Info > < hats > < vkpeoplesoft000 > < RbacxAdmin > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1302195457234 > < BEA-149059 > < Module rbacx.war of application rbacx is transition of STATE_ADMIN of STATE_PREPARED on the RbacxAdmin server. >
  
  # < 7 April 2011 11:57:37 AM GMT - 05:00 > < Info > < ServletContext-/ rbacx > < vkpeoplesoft000 > < RbacxAdmin > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < < > anonymous > > <>< 1302195457234 > < BEA-000000 > < log4j stop >
  
  # < 7 April 2011 11:57:37 AM GMT - 05:00 > < Info > < hats > < vkpeoplesoft000 > < RbacxAdmin > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1302195457265 > < BEA-149060 > < Module rbacx.war of application rbacx successfully increased from STATE_ADMIN to STATE_PREPARED on the RbacxAdmin server. >
  
  See the full changelog:
  http://YourPaste.NET/7984
  
  Recognizing

  Hello

  I could be wrong and if you have not already, do not use to extend the file rbacx.war... WebLogic expand the war first file and then try to deploy the directory located in Weblogic.

  To extend progressively the command something like... jar xvf-./rbacx.war

  Kind regards
  Daniel

• Serve the application automatically under Weblogic servers logs

  Hello
  
  I am studying serving them in Weblogic server.
  
  Could someone help me to find a setting (if it exists) in Weblogic properties files, which will serve the application automatically logs after "n" number of days.
  
  
  for example, in the D:\Hyperion\deployments\WebLogic9\servers\aas\logs directory, I see many eas log files created with the extensions of .log00001 to .log00427. Is it possible to remove these automatically without using windows scripts.
  
  
  Thank you
  Prasad

  This is configured in the logging of every server (servers-> servername-> logging) tab. Set the type of rotation for 'Time', to keep files and rotation interval (default value of 24 hours), etc. This will keep the files to a fixed number.

• Application of the fix in weblogic

  Hello
  
  I'm new to weblogic.
  Now, I need to apply the patch for weblogic.
  Could you please share some doc or steps to apply the patch via the command prompt to weblogic server running on Linux platform.
  
  Thanks in advance.

  If you have access to My Oracle Support (MOS), you can find detailed instructions with examples in KM note ID: 876004.1

  Same steps for your reference:
  1. download the patch to My Oracle Support (MOS). For more details, please see the master Note: how to locate and download the patches for WebLogic Server using My Oracle Support Note 1302053.1.
  2. extract the contents of the zip file: you will have a file jar and patch - catalog_xxx.xml. A readme file can also be included.
  3 copy the files (for example, E5W8.jar) and patch - catalog_xxx.xml in the zip on the target machine. You don't need the file readme. Copy the files into the appropriate directory cache_dir on the target system: for example, $MIDDLEWARE_HOME, utils, bsu, cache_dir.
  4. run the script $MIDDLEWARE_HOME/utils/bsu/bsu.sh as shown in the example to apply the patch below
  SYNTAX:
  . /BSU.sh - prod_dir = $WEBLOGIC_HOME - patchlist = - verbose--install
  FOR EXAMPLE:
  . /BSU.sh-prod_dir=/opt/Oracle/wlserver_10.3 - patchlist = E5W8-verbose - install

  NOTE: Before you run the above commands, the servers must be stopped. After you apply the fix, it can be restarted.

  Arun