Custom Managed Servers

what are advantages of creating Custom Managed Servers ?
we have WC_Spaces, WC_Portlet etc etc that comes with webcenter suite. We also have default MDS created.
Why do we need to craete Custom Managed Servers and also custom MDS ? Meaning, we can always depoly our application on WC_Server.
Then why doc talks about Custom Managed Servers ?

It depends on what stuff you are going to deploy.
If you create an application which requires a lot of resources, it is wise to deploy it to a dedicated managed server which can then be tuned specifically for that application.
Another consideration might be to keep the standard managed servers as clean as possible.
If you do not deploy any custom code to the standard managed servers and something goes wrong in these standard servers, it might be easier for Oracle support to analyse the issue.
In short, for production I'ld recommend to always use a custom managed server.
For development, you might want to deploy your application in a standard managed server, but it is not recommended (you always want to develop against an environment which is most similar to production, right?)
Kind regards,
Rob

Similar Messages

Error : Running Managed Servers in a cluster

Hi,
I tried creating a new domain from my local pc - by using the configuration wizard provided by weblogic.. the configuration used is like this -
Admin Server - adminServer - 1.1.1.19 - on port 7001
Managed servers - machines:ip's - port
1. mgndServer1 - 1.1.1.19 - 7011
2. mgndServer2 - 1.1.1.20 - 7011
mgndCluster defined as - mgndServer1:7011, mgndServer2:7011
node manager ; - 1.1.1.19 - 5555
In the last step i didnt check ( select box ) the WLI Start up , WLI Shutdown classes for the managed cluster , but Set the WLI Start up , shut down classes for admin server.
Started the admin server and from the admin console, state of the node manager was running , I tried starting the managed servers, but it failed with the below error - and managed servers never come into running state..
Log :
<Jan 29, 2010 10:36:26 AM CET> <Info> <NodeManager@*.*:5555> <Starting Server adminServer ::mgndServer1 ...>
<Jan 29, 2010 10:36:26 AM CET> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.4.2_05-b04 from Sun Microsystems Inc.>
<Jan 29, 2010 10:36:26 AM CET> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://1.1.1.19:7001 to check if there exists a running admin server at this URL.>
<Jan 29, 2010 10:36:26 AM CET> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Jan 29, 2010 10:36:26 AM CET> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647 >
<Jan 29, 2010 10:36:26 AM CET> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://1.1.1.19:7001 to retrieve the initial configuration.>
<Jan 29, 2010 10:36:27 AM CET> <Info> <NodeManager@*.*:5555> <Server myDomain::mgndServer1 started, process id = 6,888>
<Jan 29, 2010 10:36:28 AM CET> <Notice> <Log Management> <BEA-170019> <The server log file C:\bea\weblogic81\common\nodemanager\mgndServer2\mgndServer2.log is opened. All server side log events will be written to this file.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\weblogic81\server\lib\DemoTrust.jks.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\jdk142_05\jre\lib\security\cacerts.>
<Jan 29, 2010 10:36:30 AM CET> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "mgndServer1" for domain "myDomain">
<Jan 29, 2010 10:36:57 AM CET> <Notice> <Cluster> <BEA-000138> <Listening for announcements from cluster mgndCluster on 237.0.0.13:7011.>
<Jan 29, 2010 10:36:57 AM CET> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of mgndCluster.>
<Jan 29, 2010 10:37:27 AM CET> <Notice> <JTA> <BEA-110025> <Creating new transaction log file [.\mgndServer1\./mgndServer1.0000.tlog].>
<Jan 29, 2010 10:37:27 AM CET> <Notice> <JTA> <BEA-110025> <Creating new transaction log file [.\mgndServer1\./mgndServer1.heur.0000.tlog].>
<Jan 29, 2010 10:37:35 AM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application WLI Worklist due to error weblogic.management.ManagementException: [Deployer:149233]An unexpected error was encountered during the deployment process. - with nested exception:
[java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/SLSBContainerBean].
java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/SLSBContainerBean
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:480)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:182)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:224)
at weblogic.ejb20.deployer.EJBModule.setupEJBToImplClassDependencies(EJBModule.java:1030)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:481)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
--------------- nested within: ------------------
weblogic.management.ManagementException: [Deployer:149233]An unexpected error was encountered during the deployment process. - with nested exception:
[java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/SLSBContainerBean]
at weblogic.management.deploy.slave.SlaveDeployer.convertThrowable(SlaveDeployer.java:1017)
at weblogic.management.deploy.slave.SlaveDeployer.access$500(SlaveDeployer.java:124)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3034)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
>
<Jan 29, 2010 10:37:38 AM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application WLI System EJBs due to error weblogic.management.ApplicationException: prepare failed for WLI Process Tracking
Module Name: WLI Process Tracking, Error: Exception preparing module: EJBModule(WLI Process Tracking,status=NEW)
Unable to deploy EJB: .\mgndServer2\stage\WLI System EJBs\tracking from tracking:
weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: com.bea.wli.management.tracking.ProcessTrackingBean
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:550)
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:232)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1324)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
weblogic.management.ApplicationException: prepare failed for WLI Process Tracking
Module Name: WLI Process Tracking, Error: Exception preparing module: EJBModule(WLI Process Tracking,status=NEW)
Unable to deploy EJB: .\mgndServer2\stage\WLI System EJBs\tracking from tracking:
weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: com.bea.wli.management.tracking.ProcessTrackingBean
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:550)
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:232)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1324)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1604)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
>
Please help me in understand what went wrong here ? can anyone quickly guide me ..
thanks
patrick

