Creating Weblogic domain with Admin Server and managed servers on different
I am trying to create Weblogic domain where Admin Server and managed servers on different machines. However I am unable to find any steps which would allow me to do so. The config.sh script always creates an Admin Server. Please help.
Whilst the method that Lawrence gives can result in a domain that is perfectly functional, it is a method that can result in errors as you are having to enter the same information twice. Also you will create two admin servers, as the second domain creation will have the console added to it on the renamed admin server and this will give issues.
The best method to create a domain spamming multiple physical machines, is to create the domain with all the components on the first machine. This means planning the domain and making sure all components are added once; so having the information about the domain written out is wise. Ensure that the WLS software is installed in the same path on each machine before starting.
Then copy the domain that you have created from one machine to the other, keeping the same paths. You can simply copy (I've used this method multiple times without issue) but the supported way would be to use the WLST PACK and UNPACK methods. These create and extract domains from templates. Some more information on these is given here -> http://docs.oracle.com/cd/E13179_01/common/docs100/pack/intro.html#wp1069056
Similar Messages
-
Problem creating a domain w/ one Admin Server and Managed Server
I went through the config wizard (Weblogic 10.2) and set up a domain w/ 1 Admin Server and Managed Server. When I start the Admin server I get the following error:
####<Jul 30, 2008 6:05:28 PM PDT> <Error> <Store> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328289> <BEA-280061> <The persistent store "pfProliferationJMSStore" could not be deployed: weblogic.store.PersistentStoreException: Can't find JDBC DataSource portalFrameworkPoolNeverXA: javax.naming.NameNotFoundException: Unable to resolve 'portalFrameworkPoolNeverXA'. Resolved ''; remaining name 'portalFrameworkPoolNeverXA'
weblogic.store.PersistentStoreException: Can't find JDBC DataSource portalFrameworkPoolNeverXA: javax.naming.NameNotFoundException: Unable to resolve 'portalFrameworkPoolNeverXA'. Resolved ''; remaining name 'portalFrameworkPoolNeverXA'
at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:105)
at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:184)
at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:162)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:57)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
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)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
javax.naming.NameNotFoundException: Unable to resolve 'portalFrameworkPoolNeverXA'. Resolved ''; remaining name 'portalFrameworkPoolNeverXA'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1138)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:251)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:205)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:100)
at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:184)
at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:162)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:57)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
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)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Jul 30, 2008 6:05:28 PM PDT> <Warning> <Management> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328289> <BEA-141197> <The deployment of pfProliferationJMSStore failed.
weblogic.management.DeploymentException:
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:60)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
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)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
javax.naming.NameNotFoundException: Unable to resolve 'portalFrameworkPoolNeverXA'. Resolved ''; remaining name 'portalFrameworkPoolNeverXA'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1138)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:251)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:205)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:100)
at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:184)
at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:162)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:57)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
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)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Jul 30, 2008 6:05:28 PM PDT> <Error> <JMS> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328368> <BEA-040123> <Failed to start JMS Server "pfJMSServer" due to weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist.
weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:296)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:184)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
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)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Jul 30, 2008 6:05:28 PM PDT> <Warning> <Management> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328368> <BEA-141197> <The deployment of pfJMSServer failed.
weblogic.management.DeploymentException: Internalrror activating the JMS Server pfJMSServer: weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:198)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
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)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:296)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:184)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
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)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Jul 30, 2008 6:05:28 PM PDT> <Error> <Deployer> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328461> <BEA-149231> <Unable to set the activation state to true for the application 'pf-proliferation-jms'.
weblogic.application.ModuleException: ERROR: Could not activate pf-proliferation-jms!pfProliferationQueue
at weblogic.jms.backend.BEDestinationRuntimeDelegate.activate(BEDestinationRuntimeDelegate.java:238)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1717)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
at weblogic.jms.module.JMSModule.activate(JMSModule.java:332)
at weblogic.jms.module.ModuleCoordinator.activate(ModuleCoordinator.java:182)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:182)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:359)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:42)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
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)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
weblogic.messaging.kernel.KernelException: The Messaging Kernel pfJMSServer has not yet been opened
at weblogic.messaging.kernel.internal.KernelImpl.checkOpened(KernelImpl.java:191)
at weblogic.messaging.kernel.internal.DestinationImpl.activate(DestinationImpl.java:279)
at weblogic.messaging.kernel.internal.QueueImpl.activate(QueueImpl.java:1633)
at weblogic.messaging.kernel.internal.DestinationImpl.resume(DestinationImpl.java:263)
at weblogic.messaging.kernel.internal.QueueImpl.resume(QueueImpl.java:1809)
at weblogic.jms.backend.BEDestinationImpl.start(BEDestinationImpl.java:609)
at weblogic.jms.backend.BEDestinationRuntimeDelegate.activate(BEDestinationRuntimeDelegate.java:235)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1717)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
at weblogic.jms.module.JMSModule.activate(JMSModule.java:332)
at weblogic.jms.module.ModuleCoordinator.activate(ModuleCoordinator.java:182)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:182)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:359)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:42)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
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)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>I am using the default db the installation uses which is PointBase. I am not using any specific db, JDBC Datasource/Connection pool Configuration.
Just to try something different, I tried creating a domain w/ one Admin and Managed Server which uses a Cluster and I did not get any errors. From what I read, a cluster is not necessary but not sure why it works without errors w/ a cluster.
I will try commenting out the datasource from the config and see what happens and will let you know. -
Different service packs in admin server and managed server
Hi,
Has anybody successfully used a WebLogic 6.1 SP1 managed server that
connects to a WebLogic 6.1 SP 2 admin server?
BEA's docs claim:
"The Administration Server must be running the same version of
WebLogic Server as the Managed Servers in its domain. The
Administration Server must also have the same or later service pack
installed as the Managed Servers in its domain. For example, the
Administration Server could be running version 6.1, Service Pack 2
while the Managed Servers are running version 6.1, Service Pack 1."
This is precisely what we want to do, but it's not working. In this
case, we need to run the admin server and managed server on the same
machine, but we need the managed server to run SP 1 to work around a
bug in SP 2. So to our initial installation of WebLogic 6.1 SP 2,
where I run the admin server, I added a second installation, this time
WebLogic 6.1 SP 1, with a different BEA_HOME. When I start the
managed server from this second installation, I can see from the logs
that it is starting up correctly as 6.1 SP 1. But then it fails with
a ClassCastException when connecting to the admin server (I have
included the stack trace below). This seems typical of version
compatibility problems I've had when I've tried connecting to a server
with a client of a different version.
But in this case, you are supposed to be able to have the managed
server with a lower service pack. Does this work for anybody? Has
anybody encountered the problem I'm having? Note that the servers are
not clustered, if that makes any difference, and we have a custom
security realm in addition to the default file realm (though "system"
of course is in the default file realm).
Thanks in advance for any help,
Jim Doyle
[email protected]
####<Aug 8, 2002 10:25:38 AM EDT> <Emergency> <Server></server>
<chile.iso-ne.com> <webui
server> <main> <system> <> <000000> <Unable to initialize the server:
'Fatal ini
tialization exception
Throwable: java.lang.ClassCastException:
weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException:
weblogic.security.acl.DefaultUserInfoImpl
at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:164)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack traceHi,
Has anybody successfully used a WebLogic 6.1 SP1 managed server that
connects to a WebLogic 6.1 SP 2 admin server?
BEA's docs claim:
"The Administration Server must be running the same version of
WebLogic Server as the Managed Servers in its domain. The
Administration Server must also have the same or later service pack
installed as the Managed Servers in its domain. For example, the
Administration Server could be running version 6.1, Service Pack 2
while the Managed Servers are running version 6.1, Service Pack 1."
This is precisely what we want to do, but it's not working. In this
case, we need to run the admin server and managed server on the same
machine, but we need the managed server to run SP 1 to work around a
bug in SP 2. So to our initial installation of WebLogic 6.1 SP 2,
where I run the admin server, I added a second installation, this time
WebLogic 6.1 SP 1, with a different BEA_HOME. When I start the
managed server from this second installation, I can see from the logs
that it is starting up correctly as 6.1 SP 1. But then it fails with
a ClassCastException when connecting to the admin server (I have
included the stack trace below). This seems typical of version
compatibility problems I've had when I've tried connecting to a server
with a client of a different version.
But in this case, you are supposed to be able to have the managed
server with a lower service pack. Does this work for anybody? Has
anybody encountered the problem I'm having? Note that the servers are
not clustered, if that makes any difference, and we have a custom
security realm in addition to the default file realm (though "system"
of course is in the default file realm).
Thanks in advance for any help,
Jim Doyle
[email protected]
####<Aug 8, 2002 10:25:38 AM EDT> <Emergency> <Server></server>
<chile.iso-ne.com> <webui
server> <main> <system> <> <000000> <Unable to initialize the server:
'Fatal ini
tialization exception
Throwable: java.lang.ClassCastException:
weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException:
weblogic.security.acl.DefaultUserInfoImpl
at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:164)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace -
Communication protocol between Admin Server and Managed Server
Hello - I am hoping someone can help me here to understand the communication protocols used in my setup.
Here is my understanding of the protocol that are used between each component.
End User <--->HTTPS<--->LoadBalancer Device<--->HTTPS<--->Web Server<---->HTTPS<--->WebLogic Server(Managed Server)<--->LDAP/JDBC<-->Data tier components
AdminServer<--->T3<--->Managed Server i.e. The communication protocol between Admin Server and Managed server is T3
The communication protocol between Managed Servers running in one cluster on two seperate machine is What?
Thank you.Hello, interesting question.
In the documentation " [cluster multicast communication|http://download.oracle.com/docs/cd/E13222_01/wls/docs90/cluster/features.html#1007001] " don't specify the used protocol to pack the information for example in a session replication.
Although in a session replication all objects must be serializable i don't think rmi protocol is used.
I hope some expert give us some light in this issue :-)
http://download.oracle.com/docs/cd/E13222_01/wls/docs90/cluster/features.html#1007001 -
Admin Server and Managed server startup problem
Hi,
My weblogic server version is 11g and OS is Linux.
When i am trying to start the admin server a frer i created the domain i am getting following exceptions in the server log and server is shutting down.
FPR6 4008000000000000 (f: 0.000000, d: 3.000000e+00)
FPR7 4010000000000000 (f: 0.000000, d: 4.000000e+00)
FPR8 006f007300690078 (f: 6881400.000000, d: 1.379624e-306)
FPR9 0053006f0063006b (f: 6488171.000000, d: 4.228017e-307)
FPR10 00650074004d0075 (f: 5046389.000000, d: 9.346098e-307)
FPR11 0078006500720024 (f: 7471140.000000, d: 2.136208e-306)
FPR12 3fe8000000000000 (f: 0.000000, d: 7.500000e-01)
FPR13 4068000000000000 (f: 0.000000, d: 1.920000e+02)
FPR14 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR15 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR16 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR17 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR18 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR19 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR20 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR21 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR22 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR23 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR24 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR25 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR26 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR27 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR28 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR29 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR30 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR31 0000000000000000 (f: 0.000000, d: 0.000000e+00)
Module=/usr/Oracle/Middleware/wlserver_10.3/server/native/aix/ppc64/libmuxer.so
Module_base_address=0800000000003000
Target=2_40_20090409_033254_BHdSMr (AIX 5.3)
CPU=ppc64 (4 logical CPUs) (0x220000000 RAM)
- Stack Backtrace -
/usr/Oracle/Middleware/wlserver_10.3/server/native/aix/ppc64/libmuxer.so:0x000046F4 [0x00003000 +0x000016F4]
/usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005F7088 [0x005AF000 +0x00048088]
/usr/java6_64/jre/lib/ppc64/default/libjclscar_24.so:0x00FB8228 [0x00FAB000 +0x0000D228]
/usr/java6_64/jre/lib/ppc64/default/libjclscar_24.so:0x00FB884C [0x00FAB000 +0x0000D84C]
/usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005EDE08 [0x005AF000 +0x0003EE08]
/usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005EF600 [0x005AF000 +0x00040600]
/usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005EF3A8 [0x005AF000 +0x000403A8]
/usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005EC1A0 [0x005AF000 +0x0003D1A0]
/usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005BB5B4 [0x005AF000 +0x0000C5B4]
/usr/java6_64/jre/lib/ppc64/default/libj9prt24.so:0x0064C21C [0x00649000 +0x0000321C]
/usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005BB4D0 [0x005AF000 +0x0000C4D0]
/usr/java6_64/jre/lib/ppc64/default/libj9thr24.so:0x006375F0 [0x00635000 +0x000025F0]
/usr/lib/libpthreads.a:0x005084F0 [0x00505000 +0x000034F0]
0x00000000
JVMDUMP006I Processing dump event "gpf", detail "" - please wait.
JVMDUMP007I JVM Requesting System dump using '/usr/Oracle/Middleware/user_projects/domains/test_domain/core.20100513.125306.852102.0001.dmp'
JVMDUMP010I System dump written to /usr/Oracle/Middleware/user_projects/domains/test_domain/core.20100513.125306.852102.0001.dmp
JVMDUMP007I JVM Requesting Snap dump using '/usr/Oracle/Middleware/user_projects/domains/test_domain/Snap.20100513.125306.852102.0002.trc'
UTE105: Error writing header to tracefile: /usr/Oracle/Middleware/user_projects/domains/test_domain/Snap.20100513.125306.852102.0002.trc
JVMDUMP010I Snap dump written to /usr/Oracle/Middleware/user_projects/domains/test_domain/Snap.20100513.125306.852102.0002.trc
JVMDUMP007I JVM Requesting Java dump using '/usr/Oracle/Middleware/user_projects/domains/test_domain/javacore.20100513.125306.852102.0003.txt'
JVMDUMP012E Error in Java dump: /usr/Oracle/Middleware/user_projects/domains/test_domain/javacore.20100513.125306.852102.0003.txt
JVMDUMP013I Processed dump event "gpf", detail "".
After adding "<native-io-enabled>false</native-io-enabled>" in cofig.xml as shown below , i am able to start the admin server.
<server>
<name>AdminServer</name>
<native-io-enabled>false</native-io-enabled>
<listen-port>9595</listen-port>
<listen-address>10.10.15.16</listen-address>
</server>
i did the same thing for managed servers to start the server.
My Question is:
Are we missing any configurations/settings while creating domain?
Is there any other option to start the server without adding <native-io-enabled>false</native-io-enabled>?
Regards,
NagaHi,
my managed server heap size properties are
-XX:PermSize=256m -XX:MaxPermSize=256m -Xms256M -Xmx512M
But the error with Admin server also and we are not providing any heap size properties to admin server. Becuase while creating the domain, i haven't got any
option to set the heap size for Admin server. Am i required to set heap size properties in Admin server by following this path "Summary of Servers >AdminServer->Server start->"Arguements"?
Sorry, i am not able to find activity.log. Can you please tell me the location where i can find acivity.log. If i am not wrong, are you taling about serverOut.log? If that is serverOut.log, please tell me which log you require? is it admin server or managed server? -
Weblogic server and managed servers sudden shutdown
Hi,
when trying to restart both the admin and managed osb servers. after some time the admin and managed servers are getting shut down. This is what the information i got from logs. Appreciate your help in this regard
####<Aug 18, 2011 12:51:44 PM EDT> <Info> <Health> <weblogic.GCMonitor> <<anonymous>> <> <8beb4c4d69347bb8:6c6553af:131ddaf5db4:-7ff7-0000000000000011> <1313686304697> <BEA-310002> <38% of the total memory in the server is free>
####<Aug 18, 2011 12:52:06 PM EDT> <Error> <JDBC> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <8beb4c4d69347bb8:6c6553af:131ddaf5db4:-7ff7-0000000000000109> <1313686326579> <BEA-001112> <Test "SELECT 1 FROM DUAL" set up for pool "GLTOdatasource" failed with exception: "oracle.jdbc.xa.OracleXAException".>
####<Aug 18, 2011 12:52:06 PM EDT> <Info> <JDBC> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <8beb4c4d69347bb8:6c6553af:131ddaf5db4:-7ff7-0000000000000109> <1313686326580> <BEA-001128> <Connection for pool "GLTOdatasource" closed.>
####<Aug 18, 2011 12:52:44 PM EDT> <Info> <Health> <weblogic.GCMonitor> <<anonymous>> <> <8beb4c4d69347bb8:6c6553af:131ddaf5db4:-7ff7-0000000000000011> <1313686364766> <BEA-310002> <61% of the total memory in the server is free>
####<Aug 18, 2011 12:56:45 PM EDT> <Info> <Health> <weblogic.GCMonitor> <<anonymous>> <> <8beb4c4d69347bb8:6c6553af:131ddaf5db4:-7ff7-0000000000000011> <1313686605051> <BEA-310002> <44% of the total memory in the server is free>
####<Aug 18, 2011 12:58:18 PM EDT> <Info> <Security> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <8beb4c4d69347bb8:6c6553af:131ddaf5db4:-7ff7-0000000000000111> <1313686698580> <BEA-090516> <The CredentialMapper provider has preexisting LDAP data.>
####<Aug 18, 2011 1:02:23 PM EDT> <Notice> <WebLogicServer> <Thread-1> <<WLS Kernel>> <> <8beb4c4d69347bb8:6c6553af:131ddaf5db4:-7ff7-0000000000000117> <1313686943979> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>
####<Aug 18, 2011 1:02:23 PM EDT> <Alert> <gifosb_admin> <Thread-1> <<WLS Kernel>> <> <8beb4c4d69347bb8:6c6553af:131ddaf5db4:-7ff7-0000000000000117> <1313686943996> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>>
####<Aug 18, 2011 1:02:24 PM EDT> <Notice> <WebLogicServer> <Thread-1> <<WLS Kernel>> <> <8beb4c4d69347bb8:6c6553af:131ddaf5db4:-7ff7-0000000000000117> <1313686944005> <BEA-000365> <Server state changed to FORCE_SUSPENDING>
Thanks,
Bharath<JVM called WLS shutdown hook. The server will force shutdown now>This is your JVM process which is getting killed and hence server is forced to shutdown. On which OS, servers are running? How are you starting the server? If you are on windows, DO NOT close the command prompt through which you started the server.
Regards,
Anuj -
Can I run the admin and managed servers as different users?
in unix, is it possible to run my admin and manged servers as different users with
7.1?As long as users are in admin group, there could be different users starting different
servers.
"Frank" <[email protected]> wrote:
>
"Erik Johnson" <[email protected]> wrote:
Hi, Frank.
Could you be a little more specific about what it is you want to do?
Thanks.
erikUh, I'm on unix, I have Weblogic 7.0 service pack4. I have 1 managed
server and
I have one admin server...Can I run the admin server as user 'hithere'
and run
the managed server as user, 'byethere'......
"Frank" <[email protected]> wrote:
in unix, is it possible to run my admin and manged servers as different
users with
7.1? -
Keep weblogic admin server and managed server running after exiting PUTTY
How do i keep my managed servers and admin servers running on SOLARIS (unix) boxes even after exiting putty and starting them? Do i need to create like a cron job or something?
*(after running nohup ./startWebLogic.sh i get Sending output to nohup.out and hangs there)*
out put from nohup.out =>
JAVA Memory arguments: -Xms256m -Xmx512m -XX:MaxPermSize=256m
WLS Start Mode=Production
CLASSPATH=/usr/Oracle/Middleware/patch_wls1034/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/usr/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/d/ct0/home/shahs06/JAVA/jdk1.6.0_25/lib/tools.jar:/usr/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/usr/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/usr/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.4.0.jar:/usr/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/usr/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/usr/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/usr/Oracle/Middleware/wlserver_10.3/common/derby/lib/derbyclient.jar:/usr/Oracle/Middleware/wlserver_10.3/server/lib/xqrl.jar
PATH=/usr/Oracle/Middleware/wlserver_10.3/server/bin:/usr/Oracle/Middleware/modules/org.apache.ant_1.7.1/bin:/d/ct0/home/shahs06/JAVA/jdk1.6.0_25/jre/bin:/d/ct0/home/shahs06/JAVA/jdk1.6.0_25/bin:/usr/sbin:/usr/bin:/usr/local/bin:/d/ct0/home/shahs06/JAVA/jdk1.6.0_25/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_25"
Java(TM) SE Runtime Environment (build 1.6.0_25-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.0-b11, mixed mode)
Starting WLS with line:
/d/ct0/home/shahs06/JAVA/jdk1.6.0_25/bin/java -server -d64 -Xms256m -Xmx512m -XX:MaxPermSize=256m -Dweblogic.Name=AdminServer -Djava.security.policy=/usr/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.ProductionModeEnabled=true -da -Dplatform.home=/usr/Oracle/Middleware/wlserver_10.3 -Dwls.home=/usr/Oracle/Middleware/wlserver_10.3/server -Dweblogic.home=/usr/Oracle/Middleware/wlserver_10.3/server -Dweblogic.management.discover=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/usr/Oracle/Middleware/patch_wls1034/profiles/default/sysext_manifest_classpath:/usr/Oracle/Middleware/patch_ocp360/profiles/default/sysext_manifest_classpath weblogic.Server
<9-May-2011 1:33:56 o'clock PM PDT> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<9-May-2011 1:33:57 o'clock PM PDT> <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>
<9-May-2011 1:33:59 o'clock PM PDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.0-b11 from Sun Microsystems Inc.>
<9-May-2011 1:34:04 o'clock PM PDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.4.0 Fri Dec 17 20:47:33 PST 2010 1384255 >
<9-May-2011 1:34:12 o'clock PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<9-May-2011 1:34:12 o'clock PM PDT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<9-May-2011 1:34:12 o'clock PM PDT> <Notice> <Log Management> <BEA-170019> <The server log file /usr/Oracle/Middleware/user_projects/domains/base_domain/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.>
<9-May-2011 1:34:27 o'clock PM PDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<9-May-2011 1:34:45 o'clock PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<9-May-2011 1:34:45 o'clock PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
9-May-2011 1:34:58 PM com.sun.faces.config.ConfigureListener contextInitialized
INFO: Initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/console'
9-May-2011 1:34:58 PM com.sun.faces.config.ConfigureListener contextInitialized
INFO: Completed initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/console'
<9-May-2011 1:35:04 o'clock PM PDT> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<9-May-2011 1:35:04 o'clock PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<9-May-2011 1:35:04 o'clock PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<9-May-2011 1:35:06 o'clock PM PDT> <Notice> <Security> <BEA-090171> <Loading the identity certificate and private key stored under the alias DemoIdentity from the jks keystore file /usr/Oracle/Middleware/wlserver_10.3/server/lib/DemoIdentity.jks.>
<9-May-2011 1:35:06 o'clock PM PDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /usr/Oracle/Middleware/wlserver_10.3/server/lib/DemoTrust.jks.>
<9-May-2011 1:35:06 o'clock PM PDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /d/ct0/home/shahs06/JAVA/jdk1.6.0_25/jre/lib/security/cacerts.>
<9-May-2011 1:35:06 o'clock PM PDT> <Alert> <Security> <BEA-090152> <Demo trusted CA certificate is being used in production mode: [
Version: V3
Subject: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
Key: SunPKCS11-Solaris RSA public key, 512 bits (id 4371458208, session object)
modulus: 9550192877869244258838480703390456015046425375252278279190673063544122510925482179963329236052146047356415957587628011282484772458983977898996276815440753
public exponent: 65537
Validity: [From: Thu Mar 21 12:12:27 PST 2002,
To: Tue Mar 22 13:12:27 PDT 2022]
Issuer: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
SerialNumber: [ 33f10648 fcde0deb 4199921f d64537f4]
Certificate Extensions: 1
[1]: ObjectId: 2.5.29.15 Criticality=true
KeyUsage [
Key_CertSign
] -
How to setup WebLogic Admin Server and Managed Server
Hi,
I working to setup a Weblogic admin and managed server but fail.
May i know the correct steps to setup the system ?
Tx.TX. I will proceed to upload more logs here later.
Anyway I notice that after i follow the guide to setup the admin and managed server, I only able to access the web apps on admin server. I can not access web apps for managed server.
I setup the admin server using port 7001 and managed server using port 7003 based on oracle guide.
I found weird here. when I browse to http://adminserver:7001/apps, it works. But when i browse to http://managedserver:7003/apps it does not work.
But funny thing is when i browse to http://adminserver:7003/apps, it works.
I confuse that which configuration I have done is incorrect and have this result???
besides that I notice that in the nodemanager setting...the listening address is set to localhost and it works. If i configure it to IP address, it will give me errors.
Edited by: Wilson78 on Dec 22, 2008 12:29 PM -
Admin server and Managed Server not Running
Hi,
Admin server doesnot change its state to RUNNING from STARTING. Even after hrs of starting the server.. the satus is as shown.
<Jun 1, 2011 10:22:59 AM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.4.0 Fri Dec 17 20:47:33 PST 2010 1384255 >
<Jun 1, 2011 10:23:01 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Jun 1, 2011 10:23:01 AM IST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Jun 1, 2011 10:23:02 AM IST> <Notice> <LoggingService> <BEA-320400> <The log file D:\OSB11g_Home\user_projects\domains\osb11g_domain\servers\AdminServer\logs\AdminServ
er.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Jun 1, 2011 10:23:02 AM IST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to D:\OSB11g_Home\user_projects\domains\osb11g_domain\servers\AdminS
erver\logs\AdminServer.log00056. Log messages will continue to be logged in D:\OSB11g_Home\user_projects\domains\osb11g_domain\servers\AdminServer\logs\AdminServer.log.
>
<Jun 1, 2011 10:23:02 AM IST> <Notice> <Log Management> <BEA-170019> <The server log file D:\OSB11g_Home\user_projects\domains\osb11g_domain\servers\AdminServer\logs\Ad
minServer.log is opened. All server side log events will be written to this file.>
<Jun 1, 2011 10:23:07 AM IST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Jun 1, 2011 10:23:17 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Jun 1, 2011 10:23:17 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
It just stops at this stage. Facing the same prob with Managed Server as well.
I tried Killing all the java process, as well as updated boot.properties file and restarted which dint help.
can anyone Help me on this.
Thanks & Regards,
InduYes, i do have applications deployed.
Here is my config.xml
<?xml version='1.0' encoding='UTF-8'?>
<domain xmlns="http://xmlns.oracle.com/weblogic/domain" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/security/xacml http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator/1.0/passwordvalidator.xsd http://xmlns.oracle.com/weblogic/domain http://xmlns.oracle.com/weblogic/1.0/domain.xsd http://xmlns.oracle.com/weblogic/security http://xmlns.oracle.com/weblogic/1.0/security.xsd http://xmlns.oracle.com/weblogic/security/wls http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.xsd">
<name>osb11g_domain</name>
<domain-version>10.3.4.0</domain-version>
<security-configuration>
<name>osb11g_domain</name>
<realm>
<sec:authentication-provider xsi:type="wls:default-authenticatorType">
<wls:use-retrieved-user-name-as-principal>true</wls:use-retrieved-user-name-as-principal>
</sec:authentication-provider>
<sec:authentication-provider xsi:type="wls:default-identity-asserterType">
<sec:active-type>AuthenticatedUser</sec:active-type>
</sec:authentication-provider>
<sec:role-mapper xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
<sec:authorizer xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
<sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
<sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
<sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
<sec:name>myrealm</sec:name>
<sec:password-validator xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator" xsi:type="pas:system-password-validatorType">
<sec:name>SystemPasswordValidator</sec:name>
<pas:min-password-length>8</pas:min-password-length>
<pas:min-numeric-or-special-characters>1</pas:min-numeric-or-special-characters>
</sec:password-validator>
</realm>
<default-realm>myrealm</default-realm>
<credential-encrypted>{AES}sLWSLcQMQZchzo4SR4mjU9t+aXrRFlW76I0/Ie1V/yHuMxEZuy5UXjjl3D0Nzrx43Y4+uYwH+l4fz2RHNJdUBNyjN06wyjujzfOf1o61GuXTvWeBrT5LAIlAhstSWvMZ</credential-encrypted>
<node-manager-username>weblogic</node-manager-username>
<node-manager-password-encrypted>{AES}vIICdR6YTBvPsRxkaKtwek5yf6wEPemMg5NLqoMoSSY=</node-manager-password-encrypted>
</security-configuration>
<server>
<name>AdminServer</name>
<listen-address>localhost</listen-address>
<server-diagnostic-config>
<name>AdminServer</name>
<diagnostic-context-enabled>true</diagnostic-context-enabled>
</server-diagnostic-config>
</server>
<server>
<name>osb_server1</name>
<listen-port>8011</listen-port>
<listen-address></listen-address>
<server-diagnostic-config>
<name>osb_server1</name>
<diagnostic-context-enabled>true</diagnostic-context-enabled>
</server-diagnostic-config>
</server>
<embedded-ldap>
<name>osb11g_domain</name>
<credential-encrypted>{AES}y3pEDYlwHWeJTJDCHip1ctAwdCh6Q+4nW09EsH6rlDtzqCsaxpc5fx4SoASAKkIo</credential-encrypted>
</embedded-ldap>
<configuration-version>10.3.4.0</configuration-version>
<app-deployment>
<name>FMW Welcome Page Application#11.1.0.0.0</name>
<target>AdminServer</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.jrf_11.1.1/fmw-welcome.ear</source-path>
<deployment-order>5</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>wsil-wls</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.webservices_11.1.1/wsil-wls.ear</source-path>
<deployment-order>5</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>DMS Application#11.1.1.1.0</name>
<target>AdminServer,osb_server1</target>
<module-type>war</module-type>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.dms_11.1.1/dms.war</source-path>
<deployment-order>5</deployment-order>
<security-dd-model>CustomRoles</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>FileAdapter</name>
<target>AdminServer,osb_server1</target>
<module-type>rar</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/soa/connectors/FileAdapter.rar</source-path>
<deployment-order>321</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>DbAdapter</name>
<target>AdminServer,osb_server1</target>
<module-type>rar</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/soa/connectors/DbAdapter.rar</source-path>
<deployment-order>322</deployment-order>
<plan-dir xsi:nil="true"></plan-dir>
<plan-path>D:\OSB11g_Home\Oracle_OSB1\soa\connectors\Plan.xml</plan-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>JmsAdapter</name>
<target>AdminServer,osb_server1</target>
<module-type>rar</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/soa/connectors/JmsAdapter.rar</source-path>
<deployment-order>323</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>AqAdapter</name>
<target>AdminServer,osb_server1</target>
<module-type>rar</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/soa/connectors/AqAdapter.rar</source-path>
<deployment-order>324</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>FtpAdapter</name>
<target>AdminServer,osb_server1</target>
<module-type>rar</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/soa/connectors/FtpAdapter.rar</source-path>
<deployment-order>325</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>SocketAdapter</name>
<target>AdminServer,osb_server1</target>
<module-type>rar</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/soa/connectors/SocketAdapter.rar</source-path>
<deployment-order>326</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>MQSeriesAdapter</name>
<target>AdminServer,osb_server1</target>
<module-type>rar</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/soa/connectors/MQSeriesAdapter.rar</source-path>
<deployment-order>327</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>OracleAppsAdapter</name>
<target>AdminServer,osb_server1</target>
<module-type>rar</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/soa/connectors/AppsAdapter.rar</source-path>
<deployment-order>328</deployment-order>
<plan-dir xsi:nil="true"></plan-dir>
<plan-path>D:\OSB11g_Home\Oracle_OSB1\soa\connectors\Plan_Apps.xml</plan-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>OracleBamAdapter</name>
<target>AdminServer,osb_server1</target>
<module-type>rar</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/soa/connectors/OracleBamAdapter.rar</source-path>
<deployment-order>329</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>ALSB Cluster Singleton Marker Application</name>
<target>osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/common/clustersingletonmarker.ear</source-path>
<deployment-order>80</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>ALSB Domain Singleton Marker Application</name>
<target>osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/common/domainsingletonmarker.ear</source-path>
<deployment-order>85</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>ALSB Framework Starter Application</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/common/frameworkstarter.ear</source-path>
<deployment-order>90</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>ALSB Coherence Cache Provider</name>
<target>osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/coherence.ear</source-path>
<deployment-order>93</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>XBus Kernel</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/kernelEar</source-path>
<sub-deployment>
<name>/httpTransport</name>
<module-type>war</module-type>
<compatibility-name>XBus HTTP Transport Webapp</compatibility-name>
</sub-deployment>
<deployment-order>95</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>ALSB UDDI Manager</name>
<target>AdminServer</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/uddiEar</source-path>
<deployment-order>122</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>ALSB Subscription Listener</name>
<target>osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/uddi_subscription</source-path>
<deployment-order>123</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>JMS Reporting Provider</name>
<target>osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/common/jmsreportprovider.ear</source-path>
<deployment-order>125</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>Message Reporting Purger</name>
<target>osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/common/msgpurger.ear</source-path>
<deployment-order>126</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>Ftp Transport Provider</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<compatibility-name>FTP Transport</compatibility-name>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/transports/ftp_transport.ear</source-path>
<sub-deployment>
<name>ftp_transport.jar</name>
<target>osb_server1</target>
<module-type>jar</module-type>
<compatibility-name>ftp_transport.jar</compatibility-name>
</sub-deployment>
<deployment-order>151</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>SFTP Transport Provider</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<compatibility-name>SFTP Transport</compatibility-name>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/transports/sftp_transport.ear</source-path>
<sub-deployment>
<name>sftp_transport.jar</name>
<target>osb_server1</target>
<module-type>jar</module-type>
<compatibility-name>sftp_transport.jar</compatibility-name>
</sub-deployment>
<deployment-order>165</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>Email Transport Provider</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<compatibility-name>EMail Transport</compatibility-name>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/transports/emailtransport.ear</source-path>
<sub-deployment>
<name>emailtransport.jar</name>
<target>osb_server1</target>
<module-type>jar</module-type>
<compatibility-name>emailtransport.jar</compatibility-name>
</sub-deployment>
<deployment-order>153</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>File Transport Provider</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<compatibility-name>File Transport</compatibility-name>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/transports/file_transport.ear</source-path>
<sub-deployment>
<name>filepoll.jar</name>
<target>osb_server1</target>
<module-type>jar</module-type>
<compatibility-name>filepoll.jar</compatibility-name>
</sub-deployment>
<deployment-order>155</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>MQ Transport Provider</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<compatibility-name>MQ Transport</compatibility-name>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/transports/mq_transport.ear</source-path>
<deployment-order>172</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>EJB Transport Provider</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/transports/ejbtransport.ear</source-path>
<deployment-order>157</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>Tuxedo Transport Provider</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/transports/tuxedo_transport.ear</source-path>
<deployment-order>159</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>ALDSP Transport Provider</name>
<target>AdminServer,osb_server1</target>
<module-type>war</module-type>
<compatibility-name>ALDSP Transport</compatibility-name>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/transports/aldsp_transport.ear</source-path>
<deployment-order>161</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>SB Transport Provider</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<compatibility-name>SB Transport</compatibility-name>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/transports/sb_transport.ear</source-path>
<deployment-order>163</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>WS Transport Provider</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<compatibility-name>WS Transport</compatibility-name>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/transports/ws_transport.ear</source-path>
<deployment-order>166</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>WS Transport Async Applcation</name>
<target>osb_server1</target>
<module-type>war</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/bea_alsb_ws_async_response.war</source-path>
<deployment-order>167</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>FLOW Transport Provider</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<compatibility-name>FLOW Transport</compatibility-name>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/transports/flow_transport.ear</source-path>
<deployment-order>175</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>BPEL 10g Transport Provider</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<compatibility-name>BPEL 10g Transport</compatibility-name>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/transports/bpel10gtransport.ear</source-path>
<deployment-order>177</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>JCA Transport Provider</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<compatibility-name>JCA Transport</compatibility-name>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/transports/jcatransport.ear</source-path>
<deployment-order>181</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>JEJB Transport Provider</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<compatibility-name>JEJB Transport</compatibility-name>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/transports/jejb_transport.ear</source-path>
<deployment-order>184</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>SOA-DIRECT Transport Provider</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<compatibility-name>SOA-DIRECT Transport</compatibility-name>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/transports/soa_transport.ear</source-path>
<deployment-order>185</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>ALSB Routing</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/stages/xbusrouting.ear</source-path>
<deployment-order>410</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>ALSB Transform</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/stages/xbustransform.ear</source-path>
<deployment-order>420</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>ALSB Publish</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/stages/xbuspublish.ear</source-path>
<deployment-order>430</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>ALSB Logging</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/stages/xbuslogging.ear</source-path>
<deployment-order>440</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>ALSB Resource</name>
<target>osb_server1</target>
<module-type>war</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/sbresourceWar/sbresource.war</source-path>
<deployment-order>500</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>ALSB WSIL</name>
<target>osb_server1</target>
<module-type>war</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/wsilWar/wsil.war</source-path>
<deployment-order>510</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>ServiceBus_Console</name>
<target>AdminServer</target>
<module-type>war</module-type>
<compatibility-name>sbconsole</compatibility-name>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/sbconsoleEar</source-path>
<deployment-order>810</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>ALSB Test Framework</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/sbTestFwk.ear</source-path>
<deployment-order>910</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<library>
<name>oracle.bi.jbips#[email protected]</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.bi.presentation_11.1.1/bi-jbips-slib-stub.ear</source-path>
<deployment-order>100</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.bi.composer#[email protected]</name>
<target>AdminServer,osb_server1</target>
<module-type>war</module-type>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.bi.presentation_11.1.1/bi-composer-slib-stub.war</source-path>
<deployment-order>100</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.bi.adf.model.slib#[email protected]</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.bi.presentation_11.1.1/bi-adf-model-slib.ear</source-path>
<deployment-order>100</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.bi.adf.view.slib#[email protected]</name>
<target>AdminServer,osb_server1</target>
<module-type>war</module-type>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.bi.presentation_11.1.1/bi-adf-view-slib.war</source-path>
<deployment-order>100</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.bi.adf.webcenter.slib#[email protected]</name>
<target>AdminServer,osb_server1</target>
<module-type>war</module-type>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.bi.presentation_11.1.1/bi-adf-webcenter-slib.war</source-path>
<deployment-order>100</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.wsm.seedpolicies#[email protected]</name>
<target>AdminServer,osb_server1</target>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.wsm.policies_11.1.1/wsm-seed-policies.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.jsp.next#[email protected]</name>
<target>AdminServer,osb_server1</target>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.jsp_11.1.1/ojsp.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.dconfig-infra#[email protected]</name>
<target>AdminServer,osb_server1</target>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.dconfig-infra_11.1.1.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>orai18n-adf#[email protected]</name>
<target>AdminServer,osb_server1</target>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.nlsgdk_11.1.0/orai18n-adf.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.adf.dconfigbeans#[email protected]</name>
<target>AdminServer,osb_server1</target>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.adf.dconfigbeans_11.1.1.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.pwdgen#[email protected]</name>
<target>AdminServer,osb_server1</target>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.pwdgen_11.1.1/pwdgen.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.jrf.system.filter</name>
<target>AdminServer,osb_server1</target>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.jrf_11.1.1/system-filters.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>adf.oracle.domain#[email protected]</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.adf.model_11.1.1/adf.oracle.domain.ear</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>adf.oracle.businesseditor#[email protected]</name>
<target>AdminServer,osb_server1</target>
<module-type>war</module-type>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.adf.businesseditor_11.1.1/adf.businesseditor.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.adf.management#[email protected]</name>
<target>AdminServer,osb_server1</target>
<module-type>war</module-type>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.adf.management_11.1.1/adf-management.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>adf.oracle.domain.webapp#[email protected]</name>
<target>AdminServer,osb_server1</target>
<module-type>war</module-type>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.adf.view_11.1.1/adf.oracle.domain.webapp.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>jsf#[email protected]</name>
<target>AdminServer,osb_server1</target>
<module-type>war</module-type>
<source-path>D:\OSB11g_Home\wlserver_10.3/common/deployable-libraries/jsf-1.2.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>UIX#[email protected]</name>
<target>AdminServer,osb_server1</target>
<module-type>war</module-type>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.uix_11.1.1/uix11.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>ohw- -
Shutdown(block='false') only works via Admin Server, not managed servers
Hello,
We want to shut down all 10 managed servers in our domain gracefully, and in parallel. 5 of those managed servers are on the same OS/host as the AdminServer, the other 5 are on a separate OS/host (i.e. we have 5 x 2-node clusters).
I'm writing scripts to gracefully shut down all of our servers upon an OS reboot command. On the OS with the AdminServer (and 5 managed servers), I can simply do this:
connect(user, pwd, http://localhost:7001)
shutdown('myserver1', 'Server', block='false')
shutdown('myserver3', 'Server', block='false')
shutdown('myserver5', 'Server', block='false')
shutdown('myserver7', 'Server', block='false')
shutdown('myserver9', 'Server', block='false')
All 5 servers will be shutting down at the same time. If they each took 2 minutes to shut down, the whole shutdown process would take 2 minutes.
However, on the OS running the other managed servers, I cannot assume that the AdminServer [on the other OS] will be online. Hence, I would like to gracefully shut down each server locally like this:
connect(user, pwd, url='t3://localhost:8001')
shutdown(block='false')
disconnect()
connect(user, pwd, url='t3://localhost:9001')
shutdown(block='false')
disconnect()
connect(user, pwd, url='t3://localhost:10001')
shutdown(block='false')
disconnect()
connect(user, pwd, url='t3://localhost:11001')
shutdown(block='false')
disconnect()
connect(user, pwd, url='t3://localhost:12001')
shutdown(block='false')
disconnect()
NOTE that the ports are different (i.e. I connect via WLST to the managed servers themselves rather than to the AdminServer).
Unfortunately, in this scenario, the block='false' does not work. WLST waits until the managed server is shut down before proceeding to the next connect() command. So if each server took 2 minutes to shut down, the whole shutdown process now takes 10 minutes.
We don't want to use the nmKill() command on the local Node Manager because we want a graceful shutdown.
What options do we have to issue a graceful shutdown command either to a local Node Manager or to the managed servers themselves (since we can't expect the AdminServer to be online when our script runs)?
Best regards,
MichaelHi Mike,
WLST will create it temp directory with /var/tmp/wlstTemp which is shared by all users. Since we cannot differentiated by different users which cause block on particular user at that time.
One solution is to grant write access to all users to the directory where the WLST temporary directory is created (e.g. on Solaris /var/tmp; you can verify the default on your system by executing java utils.getProperty and search for java.io.tmpdir).
If for whatever reason you cannot grant these access modes on the temporary directory, then you can create a directory somewhere on the file system where every user has the correct permissions.
Start the scripting tool with one the following options to redirect the cache files to the specified directory. Dependent on your environment one or the other will apply.
java -Djava.io.tmpdir=<path-to-tmpDir> weblogic.WLST
or
java -Dpython.cachedir=<path-to-tmpDir> weblogic.WLST
This will be useful to make shutdown of servers without any problem.
Note: block=false will always works it should not be the problem.
Regards,
Kal -
Admin server looses managed servers
we hava 2 clusters of 2 wls 6.1 sp2 instances each on 2 hpux 11 boxes. The wls console
shows all the instances when booted up. But suddenly, after a period( and this random
without a pattern), the admin seems to loose some of the managed servers. The console
does not show them running but if I ping the server it is there and applications
on those 'lost' instances are responding. We are not able to predict this beheaviour.
We are still trying to device a way to identify when it happens. When this happens
applications work properly but new deployments are not possible and we have to recycle
the 'lost' managed instances. Obvoiusly we are not able to look at any stats for
monitoring from the console.
Has anybody experienced something like this.
thanks
Devaraju, SushantI was just getting ready to post for an exact same symptom (scary).
Only difference is that I am running WLS 6.1 on Compaq Tru64 (unix).
Appreciate any help on where to start.
Sushant: Pls post (or email) any responses or resolution.
Thanks-
Rama
"sushant" <[email protected]> wrote:
>
we hava 2 clusters of 2 wls 6.1 sp2 instances each on 2 hpux 11 boxes. The
wls console
shows all the instances when booted up. But suddenly, after a period( and
this random
without a pattern), the admin seems to loose some of the managed servers.
The console
does not show them running but if I ping the server it is there and applications
on those 'lost' instances are responding. We are not able to predict this
beheaviour.
We are still trying to device a way to identify when it happens. When this
happens
applications work properly but new deployments are not possible and we have
to recycle
the 'lost' managed instances. Obvoiusly we are not able to look at any stats
for
monitoring from the console.
Has anybody experienced something like this.
thanks
Devaraju, Sushant -
Running managed servers from different WL versions under a domain
Hi,
Would it be possible to run managed servers (in non clustered way) from different versions of WebLogic under a single domain, with admin server of higher WebLogic version controlling the domain and the managed servers?
Regards,
GobiHi Gobi,
we can make it run such a way but it may lead to many complication with patch sets.
Few thing work in one environment and other will not so it is not at all recommended way to set such configuration.
Regards,
Kal -
Automating start / restart of WebLogic Admin and managed servers on MS Windows
Hi All,
Please help me to do the automation of start and stop scrip of Oracle Weblogic 10.3.6 and Forms and Reports 11.1.2.2.0(Managed Servers) On Windows server 2008.
Here are two options for automating start / stop of WebLogic Admin and managed servers on MS Windows. Please suggesst which one is standrad procedure.
Use NodeManager (installed as a MS Windows Service)
or
Create Windows Service(s) for the server(s) - no NodeManager
Following Document : 1060058.1
Please suggest me the best practice. Many thanks in advance.
Kind Regards,
MohanHi Borys,
Thank you for quick reply...
If we use the first option "Create Windows Service(s) for the server(s) - no NodeManager" then we will be facing issue Like "Admin Server or Managed Server may go into an unhealthy or failed state but the JVM is still running"
In the document : 1060058.1 : Mentioned as Important Note: The second option has a limitations.
Limitaion is below when we use first option : "Create Windows Service(s) for the server(s) - no NodeManager" -
Windows Services Manager only monitors the JVM process. If the JVM process fails (shuts down), then Windows Services Manager will attempt to restart it. But there are some scenarios where the Admin Server or Managed Server may go into an unhealthy or failed state but the JVM is still running. The Windows Service will not know to restart the process in these cases. If a server is started using NodeManager, NodeManager would recognize such a state and restart the process accordingly. Furthermore, if you start up managed servers via a MS Windows Service, you cannot monitor and/ or stop the managed server via the Weblogic Admin Console and/or Fusion Middleware ( Enterprise Manager ) Control.
I have implemented the second option "Use NodeManager starting admin and manged servers via WLST script" - Python script. Its working well without issue...No Limitation...
Script Contains Below :
print "================== Start scripts of Managed servers and Admin server ======================"
nmConnect(userConfigFile='D:/myFiles/myuserconfigfile.secure',userKeyFile='D:/myFiles/myuserkeyfile.secure',host='00.0.00.00',port='5556',domainName='ClassicDomain',domainDir='D:\Oracle\Middleware\user_projects\domains\ClassicDomain',nmType='ssl')
print "================== Adminserver Starting ================================================"
nmStart('AdminServer')
connect('weblogic','Password1','10.4.93.117:7001')
print "================== MANAGED SERVER (FROMS) Starting ====================================="
start('WLS_FORMS','Server')
print "================== MANAGED SERVER (REPORTS) Starting ==================================="
start('WLS_REPORTS','Server')
exit()
HOPE WE WILL MEET AGAIN AND AGAIN...
Many thanks for your comments!
Kind Regards,
Mohan -
1 NodeManager, 1 Admin Server and 2 Managed Servers
Hi All, I'm new in Weblogic and this is my 1st time to post a question on this forum. Would like ask for help from you all above my setup, I'm not sure whether it will work or not. Please find out the scenario below:
Setup:
1 Machine (RedHat Enterprise Linux 5.5)
1 NodeManager
1 AdminServer (Name: APP)
2 Managed Servers (Name: APPLIVE, APPUAT)
Currently I would like to using one NodeManager to control both Managed Servers under 1 machine. When I configure my APP Admin Server and two Managed Servers, i would like to nmEnroll both Managed Servers under one NodeManager but it will overwrite my enroll entries if i enroll 2nd Managed Server.
Is it possible to configure NodeManager to accept both Managed Servers entries? Thanks. :)
Edited by: user13602952 on Jan 2, 2011 9:54 PMHi Hong,
Following are the few things which you help you understand about NodeManager and nmEnroll
- First of all a Node Manager process is not associated with a specific WebLogic domain but with a machine
- When you run a nmEnroll then you just give "domainDir" and "nmHome" which would then gets the file called "*nm_password.properties*" which contains the encrypted username and password that is used for server authentication and "*SerializedSystemIni.dat*" file.
Example:
nmEnroll([domainDir], [nmHome])
- With above files it also updates the nodemanager.domains file with the domain information which was mentioned in the above command.
Thus when you run the nmEnroll command it would get all the details which it needs to start any managed servers in the same Machine, hence you do not need to run the same commend for each managed servers in the same Machine.
For more information have a look at the below links:
Topic: Search for "nmEnroll"
http://download.oracle.com/docs/cd/E13222_01/wls/docs92/config_scripting/reference.html
Topic: Overview of Node Manager
http://download.oracle.com/docs/cd/E13222_01/wls/docs90/server_start/nodemgr.html#1091317
Regards,
Ravish Mody
http://middlewaremagic.com/weblogic/
Come, Join Us and Experience The Magic…
Maybe you are looking for
-
Uploading Importing text file & crosstab display
<p> I want to upload a text tab delimited file into our db, currently we are uploading it to a temp table in the db, do some validation checks and write to a table when done. I have two questions:</P> <p> 1) Is there a more efficient way of upload/im
-
Blue screen of death when running labwindows, pxi chassis, and windows 2000
Hi, when programming under labwindows the software crashes cvi, and windows NT and i get the blue screen of death...usually every hr or so. I checked the hw config and there are no conflicts. Is it normal to share IRQ 9 for all? is there a document t
-
Hello, mail.app act weird since a few weeks. It doesnt show the emails for one particular account I have. Everything syncs, it shows the new mails I receive, but when I click on the mailbox, its empty. At some point, when I restarted the computer, it
-
Cost capture for Rework for Incoming Inspections
Hi xperts, Scenario Incoming inspection, QC department checks and finds rejects No UD stock posting is done. They use in house personnel for reworking the partial rejects they have. (This is because they have imported raw materials with lead time of
-
Different transitions page build in and build out
is there a way to create different transitions for page build in and build out in indesign?