Management Servers in untrusted domains

Hi,
I am planning a deployment of SCOM 2012 R2 and have several questions regarding the appropriate placement of management and gateway servers.
The environment has multiple untrusted domains and need to monitor both Windows and Linux computers on both sides of the firewall. The main domain has 1500 Windows computers and 1300 Linux computers. The untrusted domain has 250 Windows servers and
450 Linux servers.
It is understandable that gateway servers are utilized to communicate across the firewall.
The questions are:
1. Is it possible to locate one or more management servers in the untrusted domain for the Linux servers and another management server to work with the Windows servers and have those management servers in the untrusted domain communicate through the firewall
via gateway servers to the databases in the main domain?
2. If it is not possible to have management servers in the untrusted domain communicate via the gateways; how many gateways would be required to relay to the management servers in the main domains management group?
3. With the number of Linux servers in the untrusted domain is it better to install a separate management group there?
Thanks, for any advice in dealing with the above scenario.
--SG

Hi There,
Microsoft recommends you to place all the management servers in the same data center so if 1 goes down the other comes to know about it asap.
If you place it in another location then fail over may happen late.
Also you have mentioned to place the management servers in another domain, Which is possible but you need to have trust and permission stuff which is a very hectic work.
So i would suggest you to place gateways as it will help in compression if the network bandwidth is low between the domains and sites.
And based on the MS's Sizing and management options a Gateway server can manage 100 Unix boxes for a dedicated gateway server and 500 per management server on the same domain.
So based on your situation as below:
1300 Linux - Same domain
450 - Different domain
3 Management servers for the main domain for dedicated Linux
1 MS For Windows Agent monitoring.
Totally 4 in a management group for the same domain one.
1 Separate management group with 1 MS will be fine for dedicated Linux monitoring for the 450 servers in the other domain.
If you want to still place gateways then you will need to place 5 Gateway servers which is difficult to manage.
Operations Manager supports the following number of monitored items.
Monitored item
Recommended limit
Simultaneous Operations consoles
50
Agent-monitored computers reporting to a management server
3,000
Agent-monitored computers reporting to a gateway server
2,000
Agentless Exception Monitored (AEM)-computers per dedicated management server
25,000
Agentless Exception Monitored (AEM)-computers per management group
100,000
Collective client monitored computers per management server
2,500
Management servers per agent for multihoming
4
Agentless-managed computers per management server
10
Agentless-managed computers per management group
60
Agent-managed and UNIX or Linux computers per management group
6,000 (with 50 open consoles); 15,000 (with 25 open consoles)
UNIX or Linux computers per dedicated management server
500
UNIX or Linux computers monitored per dedicated gateway server
100
Network devices managed by a resource pool with three or more management servers
1,000
Network devices managed by two resource pools
2,000
Agents for Application Performance Monitoring (APM)
700
Applications for Application Performance Monitoring (APM)
400
URLs monitored per dedicated management server
3000
URLs monitored per dedicated management group
12,000
URLs monitored per agent
50
Refer the below link for the managing details: https://technet.microsoft.com/en-us/library/dn249696.aspx?f=255&MSPPError=-2147217396
Gautam.75801