Hi,
OPTION-A)
If you are able to start the Managed Server using ...the Start Scripts then it means that the Missing class gets included in the Server Classpath ....when we use StartScripts to Start the Server.
If above one works fine...then Just try the following..
Step1). Open the "nodemanager.properties" file and then "startScriptEnabled=true" and "startScriptName=startWebLogic.cmd" ....provide these two entries there....remember if you are using any custom scripts to start your managed server ...then give that scriptname in "startScriptName" parameter..
Step2). restart the Node Manager and then try to start the Managed Server from Admin Console.
for more informations Please refer to "nodemanager.properties" details:
http://download-llnw.oracle.com/docs/cd/E15051_01/wls/docs103/nodemgr/java_nodemgr.html#wp1068415
OPTION-B)
Start the ManagedServer using the StartScripts and then open the server OUT file....
Find the value of CLASSPATH in that OUT File ...copy the CLASSPATH Value and then Login to Admin Console....
Servers--->Click on ServerName (Example MS1)---> configuration Page ---> ServerStart (TAB)
In this page Paste the CLASSPATH Value which u have copied....in the CLASSPATH Test Field...
Now restart your Server using AdminConsole.
Thanks
Jay SenSharma
Edited by: Jay SenSharma on Jan 30, 2010 10:55 PM

How to Separate Management Servers for Ease of Administration?

Hello,
I am fairly new to SCOM, though have been charged with creating a monitoring solution for a particular group of customers and integrating it as far as possible into our existing corporate SCOM implementation, so any help, tips and so on would be greatly
appreciated.
The customer monitoring requirements will be very different to those of our fairly standard corporate environment - we will need to monitor very different technologies, with some systems sat in different domains or a DMZ. Our central servicedesk will still
need to monitor and action alerts and events for both environments as seamlessly as possible.
At the same time, I would like to separate the environments as the configuration of the management servers for the customer environment will be quite different from our corporate one, and I want to avoid having to make changes to all our corporate servers
every time I need to change something on the customer environment - so things like management pack installs, certificate admin, static DNS config and so on.
How would I go about this please? Would it be better to create a separate management group, with servers dedicated to the customer environment, then connect this to the corporate management group so that the servicedesk can still monitor it, or is there
another way of doing it? Perhaps using resource pools? Time will be a factor here, though ultimately the goal is ease of administration going forward.
Thanks

