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, Sushant

I 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

Similar Messages

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

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,
Michael

Hi 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

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 trace

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 trace

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,
Naga

Hi,
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?

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

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.

How to access JNDI tree of Admin Server from Managed Server

Hello,
I created Managed and Admin Server for Domain.
On Managed Server I use:
InitialContext con = new InitialContext()
It points to Managed Server local JNDI tree and
Managed Server can't find JNDI tree of Admin Server.
Looks like Managed Server is regular remote client of Admin Server.
How to access JNDI tree of Admin Server from Managed Server?
Thanks.
Oleg.

Hello,
I created Managed and Admin Server for Domain.
On Managed Server I use:
InitialContext con = new InitialContext()
It points to Managed Server local JNDI tree and
Managed Server can't find JNDI tree of Admin Server.
Looks like Managed Server is regular remote client of Admin Server.
How to access JNDI tree of Admin Server from Managed Server?
Thanks.
Oleg.

Use Admin Server to Manage multiple managed servers through Nodemanager

hi guys,
Iam trying to simulate the production environment for a Weblogic based application.
I want to use one Admin Server(adminServer) to control 2 managed servers(weblogic,Bizarro).
adminServer & weblogic sit on windows machine (prod1) and Bizarro sits on OakStage(unix
machine).
I have nodeManagers running on both machines. They were started using the default
start scripts that were provided.
I can sucessfully start&stop instance weblogic (the instance that resides on the
same machine as adminServer). When I try to start Bizarro i get the following
error in the console
<Oct 18, 2002 7:59:22 AM PDT> <Error> <NodeManager> <Could not start server 'Bizarro'
via Node Manager - reason: '[SecureCommandInvoker: Could not create a socket to
the NodeManager running on host '192.168.0.97:5555' to execute command 'online
Bizarro', reason: Operation timed out: connect. Ensure that the NodeManager on
host '192.168.0.97' is configured to listen on port '5555' and that it is actively
listening]'>
but iam sure node manager is running on port 5555 on that box.
Here is my config.xml file. Is there something Iam missing?
I have also modified the hosts file to only have the ip address of the admin server.
<?xml version="1.0" encoding="UTF-8"?>