Similar Messages

  • Shutdown(block='false') only works via Admin Server, not managed servers

    Hello,
    We want to shut down all 10 managed servers in our domain gracefully, and in parallel. 5 of those managed servers are on the same OS/host as the AdminServer, the other 5 are on a separate OS/host (i.e. we have 5 x 2-node clusters).
    I'm writing scripts to gracefully shut down all of our servers upon an OS reboot command. On the OS with the AdminServer (and 5 managed servers), I can simply do this:
    connect(user, pwd, http://localhost:7001)
    shutdown('myserver1', 'Server', block='false')
    shutdown('myserver3', 'Server', block='false')
    shutdown('myserver5', 'Server', block='false')
    shutdown('myserver7', 'Server', block='false')
    shutdown('myserver9', 'Server', block='false')
    All 5 servers will be shutting down at the same time. If they each took 2 minutes to shut down, the whole shutdown process would take 2 minutes.
    However, on the OS running the other managed servers, I cannot assume that the AdminServer [on the other OS] will be online. Hence, I would like to gracefully shut down each server locally like this:
    connect(user, pwd, url='t3://localhost:8001')
    shutdown(block='false')
    disconnect()
    connect(user, pwd, url='t3://localhost:9001')
    shutdown(block='false')
    disconnect()
    connect(user, pwd, url='t3://localhost:10001')
    shutdown(block='false')
    disconnect()
    connect(user, pwd, url='t3://localhost:11001')
    shutdown(block='false')
    disconnect()
    connect(user, pwd, url='t3://localhost:12001')
    shutdown(block='false')
    disconnect()
    NOTE that the ports are different (i.e. I connect via WLST to the managed servers themselves rather than to the AdminServer).
    Unfortunately, in this scenario, the block='false' does not work. WLST waits until the managed server is shut down before proceeding to the next connect() command. So if each server took 2 minutes to shut down, the whole shutdown process now takes 10 minutes.
    We don't want to use the nmKill() command on the local Node Manager because we want a graceful shutdown.
    What options do we have to issue a graceful shutdown command either to a local Node Manager or to the managed servers themselves (since we can't expect the AdminServer to be online when our script runs)?
    Best regards,
    Michael

    Hi Mike,
    WLST will create it temp directory with /var/tmp/wlstTemp which is shared by all users. Since we cannot differentiated by different users which cause block on particular user at that time.
    One solution is to grant write access to all users to the directory where the WLST temporary directory is created (e.g. on Solaris /var/tmp; you can verify the default on your system by executing java utils.getProperty and search for java.io.tmpdir).
    If for whatever reason you cannot grant these access modes on the temporary directory, then you can create a directory somewhere on the file system where every user has the correct permissions.
    Start the scripting tool with one the following options to redirect the cache files to the specified directory. Dependent on your environment one or the other will apply.
    java -Djava.io.tmpdir=<path-to-tmpDir> weblogic.WLST
    or
    java -Dpython.cachedir=<path-to-tmpDir> weblogic.WLST
    This will be useful to make shutdown of servers without any problem.
    Note: block=false will always works it should not be the problem.
    Regards,
    Kal

  • Managed servers on multiple platforms?

    Hi,
    I was wondering if all of my managed servers in a Weblogic domain have to be running on the same platform. For example, can I mix Solaris/SPARC and Linux/x86 boxes within the same domain such that some remote managed servers in the domain are different? In the WL documentation, it mentions that all WLS instances in a domain must be running the same version of WLS itself, but it doesn't mention the underlying OS or hardware. I'm assuming that since everything is running in a JDK, it's OK to do, especially since I'm using a generic WLS installer for UNIX platforms.
    Install WebLogic Server on the machines on which you want to host Managed Servers for the WebLogic domain.
    Note:
    All WebLogic Server instances within a WebLogic domain must run the same version of the WebLogic Server software.
    Thanks in advance for your help.

    Hi Kent,
    It should work fine.
    This kind of mixes are generally not recommended in order to avoid conflicts due to packages specific for each OS, but should not be the case of the generic installer.
    The generic installer is truly generic to all OS platforms. Note that you must comply with the published supported platforms (OS, chip set, etc).
    Sinice Java is platform independent, there is no distinction between a Java application running on Linux and the same application running on Windows. A Java application is the same and can be run on any OS bit version of any flavor without a single change.
    At its root, WebLogic Server is a Java application, nothing more, nothing less. So, think of WebLogic Server as a Java application that is run like any other Java application by invoking the main method. In WebLogic Server the main method is in the weblogic.Server class. So, to start WebLogic Server we use the java command, the same as for any other Java application:
    java <MEM_ARGS> -cp <CLASSPATH> <JAVA_OPTIONS> weblogic.Server
    As mentioned in your post, make sure the JVM is the same (JVM mixtures in a cluster are not supported).
    -Cris

  • Starting managed servers

    Hi,
    Environment: WebLogic 6.1 SP2, JDK1.3.1, Solaris 8
    1. How to start the managed servers using NodeManager from the command line? Already
    NodeManager configured and able to start managed servers from the Admin Console.
    So from the console start/stop/kill managed servers is fine. From the command
    line, if I use `weblogic.Server` to start managed server it's not using the node
    manager.
    2. In the `java weblogic.nodemanager.NodeManager help`, option `starttemplate`
    defaults to `nodemanager.sh`. Any details on this please ?
    3. Each time we start managed server with Node Manager, it writes the output to
    the new file `OutputFile=./config/NodeManagerlogs/<server>/startserver-<XXXX.log`.
    From the documentation it looks like we can set logs directory
    `-Dweblogic.nodemanager.savedLogsDirectory=path`, however is it possible to specify
    the log file name also?
    4. Where is the location of the java applications `System.out`, if the managed
    server is started with NodeManager. If the managed server is started with `weblogic.Server`
    the `System.out` are printed to the console. So this enables us to redirect to
    a file.
    thanks
    Sarva Meduri

    I think you can configure the NodeMgr to start ManagedServers instead of having the
    Windows Service start the servers. Basically you configure NodeMgr as a Windows Service
    and then let NM take care of starting other servers. I believe you have to set
    ManagedServer's HostsMigratableServices attribute to false to enable NM start the server.
    By default it is true.
    prasen
    Gerardo Rojas wrote:
    Hi:
    I have been trying to configure my WebLogic environment to start the managed servers
    in a domain automatically when the machine is rebooted. I have done some testing
    with Node Manager but, as I understood, Node Manager only restarts a server if
    it was started using Node Manager and the server crashes or fails. On the other
    hand, if the server is installed as a Windows service, it will be started at reboot
    time, but not when the server (not the machine) crashes or fails. So, both solutions
    seems to be uncompatible. Is it right?? Is it possible to have both benefits,
    that is, to get the managed servers started at boot time (as done by Windows services)
    and restarted each time they fail (as done by Node Manager)?
    Thanks,
    Gerardo

  • Starting managed servers after rebooting

    Hi:
    I have been trying to configure my WebLogic environment to start the managed servers
    in a domain automatically when the machine is rebooted. I have done some testing
    with Node Manager but, as I understood, Node Manager only restarts a server if
    it was started using Node Manager and the server crashes or fails. On the other
    hand, if the server is installed as a Windows service, it will be started at reboot
    time, but not when the server (not the machine) crashes or fails. So, both solutions
    seems to be uncompatible. Is it right?? Is it possible to have both benefits,
    that is, to get the managed servers started at boot time (as done by Windows services)
    and restarted each time they fail (as done by Node Manager)?
    Thanks,
    Gerardo

    I think you can configure the NodeMgr to start ManagedServers instead of having the
    Windows Service start the servers. Basically you configure NodeMgr as a Windows Service
    and then let NM take care of starting other servers. I believe you have to set
    ManagedServer's HostsMigratableServices attribute to false to enable NM start the server.
    By default it is true.
    prasen
    Gerardo Rojas wrote:
    Hi:
    I have been trying to configure my WebLogic environment to start the managed servers
    in a domain automatically when the machine is rebooted. I have done some testing
    with Node Manager but, as I understood, Node Manager only restarts a server if
    it was started using Node Manager and the server crashes or fails. On the other
    hand, if the server is installed as a Windows service, it will be started at reboot
    time, but not when the server (not the machine) crashes or fails. So, both solutions
    seems to be uncompatible. Is it right?? Is it possible to have both benefits,
    that is, to get the managed servers started at boot time (as done by Windows services)
    and restarted each time they fail (as done by Node Manager)?
    Thanks,
    Gerardo

  • 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()

  • How to start managed servers simultaneously using WLST?

    Hi folks,
    I am trying to write a simple script to provide a simple way to bounce my env, I am pretty much done. However, my script now starts (and stops) the managed servers sequentially which is not what I wanted.
    I am wondering if there is a way to start (and stop) the managed servers within a domain in parallel as I can definitely do that using Admin Console.
    I do have an idea in mind:
    Write a simple python script to start/stop a single managed server, then use another shell script to trigger the python script in background mode.
    But I think this approach is really ugly, and am wondering if there is a native way to do that in WLST.
    Thanks for your repose in advance.

    This does not solve my problem, what I am trying to do is to being a an indefinite about of managed servers at the same time, not all the managed servers.
    For example, suppose I have 5 clusters in a domain, and there are 3 servers in each cluster. I might want to bring up all the major servers first at the same time,
    which mean to bring up one server in each cluster at the same time.
    Please help.

  • Admin server not sending bootstrap servlet configuration to managed servers

    I am having a bit of strange issue.
    I have weblogic 8.1 SP5 domain in PROD.
    14 managed servers in the domain
    When i start the managed serverA, sometimes it starts, sometimes it doesnt.
    By looking at admin server logs, i found the following.
    When the managed ServerA doesnt start, the admin server has the following log snippet
    <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action isrunning from managed server ServerA.>
    ####<Apr 14, 2009 2:37:01 AM EDT> <Info> <Configuration Management> <MachineA> <adminServer> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150030> <The bootstrap servlet has acknowledged that the admin server is running to the booting managed server serverA>
    ####<Apr 14, 2009 2:37:01 AM EDT> <Info> <Configuration Management> <MachineA> <adminServer> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action bootstrap from managed server serverA.>
    When the managed ServerA starts, the admin server has the following log snippet
    Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action isrunning from managed server serverA.>
    ####<Apr 14, 2009 2:38:15 AM EDT> <Info> <Configuration Management> <MachineA> <adminServer> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150030> <The bootstrap servlet has acknowledged that the admin server is running to the booting managed server serverA.>
    ####<Apr 14, 2009 2:38:15 AM EDT> <Info> <Configuration Management> <MachineA> <adminServer> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action bootstrap from managed server serverA.>
    ####<Apr 14, 2009 2:38:21 AM EDT> <Info> <Configuration Management> <catlmsxp166.corp.cox.com> <adminServer> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150031> *<The bootstrap servlet has finished sending the configuration to serverA.>*
    The difference is that admin server unable to send the bootstrap servlet configuration to managed servers, as highlighted above
    Has anyone encountered this issue?
    If so, is there is solution to this?
    Right now i am doing the work around (Which is restart admin server and then start managed server, for every managed server that does not start)
    But i cant do this all the time.
    MY domain has 14 managed servers. All of them exhibit similar behaviour.
    Some times they start, some times they dont.
    Edited by: gvamsius on Apr 14, 2009 1:22 PM
    Edited by: gvamsius on Apr 14, 2009 1:23 PM

    Honestly I've never seen a similar problem.
    Could you show us the "standard out" when you start the servers?
    Could you to show us the standard out when you start the servers?

  • Node Manager starting managed servers under different users

    Hi all,
    I have multiple domains running on the same server.
    Is it possible to get node manager to start managed servers from different domains under different users?
    Default is the user under which node manager was started originally.
    Thanks
    Arnaud

    Oracle documentation is still in confussion state for Unix platform nodemanager.
    NodeManager Admin Guide had chapter 3 for General configuration of nodemanger. Chapter 5 is for script based nodemanager.
    In chapter 5 there is clear way defined for " Starting a node manger for Unix machine".
    chapter 3 is mess there is clear-cut direction to reach the remote startup of servers.
    Why we have so many types of nodemanager for connect. howbout start them?
    Can someone expert in Oracle WebLogic please respond to this.
    *Nodemanagers are NOT meant for multiuser development env.
    They are defined for production env and for HA, FailOver.*
    Edited by: PavanBhavanishekhar on Jan 6, 2010 9:10 PM

  • 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

  • Running managed servers from different WL versions under a domain

    Hi,
    Would it be possible to run managed servers (in non clustered way) from different versions of WebLogic under a single domain, with admin server of higher WebLogic version controlling the domain and the managed servers?
    Regards,
    Gobi

    Hi Gobi,
    we can make it run such a way but it may lead to many complication with patch sets.
    Few thing work in one environment and other will not so it is not at all recommended way to set such configuration.
    Regards,
    Kal

  • Can on one domain coexist managed servers for ADF11g and Forms&Reports 11g

    Is it possible on one Weblogic Domain to exist both Managed server for ADF 11g and Managed servers for Forms 11g and Reports 11g?
    How to install on one Weblogic server these two things? Is it possible and what is recommended in this case?
    Thnx in advance!

    Hi Rade,
    Yes, i think it is possible. In my case I have one Weblogic Server Domain with 3 Managed Server,one for deploy application and the others are the Forms & Reports 11g.
    For that you have to install Fusion Middlware 11g.
    For ADF 11g i think you have to install Oracle Fusion Application.
    Edit:
    Please read the note: Installing ADF 11.1.1.3 Runtime into WebLogic 11gR1 Patchset 2 (10.3.3) [ID 1094153.1]
    Hope this help
    Regards
    Edited by: scapy on 6/Out/2011 3:14

  • Creating Weblogic domain with Admin Server and managed servers on different

    I am trying to create Weblogic domain where Admin Server and managed servers on different machines. However I am unable to find any steps which would allow me to do so. The config.sh script always creates an Admin Server. Please help.

    Whilst the method that Lawrence gives can result in a domain that is perfectly functional, it is a method that can result in errors as you are having to enter the same information twice. Also you will create two admin servers, as the second domain creation will have the console added to it on the renamed admin server and this will give issues.
    The best method to create a domain spamming multiple physical machines, is to create the domain with all the components on the first machine. This means planning the domain and making sure all components are added once; so having the information about the domain written out is wise. Ensure that the WLS software is installed in the same path on each machine before starting.
    Then copy the domain that you have created from one machine to the other, keeping the same paths. You can simply copy (I've used this method multiple times without issue) but the supported way would be to use the WLST PACK and UNPACK methods. These create and extract domains from templates. Some more information on these is given here -> http://docs.oracle.com/cd/E13179_01/common/docs100/pack/intro.html#wp1069056

  • Domain log of managed servers

    Hi,
    Having gone over the documetation for WL7 logging, I understood that in a
    managed environment besides having a local log, the managed servers also
    send the messages to the administration server via JMX to a single domain
    log.
    My question is, what happens if the admin server goes down? will those log
    messages be missed, or are they stored somewhere and when the server is up
    again they are logged? can someone please shed some light on the workings
    of this mechanism.
    Thanks
    Trevor

    Hello,
    I guess this thread detail can help you:
    http://social.technet.microsoft.com/Forums/sharepoint/en-US/e547a497-7e17-4632-a636-85f0055effdf/advice-on-domain-change-scenario-for-sharepoint-2007-server?forum=sharepointadminlegacy
    http://blogs.technet.com/b/sushrao/archive/2011/12/02/sharepoint-migrating-sharepoint-server-from-one-domain-to-another.aspx
    Hemendra:Yesterday is just a memory,Tomorrow we may never see
    Please remember to mark the replies as answers if they help and unmark them if they provide no help

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

Maybe you are looking for