Number managed servers per physical machine

Hi
I seem to remember reading somewhere that oracle recommend that you have 2 managed servers per physical machine. The reason I think was something to do with heap size or garbage collection.
Does anyone know for sure if oracle/bea did recommend 2 managed servers? And if so what is the reason for this.
many thanks in advance.

There is no such restriction. The recommendation of the number of managed servers per machine would depend on each machines available resources.

Similar Messages

  • Maximum number of domains per physical server

    I am curious as to whether or not there is a maximum number of domains per physical server. Is it just based on resources, i.e. memory, hdd space, etc. or does Oracle have it's own specific recommendations? I realize, as implied, that one could put a number of vm's on a server that would utilize the server ram up to an amount reserved for the OS.
    Just wondering if there is a recommendation.
    By the way, we are running WLS (10.0MP1) and OSB (3.0) on top of Win2K3.
    Thanks for nay info,
    Todd

    Typically it depends on the resources.
    If the WLS instances are heavily utilized, at some point having more JVM's than the number of cores impacts performance if the apps are CPU bound. Similar applies for apps that use a lot of memory or sessions. There is no blanket answer and there is no hard and fast limit.

  • WLS61-WinNT:  Admin/Managed servers on same machine with NodeManager?

    Hi,
    I'm trying to set up a development environment with a Admin server
    that controls at least one Managed server. I can start the Admin
    server (7001) successfully, and "startNodeManager" seems to work fine
    on the default port 5555. No clustering is being done. Only
    DefaultWebApp is available.
    I'm starting "setEnv" and "startWebLogic" from
    C:\dev\bea\wlserver6.1\config\devdomain
    and "startNodeManager" from
    C:\dev\bea\wlserver6.1\config
    I have a Machine, "devmachine", assigned to port 5555 (thus attaching
    it to the NodeManager) using the default config files.
    I have 2 Servers created:
    "adminserver", which listens on port 7001 (no great surprise), and
    "devserver", which listens on port 7011. I have also tried
    "devserver" on port 5555.
    DefaultWebApp has chosen both Servers.
    When I go to the Console, right-click on "devserver", and select
    "Start this server...", I get the "Are you sure?" page.
    Clicking "Yes", I get messages on the "startNodeManager" console:
    <Date><Info><Nodemanager@localhost:5555><WindowsProcessControl: online
    successfully invoked on server 'devserver', pid: 488>
    This sounds good, but the console browser returns:
    java.lang.NoClassDefFoundError: weblogic/Server
    Exception in thread "main"
    <Date><Info><Nodemanager@localhost:5555><WindowsProcessControl: online
    successfully invoked on server 'devserver', pid: 488>
    StartNodeManager's output confirms that "weblogic.jar" is in the
    classpath.
    It's location is: .\lib\weblogic.jar
    Clicking on the Servers branch confirms that 'devserver:7011' is not
    running, and that 'adminserver:7001' is running.
    I believe that I'm making some sort of simple configuration error, but
    I have been unable to find any documentation that clarifies this
    problem.
    Has anyone gotten this Admin/Managed combination to work on 1 physical
    machine? If so, am I simply not matching ports in the config.xml file
    correctly? Am I missing something obvious?
    Many Thanks!
    Jeff

    Hi,
    It may not be obvious, but a clean install seemed to solve it. A
    wacky config issue? The world may never know...or care. :>
    Jeff
    [email protected] (Jeff Murdoch) wrote in message news:<[email protected]>...
    Hi,
    I'm trying to set up a development environment with a Admin server
    that controls at least one Managed server. I can start the Admin
    server (7001) successfully, and "startNodeManager" seems to work fine
    on the default port 5555. No clustering is being done. Only
    DefaultWebApp is available.
    I'm starting "setEnv" and "startWebLogic" from
    C:\dev\bea\wlserver6.1\config\devdomain
    and "startNodeManager" from
    C:\dev\bea\wlserver6.1\config
    I have a Machine, "devmachine", assigned to port 5555 (thus attaching
    it to the NodeManager) using the default config files.
    I have 2 Servers created:
    "adminserver", which listens on port 7001 (no great surprise), and
    "devserver", which listens on port 7011. I have also tried
    "devserver" on port 5555.
    DefaultWebApp has chosen both Servers.
    When I go to the Console, right-click on "devserver", and select
    "Start this server...", I get the "Are you sure?" page.
    Clicking "Yes", I get messages on the "startNodeManager" console:
    <Date><Info><Nodemanager@localhost:5555><WindowsProcessControl: online
    successfully invoked on server 'devserver', pid: 488>
    This sounds good, but the console browser returns:
    java.lang.NoClassDefFoundError: weblogic/Server
    Exception in thread "main"
    <Date><Info><Nodemanager@localhost:5555><WindowsProcessControl: online
    successfully invoked on server 'devserver', pid: 488>
    StartNodeManager's output confirms that "weblogic.jar" is in the
    classpath.
    It's location is: .\lib\weblogic.jar
    Clicking on the Servers branch confirms that 'devserver:7011' is not
    running, and that 'adminserver:7001' is running.
    I believe that I'm making some sort of simple configuration error, but
    I have been unable to find any documentation that clarifies this
    problem.
    Has anyone gotten this Admin/Managed combination to work on 1 physical
    machine? If so, am I simply not matching ports in the config.xml file
    correctly? Am I missing something obvious?
    Many Thanks!
    Jeff

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

  • Managed Servers on another machine

              I'm having problems getting a managed server running on
              another machine with NT. For simplicity, I'm using the
              'mydomain' that comes in the install. From the
              'mydomain' directory, I just:
              startWebLogic.cmd
              which starts up the weblogic server after adding my
              system password. Then, from the console, I add a new
              machine and a server on this machine. Then from the
              other machine in the equivalent 'mydomain' directory, I
              run:
              startManagedWebLogic.cmd server-2 machine1:7001
              And, it gives me this error:
              D:\bea\wlserver6.0>"D:\bea\jdk130\bin\java" -hotspot
              -ms64m -mx64m -classpath .;
              .\lib\weblogic_sp.jar;.\lib\weblogic.jar
              -Dweblogic.Domain=mydomain -Dweblogic.N
              ame="server-2" "-Dbea.home=D:\bea"
              -Dweblogic.management.server="machine1:7001"
              "-Djava.security.policy==D:\bea\wlserver6.0/lib/weblogic.policy"
              -Dweblogic.mana
              gement.password= weblogic.Server
              Enter password to boot weblogic server:system123
              Starting WebLogic Server ....
              Connecting to http://machine1:7001...
              The WebLogic Server did not start up properly.
              Exception raised:
              weblogic.management.configuration.ConfigurationException:
              serv
              er-2 not found
              weblogic.management.configuration.ConfigurationException:
              server-2 not found
              at
              weblogic.management.Admin.getBootstrapLocalServer(Admin.java:831)
              at
              weblogic.management.Admin.initialize(Admin.java:274)
              at
              weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:317)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
              at weblogic.Server.main(Server.java:35)
              Reason: Fatal initialization exception
              D:\bea\wlserver6.0>goto finish
              D:\bea\wlserver6.0>cd config\mydomain
              D:\bea\wlserver6.0\config\mydomain>ENDLOCAL
              I had a similar error when starting a managed server on
              the same machine, but I got it to work by changing the
              admin URL from "http://machine1:7001/" to just
              "machine1:7001".
              Any ideas?
              --Kurt
              

              I finally got this going, so I want to share it with others getting started in
              managed servers/clusters.
              Apparently, "weblogic.admin.host" and "weblogic.management.server" are equivalent
              properties. After I got things working, it didn't seem to matter which one I
              used.
              Beware of adding a trailing slash on the end of the URL such as
              "http://localhost:7001". I've been trained that this is not a well formed URL,
              so I add it by habit; however, Weblogic will complain about not finding your
              server. Just giving the "localhost:7001" will work as well.
              Whenever changing machines, servers, etc with the console, it's best to reboot
              all the servers. I realize that it should be dynamic, but it doesn't seem to
              work out that way. I'm learning to edit the 'config.xml' which seems to be a
              safer bet at the moment.
              --Kurt
              Prasad Peddada wrote:
              > Kurt,
              > Your command line arguments are incorrect.
              >
              > its actually -Dweblogic.admin.host=machine1:7701
              >
              > Make sure you have server named server-2 in your config file and admin server
              > is not part of cluster.
              >
              > Cheers,
              >
              > -- Prasad
              >
              > Kurt Guenther wrote:
              >
              > > I'm having problems getting a managed server running on
              > > another machine with NT. For simplicity, I'm using the
              > > 'mydomain' that comes in the install. From the
              > > 'mydomain' directory, I just:
              > >
              > > startWebLogic.cmd
              > >
              > > which starts up the weblogic server after adding my
              > > system password. Then, from the console, I add a new
              > > machine and a server on this machine. Then from the
              > > other machine in the equivalent 'mydomain' directory, I
              > > run:
              > >
              > > startManagedWebLogic.cmd server-2 machine1:7001
              > >
              > > And, it gives me this error:
              > >
              > > D:\bea\wlserver6.0>"D:\bea\jdk130\bin\java" -hotspot
              > > -ms64m -mx64m -classpath .;
              > > .\lib\weblogic_sp.jar;.\lib\weblogic.jar
              > > -Dweblogic.Domain=mydomain -Dweblogic.N
              > > ame="server-2" "-Dbea.home=D:\bea"
              > > -Dweblogic.management.server="machine1:7001"
              > > "-Djava.security.policy==D:\bea\wlserver6.0/lib/weblogic.policy"
              > > -Dweblogic.mana
              > > gement.password= weblogic.Server
              > > Enter password to boot weblogic server:system123
              > > Starting WebLogic Server ....
              > > Connecting to http://machine1:7001...
              > > ***************************************************************************
              > >
              > > The WebLogic Server did not start up properly.
              > > Exception raised:
              > > weblogic.management.configuration.ConfigurationException:
              > > serv
              > > er-2 not found
              > > weblogic.management.configuration.ConfigurationException:
              > > server-2 not found
              > > at
              > > weblogic.management.Admin.getBootstrapLocalServer(Admin.java:831)
              > >
              > > at
              > > weblogic.management.Admin.initialize(Admin.java:274)
              > > at
              > > weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:317)
              > > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
              > >
              > > at weblogic.Server.main(Server.java:35)
              > > Reason: Fatal initialization exception
              > > ***************************************************************************
              > >
              > > D:\bea\wlserver6.0>goto finish
              > >
              > > D:\bea\wlserver6.0>cd config\mydomain
              > >
              > > D:\bea\wlserver6.0\config\mydomain>ENDLOCAL
              > >
              > > I had a similar error when starting a managed server on
              > > the same machine, but I got it to work by changing the
              > > admin URL from "http://machine1:7001/" to just
              > > "machine1:7001".
              > >
              > > Any ideas?
              > >
              > > --Kurt
              

  • 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

  • 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

  • How can I restrict the total no. of recs. per physical page

    Hi !
    I have created a report and I am saving that in a text file. The
    problem is that when I try to take the output on the printer
    then the total no of records overflows to the next pages and the
    next page heading comes much below to it's designated place.
    Max.no of records property in the repaeting frame is for the
    logical page.
    How can I restrict the max. number of records per physical page ?
    Any pointer will be welcome,
    Thanks in advance,
    Shobhit
    null

    Just for fun (and in case this wasn't done to death in the other thread), the rule posted here states:
    Most years have 365 days, but a leap year has 366 days. That adds up to 52 weeks (where each week is exactly 7 days) PLUS 1 or 2 additional days. The year 2012 has exactly 366 days.Now if the year starts on a Sunday in a non-leap year, you end up with 53 Sundays. Or if either of the first two days lands on a Sunday during a leap year, then you can also get 53 Sundays.>
    which allows a calculation like this:
    with test_data as
         ( select rownum + 1999 as test_year from dual
           connect by rownum <= 15 )
    select test_year
         , case
              when first_day = 'SUN'
              or ( first_day = 'SAT' and leap_year = 'Y' )
                 then 53
              else 52
           end as sundays
    from   ( select test_year
                  , to_char(to_date(d.test_year||'-01-01','YYYY-MM-DD'),'DY', 'NLS_DATE_LANGUAGE=ENGLISH') first_day
                  , case extract(day from last_day(to_date(d.test_year||'-02','YYYY-MM'))) when 29 then 'Y' else 'N' end as leap_year
             from   test_data d );
    TEST_YEAR    SUNDAYS
          2000         53
          2001         52
          2002         52
          2003         52
          2004         52
          2005         52
          2006         53
          2007         52
          2008         52
          2009         52
          2010         52
          2011         52
          2012         53
          2013         52
          2014         52
    15 rows selected.

  • What should be the client url for managed servers in a cluster

    Hi guys,
    I have created a cluster(cluster_1) having 4 managed servers. 2 managed servers on my machine(IP1) and 2 managed servers on other machine(IP2).
    I am able to deploy a xxx.war file on my admin server
    also
    I am able to deploy the same war file on my cluster
    When I try to hit the client url, it gives me back the correct data, but it creates the session on the admin server and not the cluster.
    If I remove the xxx.war file from the deployment(deployed on admin server) and redeploy the xxx,war file on the cluster, it gets deployed successfully , but the client url gives me a 404 error.
    What should I do, so that after hitting the client url, it creates the session on the managed servers in the cluster ?
    My admin server is not the part of this cluster.
    cluster ip:127.0.0.1
    ip1: 10.25.63.130
    ip2: 10.25.63.131
    please help
    Salil

    Hi Salil
    This is exactly what I mentioned in my earlier post. You CANNOT and should NOT expose the managed server url (host, port) to the end users. Because as you already figured out, you can specify only one. Or they cannot try one at a time like that.
    This is where, the Load Balancer will come into picture like Apache Web Server. After installing Apache web server, usually it runs at default port 80. So you just expose the apache host to outside world. Also most companies will have Firewalls and Apache is outside of Firewall and all weblogic servers are inside the Firewall. In apache, you configure the weblogic cluster details like the host names and ports of each managed server etc in httpd.conf file etc.
    Ex: For outside users, they may try like http://apachehost/myWeb/myHello.jsp -> apachehost is the host name where Apache web server is running at port 80. NOW Apache is smart enough to do Load Balancing and Failover. If 100 users access the site with 4 managed servers, ideally each managed server will get 25 requests (load balancing). Also if 2 servers are killed, automatically, request will NOT go to them, but to other 2 live servers etc etc. Apache takes care of this.
    Bottom line, please see my earlier post, and you need to have some sort of Web Server like Apache for your cluster setup.
    Thanks
    Ravi Jegga

  • SSL on managed servers

    i installed the weblogic 10.3.3 on a system and configured an admin server (7001 and ssl-7002) and one managed server (7003 and ssl-7004)on it.created a machine and added both the admin and managed server to this machine.i deployed my webapplication on managed server.i am using node manager to start the servers. i uncheck Listen Port Enabled on my managed server so that my webapllication should only work on https.my node manager is running.
    in admin console,
    1)i still can see the Listen port as 7003 for managed server on admin console--> Environment --> servers --> configuration tab.(i disabled Listen Port Enabled)
    2)i am able to access my web aplication running on managed server(through https) but the state of managed server is shown as UNKNOWN on admin console
    when i try to start the managed server from nodemanager using nmStart('managedServer1') i am getting the error managedServer1 already been started
    3)i am not able to monitor my managedserver from admin console its saying 'Server is not currently reachable. No additional health information available'.
    i am not able to shutdown the managed server from admin console or using nodemanager
    please help me in fixing this issues
    Another doubt is whether is it possible to deploy a http webapplication and an https webapplication to managed servers on same machine
    Thanks and Regards,

    You should be able to see the status of your node manager regardless of whether you have any managed server at all or any applications or whether you use SSL or not.
    So what do you see when you click Machines -> "your machine" -> Monitoring? Does it show "Reachable"? This confirms that your NM and Admin server are connected.

  • 1 NodeManager, 1 Admin Server and 2 Managed Servers

    Hi All, I'm new in Weblogic and this is my 1st time to post a question on this forum. Would like ask for help from you all above my setup, I'm not sure whether it will work or not. Please find out the scenario below:
    Setup:
    1 Machine (RedHat Enterprise Linux 5.5)
    1 NodeManager
    1 AdminServer (Name: APP)
    2 Managed Servers (Name: APPLIVE, APPUAT)
    Currently I would like to using one NodeManager to control both Managed Servers under 1 machine. When I configure my APP Admin Server and two Managed Servers, i would like to nmEnroll both Managed Servers under one NodeManager but it will overwrite my enroll entries if i enroll 2nd Managed Server.
    Is it possible to configure NodeManager to accept both Managed Servers entries? Thanks. :)
    Edited by: user13602952 on Jan 2, 2011 9:54 PM

    Hi Hong,
    Following are the few things which you help you understand about NodeManager and nmEnroll
    - First of all a Node Manager process is not associated with a specific WebLogic domain but with a machine
    - When you run a nmEnroll then you just give "domainDir" and "nmHome" which would then gets the file called "*nm_password.properties*" which contains the encrypted username and password that is used for server authentication and "*SerializedSystemIni.dat*" file.
    Example:
    nmEnroll([domainDir], [nmHome])
    - With above files it also updates the nodemanager.domains file with the domain information which was mentioned in the above command.
    Thus when you run the nmEnroll command it would get all the details which it needs to start any managed servers in the same Machine, hence you do not need to run the same commend for each managed servers in the same Machine.
    For more information have a look at the below links:
    Topic: Search for "nmEnroll"
    http://download.oracle.com/docs/cd/E13222_01/wls/docs92/config_scripting/reference.html
    Topic: Overview of Node Manager
    http://download.oracle.com/docs/cd/E13222_01/wls/docs90/server_start/nodemgr.html#1091317
    Regards,
    Ravish Mody
    http://middlewaremagic.com/weblogic/
    Come, Join Us and Experience The Magic…

  • Limit on number of Managed Servers in a cluster

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

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

  • Creation of Managed servers using WLST on two different machines

    Hello,
    I am looking for a use case, where i need to create two managed servers to running admin servers
    condition 1: Adminserver and managed_server1 will be in same machine.
    codition 2: managed_server2 will be in other machine.
    Example: AdminSever and managed_server1 will be in the 10.10.10.101 and Managed_server2 will be in 10.10.10.102
    I have a code which will create two managed servers in a same machine. How can i modify this code???
    import java.io.BufferedReader;
    import java.io.IOException;
    import java.io.InputStreamReader;
    import java.util.*;
    import weblogic.management.scripting.utils.WLSTInterpreter;
    import org.python.util.InteractiveInterpreter;
    public class EmbeddedWLST
    static InteractiveInterpreter interpreter = null;
    EmbeddedWLST()
    System.out.println(“Inside the constructor()”);
    interpreter = new WLSTInterpreter();
    private static void connect()
    System.out.println(“Inside the Connect method()”);
    StringBuffer buffer = new StringBuffer();
    buffer.append(“connect(‘weblogic’,’1qaz2wsx’,'t3://localhost:7001′)”);
    System.out.println(“After Connect method()”);
    interpreter.exec(buffer.toString());
    System.out.println(“at the end of conenct method”);
    private static void createServers()
    System.out.println(“Inside the CreateServer method()”);
    StringBuffer buf = new StringBuffer();
    buf.append(startTransaction());
    buf.append(“man1=create(‘msEmbedded1′,’Server’)\n”);
    buf.append(“man2=create(‘msEmbedded2′,’Server’)\n”);
    buf.append(“mach=create(‘machineEmbedded’,'Machine’)\n”);
    buf.append(“clus=create(‘clusterEmbedded’,'Cluster’)\n”);
    buf.append(“man1.setListenPort(8001)\n”);
    buf.append(“man2.setListenPort(9001)\n”);
    buf.append(“man1.setCluster(clus)\n”);
    buf.append(“man2.setCluster(clus)\n”);
    buf.append(“man1.setMachine(mach)\n”);
    buf.append(“man2.setMachine(mach)\n”);
    buf.append(endTransaction());
    //buf.append(“print Script ran successfully … \n”);
    interpreter.exec(buf.toString());
    private static String startTransaction() {
    StringBuffer buf = new StringBuffer();
    buf.append(“edit()\n”);
    buf.append(“startEdit()\n”);
    return buf.toString();
    private static String endTransaction() {
    StringBuffer buf = new StringBuffer();
    buf.append(“save()\n”);
    buf.append(“activate(block=’true’)\n”);
    return buf.toString();
    public static void main(String[] args) throws IOException
    System.out.println(“inside the main “);
    Runtime rt2 = Runtime.getRuntime();
    Process pr2 = rt2.exec(“cmd /c C:\\Oracle\\Middleware\\wlserver_10.3\\server\\bin\\setWLSEnv.cmd “);
    BufferedReader br = new BufferedReader(new InputStreamReader(pr2.getInputStream()));
    String line = “”;
    while ((line = br.readLine()) != null)
    System.out.println(line);
    new EmbeddedWLST();
    connect();
    createServers();
    Help me out please.
    Thanks,
    Alok

    Hi Shane --
    Yes, they were installed from the same disk (I'm pretty sure I did a software update on both but will double-check tonight).
    When I try to Import the project, it is grayed out in the 'Choose a File' window. If I double-click the project from the Finder, I get "General Error (41)" -- which is a different one than when I tried it yesterday (when I had no other sequences active).
    Also something weird today -- although the edited footage is all linked fine & plays properly, in the timeline most of the footage shows the red "Media Offline" frame for its thumbnail.
    Any ideas?
    Many thanks!!
    -- Sean

  • What is the recommended number of clients per Mac server? Also what are some recommended specs when purchasing an Apple machine that will have Mac OS X server installed?

    What is the recommended number of clients per Mac server? Also what are some recommended specs when purchasing an Apple machine that will have Mac OS X server installed? We have around 300 clients that need to be enroled on the Mac server. I want to know what is the recommended amount of clients a Mac server should contain. Also what are some recommended specs to make sure the server will flawlessly?

    Hello cpreasbeck,
    Thank you for contacting Apple Support Communities.
    I was able to find the following transition guide for Xserve that provides some workload guidance to determine performance when planning a server deployment.
    Transition Guide Xserve
    http://images.apple.com/xserve/pdf/L422277A_Xserve_Guide.pdf
    On page 9, Performance there is a chart that provides maximum numbers of connected users for various activities such as file sharing, mail, web, calendar, directory services and Time Machine and the CPU used as a server (Xserve, Mac Pro, Mac Mini). This information is a bit dated as the referenced software is Snow Leopard Server (OS X 10.6), and the hardware is older also, but it should give you a general idea of what you might need to look for.
    Regards,
    Jeff D.

  • WLI 8.1SP2 Cluster over 2 Physical Machines Errs on Managed Svrs on 2nd mac

    I set up WLI Clustering 8.1sp2 with 4 total managed servers, 2 colocated with the admin server, and 2 on a vanilla installation of WLP 8.1sp2.
    While the colocated servers boot up correctly (and are able to be recovered by the node manager), I cannot seem to get the remote managed servers to come up properly. The node manager on the remote machine reports the following error:
    ####<Sep 23, 2004 5:49:50 PM EDT> <Notice> <Log Management> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-170019> <The server log file C:\bea\user_projects\domains\myClusterTest08\new_managedServer_3\new_managedServer_3.log is opened. All server side log events will be written to this file.>
    ####<Sep 23, 2004 5:49:51 PM EDT> <Info> <Socket> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000406> <NTSocketMuxer was built on Jun 19 2003 15:39:24
    >
    ####<Sep 23, 2004 5:49:51 PM EDT> <Info> <Socket> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000436> <Allocating 2 reader threads.>
    ####<Sep 23, 2004 5:50:05 PM EDT> <Info> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server new_managedServer_3 for security realm myrealm.>
    ####<Sep 23, 2004 5:50:05 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090082> <Security initializing using security realm myrealm.>
    ####<Sep 23, 2004 5:50:06 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090170> <Loading the private key stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
    ####<Sep 23, 2004 5:50:07 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090171> <Loading the identity certificate stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
    ####<Sep 23, 2004 5:50:07 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\weblogic81\server\lib\DemoTrust.jks.>
    ####<Sep 23, 2004 5:50:07 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\jrockit81sp2_141_05\jre\lib\security\cacerts.>
    ####<Sep 23, 2004 5:50:08 PM EDT> <Notice> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000328> <Starting WebLogic Managed Server "new_managedServer_3" for domain "myClusterTest08">
    ####<Sep 23, 2004 5:50:08 PM EDT> <Info> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000214> <WebLogic Server "new_managedServer_3" version:
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic Integration 8.1 SP2 Thu Dec 11 22:07:14 PST 2003 148883 (c) 1995, 1996, 1997, 1998 WebLogic, Inc.
    (c) 1999, 2000, 2001 BEA Systems, Inc.>
    ####<Sep 23, 2004 5:50:08 PM EDT> <Info> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000215> <Loaded License : C:\bea\license.bea>
    ####<Sep 23, 2004 5:50:08 PM EDT> <Info> <RJVM> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000570> <Network Configuration for Channel "new_managedServer_3"
    Listen Address informatica-svr:7001
    Public Address N/A
    Http Enabled true
    Tunneling Enabled false
    Outbound Enabled false
    Admin Traffic Enabled true>
    ####<Sep 23, 2004 5:50:08 PM EDT> <Debug> <RJVM> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000571> <Network Configuration Detail for Channel "new_managedServer_3"
    Channel Weight 50
    Accept Backlog 50
    Login Timeout 5000ms
    Max Message Size 10000000
    Message Timeout 60s
    Idle Timeout 65s
    Tunneling Timeout 40s
    Tunneling Ping 45s>
    ####<Sep 23, 2004 5:50:08 PM EDT> <Info> <XML> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-130036> <Initializing XMLRegistry.>
    ####<Sep 23, 2004 5:50:08 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001135> <Initializing the JDBC service.>
    ####<Sep 23, 2004 5:50:09 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001137> <Initialization complete.>
    ####<Sep 23, 2004 5:50:09 PM EDT> <Info> <Connector> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-190000> <Initializing J2EE Connector Service>
    ####<Sep 23, 2004 5:50:09 PM EDT> <Info> <Connector> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-190001> <J2EE Connector Service initialized successfully>
    ####<Sep 23, 2004 5:50:09 PM EDT> <Info> <IIOP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-002014> <IIOP subsystem enabled.>
    ####<Sep 23, 2004 5:50:10 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040090> <Deployed 5 default connection factories.>
    ####<Sep 23, 2004 5:50:10 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040305> <JMS service is initialized and in standby mode.>
    ####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101128> <Initializing HTTP services.>
    ####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101133> <Initializing Web server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101052> <[HTTP new_managedServer_3] Initialized>
    ####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101135> <new_managedServer_3 is the default Web server.>
    ####<Sep 23, 2004 5:50:11 PM EDT> <Info> <J2EE> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-160037> <J2EE service initializing.>
    ####<Sep 23, 2004 5:50:11 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149207> <Initializing.>
    ####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from unprepared to prepared on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from unprepared to prepared on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from unprepared to prepared on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from unprepared to prepared on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from unprepared to prepared on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from unprepared to prepared on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from prepared to active on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from prepared to active on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from prepared to active on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from prepared to active on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from prepared to active on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from prepared to active on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149208> <Initialization Complete.>
    ####<Sep 23, 2004 5:50:17 PM EDT> <Notice> <Cluster> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000138> <Listening for announcements from cluster new_cluster_1 on 237.0.0.1:7001.>
    ####<Sep 23, 2004 5:50:17 PM EDT> <Notice> <Cluster> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000133> <Waiting to synchronize with other running members of new_cluster_1.>
    ####<Sep 23, 2004 5:50:48 PM EDT> <Info> <JTA> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-110441> <Opening transaction log with driver version "j1.0" and synchronous write policy "Cache-Flush". For information on synchronous write policies, refer to the weblogic.management.configuration.ServerMBean javadoc or console online help.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001138> <Resuming the JDBC service.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001140> <Resume complete.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultXAConnectionFactory" is started.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "QueueConnectionFactory" is started.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "MessageDrivenBeanConnectionFactory" is started.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultConnectionFactory" is started.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "TopicConnectionFactory" is started.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040306> <JMS service is active now.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101129> <Initializing the Web application container.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101238> <HTTP log rotation is size based for the Web server: new_managedServer_3.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101051> <[HTTP new_managedServer_3] started>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <WebService> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-220031> <The server does not support reliable SOAP messaging.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <WebService> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-220027> <Web Service reliable agents are started on the server.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149209> <Resuming.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000625> <The application has disabled periodic testing of free resources in pool "cgPool".>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000628> <Created "5" resources for pool "cgPool", out of which "5" are available and "0" are unavailable.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001124> <Created Connection Pool named cgPool.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000625> <The application has disabled periodic testing of free resources in pool "bpmArchPool".>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000628> <Created "5" resources for pool "bpmArchPool", out of which "5" are available and "0" are unavailable.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001124> <Created Connection Pool named bpmArchPool.>
    ####<Sep 23, 2004 5:50:51 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001121> <Created TX Data Source named cgDataSource for Pool cgPool.>
    ####<Sep 23, 2004 5:50:51 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001121> <Created TX Data Source named bpmArchDataSource for Pool bpmArchPool.>
    ####<Sep 23, 2004 5:50:51 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "WLI-B2B System Topic Factory" is started.>
    ####<Sep 23, 2004 5:50:56 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040322> <JMSServer "cgJMSServer_auto_3" is activating for migration.>
    ####<Sep 23, 2004 5:50:56 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040321> <JMSServer "cgJMSServer_auto_3" is resuming.>
    ####<Sep 23, 2004 5:50:58 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040117> <JMSServer "cgJMSServer_auto_3". Opening JDBC store tables "myC_3JMSStore" and "myC_3JMSState" using connection pool "cgPool".>
    ####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040118> <JMSServer "cgJMSServer_auto_3". Finished scan of JDBC store. Found 3 records.>
    ####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040010> <JMSServer "cgJMSServer_auto_3" configured no session pools.>
    ####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040109> <JMSServer "cgJMSServer_auto_3" is started.>
    ####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040309> <JMS server "cgJMSServer_auto_3" is activated.>
    ####<Sep 23, 2004 5:51:00 PM EDT> <Info> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000256> <Invoking com.bea.wli.init.BPMStartup.main(null)>
    ####<Sep 23, 2004 5:51:00 PM EDT> <Debug> <Management> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-141132> <Dynamic invocation while executing action updateDeployments on myClusterTest08:Location=new_managedServer_3,Name=new_managedServer_3,Type=ServerConfig MBean instance failed. The method updateDeployments with signature [] was invoked with parameters as [].
    weblogic.management.AbortDeploymentException: weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
    [java.lang.NullPointerException]
    at weblogic.t3.srvr.StartupClassService.addDeployment(Lweblogic.management.configuration.DeploymentMBean;)V(StartupClassService.java:92)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Lweblogic.management.configuration.DeploymentMBean;)Z(DeploymentTarget.java:330)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Ljava.util.List;)V(DeploymentTarget.java:590)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments()V(DeploymentTarget.java:568)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments()V(DeploymentTarget.java:240)
    at COM.jrockit.reflect.NativeMethodInvoker.invoke0(ILjava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Native Method)
    at COM.jrockit.reflect.NativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
    at COM.jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
    at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(DynamicMBeanImpl.java:711)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(DynamicMBeanImpl.java:690)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(ConfigurationMBeanImpl.java:476)
    at com.sun.management.jmx.MBeanServerImpl.invoke(Ljava.lang.Object;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(MBeanServerImpl.java:1557)
    at com.sun.management.jmx.MBeanServerImpl.invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(MBeanServerImpl.java:1525)
    at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(RemoteMBeanServerImpl.java:947)
    at weblogic.management.internal.RemoteMBeanServerImpl.invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(RemoteMBeanServerImpl.java:908)
    at weblogic.management.internal.MBeanProxy.invoke(Ljava.lang.String;[Ljava.lang.Object;)Ljava.lang.Object;(MBeanProxy.java:946)
    at weblogic.management.internal.MBeanProxy.invokeForCachingStub(Ljava.lang.String;[Ljava.lang.Object;)Ljava.lang.Object;(MBeanProxy.java:481)
    at weblogic.management.configuration.ServerMBean_Stub.updateDeployments()V(ServerMBean_Stub.java:7271)
    at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments()V(SlaveDeployer.java:1210)
    at weblogic.management.deploy.slave.SlaveDeployer.resume()V(SlaveDeployer.java:362)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume()V(DeploymentManagerServerLifeCycleImpl.java:229)
    at weblogic.t3.srvr.SubsystemManager.resume()V(SubsystemManager.java:131)
    at weblogic.t3.srvr.T3Srvr.resume()V(T3Srvr.java:964)
    at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:359)
    at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)
    >
    ####<Sep 23, 2004 5:51:00 PM EDT> <Error> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149601> <The deployment framework was unable to resume accepting requests.>
    ####<Sep 23, 2004 5:51:00 PM EDT> <Emergency> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000342> <Unable to initialize the server: [Deployer:149601]The 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.NullPointerException]>

    I set up WLI Clustering 8.1sp2 with 4 total managed servers, 2 colocated with the admin server, and 2 on a vanilla installation of WLP 8.1sp2.
    While the colocated servers boot up correctly (and are able to be recovered by the node manager), I cannot seem to get the remote managed servers to come up properly. The node manager on the remote machine reports the following error:
    ####<Sep 23, 2004 5:49:50 PM EDT> <Notice> <Log Management> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-170019> <The server log file C:\bea\user_projects\domains\myClusterTest08\new_managedServer_3\new_managedServer_3.log is opened. All server side log events will be written to this file.>
    ####<Sep 23, 2004 5:49:51 PM EDT> <Info> <Socket> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000406> <NTSocketMuxer was built on Jun 19 2003 15:39:24
    >
    ####<Sep 23, 2004 5:49:51 PM EDT> <Info> <Socket> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000436> <Allocating 2 reader threads.>
    ####<Sep 23, 2004 5:50:05 PM EDT> <Info> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server new_managedServer_3 for security realm myrealm.>
    ####<Sep 23, 2004 5:50:05 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090082> <Security initializing using security realm myrealm.>
    ####<Sep 23, 2004 5:50:06 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090170> <Loading the private key stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
    ####<Sep 23, 2004 5:50:07 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090171> <Loading the identity certificate stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
    ####<Sep 23, 2004 5:50:07 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\weblogic81\server\lib\DemoTrust.jks.>
    ####<Sep 23, 2004 5:50:07 PM EDT> <Notice> <Security> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\jrockit81sp2_141_05\jre\lib\security\cacerts.>
    ####<Sep 23, 2004 5:50:08 PM EDT> <Notice> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000328> <Starting WebLogic Managed Server "new_managedServer_3" for domain "myClusterTest08">
    ####<Sep 23, 2004 5:50:08 PM EDT> <Info> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000214> <WebLogic Server "new_managedServer_3" version:
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic Integration 8.1 SP2 Thu Dec 11 22:07:14 PST 2003 148883 (c) 1995, 1996, 1997, 1998 WebLogic, Inc.
    (c) 1999, 2000, 2001 BEA Systems, Inc.>
    ####<Sep 23, 2004 5:50:08 PM EDT> <Info> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000215> <Loaded License : C:\bea\license.bea>
    ####<Sep 23, 2004 5:50:08 PM EDT> <Info> <RJVM> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000570> <Network Configuration for Channel "new_managedServer_3"
    Listen Address informatica-svr:7001
    Public Address N/A
    Http Enabled true
    Tunneling Enabled false
    Outbound Enabled false
    Admin Traffic Enabled true>
    ####<Sep 23, 2004 5:50:08 PM EDT> <Debug> <RJVM> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000571> <Network Configuration Detail for Channel "new_managedServer_3"
    Channel Weight 50
    Accept Backlog 50
    Login Timeout 5000ms
    Max Message Size 10000000
    Message Timeout 60s
    Idle Timeout 65s
    Tunneling Timeout 40s
    Tunneling Ping 45s>
    ####<Sep 23, 2004 5:50:08 PM EDT> <Info> <XML> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-130036> <Initializing XMLRegistry.>
    ####<Sep 23, 2004 5:50:08 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001135> <Initializing the JDBC service.>
    ####<Sep 23, 2004 5:50:09 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001137> <Initialization complete.>
    ####<Sep 23, 2004 5:50:09 PM EDT> <Info> <Connector> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-190000> <Initializing J2EE Connector Service>
    ####<Sep 23, 2004 5:50:09 PM EDT> <Info> <Connector> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-190001> <J2EE Connector Service initialized successfully>
    ####<Sep 23, 2004 5:50:09 PM EDT> <Info> <IIOP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-002014> <IIOP subsystem enabled.>
    ####<Sep 23, 2004 5:50:10 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040090> <Deployed 5 default connection factories.>
    ####<Sep 23, 2004 5:50:10 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040305> <JMS service is initialized and in standby mode.>
    ####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101128> <Initializing HTTP services.>
    ####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101133> <Initializing Web server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101052> <[HTTP new_managedServer_3] Initialized>
    ####<Sep 23, 2004 5:50:10 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101135> <new_managedServer_3 is the default Web server.>
    ####<Sep 23, 2004 5:50:11 PM EDT> <Info> <J2EE> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-160037> <J2EE service initializing.>
    ####<Sep 23, 2004 5:50:11 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149207> <Initializing.>
    ####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from unprepared to prepared on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from unprepared to prepared on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from unprepared to prepared on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:13 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from unprepared to prepared on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from unprepared to prepared on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from unprepared to prepared on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from prepared to active on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from prepared to active on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from prepared to active on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from prepared to active on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from prepared to active on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from prepared to active on server new_managedServer_3.>
    ####<Sep 23, 2004 5:50:14 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149208> <Initialization Complete.>
    ####<Sep 23, 2004 5:50:17 PM EDT> <Notice> <Cluster> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000138> <Listening for announcements from cluster new_cluster_1 on 237.0.0.1:7001.>
    ####<Sep 23, 2004 5:50:17 PM EDT> <Notice> <Cluster> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000133> <Waiting to synchronize with other running members of new_cluster_1.>
    ####<Sep 23, 2004 5:50:48 PM EDT> <Info> <JTA> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-110441> <Opening transaction log with driver version "j1.0" and synchronous write policy "Cache-Flush". For information on synchronous write policies, refer to the weblogic.management.configuration.ServerMBean javadoc or console online help.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001138> <Resuming the JDBC service.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001140> <Resume complete.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultXAConnectionFactory" is started.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "QueueConnectionFactory" is started.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "MessageDrivenBeanConnectionFactory" is started.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultConnectionFactory" is started.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "TopicConnectionFactory" is started.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040306> <JMS service is active now.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101129> <Initializing the Web application container.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101238> <HTTP log rotation is size based for the Web server: new_managedServer_3.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <HTTP> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-101051> <[HTTP new_managedServer_3] started>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <WebService> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-220031> <The server does not support reliable SOAP messaging.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <WebService> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-220027> <Web Service reliable agents are started on the server.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149209> <Resuming.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000625> <The application has disabled periodic testing of free resources in pool "cgPool".>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "cgPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "cgPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000628> <Created "5" resources for pool "cgPool", out of which "5" are available and "0" are unavailable.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001124> <Created Connection Pool named cgPool.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000625> <The application has disabled periodic testing of free resources in pool "bpmArchPool".>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001068> <Connection for pool "bpmArchPool" created.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001154> <Disabling statement caching for connection in pool "bpmArchPool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <Common> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000628> <Created "5" resources for pool "bpmArchPool", out of which "5" are available and "0" are unavailable.>
    ####<Sep 23, 2004 5:50:50 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001124> <Created Connection Pool named bpmArchPool.>
    ####<Sep 23, 2004 5:50:51 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001121> <Created TX Data Source named cgDataSource for Pool cgPool.>
    ####<Sep 23, 2004 5:50:51 PM EDT> <Info> <JDBC> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-001121> <Created TX Data Source named bpmArchDataSource for Pool bpmArchPool.>
    ####<Sep 23, 2004 5:50:51 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040108> <User connection factory "WLI-B2B System Topic Factory" is started.>
    ####<Sep 23, 2004 5:50:56 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040322> <JMSServer "cgJMSServer_auto_3" is activating for migration.>
    ####<Sep 23, 2004 5:50:56 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040321> <JMSServer "cgJMSServer_auto_3" is resuming.>
    ####<Sep 23, 2004 5:50:58 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040117> <JMSServer "cgJMSServer_auto_3". Opening JDBC store tables "myC_3JMSStore" and "myC_3JMSState" using connection pool "cgPool".>
    ####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040118> <JMSServer "cgJMSServer_auto_3". Finished scan of JDBC store. Found 3 records.>
    ####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040010> <JMSServer "cgJMSServer_auto_3" configured no session pools.>
    ####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040109> <JMSServer "cgJMSServer_auto_3" is started.>
    ####<Sep 23, 2004 5:50:59 PM EDT> <Info> <JMS> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-040309> <JMS server "cgJMSServer_auto_3" is activated.>
    ####<Sep 23, 2004 5:51:00 PM EDT> <Info> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000256> <Invoking com.bea.wli.init.BPMStartup.main(null)>
    ####<Sep 23, 2004 5:51:00 PM EDT> <Debug> <Management> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-141132> <Dynamic invocation while executing action updateDeployments on myClusterTest08:Location=new_managedServer_3,Name=new_managedServer_3,Type=ServerConfig MBean instance failed. The method updateDeployments with signature [] was invoked with parameters as [].
    weblogic.management.AbortDeploymentException: weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
    [java.lang.NullPointerException]
    at weblogic.t3.srvr.StartupClassService.addDeployment(Lweblogic.management.configuration.DeploymentMBean;)V(StartupClassService.java:92)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Lweblogic.management.configuration.DeploymentMBean;)Z(DeploymentTarget.java:330)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Ljava.util.List;)V(DeploymentTarget.java:590)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments()V(DeploymentTarget.java:568)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments()V(DeploymentTarget.java:240)
    at COM.jrockit.reflect.NativeMethodInvoker.invoke0(ILjava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Native Method)
    at COM.jrockit.reflect.NativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
    at COM.jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
    at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(DynamicMBeanImpl.java:711)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(DynamicMBeanImpl.java:690)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(ConfigurationMBeanImpl.java:476)
    at com.sun.management.jmx.MBeanServerImpl.invoke(Ljava.lang.Object;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(MBeanServerImpl.java:1557)
    at com.sun.management.jmx.MBeanServerImpl.invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(MBeanServerImpl.java:1525)
    at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(RemoteMBeanServerImpl.java:947)
    at weblogic.management.internal.RemoteMBeanServerImpl.invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(RemoteMBeanServerImpl.java:908)
    at weblogic.management.internal.MBeanProxy.invoke(Ljava.lang.String;[Ljava.lang.Object;)Ljava.lang.Object;(MBeanProxy.java:946)
    at weblogic.management.internal.MBeanProxy.invokeForCachingStub(Ljava.lang.String;[Ljava.lang.Object;)Ljava.lang.Object;(MBeanProxy.java:481)
    at weblogic.management.configuration.ServerMBean_Stub.updateDeployments()V(ServerMBean_Stub.java:7271)
    at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments()V(SlaveDeployer.java:1210)
    at weblogic.management.deploy.slave.SlaveDeployer.resume()V(SlaveDeployer.java:362)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume()V(DeploymentManagerServerLifeCycleImpl.java:229)
    at weblogic.t3.srvr.SubsystemManager.resume()V(SubsystemManager.java:131)
    at weblogic.t3.srvr.T3Srvr.resume()V(T3Srvr.java:964)
    at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:359)
    at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)
    >
    ####<Sep 23, 2004 5:51:00 PM EDT> <Error> <Deployer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-149601> <The deployment framework was unable to resume accepting requests.>
    ####<Sep 23, 2004 5:51:00 PM EDT> <Emergency> <WebLogicServer> <informatica-svr> <new_managedServer_3> <Thread-1> <<WLS Kernel>> <> <BEA-000342> <Unable to initialize the server: [Deployer:149601]The 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.NullPointerException]>

Maybe you are looking for