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

Similar Messages

  • 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.
     

  • Domain Created: Failed Restarting 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 Revanth,
    The issue seems to be with the JMX URL value defined in the 'server URL' property.
    Apparently I ran into the same issue as I was unable to access the Admin Server URL from the SMA.
    Changing the Host and Port value properly resolved the issue for me.
    Regards,
    Anandraj

  • 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,
    <font color=red>OPTION-A)</font>
    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
    <font color=red>OPTION-B)</font>
    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

  • Cisco Prime Infrastructure 2.1 can't add Cisco ISE 1.2 to "External Management Servers"

    Hi all,
    I'm trying to add Ciso ISE 1.2 (1.2.0.899 with version 13 patch) servers (primary and secondary) as "External Management Servers" in Cisco PI 2.1 (2.1.0.0.87) but there appears such message indicating that ISE server is not reachable: 
    The weird thing is that ISE servers are reachable from PI and vice-versa (I can ping each other from their CLIs)
    There were added ISE servers to PI long ago (primary and secondary ISE) and then secondary was deleted from PI. Primary ISE still persists in PI but its status is unreachable:
    But I can see info about wired clients authenticating on the switchs (NADs for ISE) - weird, status is unreachable but client info is being received from ISE.
    I tried application stop NCS/application start NCS on PI and application stop ise/application start ise on ISE - no success for that issue.
    So I can't find a way to solve that weird issue, maybe you can help me find out the cause of such things. Thanks. 

    Hi,
    -- Please Go to Administration > Logging > set the Message level to TRACE > Click save
    -- Then try to add the ISE.
    -- Once it fails, collect the logs from Administration > Logging > 
    check the "ncs-0-0.log"  & search the file for "ERROR" & paste the results here. This will give us exact reason.
    - Ashok
    Please rate the post or mark as correct answer as it will help others looking for similar information

  • Problem while starting Managed Servers from Admin Server console

    I am facing a problem while trying to start the managed servers in wlp8.1 portal from the admin server console.
    <Dec 7, 2004 4:52:14 PM IST> <Info> <NodeManager@*.*:5555> <Starting Server orbitPortalDomain::orbit_ManagedServer1 ...>
    <Dec 7, 2004 4:52:16 PM IST> <Info> <NodeManager@*.*:5555> <Server orbitPortalDomain::orbit_ManagedServer1 started, process id = 1,832>
    <Dec 7, 2004 4:52:17 PM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.4.2_04-b05 from Sun Microsystems Inc.>
    <Dec 7, 2004 4:52:18 PM IST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://10.6.0.212:7001 to check if there exists a running admin server at this URL.>
    <Dec 7, 2004 4:52:18 PM IST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
    <Dec 7, 2004 4:52:18 PM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic XMLX Module 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973 >
    <Dec 7, 2004 4:52:18 PM IST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://10.6.0.212:7001 to retrieve the initial configuration.>
    <Dec 7, 2004 4:52:21 PM IST> <Notice> <Log Management> <BEA-170019> <The server log file D:\bea_turner\weblogic81\common\nodemanager\orbit_ManagedServer1\orbit_ManagedServer1.log is opened. All server side log events will be written to this file.>
    The WebLogic Server did not start up properly.
    java.lang.NoClassDefFoundError: com/bea/wsrp/util/debug/Debug
    at com.bea.wsrp.security.WSRPIdentityAsserterProviderImpl.<clinit>(WSRPIdentityAsserterProviderImpl.java:45)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
    at java.lang.Class.newInstance0(Class.java:308)
    at java.lang.Class.newInstance(Class.java:261)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.createSecurityProvider(SecurityServiceManagerDelegateImpl.java:232)
    at weblogic.security.service.SecurityServiceManager.createSecurityProvider(SecurityServiceManager.java:939)
    at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:151)
    at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:257)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.doATN(SecurityServiceManagerDelegateImpl.java:581)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealm(SecurityServiceManagerDelegateImpl.java:420)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.loadRealm(SecurityServiceManagerDelegateImpl.java:698)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealms(SecurityServiceManagerDelegateImpl.java:731)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(SecurityServiceManagerDelegateImpl.java:874)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:717)
    at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:822)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:670)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:344)
    at weblogic.Server.main(Server.java:32)
    Reason: com/bea/wsrp/util/debug/Debug
    pls advice
    Thanks
    Sasanka

    Hello,
    There is a lot of stuff on this thread:
    http://forum.java.sun.com/thread.jspa?threadID=567363&messageID=2801617
    these guys are trying to run weblogic with JBuilder.
    Looks like your classpath is incorrect, can you go to your admin console-->server-->remote start
    copy the classpath and post it here.
    Check for spaces in your classpath, missing jars or directories and miss spelt paths.
    Has this problem been occuring as soon as you installed WLP or not?
    Cheers,
    Hoos

  • 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,
    <font color=red>OPTION-A)</font>
    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
    <font color=red>OPTION-B)</font>
    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

  • 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"?>
    <!--If your domain is active, please do not edit the config.xml file. Any changes
    made to that file while the domain is active will not have any effect on the domain's
    configuration and are likely to be lost. If your domain is inactive, you may edit
    this file with an XML editor. If you do so, please refer to the BEA Weblogic Server
    Configuration Reference documentation available from http://edocs.bea.com/wls/docs61/reference.html.
    In general, we recommend that changes to your configuration file be made through
    the Administration Console.-->
    <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

  • Weblogic managed servers question

    Hi all,
    I'm trying to set up a 3 machines , one having weblogic admin
    server and two machines having managed weblogic servers.what i'm not
    undersatnding is :
    1. Do i have to install the weblogic software on all machines with the same
    domain name .?
    2. Do i have to deploy my components/web applications on all machines?
    3. Do i have to put the above machines in a cluster to achieve load
    balancing etc.
    4. How will i access my manage servers considering that they will have 2
    different ips (since they are installed on 2 different
    machines)?
    5.Does anyone know any dosc online which explains these matters.I have gone
    through the weblogic server administrator
    guide , but could not find the information i'm looking for (or have i
    missed any section)?
    Thanks in advance
    Prashant

    Hi.
    My answers are embedded:
    Prashant S wrote:
    Hi all,
    I'm trying to set up a 3 machines , one having weblogic admin
    server and two machines having managed weblogic servers.what i'm not
    undersatnding is :
    1. Do i have to install the weblogic software on all machines with the same
    domain name .?I'm not sure what you mean. The managed servers need to be in the same
    weblogic domain (ie directory under config) if you are using clustering. Also
    if you are using clustering the cluster members (managed servers) need to be on
    the same LAN/subnet.
    >
    2. Do i have to deploy my components/web applications on all machines?You do not have to deploy your applications on your admin server. Typically I
    install a webapp (or whatever) on the admin server then select the targets for
    deployment to the managed servers.
    >
    3. Do i have to put the above machines in a cluster to achieve loadbalancing
    etc.Yes.
    >
    4. How will i access my manage servers considering that they will have 2
    different ips (since they are installed on 2 different machines)?For web applications the standard practice is to use a proxy front-end to the
    cluster. We offer plugin's for Netscape, Apache and IIS that handle
    loadbalancing and failover for weblogic clusters. We also offer the
    HttpClusterServlet if you prefer to use an instance of WLS to proxy to your
    cluster. Use your browser to hit the proxy, which will pass your request on to
    a cluster member. See the following link for details:
    http://edocs.bea.com/wls/docs61/adminguide/http_proxy_cluster.html
    >
    5.Does anyone know any dosc online which explains these matters.I have gone
    through the weblogic server administrator
    guide , but could not find the information i'm looking for (or have i
    missed any section)?
    Thanks in advance
    Prashantnot sure if you have seen this but
    http://edocs.bea.com/wls/docs61/cluster/index.html contains links to docs
    discussing most cluster administration issues.
    Hope this helps.
    Michael Young
    Developer Relations Engineer
    BEA Support

  • JMS with managed servers

    I have created two independent server instances, each with their own applications directory, config.xml file, etc. Now I want them to be able to use JMS to communicate with each other. It is my impression that there are a couple of ways to do this, the easiest of these being to add the server instances as managed servers to the same administration server so they exist in the same domain, then set up a single JMS configuration for that domain. Is this right?
              If so, how do I set the administration server for an independent server instance? Must I also explicitly change its domain to match that of the administration server?
              Or is this not possible and I need to use a messaging bridge?
              Thanks in advance.
              David

    Hi David,
              I'm not sure, but I don't think you can set up an admin server for an "independent server instance". I think all servers in the domain are either a "managed server", or an "admin server", where managed servers get their configuration from the admin server. Regardless, with the "domain" approach, I assume you are leaning towards going a bit further and configuring a cluster, which would automatically allow any app on any server within the cluster to transparently lookup any resource in the cluster in the global JNDI context. All of this information is in the general documentation (not the JMS documentation).
              I think there are pluses and minuses to either approach you mention. For simplicity, if you don't need clustering features, you might simply want to try the "interop" approach and see if its good enough for your purposes, rather than going through the trouble of setting up an admin server and a cluster:
              http://e-docs.bea.com/wls/docs81/faq/interop.html
              In this approach, cross-communication always involves references the remote server's URL at some point, but this URL might be specified via configuration (MDB, bridge, SAF, foreign dest all provide ability to specify a URL).
              Hope this helps,
              Tom

  • Why 2 floating IP's are used to Weblogic managed servers?

    In the configuration example discussed in this guide, two floating addresses
    are used to each of the WebLogic Managed Servers and to the Administration
    Server. The first type of floating IP address uses the IPoIB (BOND0) interface,
    and the second type of floating IP uses the EoIB (BOND1) interface.
    The above are excerpts from this document: http://docs.oracle.com/cd/E18476_01/doc.220/e18479.pdf page 3-10
    My question is, why do I have to use 2 floating IP's, one uses bond0 and the other uses bond1? can I just create one floating on bond1 and for all purposes, for instance? For what reasons, do I have to use 2 floating IP's?
    Thanks!
    Edited by: 943714 on Jan 29, 2013 12:01 PM

    Hi,
    Two floating IP's should be used because on an Exalogic machine there are multiple network interfaces. As it says on that document, bond0 is for IPoIB and bond1 is EoIB.
    bond1 is the interface available outside the Exalogic machine. But, for example, if you need to connect to an Exadata machine (using Weblogic with JDBC/GridLink) that must be done through InfiniBand (IPoIB - bond0 interface).
    Hope this helps.
    -Cris

  • 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.

  • Problem with discovering Managed Servers

    Hi,
    I got problem with discovering managed servers, when I restart only administration
    server while managed servers are running. During restart of admin server everything
    seems to be ok (the directive: Starting discovery of managed server... appears
    on the screen).
    However when I start admin console through http, I cannot monitor performance,
    browse logs etc. I can only shutdown managed server and I can see in a server
    tag that particular managed servers are running.
    I'm looking forward for any clues
    Michal

    Sorry,
    i cannot stop those managed server - in Control tab I have active only option
    to start those server but they are running. In logging tab when I want to browse
    the log the message that probably this server is not running appear. However in
    the tab when all servers are listened there is a message that they are running
    "Michal" <[email protected]> wrote:
    >
    Hi,
    I got problem with discovering managed servers, when I restart only administration
    server while managed servers are running. During restart of admin server
    everything
    seems to be ok (the directive: Starting discovery of managed server...
    appears
    on the screen).
    However when I start admin console through http, I cannot monitor performance,
    browse logs etc. I can only shutdown managed server and I can see in
    a server
    tag that particular managed servers are running.
    I'm looking forward for any clues
    Michal

  • Status of managed servers in a cluster

    i have an environment with multiple clusters . I want to deploy code using WLST to a specific cluster. Before deploying i want to check if the managed servers in that cluster are running ...
    how to check only managed servers in a specific cluster ... and not all managed servers in that domain ..
    connect("weblogic","xyz",admin:port)
    deploy ("abc","xyz.war","mycluster")
    where mycluster has 2 managed servers. My domain has several clusters
    thanks

    import sys
    import time
    url = sys.argv[ 1 ]
    username = sys.argv[ 2 ]
    password = sys.argv[ 3 ]
    try:
         connect( username, password, url )
    except WLSTException:
         print 'Administration server not running.'
         exit()
    print 'Shutting down servers for domain at url ' + url + '...'
    adminServer = cmo.getAdminServerName()
    cd( 'Servers' )
    servers = cmo.getServers()
    domainRuntime()
    for s in servers:
         serverName = s.getName()
         if serverName != adminServer:
              try:
                   serverRuntime = getMBean( '/ServerRuntimes/' + serverName )
                   serverState = serverRuntime.getState()
                   if serverState == 'RUNNING':
                        shutdown( name = serverName, entityType = 'Server', force = 'true', block = 'true', timeOut = 60000 )
                        print 'Server ' + serverName + ' shut down.'
              except AttributeError:
                   print 'Server ' + serverName + ' is not currently running.'
                   continue
    try:
         shutdown( name = adminServer, entityType = 'Server', force = 'true', block = 'false', timeOut = 60000)
    except WLSTException:
         print 'WARNING: Error occurred while attempting to shut down server ' + adminServer + ' .'
    print 'Server ' + adminServer + ' shutting down.'
    exit()

  • Scripts for starting/stopping managed servers

    All,
    Could someone provide me with some sample scripts for starting/stopping managed Weblogic servers?  I'm specifically looking for ways to start/stop them WITHOUT starting the AdminServer.  I'm running WLS 10.3.6 on Windows Server 2003, and I have NodeManager set to start automatically as a Windows service.
    I know how to set my managed servers up as Windows services so that they will start automatically at boot, but this requires the AdminServer to be running, which I do not want.  I just want a few scripts for starting/stopping the managed servers (and maybe some hints as to how to make them start automatically without starting the AdminServer).
    Thanks in advance,
    Tom

    Hello Puneet,
    Admin console is an web application deployed into AdminServer. Hence if you shutdown AdminServer then you wouldn't able to access Admin console.
    Managed Server would function in MSI mode, however you will not be able to make any configuration or administration activities like deployment , any configuration changes , etc.
    Hello PRISM,
    Can you confirm your requirement about why you don't want AdminServer to be running?
    As I said,  you will loose the administration capability if you don't have admin server running.
    Regards
    Rosario