Using resource pools will not allow you to separate configuration such as MP installs, security, etc. as they are all part of the same management group. From Technet, "A resource pool is a collection of management servers used to distribute
work amongst themselves and take over work from a failed member." If configuration needs to be completely separate from the base configuration perspective, you could use separate connected management groups.
Another option is to separate the configuration within the management group. For example, if you need to monitor SQL computers in your corp environment but not the customer environment, simply create a group containing customer computers and override
the SQL discovery. This applies to other technologies as well. You can even group computers by environment (corp/customer) by using reg key attributes like Kevin Holman describes here: (While my account is being verified
I can't post links but you can search "Creating custom dynamic computer groups based on registry keys on agents"). If you are familiar with MP authoring, you could create a new MP with a new Windows Computer based class instead of extending
the Windows Computer class. From a capabilities perspective, you can certainly monitor corporate, customer, DMZ, and other domains in the same management group. If the domain is untrusted or in the case of the DMZ, workgroups computers, you can
utilize gateway servers with certificate authentication which will be configured for each domain/dmz gateway.
Ease of administration is a tricky concept here...if you utilize separate management groups, administration will have to be handled completely separate in 2 separate consoles. If there are separate SCOM admins per management group, this is
of no issue, but if 1 team/person is managing both, this can be difficult. Alternatively, there will be some up front work to using groups to separate the environments using groups, discoveries, etc.

Problem in running Managed Servers

Hi,
I used the configuration wizard and tried creating a domain ( admin server , 2 managed servers ('new_Server_1' , 'new_Server_2' )) . Admin server listens to the port 7003.
Set up details :
Managed Servers - IP's - Port
new_Server_1 - 1.1.1.10 - 7011
new_Server_2 - 1.1.1.11 - 7011
Node Manager - 1.1.1.10 - 5555
I login into the admin console after the whole set up, node manager was running , admin server wa s running and tried starting the managed servers ,But they failed to start giving the error message -
<Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.4.2_05-b04 from Sun Microsystems Inc.>
<Jan 9, 2010 11:29:57 AM CET> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://1.1.1.10:7003 to check if there exists a running admin server at this URL.>
<Jan 9, 2010 11:29:57 AM CET> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Jan 9, 2010 11:29:57 AM CET> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647 >
<Jan 9, 2010 11:29:57 AM CET> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://1.1.1.10:7003 to retrieve the initial configuration.>
<Jan 9, 2010 11:29:58 AM CET> <Notice> <Log Management> <BEA-170019> <The server log file C:\bea\weblogic81\common\nodemanager\new_Server_1\new_Server_1.log is opened. All server side log events will be written to this file.>
<Jan 9, 2010 11:30:00 AM CET> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Jan 9, 2010 11:30:00 AM CET> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
<Jan 9, 2010 11:30:00 AM CET> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
<Jan 9, 2010 11:30:00 AM CET> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\weblogic81\server\lib\DemoTrust.jks.>
<Jan 9, 2010 11:30:00 AM CET> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\jdk142_05\jre\lib\security\cacerts.>
<Jan 9, 2010 11:30:00 AM CET> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "new_Server_1" for domain "integration">
<Jan 9, 2010 11:30:03 AM CET> <Notice> <Cluster> <BEA-000138> <Listening for announcements from cluster new_Cluster on 237.0.0.1:7011.>
<Jan 9, 2010 11:30:03 AM CET> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of new_Cluster.>
<Jan 9, 2010 11:30:36 AM CET> <Error> <Deployer> <BEA-149601> <The deployment framework was unable to resume accepting requests.>
<Jan 9, 2010 11:30:36 AM CET> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: Deployer:149601The deployment framework was unable to resume accepting requests.weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
java.lang.ClassNotFoundException: com.bea.wli.init.BPMStartup>
The WebLogic Server did not start up properly.
weblogic.management.AbortDeploymentException: weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
java.lang.ClassNotFoundException: com.bea.wli.init.BPMStartup
at weblogic.t3.srvr.StartupClassService.addDeployment(StartupClassService.java:92)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
Reason: Deployer:149601The deployment framework was unable to resume accepting requests.weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
java.lang.ClassNotFoundException: com.bea.wli.init.BPMStartup
Is this due to the WLI Start up classes set to both admin and managed servers caused this problem / jars missed out while creating a domain ,, ? any pointers to solve this issue.
thank you in advance.
colonel

Hi,
OPTION-A)
If you are able to start the Managed Server using ...the Start Scripts then it means that the Missing class gets included in the Server Classpath ....when we use StartScripts to Start the Server.
If above one works fine...then Just try the following..
Step1). Open the "nodemanager.properties" file and then "startScriptEnabled=true" and "startScriptName=startWebLogic.cmd" ....provide these two entries there....remember if you are using any custom scripts to start your managed server ...then give that scriptname in "startScriptName" parameter..
Step2). restart the Node Manager and then try to start the Managed Server from Admin Console.
for more informations Please refer to "nodemanager.properties" details:
http://download-llnw.oracle.com/docs/cd/E15051_01/wls/docs103/nodemgr/java_nodemgr.html#wp1068415
OPTION-B)
Start the ManagedServer using the StartScripts and then open the server OUT file....
Find the value of CLASSPATH in that OUT File ...copy the CLASSPATH Value and then Login to Admin Console....
Servers--->Click on ServerName (Example MS1)---> configuration Page ---> ServerStart (TAB)
In this page Paste the CLASSPATH Value which u have copied....in the CLASSPATH Test Field...
Now restart your Server using AdminConsole.
Thanks
Jay SenSharma
Edited by: Jay SenSharma on Jan 30, 2010 6:42 PM
Edited by: Jay SenSharma on Jan 30, 2010 10:57 PM

Problem Starting Managed Servers