<Domain Name="adminDomain">
<Security Name="adminDomain" PasswordPolicy="wl_default_password_policy" Realm="wl_default_realm"/>
<PasswordPolicy Name="wl_default_password_policy"/>
<FileRealm Name="wl_default_file_realm"/>
<StartupClass ClassName="com.ias.hub.weblogic.WeblogicStartup" Name="hubStartup"
Targets="weblogic"/>
<CustomRealm ConfigurationData="user.filter=(&(uid=%u)(objectclass=person));user.dn=ou=people,
o=beasys.com;server.principal=uid=admin, ou=Administrators, ou=TopologyManagement,
o=NetscapeRoot;membership.filter=(&(uniquemember=%M)(objectclass=groupofuniquenames));group.filter=(&(cn=%g)(objectclass=groupofuniquenames));server.host=ldapserver.example.com;group.dn=ou=groups,
o=beasys.com" Name="defaultLDAPRealmForNetscapeDirectoryServer" Notes="This is
provided as an example. Before enabling this Realm, you must edit the configuration
parameters as appropriate for your environment." Password="{3DES}CqUY0ZB2q6DOFOH3DpKGnQ=="
RealmClassName="weblogic.security.ldaprealmv2.LDAPRealm"/>
<Server ListenPort="9000" Machine="Prod1" Name="weblogic" StdoutDebugEnabled="true"
StdoutSeverityLevel="64">
<ServerStart ClassPath="my correct claspath" Name="weblogic" OutputFile="weblogic.log"/>
<SSL ListenPort="9001" Name="weblogic"/>
<ServerDebug Name="weblogic"/>
<KernelDebug Name="weblogic"/>
<Log FileName="weblogic.log" Name="weblogic"/>
<ExecuteQueue Name="default" ThreadCount="15"/>
<WebServer LogFileName="./config/adminDomain/logs/access.log" LoggingEnabled="true"
Name="weblogic"/>
</Server>
<JDBCConnectionPool CapacityIncrement="2" DriverName="weblogic.jdbc.oci.Driver"
InitialCapacity="15" LoginDelaySeconds="1" MaxCapacity="15" Name="IasPool" Properties="user=stage2;password=******;server=ORCL_STAGE.INTERASSET.COM"
RefreshMinutes="25" Targets="weblogic" TestTableName="DUAL" URL="jdbc:weblogic
racle"/>
<SNMPAgent Name="adminDomain"/>
<Application Deployed="true" Name="certificate" Path=".\config\adminDomain\applications">
<WebAppComponent Name="certificate" Targets="adminServer" URI="certificate.war"/>
</Application>
<JDBCDataSource JNDIName="IAS_DATA_SOURCE" Name="IasDataSource" PoolName="IasPool"
Targets="weblogic"/>
<Application Deployed="true" Name="DefaultWebApp" Path=".\config\adminDomain\applications">
<WebAppComponent Name="DefaultWebApp" Targets="adminServer" URI="DefaultWebApp"/>
</Application>
<CustomRealm ConfigurationData="user.filter=(&(uid=%u)(objectclass=person));user.dn=ou=people,
dc=example, dc=com;server.principal=cn=Manager, dc=example, dc=com;membership.filter=(&(uniquemember=%M)(objectclass=groupofuniquenames));group.filter=(&(cn=%g)(objectclass=groupofuniquenames));server.host=ldapserver.example.com;group.dn=ou=groups,
dc=example, c=com" Name="defaultLDAPRealmForOpenLDAPDirectoryServices" Notes="This
is provided as an example. Before enabling this Realm, you must edit the configuration
parameters as appropriate for your environment." Password="{3DES}CqUY0ZB2q6DOFOH3DpKGnQ=="
RealmClassName="weblogic.security.ldaprealmv2.LDAPRealm"/>
<Machine Name="Prod1">
<NodeManager Name="Prod1"/>
</Machine>
<Application Deployed="true" Name="entity" Path=".\config\adminDomain\applications">
<EJBComponent Name="entity" Targets="weblogic" URI="entity.jar"/>
</Application>
<Application Deployed="true" Name="hub" Path=".\config\adminDomain\applications">
<WebAppComponent Name="hub" Targets="weblogic" URI="hub"/>
</Application>
<Server ListenAddress="192.168.0.97" ListenPort="7000" Machine="OakStage" Name="Bizarro">
<ServerStart ClassPath="my correct classpath" Name="Bizarro" OutputFile="bizarro.log"/>
<SSL Name="Bizarro"/>
<ServerDebug Name="Bizarro"/>
<KernelDebug Name="Bizarro"/>
<Log Name="Bizarro"/>
<WebServer Name="Bizarro"/>
</Server>
<Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
<ApplicationManager Name="adminDomain"/>
<CustomRealm ConfigurationData="server.host=ldapserver.example.com;membership.scope.depth=1;microsoft.membership.scope=sub;membership.filter=(|(&(memberobject=%M)(objectclass=memberof))(&(groupobject=%M)(objectclass=groupmemberof)));group.dn=ou=Groups,
o=ExampleMembershipDir;group.filter=(&(cn=%g)(objectclass=mgroup));server.principal=cn=Administrator,
ou=Members, o=ExampleMembershipDir;user.dn=ou=Members, o=ExampleMembershipDir;user.filter=(&(cn=%u)(objectclass=member))"
Name="defaultLDAPRealmForMicrosoftSiteServer" Notes="This is provided as an example.
Before enabling this Realm, you must edit the configuration parameters as appropriate
for your environment." Password="{3DES}CqUY0ZB2q6DOFOH3DpKGnQ==" RealmClassName="weblogic.security.ldaprealmv2.LDAPRealm"/>
<JTA Name="adminDomain"/>
<Server ListenPort="7000" Name="adminServer" NativeIOEnabled="true" TransactionLogFilePrefix="config/adminDomain/logs/">
<ServerStart Name="adminServer"/>
<Log FileName="config/adminDomain/logs/weblogic.log" Name="adminServer"/>
<ServerDebug Name="adminServer"/>
<ExecuteQueue Name="default" ThreadCount="15"/>
<KernelDebug Name="adminServer"/>
<WebServer DefaultWebApp="DefaultWebApp" LogFileName="./config/adminDomain/logs/access.log"
LoggingEnabled="true" Name="adminServer"/>
<SSL Enabled="true" ListenPort="7005" Name="adminServer" ServerCertificateChainFileName="config/adminDomain/ca.pem"
ServerCertificateFileName="config/adminDomain/democert.pem" ServerKeyFileName="config/adminDomain/demokey.pem"/>
</Server>
<UnixMachine Name="OakStage">
<NodeManager ListenAddress="192.168.0.97" Name="OakStage"/>
</UnixMachine>
<Log FileName="adminDomain.log" Name="adminDomain"/>
</Domain>
Thanks guys
regards
syd

Can this be done when you set up your domain along with admin and managed servers the very first time ? Even if you set up a domain with bunch of managed servers why does the library still get installed on admin server??? Also, for the method you described dont we have to update targets for statup and shutdown classes and work managers?
Also, what is the other method to do it from the console?
METHOD 2 (Other than the one you described- Please tell me if this is correct method and if we need to go to till level)
Step1:
I went to deployments base_domain (in admin console) > deployments chose each library and changed targets manually and activate the changes
Step2
Go to Startup and shutdown classes and change targets there
Step 3
Go to work managers and change targets there.
Please let me know
Edited by: user9021545 on May 12, 2011 10:18 AM