Maybe you are looking for

  • Mail routing to wrong mailbox

    I run Mail 3.3, with 10.5.4. I today just zeroed the drive and reinstalled. As is typical, the only persisting issue is Mail. This is one issue I can't recall experiencing before, though. I have mail that is addressed to two different email addresses

  • Fbl5n profit center is cracked   , itz possible to get profit center value

    fbl5n profit center is cracked u  , itz possible to get profit center value in ur zfbl5n report der r few changes in program to b made Message was edited by:         Ronei Shedi

  • Graphic collection for a presentation of BW

    Hello, I look for diagrams / graphics for a presentation of the Business Warehouse. Can someone send which to me to [email protected] ? Or do I find diagrams somewhere on sap.com? Is there a finished collection? Many greetings, Alexander

  • Cannot Update T61: Error message

    I have a T61 laptop, still under warrenty. I cannot update it. I always get the same error. At first I thought it was a swerver error, but the error haas lasted for months. I will go to System Update. I will click update. Then it tries to read my sys

  • Attach DIR at goods receipt and invoice,

    Hi SAP Gurus, Can any one help me in attaching DIR or any documents at Goods receipt stage, MIGO transaction, and invoice transaction MIRO, And also the DIR which i attach at Purchase order is not visible at Goods receipt MIGO, and Invoice receipt, M