Hi,
I am trying to start Managed Server on Sun Solaris. My admin Server and managed Server
are on the same Machine.
My admin Server starts up with out any problem. WhenI try to bring up my Managed
Server its not reading the command line arguments which I supplied through the Console:
Servers -> serverName -> Remote Start->Arguments. For some reason these command arguments
are not read and so I am having errors like Unable to load libraries, etc.
Also when I saw the log file for managed server the class path and the arguments
are printed in a different way than I have set. I dont know if thats a problem or
not. I am copying part of that for your reference.
classpath=/opt/j2sdk1_3_1_01/jre/lib/rt.jar\:/opt/weblogic6.1\:/opt/weblogic6.1/lib/weblogic_sp.jar\:/opt/weblogic6.1/lib/weblogic.jar\
serverStartArgs=-Dweblogic.management.server\=sunserver\:7210 -Djava.security.policy\=\=/opt/weblogic6.1/lib/weblogic.policy
I have checked the config.xml file and what ever I have set in the console is being
saved properly in the xml file.
Can any one know why the back slash is printed above even though I havent typed that
in the console. Has any one have experince with setting the command line arguments
and class path through console for Managed servers.
I am stuck up at this point. Any help in this regard will be greatly appreciated.
Thanks,
Kiran

Seems a method signature does not match with the implementation in the
library either due to namemangling or incompatible versions of libraries.
You are loading your own custom native libraries for security.
Best would be use the default startManagedServer -- once the server has
started, copy and paste the entire value of java.library.path into the
startup arguments for Remote start.
For instance in my server log file:
####<Apr 10, 2002 6:47:10 PM PDT> <Info> <Management> <mountview> <myserver>
<main> <system> <> <141034> <Java system property: java.library.path =
/home/sabha/600sp2only/jdk130/jre/bin/../lib/sparc/hotspot:/home/sabha/600sp
2only/jdk130/jre/bin/../lib/sparc::/home/sabha/600sp2only/wlserver6.0/lib/so
laris:/home/sabha/600sp2only/wlserver6.0/lib/solaris/oci816_8:/usr/lib>
I would set that as the arguments :
-Djava.library.path=/home/sabha/600sp2only/jdk130/jre/lib/sparc/hotspot:/hom
e/sabha/600sp2only/jdk130/jre/bin/../lib/sparc::/home/sabha/600sp2only/wlser
ver6.0/lib/solaris:/home/sabha/600sp2only/wlserver6.0/lib/solaris/oci816_8:/
usr/lib
If this does not work, then java for some reason is not taking library paths
set as java.library.path and I dont know how to set LD_LIBRARY_PATH as part
of arguments to java. Another thing is before starting the NodeManager, set
the LD_LIBRARY_PATH to point the library directories and see if this helps.
regards,
Sabha
"Kiran" <[email protected]> wrote in message
news:[email protected]...
>
Sabha,
I am trying to start the managed server via remote start. After readingyour reply
I have cleaned up the argument list for remote start. Now I am gettingaltogether
a different error.(Surpsisingly I was able to start the managed serversusing srartManagedServer.sh.
I dont know why I am having trouble to do the same through the remotestart).
>
I am getting a unsatisfied link error. In your reply you have asked me toadd -Djava.library.path
to the argument liist which I did. Below you can find the exact error Ihave got:
>
>
The WebLogic Server did not start up properly.
Exception raised:
java.lang.UnsatisfiedLinkError:/export/home/spbbprf1/Servers/v25_0/bb/pub/libinterface.so:
ld.so.1: /usr/bin/../java/bin/../bin/sparc/native_threads/java: fatal:relocation
error: file /export/home/spbbprf1/Servers/v25_0/bb/pub/libinterface.so:symbol Opsys_oneWayCryptCmpApi:
referenced symbol not found
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1382)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1306)
at java.lang.Runtime.loadLibrary0(Runtime.java:749)
at java.lang.System.loadLibrary(System.java:820)
atamdocs.APILink.accesscontrol.sum.EncryptApi.<clinit>(EncryptApi.java:20)
atamdocs.APILink.accesscontrol.sum.UserJoltBackend.<clinit>(UserJoltBackend.ja
va:52)
>
atamdocs.APILink.accesscontrol.sum.SumManagerImpl.<init>(SumManagerImpl.java:5
9)
>
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
atamdocs.uamsimpl.server.storage.multi.MultiManagerImpl.<init>(MultiManagerImp
l.java:208)
>
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
atamdocs.uamsimpl.server.storage.cache.CachingManagerImpl.<init>(CachingManage
rImpl.java:81)
>
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
at amdocs.uams.UamsSystem.getUamsManager(UamsSystem.java:156)
atamdocs.uamsimpl.server.ejb.wl6.WLUamsDelegate.<init>(WLUamsDelegate.java:61)
atamdocs.uamsimpl.server.ejb.wl6.WLUamsDelegate.<init>(WLUamsDelegate.java:55)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
at amdocs.uamsimpl.server.ejb.wl6.WLUamsRealm.<init>(WLUamsRealm.java:42)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
at weblogic.security.acl.Realm.getRealm(Realm.java:84)
at weblogic.security.acl.Realm.getRealm(Realm.java:62)
atweblogic.security.SecurityService.initializeRealm(SecurityService.java:258)
at weblogic.security.SecurityService.initialize(SecurityService.java:115)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:402)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
>
>
Please let me know if you need more description.
Thanks,
Kiran
"Sabha" <[email protected]> wrote:
Either you are attempting to start a managed server through its
NodeManager
for which the remote startup arguments are not correct or something else
is
wrong. How are you starting the server? The remote start is only when you
want to start the server through NodeManager and not for normalinvocation
of the startManagedServer script.
Does the server really start? can you paste the startup arguments for the
remote start of the managed server as saved in the config.xml.
What is the log generated when the managed server is startedup.
-Sabha
"Kiran" <[email protected]> wrote in message
news:[email protected]...
Sabha,
The main problem is:
What ever I am trying to give in the command line arguments through theConsole:
Servers -> serverName -> Remote Start->Arguments.
is not being read during managed server start up.
I have all the libraries defined defined in java.lib.path. I dont knowwhy
its not
being read by managed server during start up. Am I missing something.
-Kiran
"Sabha" <[email protected]> wrote:
If its unable to load the performance packs, try setting
java.library.path
to the solaris lib directories. /usr/lib, /home/oracle/lib paths -- oryou
can just copy what is in the admin weblogic.log file for the
java.library.path (make sure the paths are correct and applicable forthe
maanged server box also) and pass that as an argument as
in -Djava.library.path=/usr/lib:/bea/wlserver6.1/lib/solaris...
-Sabha
"Kiran" <[email protected]> wrote in message
news:[email protected]...
Hi,
I am trying to start Managed Server on Sun Solaris. My admin Server
and
managed Server
are on the same Machine.
My admin Server starts up with out any problem. WhenI try to bring
up
my
Managed
Server its not reading the command line arguments which I supplied
through
the Console:
Servers -> serverName -> Remote Start->Arguments. For some reason
these
command arguments
are not read and so I am having errors like Unable to load
libraries,
etc.
Also when I saw the log file for managed server the class path and
the
arguments
are printed in a different way than I have set. I dont know if thats
a
problem or
not. I am copying part of that for your reference.
classpath=/opt/j2sdk1_3_1_01/jre/lib/rt.jar\:/opt/weblogic6.1\:/opt/weblog
i
c
6.1/lib/weblogic_sp.jar\:/opt/weblogic6.1/lib/weblogic.jar\
serverStartArgs=-Dweblogic.management.server\=sunserver\:7210 -Djava.secur
i
t
y.policy\=\=/opt/weblogic6.1/lib/weblogic.policy
I have checked the config.xml file and what ever I have set in the
console
is being
saved properly in the xml file.
Can any one know why the back slash is printed above even though I
havent
typed that
in the console. Has any one have experince with setting the command
line
arguments
and class path through console for Managed servers.
I am stuck up at this point. Any help in this regard will be greatlyappreciated.
Thanks,
Kiran