What is the Ideal Production Setup For One Admin and 4 Managed Servers

Dear Experts
I will be starting with production setup including one Admin server and 4 managed servers in one single domain.
I am thinking of creating a single node environment(no clusters) as the machine has following configuration
OS : Windows Server 2008 R2 Datacenter
RAM : 48 GB
System Type : 64 bit
Processor : Intel(Xenon) 4 processors [email protected]
Can you please let me know if this configuration would suffice for the 4 managed servers if i assign Xmx and Xms as 4096 and Heap Space as 1024 to all the Managed Servers.
It is very urgent and i need to convey to the Infrastructure team if harware procurement is required.
We are looking at somewhere around 300 concurrent users(maximum load) and 100(minimum load) at a given point of time.
Please reply ASAP.
Thanks in advance
Edited by: Abhinav Mittal on Apr 23, 2013 7:58 PM
Edited by: Abhinav Mittal on Apr 23, 2013 8:03 PM

Heap size must be calculated according to the applications that are been deployed on each JVM.
With no deployments, you dont need more than 256k for managed servers heap size and 512k for adminserver. As biggest its your heap size, longer will take your garbage collection. And if you can prevent it, better do it.
Kinds,
Gabriel Abelha

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,
Indu

Yes, 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-

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
]

Admin Server vs Managed Server

Hi
I would like to know that what is the exact diffrence between admin and a managed
server. I create admin server and i create managed server what is exactly diffrnt
in configuration. If i create a admin server and say want to use it to deploy
my applications, can i do so ? I know it is not to be done like that but just
wanted to know if it was allowed.
Would appreciate if someone can actucally explain me exact diffrence between admin
and managed servers.
Regards
JOE

A domain includes one or more WebLogic Servers, and may include WebLogic Server
clusters.
The Administration Server is the WebLogic Server instance that configures and
manages the WebLogic Server instances in its domain.In a domain with multiple
WebLogic Servers, only one server is the Administration Server; the other servers
are called Managed Servers. Each WebLogic Managed Server obtains its configuration
at startup from the Administration Server.
thanks,
Deepak
"Joe" <[email protected]> wrote:
>
Hi
I would like to know that what is the exact diffrence between admin and
a managed
server. I create admin server and i create managed server what is exactly
diffrnt
in configuration. If i create a admin server and say want to use it to
deploy
my applications, can i do so ? I know it is not to be done like that
but just
wanted to know if it was allowed.
Would appreciate if someone can actucally explain me exact diffrence
between admin
and managed servers.
Regards
JOE

WLS: Admin Server/Node Manager

If an Admin server resides on the same node as Managed servers:
(1) Can the Admin server create, monitor, and restart a Node Manager or is the persistance of the Node Manager strictly the responsibility of the operating system (UNIX daemon, Windows service, or Tandem generic-process)?
(2) Can the Admin server role and Node Manager role be contained in the same process ?

1) The persistence of the nodemanager has to be configured by OS.
2) No, node manager is not tied to a domain (it is domain agnostic) and it is a separate process. In WLS 9, the nodemanager can monitor and manage the admin server also
Venkat

Does SNMP agent on the admin server polls managed objects automatically?

Hi All,
If I enable SNMP agent on the admin server, does it mean that it polls and caches MIB of all the managed servers in the domain and return it if a client requests for information or it polls and caches that MIB value only when requested?
2)Suppose a client requests for SNMP data of a managed instance and the instance is down, does admin server keep polling or does it timeout after a number of secs or retries. I don't see any config params in weblogic 8.1.3 or weblogic 9.0 console.
Thanks. I appreciate your answers.
Thanks,

Are you saying the notes are incorrect?
No, I wasn't commenting on that at all. I was just saying that DBUA is the recommended way of upgrading databases... and that's in spades if you're talking about 100GB databases.
I'll lay odds that DBUA to 10.2.0.1 and then patching to 10.2.0.3 is quicker than exporting and importing 100GB of data.
(Applying a 10.2.0.3 patch is done with opatch and doesn't require a fresh installation of Oracle. A patch mostly just modifies the data dictionary: it's finished in minutes, not hours).
My real point: these sorts of questions are incredibly easy to ask, answer, discard, re-ask, modify, mull over and basically experiment with in a virtual environment.
And again: it's utterly bizarre why you wouldn't have physical access to this database (and keep in mind that I can't keep in mind little nuggets of information such as this one which you didn't see fit to share earlier!)
It's in a virtual server. Virtual servers can be zipped up and emailed! (OK, maybe not 100GB... but I've shipped a small hard disk in a zip-lok pack envelope half way round the world before now -though obviously it wasn't critical to have the contents of that envelope available for use all the time... Still, it sounds to me like here's a technology (virtualisation) that's not being properly exploited).

Admin server looses managed servers

Similar Messages

Maybe you are looking for