Administration vs Managed Servers

We are preparing to upgrade from WLS5.1 to WLS8.1 and I am having a problem with
the recommendation that the typical production environment have an administration
server and one (or more) managed servers.
In our environment, we host applications for multiple customers. Currently, each
of these customers has a separate instance of WLS5.1 running. In many cases, the
connection pools have the same name between instances, but with different userids/passwords.
In the conversion to 8.1, I have been debating having a separate domain for each
customer application versus a single domain with a separate managed server for
each customer. The single domain has many desirable features, but it does not
provide for the multiple userid /passwords for a connection pool. The separate
domain per customer eliminates the connection pool issue, but essentially doubles
the number of WLS servers (1 admin and 1 managed) for each customer.
Even though BEA recommends a separate admin server and managed server, in reality,
how important is this? Will I cause myself problems in the future if I choose
to run a combined admin and managed server?
Thanks for any thoughts on this subject.

Thanks David. As God as my witness, the tech seriously told me that they all use the same JVM. Then I got seriously confused, like I was an idiot and didn't understand what a JVM was and I started second-guessing myself. The whole conversation was very strange and yes, there was definitely a language barrier and I'm guessing I just wasn't being clear enough...I don't know...all I know is I walked away from the phone call in worse shape then when I first opened the ticket.
At any rate, do you have recommendations for admin server ram? I know there are performance tuning tools to help us figure out the optimum settings for our managed server, and I plan on implementing them...but going back to the ram for the Admin server, versus managed server...is there a recommended way of specifying different heap size for the managed servers? Is the recommended way to set the the -Xms and -Xmx settings via the 'Arguments' field on Environment > Servers > serverName > Configuration > Server Start tab via the admin console?
Thanks again for your quick reply!
Cheers,
rlb

OSB Managed Servers - How to add one to the OSB Cluster

Hi,
I have an OSB Cluster of two managed servers. There is an Admin Server that controls the two.
On the Admin Server I see that there are about 137 odd Applications and a list of Libraries installed.
However on the Managed Servers I see there is not a single application.
Does Managed Server show only the Custom applications? I feel not. Applications like AQAdapter, MQ Adapter, ALSB Routing, etc. should they all not be present on the Managed Servers?
If I create a new Managed Server that I want to Add to the Cluster there is no option to deploy those applications to the newly created Managed server in one shot. The only time it can get those applications is if the Applications were deployed to the OSB Cluster and not to the managed servers.
Is there a way (apart from extending the domains again and having those applications deployed to the OSB cluster) to have all these applications running on the Managed servers as well?

Does Managed Server show only the Custom applications? I feel not. Applications like AQAdapter, MQ Adapter, ALSB Routing, etc. should they all not be present on the Managed Servers?Your understanding is correct. Managed server should have libraries and adapters targetted to it.
Is there a way (apart from extending the domains again and having those applications deployed to the OSB cluster) to have all these applications running on the Managed servers as well? Yes, manually you have to target each and every application to the cluster but it may not be an effective process. The basic funda of cluster is to make applications independent of managed server, so that if you add/remove a managed server then it does not affect the existing configuration. I think you should follow the standard practice and always create a clustered domain where all applications are targetted to cluster and NOT to the managed server. You may like to refer -
http://download.oracle.com/docs/cd/E17904_01/doc.1111/e15022/config.htm#i1531648
Regards,
Anuj

Creating new Managed Servers on remote machines

Hi,
We have a multi-machine domain already in place. Nodemanager is configured and we're using the architecture suggested in Oracle SOA Enterprise Deployment Guide, where we have one domain home for the AdminServer and one domain home for the Managed servers. Right now what we need to know is how to add new managed servers in the easiest and fastest way possible on the mserver home on both the adminserver local machine and on the remote machine, this is a development environment and we need to be able to quickly create and delete these servers for developers to work.
We know that the standard way of doing it is doing a pack (for the managed servers only), and then an unpack on the mserver home both on local and remote machine after changing the root directory of these servers to match those homes. Here is were we have our first doubts. Do the unpack command command has to be run with the already running servers down? Does this pack and unpack process affects what we already have deployed on the running managed servers? And last but not least, is there any way to automate this process? Because we need to give the developers the ability to create clusters on the environment through the admin server console, but without giving them access to the underlying operating system.
If this seems like a newbie question is because we are, we're just in the process of migrating oas 10g to weblogic 11g and there are tons of basic administration stuff that seem pretty strange for us, we've looked through the Oracle manuals and metalink but even though some show you how to create the domain with remote managed servers for the first time, we couldn't find any mention on how to add the mserver efficiently after that.
Thanks!

Cris,
Thanks again for your help, we're trying to figure out how to present this procedure to our customer, just one thought though, we were thinking about moving away from the architecture presented by de SOA Enterprise Deployment guide, and using a single domain home located on the shared storage, that way we could create the managed servers from the admin console without having to use pack/unpack and deciding where to run the servers just by configuring machines and nodemanager. However, we haven't seen this kind of configuration anywhere on Oracle manuals, is there any other problem you are aware of in this idea? We're using a storage with multipath for the shared disk so we're not very concerned about availability (and if the storage went down the weblogic domain would be the least of our problems).
Regards, Franco.

Calculating how many managed servers you need.

Hi,
Does anyone know a BEA webpage were it tells you, on the lines of :
If you have 5000 customer hitting your weblogic cluster you only need 1 managed server. If you have 30,000 you need two managed servers. If you have 500,000 you need three.
Does anyone know of a performance page like this?
Regards,
Alistair.

There is no such performance numbers from BEA. I think you need to rely on capacity planning process to estimate number of server based on your workload and performance requirements.
http://dev2dev.bea.com/pub/a/2002/11/Hazarika.html
http://edocs.bea.com/wls/docs81/capplan/capfact.html#1009720
There are some benchmark results for WebLogic are available at
http://edocs.bea.com/wls/docs81/capplan/capbase.html#1054891
http://www.spec.org/jAppServer2004/results/jAppServer2004.html
-Jayesh

How create one cluster whit managed servers in diferent hosts?

in the same domain

Have you created a domain using the config tool ( which gives you just an admin server and no managed servers )?
Start your admin server & login.
Create a session in the Change Center
Create 1 machine within the admin console for each host: ( Domains -> Environment -> Machines - > New ). Use the actual host name for the value of Machine Name.
So create a machine named "myhost1.yourcompany.com" and a machine named "myhost2.yourcompany.com".
You can also do this within the configuration tool:
http://download.oracle.com/docs/cd/E12840_01/common/docs103/confgwiz/custom.html#wp1071071

How nodemanager starts managed servers?

Hello All,
I'm facing strange issue with weblogic server. Currently i'm using WLS 8.1 SP 4 on solaris 9 server.
To start weblogic i have customize the script such that when server goes on reboot it will pick the startweblogic.sh script from /opt/bin and start the weblogic. Where as in startweblogic.sh i have mentioned -
NMLOG=/u001/wls8/bea/user_projects/prodDomain/logs/optbin/nodemanager.log; export WL8NMLOG
ADMINLOG=/u001/wls8/bea/user_projects/prodDomain/logs/optbin/adminserver.log; export WL8ADMINLOG
CLUSTERLOG=/u001/wls8/bea/user_projects/prodDomain/logs/optbin/cluster.log; export WL8CLUSTERLOG
cd /u001/wls8/bea/weblogic81/server/bin/
su weblogic -c "./startNodeManager.sh >> $NMLOG 2>&1" &
sleep 60
cd /u001/wls8/bea/user_projects/prodDomain/
su weblogic -c "./startadminserver.sh >> $ADMINLOG 2>&1" &
sleep 1200
cd /u001/wls8/bea/user_projects/prodDomain/
su weblogic -c "./startcluster.sh >> $CLUSTERLOG 2>&1" &
Though the script works as expected till adminserver is UP/Running, but script doesn't wait for 1200 secs. to start cluster. Somehow nodemanager starts the managed servers immediately after the adminserver is UP.
I have checked the nodemanager.properties file, there is nothing such mentioned. Also, from console i have unchecked the option of AutoStart for both managed servers.
Can anyone tell me how nodemanager starts the managed servers automatically??
Thanks,
HK

can you please tell me what is this .startCluster.sh script.
is it your custom script?
And the idea i have in my mind is that after
cd /u001/wls8/bea/weblogic81/server/bin/
su weblogic -c "./startNodeManager.sh >> $NMLOG 2>&1" &
sleep 60
cd /u001/wls8/bea/user_projects/prodDomain/
su weblogic -c "./startadminserver.sh >> $ADMINLOG 2>&1" &
sleep 1200
you can give the command to start the individual managed servers like:
cd /u001/wls8/bea/user_projects/prodDomain/
su weblogic -c "./startManagedWebLogic.sh <arguments> >> $CLUSTERLOG 2>&1" &
I think this way it will work....

Limit on number of Managed Servers in a cluster

          Hi All,
          Do you know if there is any limit on number of managed servers I can have in a
          cluster.
          If there is a limit then how many?
          If not, is there a recommended limit from BEA?
          We are using Weblogic 6.1 SP2 and we have 16 managed servers running in the cluster.
          Under heavy load (through put about 600-800) the console is not responding fast.
          Also when we try to monitor the Weblogic Servers from the console under Monitoring->performance
          , the screen is not getting refreshed faster(which makes me think the monitoring
          info I see on the console is not completely correct).
          I have a heap size of 96m for admin and 768m for Managed Servers.
          Did anyone see this problem before.
          Are there any command line arguments that I can add to make my console respond
          faster?
          If not, do we have any patch from BEA that makes console work faster?
          Please suggest.
          Thanks for your attention,
          Kiran


Hi Vineet,
In Latest version of SAP MDM which is 7.1 we have the liberty to use multiple Main tables so answer to your question is yes we can use 20-30 main tables, now the question is that what type of data model you are prepairing this question is just to understand your entire structure and may be suggest some thing at higher level on which you can think and then take corrective action as per your thoughts.
Generally even if you are integrating Customer/Products in single repository and then designing the main table you wont have to prepare such huge number of main tables you can have these two main tables and then rest of then as sub tables and refer it to each other also you need to know what imapct it will have on system performance becuase they would be referring to each other and also if you are creating some thousands of records in each repository then it is more advisable to use limited number of main tables and use MDM to it's fullest capability by designing such model that we have best utlisation of server performance.
Hope it helped a bit.
Let me know if you need any further information on same.
Thanks and Regards
Praful.

SCOM 2012 SP1- Getting Event ID 20070 on some agents and Event ID 200000 on management servers

On a significant number of my 2012 SP1 Agents, I am getting the following Event IDs in my OperationsManager event log:
20070
The OpsMgr Connector connected to XXXXXX.domain.net, but the connection was closed immediately after authentication occurred. The most likely
cause of this error is that the agent is not authorized to communicate with the server, or the server has not received configuration.
21006
The OpsMgr Connector could not connect to XXXXXX.domain.net:5723. The error code is 10060L(A connection attempt failed because the connected
party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.).
21015
OpsMgr was unable to set up a communications channel to XXXXXX.domain.net. Communication will resume when XXXXXX.domain.net is available and
communication from this computer is allowed.
On my various 2012 SP1 Management Servers, I am getting the following Event IDs in my OperationsManager event logs:
20000
A device which is not part of this management group has attempted to access this Health Service.
Requesting Device Name: servername.domain.com
Here are my settings and what I have tried:
We have agents assigned by AD-integration, and they are receiving their proper assignment
Agents are manually installed with SCCM 2012
“Automatically approve new manually installed agents” is selected
I have rebuilt the Health Service State folder and rebooted the service on the agent server
I have rebuilt the Health Service State folder on my management server and rebooted it to reset all services
On several agent servers that I am experiencing this issue, they are on the same network as their assigned management server, so there is no firewall issue.

Hi,
Here is a KB for your reference.
Troubleshooting gray agent states in System Center Operations Manager
http://support.microsoft.com/kb/2288515
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Not able to restart managed servers after password change in console

im doin the following steps,am i doin anything wrong?
1)shutdown all managed servers
2)change pwd in admin console
3)edit boot.properties file with new pwd in admin server
4)copy these boot file to every managed server
5)now restart admin server.(able to do it succesfully)
6)not able to restart managed servers (im getting the following error.
Can any help me out plz very urgent?
<Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(Unknown Source)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(Unknown Source)
at weblogic.security.service.SecurityServiceManager.initialize(Unknown Source)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
Truncated. see log file for complete stacktrace
<Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>

Hi,
*1)In order to export the user data on to the server,do we have to create a specific directory to save this data into the server.*
Yes ....you can give any Existing Directory Path in the AdminConsole Export Page.... Any Directory in your File System.
*2)Is there any other way by not exporting or importing the data?*
That is the only way to prevent the Data Loss....There are some other ways to do it without using Admin Console like Using WLST or Using JMX you can export the Data but all these techniques will exactly do the same thing ... The AdminConsole is the easiest way to do it.
Thanks
Jay SenSharma
http://middlewaremagic.com/weblogic/ (Middleware Magic Is Here)

Multiple Standalone Persistence Manager Servers in a single JVM?

Greetings [Kodo 3.4.1, Oracle9i]
I am currently working on introducing the Kodo Standalone Persistence
Manager Server into our architecture. One issue is that our application
accesses several different databases, each via a separate
PersistenceManagerFactory. This would mean (I think) that I would need to
start a separate Standalone PM Server for every database, which would mean
about 10 different JVMs running, just for the required Standalone PM
Servers...
The question... Will it be possible and sensible to run multiple
"Standalone" Persistence Manager Servers within a single JVM? The idea
would be for me to write a threaded server, where each of my threads invokes
kodo.jdbc.runtime.StartPersistenceManagerServer.run(someJDBCConf), where I
provide a JDBCConfiguration for each database I want to connect to. This
means that my server will effectively be listening for clients on several
different ports and accessing several databases all from within the same
JVM.
Is this feasible? Anyone with access to the source, can you say that the
StartPersistenceManagerServer.run() method may be safely run in several
different threads?
I suppose another option would be to use the HTTP Persistence Manager Server
and then simply deploy 10 servlets, one per database... But I'm trying to
avoid introducing a servlet container into the mix.
Thanks
Drew

Hi Marcus and thanks...
Yes, I want to use Remote Persistence Managers. Currently we have a 2-Tier
application, but we need to introduce a 3rd tier to be able to use the
DataCache. If we don't do this, then each running application will have
it's own DataCache, which will not "see" changes in other running
application DataCaches. I have tried to attach a "before" and "after"
diagram to illustrate...
Now if we extend this a bit further, and say that instead of just one
database, our application actually needs to access 10 different databases
(so 10 different PersistenceManagerFactories and 10 different DataCaches),
then hopefully it is clear that we would then need 10 separate Standalone
Persistence Manager Servers. I have attempted to attach another diagram to
illustrate.
I don't really want to start up 10 Remote PM servers, I would rather just
have one server, which brings me back to my original question... Can I run
them all in a single JVM?
Cheers and thanks
Drew

Custom Managed Servers

Similar Messages

Maybe you are looking for