Automatic startup of managed servers

hi all. i'm running wls 9.2, and i've got the node manager running as a windows service. i also created a managed server, and I would like it to start when windows starts. is this possible? Thanks.
qin_23

Hi there,
Using a WLST script, you should be able to do so.
More info available @ :
http://e-docs.bea.com/wls/docs92/config_scripting/manage_servers.html#wp1009240
Then just find some tools to generate a service for Windows (easily findable) and you're done !
Regards,
Maxence.

Similar Messages

Weblogic 6.0 Automatic startup of Managed Servers

Simple question -
Environ: Weblogic 6.0, NT/2K
Is there a way to start the managed servers under a given AdminServer
without configuring the individual managed servers as an NT Service?
I'd like the AdminServer be registered as a service, come up
automatically and then kick of its managed servers.
Thanks,
John

Is there a way to start the managed servers under a given
AdminServerwithout configuring the individual managed servers as an NT
Service?Nope
I'd like the AdminServer be registered as a service, come up
automatically and then kick of its managed servers.You will have to write a NT script for that. its not possible from within
the WLS infrastructure.
cheers,
Mihir

Automatically starting of Managed Servers

Hi, is it possible to start the managed servers without the use of WLST and the admin console automatically?
I want to make it such that when the Admin Server starts up, a service will run and automatically start the managed servers at a different host via the node manager?
Is it even possible? Please advise! Thanks!

Node Manager uses WLST so I'm not sure how else you would plan on using it?
Node Manager can start your machines in the last known state they were in on reboot using CrashRecoveryEnabled=true:
http://blogs.oracle.com/jamesbayer/2010/01/weblogic_nodemanager_quick_sta.html
Another option is to use the startup/services feature of your OS as Jay described. On *nix you could remotely login to another host and invoke the domain's bin/startManagedWebLogic script directly.

Best way to make managed servers start up on machine startup?

I had thought that if I used NodeManager to start servers from the admin console, if I rebooted the computer, and my RC scripts brought up the NodeManager (and AdminServer), that the NodeManager would note that the managed server had been in a running state before, and that it should be automatically restarted.
In my testing, it doesn't do that. I filed a support case to ask about this, and they concurred, saying that the NodeManager won't do that for me.
So, is the best strategy for starting up managed servers at system startup to write a wlst script that runs after NodeManager startup that tells the NodeManager to start the managed servers? Or is there a way to make the NodeManager automatically start the managed servers?

If it matters to anyone, I tried writing a WLST script taken directly from examples that connects to the NodeManager and starts up a managed server, but it didn't work (I don't have the text of the error anymore). However, a similar version that connects to the AdminServer worked perfectly fine.
At this point, however, I'm not sure that I want to do this anyway. After a server restart, it's good to have the NodeManager and AdminServer automatically start, but I'm examining whether the ManagedServer startup should be automatic. I'll have to think about it.

Concurrent startup managed servers in a cluster

I'm using WLS 6.1 sp3 on Solaris 8. I configured 24 instances in a cluster.
          I tried to startup all managed servers at the same time. Some of the
          instance failed. Due to the WLS startup time (half hour to start an instance
          cause we have many ejbs), I didn't try to start servers one by one. Here is
          the log file I got from one of the failed servers. Any help will be
          appreciated.
          Thanks!
          Wenji
          /bea/jdk131/bin/java -server -ms512m -mx512m -XX:NewSize=128m -XX:MaxNewSize
          =128m -verbosegc -classpath
          .:/appdata/wls/cbfe1b/config/prod/properties:/appdata/wls/cbfe1b/config/prod
          /properties/srv34:/oracle/product/8.1.7/jdbc/lib/classes12.zip:/appdata/wls/
          cbfe1b/config/prod/lib/externalAPIs/iioprt.jar:/appdata/wls/cbfe1b/config/pr
          od/lib/externalAPIs/xerces.jar:/appdata/wls/cbfe1b/config/prod/lib/externalA
          PIs/jdom.jar:/appdata/wls/cbfe1b/config/prod/lib/externalAPIs/log4j-1.2.5.ja
          r:/appdata/wls/cbfe1b/config/prod/lib/externalAPIs/xalan.jar:/oracle/product
          /8.1.7/jdbc/lib/nls_charset12.zip:/bea/wlserver6.1:/bea/wlserver6.1/lib/webl
          ogic.jar:/appdata/wls/cbfe1b/config/prod/classes:/appdata/wls/cbfe1b/config/
          prod/lib/eontec/eontec_custom_user_realm.jar:/appdata/wls/cbfe1b/config/prod
          /lib/ibm/mqccf.jar:/appdata/wls/cbfe1b/config/prod/lib/ibm/ccf.jar:/appdata/
          wls/cbfe1b/config/prod/lib/ibm/eablib.jar:/appdata/wls/cbfe1b/config/prod/li
          b/ibm/imsconn.jar:/appdata/wls/cbfe1b/config/prod/lib/ibm/recjava.jar -Dwebl
          ogic.Domain=prod -Dweblogic.Name=prod-srv34 -Dbea.home=/bea -Dweblogic.manag
          ement.server=milkyway:8100 -Djava.security.policy=/bea/wlserver6.1/lib/weblo
          gic.policy -Dweblogic.management.password=eontec00 -Dweblogic.RootDirectory=
          /appdata/wls/cbfe1b weblogic.Server
          Starting WebLogic Server ....
          MBean Info preloading problem:
          java.lang.NullPointerException
          at java.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2266)
          at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:514)
          at
          weblogic.management.tools.AttributeInfo.readObject(AttributeInfo.java:151)
          at java.lang.reflect.Method.invoke(Native Method)
          at
          java.io.ObjectInputStream.invokeObjectReader(ObjectInputStream.java:2209)
          at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1406)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:381)
          at java.io.ObjectInputStream.inputArray(ObjectInputStream.java:1137)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369)
          at java.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2258)
          at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:514)
          at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1407)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:381)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:231)
          at weblogic.management.internal.Helper.getMBeanInfo(Helper.java:205)
          at weblogic.management.internal.Helper.preloadMBeanInfos(Helper.java:232)
          at weblogic.management.Admin.initialize(Admin.java:226)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
          at weblogic.Server.main(Server.java:35)
          Connecting to http://milkyway:8100...
          The WebLogic Server did not start up properly.
          Exception raised:
          java.lang.NullPointerException
          <<no stack trace available>>
          --------------- nested within: ------------------
          weblogic.management.configuration.ConfigurationException: connecting to
          http://milkyway:8100/wl_management_internal2/Bootstrap - with nested
          exception:
          [java.lang.NullPointerException]
          at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1164)
          at weblogic.management.Admin.initialize(Admin.java:340)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
          at weblogic.Server.main(Server.java:35)
          Reason: Fatal initialization exception


Admin server is not a member of a cluster.
          Wenji
          Wenji Tong wrote:
          > I'm using WLS 6.1 sp3 on Solaris 8. I configured 24 instances in a cluster.
          > I tried to startup all managed servers at the same time. Some of the
          > instance failed. Due to the WLS startup time (half hour to start an instance
          > cause we have many ejbs), I didn't try to start servers one by one. Here is
          > the log file I got from one of the failed servers. Any help will be
          > appreciated.
          >
          > Thanks!
          > Wenji
          >
          >
          >
          > /bea/jdk131/bin/java -server -ms512m -mx512m -XX:NewSize=128m -XX:MaxNewSize
          > =128m -verbosegc -classpath
          > .:/appdata/wls/cbfe1b/config/prod/properties:/appdata/wls/cbfe1b/config/prod
          > /properties/srv34:/oracle/product/8.1.7/jdbc/lib/classes12.zip:/appdata/wls/
          > cbfe1b/config/prod/lib/externalAPIs/iioprt.jar:/appdata/wls/cbfe1b/config/pr
          > od/lib/externalAPIs/xerces.jar:/appdata/wls/cbfe1b/config/prod/lib/externalA
          > PIs/jdom.jar:/appdata/wls/cbfe1b/config/prod/lib/externalAPIs/log4j-1.2.5.ja
          > r:/appdata/wls/cbfe1b/config/prod/lib/externalAPIs/xalan.jar:/oracle/product
          > /8.1.7/jdbc/lib/nls_charset12.zip:/bea/wlserver6.1:/bea/wlserver6.1/lib/webl
          > ogic.jar:/appdata/wls/cbfe1b/config/prod/classes:/appdata/wls/cbfe1b/config/
          > prod/lib/eontec/eontec_custom_user_realm.jar:/appdata/wls/cbfe1b/config/prod
          > /lib/ibm/mqccf.jar:/appdata/wls/cbfe1b/config/prod/lib/ibm/ccf.jar:/appdata/
          > wls/cbfe1b/config/prod/lib/ibm/eablib.jar:/appdata/wls/cbfe1b/config/prod/li
          > b/ibm/imsconn.jar:/appdata/wls/cbfe1b/config/prod/lib/ibm/recjava.jar -Dwebl
          > ogic.Domain=prod -Dweblogic.Name=prod-srv34 -Dbea.home=/bea -Dweblogic.manag
          > ement.server=milkyway:8100 -Djava.security.policy=/bea/wlserver6.1/lib/weblo
          > gic.policy -Dweblogic.management.password=eontec00 -Dweblogic.RootDirectory=
          > /appdata/wls/cbfe1b weblogic.Server
          > Starting WebLogic Server ....
          > MBean Info preloading problem:
          > java.lang.NullPointerException
          > at java.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2266)
          > at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:514)
          > at
          > weblogic.management.tools.AttributeInfo.readObject(AttributeInfo.java:151)
          > at java.lang.reflect.Method.invoke(Native Method)
          > at
          > java.io.ObjectInputStream.invokeObjectReader(ObjectInputStream.java:2209)
          > at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1406)
          > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:381)
          > at java.io.ObjectInputStream.inputArray(ObjectInputStream.java:1137)
          > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369)
          > at java.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2258)
          > at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:514)
          > at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1407)
          > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:381)
          > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:231)
          > at weblogic.management.internal.Helper.getMBeanInfo(Helper.java:205)
          > at weblogic.management.internal.Helper.preloadMBeanInfos(Helper.java:232)
          > at weblogic.management.Admin.initialize(Admin.java:226)
          > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
          > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
          > at weblogic.Server.main(Server.java:35)
          > Connecting to http://milkyway:8100...
          > ***************************************************************************
          > The WebLogic Server did not start up properly.
          > Exception raised:
          > java.lang.NullPointerException
          > <<no stack trace available>>
          > --------------- nested within: ------------------
          > weblogic.management.configuration.ConfigurationException: connecting to
          > http://milkyway:8100/wl_management_internal2/Bootstrap - with nested
          > exception:
          > [java.lang.NullPointerException]
          > at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1164)
          > at weblogic.management.Admin.initialize(Admin.java:340)
          > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
          > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
          > at weblogic.Server.main(Server.java:35)
          > Reason: Fatal initialization exception
          > ***************************************************************************
          >
          >
          >

Automatic startup of admin server + managed server on Windws

Hello,
I have installed/configured WLS 10.3.6 + Forms/Reports 11.1.2.1 on Windows 2008 R2. All this went ok with no errors.
The NodeManager is installed as a service and runs happily after every reboot of the server. OPMN does it as well.
I can connect to the NodeManager with WLST and start/stop/status the Admin Server and the managed servers (WLS_FORMS,WLS_REPORTS) created during the
the installation/configuration step. Each server has the username/password defined (and already encrypted).
However, when I restart the Windows Server, neither the Admin Server nor the WLS_x servers are started during the boot.
I thought that the configuration process was in charge of setting all this, that was my experience with the previous version Oracle Internet Application Server (iAS) 10.1.2.x (opmn running as a service started them all).
I have run through the installation/configuration docs, and found nothing that says that Oracle will configure (or not) the automatic startup.
1) Is the Oracle configuration process (the one that creates the ClassicDomain) supposed to configure the automatic startup of the admin server + managed servers in this setup ? Am I missing perhaps some extra steps ?
or
2) Do I have to create WLST scripts (that connect to the NodeManager and start the admin server + managed servers) and deploy them as Windows Services myself ?
regards.

Hi,
During weblogic installation in window server, node manager will be automatically registered as window services. But for admin and managed servers, you need to register it manually after succesful installation and configuration for automatic startup during machine reboot.
Please refer the metaliknk id for register as window services:1060058.1.
If this helps please mark.
Regards,
Kishore

Startup.properties settings for managed servers

We are using WLS 9.2 MP3 on Solaris 10 (SPARC).
I have built a few test systems in an attempt to document configurations and noticed my managed servers on the systems start up with a different "weblogic.management.server" setting in the log files. This setting appears in the <domain>/servers/<server name>/data/nodemanager/start.properties file as "AdminURL=http:\://xxx.xxx.xxx.xxx\:7001"
Each system was built and rebuilt using the same settings. Each system has multiple interfaces. One system has an entry of AdminURL=http:\://192.168.100.100\:7001 and another system has an entry of AdminURL=http:\://10.10.10.100\:7001 even though each system was built just like the other.
Every time I manually change the adminURL setting it gets reset on each server restart (which I expected). I have not specified (that I know of) the IP address or interface of the admin server anywhere in the "server start" settings. I also notice the admin server is starting on all interfaces on the system (not sure if this is good/bad/indifferent).
Can anyone tell me where the startup.properties file entries are pulled from?
As a followup: I just noticed (after my post) a slight difference between my systems. One has a fiber connection whereas the others do not. When I execute 'ifconfig -a' I see the interfaces/IP's in different orders (because the interfaces are named differently). I also noticed a wlsifconfig.sh script in one of the startup files. It almost appears as though the wlsifconfig.sh script is setting the AdminURL value and is pulling it from the last interface it finds in the ifconfig listing?????
Thanks for any assistance

To diagnose problems with Thunderbird, try one of the following:
*Restart Thunderbird with add-ons disabled (Thunderbird Safe Mode). On the Help menu, click on "Restart with Add-ons Disabled". If Thunderbird works like normal, there is an Add-on or Theme interfering with normal operations. You will need to re-enable add-ons one at a time until you locate the offender.
*Restart the operating system in '''[http://en.wikipedia.org/wiki/Safe_mode safe mode with Networking]'''. This loads only the very basics needed to start your computer while enabling an Internet connection. Click on your operating system for instructions on how to start in safe mode: [http://windows.microsoft.com/en-us/windows-8/windows-startup-settings-including-safe-mode Windows 8], [http://windows.microsoft.com/en-us/windows/start-computer-safe-mode#start-computer-safe-mode=windows-7 Windows 7], [http://windows.microsoft.com/en-us/windows/start-computer-safe-mode#start-computer-safe-mode=windows-vista Windows Vista], [http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/boot_failsafe.mspx?mfr=true" Windows XP], [http://support.apple.com/kb/ht1564 OSX]
; If safe mode for the operating system fixes the issue, there's other software in your computer that's causing problems. Possibilities include but not limited to: AV scanning, virus/malware, background downloads such as program updates.

Managed Servers do not start automatically on machine reboot.

Hi all,
We have installed node manager as windows service.
We have configured a managed server and an admin server which are on same machine.
We are using WLST to start the admin and the managed servers.
The sequence is :
java weblogic.WLST
connect()
nmStart('AdminServer')
nmStart('ManagedServerName')
We are successfully able to start both the server's, however if we reboot the machine, the servers fail to come up even though we have installed node manager as windows service.
We also have Auto Restart and crash recovery as true/enabled.
Do we need to do any other setting??
Any pointers on the same will be highly appreciated..
Thanks.

Hi,
I'm having the same issue. I cannot start a ManagedServer using NodeManager. I'm using WLST script to start the Admin and Managed Server:
nmConnect('username', 'password', 'localhost', '5556', 'base_domain','D:\\product\\Oracle\\11.1.1\\Middleware\\user_projects\\domains\\base_domain','ssl')
nmStart('AdminServer')
connect('username','password','t3://localhost:7001')
start('managedServer', 'Server', t3://localhost:7001')
I've successfully restarted using the "startWeblogic.cmd" and "startManagedServer.cmd" scripts.

How to install Window service for Managed Servers of a Cluster

Dear All,
          I am preparing a production setup consist of three machines A,B and C. Machines A is the Admin Server which hosts a cluster consist of two managed nodes. I intend to schedule both these nodes, targeted to two different machines (machines B node-b and machine C host node-c), as startup task on daily basis. I have no Node Manager running on machine A, but on machine B and machine C.
          I am only interested to schedule started task for node-b and node-c only. I need to know how to install the Windows services for the node-b and node-c since there are targeted on remote machines. Starting managed server as Win sevice works in the case of standalone managed servers but not sure when it comes to cluster setup.I appreciate if you can throw some light on this question.
          Thanks
          Kris

Krish,
          >Let say I gracefully shutdown both managed servers while >Admin is running. Do you think both these nodes while be >brought up ? I dont think they will come up.
          If you require an automatic restart when the managed server did not enter a failed state you can use the weblogic.Admin utility to ping the servers and kick off a server startup in the normal way with nodemanger see:
          http://e-docs.bea.com/wls/docs81/admin_ref/cli.html
          http://e-docs.bea.com/wls/docs81/adminguide/confignodemgr.html
          If your servers entered a failed state you can use weblogics self health monitoring.
          >Can we use JMX MBean to start managed servers ?
          Yes.
          As long as the nodemanagers are running you can start the managed servers using scripted commands using the weblogic.Admin class or your own java app using JMX.
          I think you may also be able to use WLST
          http://dev.bea.com/codelibrary/code/wlst.jsp
          hope this helps
          cheers
          Please see the
          Hussein Badakhchani
          www.orbism.com

Node Manager Not Starting Managed Servers

I have nodemanager configured to restart managed servers automatically upon reboot but when I physically restart the 2nd node none of the managed servers start and there are no errors. Steps completed and verified....
1) Nodemanager.properties has domain path and 'crashrecoveryenabled' set to 'true'
2) managed servers have autorestart set to 'true' and -Xnohup parameter added to startup arguments.
3) Boot.properties files ave the username and password (encrypted) to start up the server.
Here is the nodemanager.log file and you can clearly see it is grabbing the startup files. It almost looks like the server files are trying to get loaded before the nodemanager port is available but I see no errors. Any ideas?
<Dec 28, 2009 9:16:59 AM> <Info> <QA10311> <WebProxyServer2> <Working directory is "C:\bea\user_projects\domains\QA10311">
<Dec 28, 2009 9:16:59 AM> <Info> <QA10311> <WebProxyServer2> <Server output log file is "C:\bea\user_projects\domains\QA10311\servers\WebProxyServer2\logs\WebProxyServer2.out">
<Dec 28, 2009 9:47:09 AM> <INFO> <Loading domains file: C:\bea\WLSERV~1.3\common\nodemanager\nodemanager.domains>
<Dec 28, 2009 9:47:16 AM> <INFO> <Loading identity key store: FileName=C:/bea/WLSERV~1.3/server\lib\DemoIdentity.jks, Type=jks, PassPhraseUsed=true>
<Dec 28, 2009 9:47:18 AM> <INFO> <Loaded node manager configuration properties from 'C:\bea\WLSERV~1.3\common\nodemanager\nodemanager.properties'>
<Dec 28, 2009 9:47:21 AM> <Info> <QA10311> <ACR2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\ACR2\data\nodemanager\startup.properties">
<Dec 28, 2009 9:47:21 AM> <Info> <QA10311> <CommandNet2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\CommandNet2\data\nodemanager\startup.properties">
<Dec 28, 2009 9:47:21 AM> <Info> <QA10311> <FPCE2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\FPCE2\data\nodemanager\startup.properties">
<Dec 28, 2009 9:47:21 AM> <Info> <QA10311> <MQServer2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\MQServer2\data\nodemanager\startup.properties">
<Dec 28, 2009 9:47:22 AM> <Info> <QA10311> <PortalServer2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\PortalServer2\data\nodemanager\startup.properties">
<Dec 28, 2009 9:47:22 AM> <Info> <QA10311> <ShoppingCart2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\ShoppingCart2\data\nodemanager\startup.properties">
<Dec 28, 2009 9:47:22 AM> <Info> <QA10311> <webapp2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\webapp2\data\nodemanager\startup.properties">
<Dec 28, 2009 9:47:22 AM> <Info> <QA10311> <WebProxyServer2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\WebProxyServer2\data\nodemanager\startup.properties">
<Dec 28, 2009 9:47:22 AM> <Info> <QA10311> <WUA2> <Startup configuration properties loaded from "C:\bea\user_projects\domains\QA10311\servers\WUA2\data\nodemanager\startup.properties">
<Dec 28, 2009 9:47:27 AM> <INFO> <Secure socket listener started on port 5556, host qaportal2.FCQA.COM>

Hi,
Entries in nodemanager.properties looks fine, but how are you testing this functionality?
If you will stop servers monitored by nodemanager, stop nodemanager and then reboot physical server, on startup if nodemanager is configured as daemon it will start nm process but will do nothing to managed server process.
To test "CrashRecoveryEnabled=true" kill the managed server pid and then stop/kill nodemanager process. Then perform physical server reboot, now if nm is configured as daemon process server reboot will start nodemanager. Once NM is up first thing it check is the server it was monitoring earlier and if under directory $WL_HOME/servers/<server>/data/nodemanager it finds "pid" and "lck" file it checks if that pid exists and if not then go for a restart of weblogic server instance.
This has worked for me...!
Thanks,
Ranjan
http://www.middlewaresupport.wordpress.com

While starting managed servers asks for password of localhost

We have a clustered environment and we are using Virtual IPs for the Managed servers. The managed servers in the forst node is not starting.
The problem I have narrowed down is that there are startup.properties file for the managed servers.
It has argument like -Dtangosol.coherence.localhost\=xgsoapd5v1.ea.com (for SOA1)
While SOA1 it is asking for password for the above host and the managed server is not starting.
Now SOA2 has the similar argument -Dtangosol.coherence.localhost\=xgsoapd5v2.ea.com (for SOA2), but it is not asking for any password and so the SOA2 managed server is sta! rting.
Similarly the while starting BAM1 it is asking for a password , but for BAM2 it is not asking for password and it is starting.
I could not yet figure out why it is behaving differently in the first node.
This is a copy of production with a chnage in the network. That means only the IP addresses are changed. xgsoapd5v1.ea.com and xgsoapd5v2.ea.com are the hostnames
It works perfectly in production environment.

Hi
Under your domain root folder say in the main machine where you have the AdminServer, you should have a folder structure something like this:
../user_projects/domains/yourBPMDomain1/servers. Under the servers folder you can see list of each server. On the main machine you will see one AdminServer folder. Under this there should be a sub-folder named security with one file named boot.properties. This boot.properties file will have encrypted username and password for the weblogic domain.
If this security/boot.properties exist under the each server folder, then when you start the managed server, it will NOT prompt for the username/password. If it DO NOT exist, it will ask for the credentials.
Solution is go to each Machine where you the ManagedServers (SOA Server or BAM Server does not matter). Go to each server and under that create a folder named security and create a file named boot.properties and in this file enter plain text username and password something like this and save the file. Now restart all those servers.
username=domainadminusername
password=doaminadminpassword
When you start the servers, server should start taking the above information. AND server will automatically ENCRYPT the above plain text data into hash codes.
In a nut shell, go to each Server folder across all the remote machines and under that particular managed server create a folder security with one file boot.properties.
Exmaple locations:
On Machine1 - user_projects/domains/bpmDomain1/servers/soa_server1/security/boot.properties
On Machine2 - user_projects/domains/bpmDomain1/servers/bam_server1/security/boot.properties
You DO NEED the admin username and password in plain text for one time to put in boot.properties. Later on it will get encrypted, so there is no threat for any security loop holes.
Thanks
Ravi Jegga

Have NodeManager start managed servers on machine reboot

Is there any way to have the Node Manager start all the managed servers belonging to a domain when a server reboots?
I know I could create a separate Windows service for each of the managed servers I want running when the server comes on-line, or I could do some fancy scripting at start-up to connect to the Node Manager and have it start the managed servers.
But I was hoping there would be a more elegant way of having the NM start them when it comes on-line.
Ideas appreciated,
dmac.

Hi Dmac,
To achieve this in Windows, you must consider the following WLS Components:
1. Node Manager
2. Admin Server
3. Managed Server
Node Manager
For Node Manager, if you want the component to start automatically on boot up, your best option is to create a Windows Service. You may have selected the option to create a service for Node Manager during the WebLogic Server installation. Use Start -> Run -> services.msc from the Start menu to load the Windows Services Manager. If there is no service for Node Manager, use the following steps to create one.
Create a Windows service for Node Manager:
1. WL_HOME\server\bin\installNodeMgrSvc.cmd
2. Verify in Windows Services that a service was created.
Admin Server
For the Admin Server, you can also create a Windows Service. Here are the steps for doing so:
Create a Windows service for the Admin Server
1. Create a text file named %MIDDLEWARE_HOME%\user_projects\domains\<domain name>\servers\AdminServer\security\boot.properties. Add the following lines:
username=weblogic
password=<the weblogic username password>
2. Create a command script called installAdmServer_Service.cmd which you will want to make sure has lines like:
SETLOCAL
set DOMAIN_NAME=<your wls domain>
set USERDOMAIN_HOME=<path to domain> # e.g., C:\middleware\FMW11g\user_projects\domains\ClassicDomain
set SERVER_NAME=AdminServer
set PRODUCTION_MODE=true
cd %USERDOMAIN_HOME%
call %USERDOMAIN_HOME%\bin\setDomainEnv.cmd
call "<your middleware home>\wlserver_10.3\server\bin\installSvc.cmd"
ENDLOCAL
3. For troubleshooting/debugging purposes it is helpful to redirect standard out and error to a text file. Although most information is captured in the AdminServer server log files, you will not see all standard out and error when the server is started via a MS Windows Service (unlike when you start an AdminServer from the command prompt using startWebLogic.cmd). To redirect standard out to a text file, backup and edit installSvc.cmd and change the line at the bottom of the file so it includes the -log parameter, e.g.
"%WL_HOME%\server\bin\beasvc" -install -svcname:"%DOMAIN_NAME%_%SERVER_NAME%" -javahome:"%JAVA_HOME%" -execdir:"%USERDOMAIN_HOME%" -extrapath:"%WL_HOME%\server\bin" -password:"%WLS_PW%" -cmdline:%CMDLINE% -log:"<your middleware home>\user_projects\domains\<your wls domain name>\servers\AdminServer\logs\AdminServer-stdout.txt"
4. Now run "installAdmServer_Service.cmd." The Service should be installed. It will have a name like "beasvc %DOMAIN_NAME%_%SERVER_NAME%" (e.g. beasvc ClassicDomain_AdminServer). The Service "Startup Type" will be "Automatic." Start the Service. The Service will come back fairly quickly to say it is started. The actual time taken for the admin server to start and reach a state of 'RUNNING' will be longer - perhaps two or three minutes. The state of the server can be monitored by reviewing the stdout txt file.
Managed Server
For the Managed Server, you can also create a Windows Service. Here are the steps for doing so:
Create a Windows service for the Managed Server (using wls_forms as an example)
1. Create a text file named %MIDDLEWARE_HOME%\user_projects\domains\<domain name>\servers\WLS_FORMS\security\boot.properties. Add the following lines:
username=weblogic
password=<the weblogic username password e.g manager11g>
2. Create a command script called installWLSFORMS_Service.cmd which has lines like
SETLOCAL
set DOMAIN_NAME=<your wls domain>
set USERDOMAIN_HOME=<path to domain> # e.g. C:\middleware\FMW11g\user_projects\domains\ClassicDomain
set SERVER_NAME=WLS_FORMS
set PRODUCTION_MODE=true
set ADMIN_URL=http://mymachine.mycompany.com:7001
cd %USERDOMAIN_HOME%
call %USERDOMAIN_HOME%\bin\setDomainEnv.cmd
call "<your middleware home>\wlserver_10.3\server\bin\installSvc.cmd"
ENDLOCAL
NOTES:
a. The ADMIN_URL value should reference the AdminServer hostname and listen port.
b. The SERVER_NAME value is case sensitive. For example, if you are creating a MS Windows service for a different managed server such as 'wls_ods1' then the value needs to match the case of the server name otherwise the startup of the server via the MS Windows service will fail.
c. Be careful that there are no trailing spaces after each line in the command file - trailing spaces will cause the managed server to fail at startup. For example a trailing space in the ADMIN_URL value will result in the error
<19-Jan-2010 11:37:58 o'clock GMT> <Error> <EmbeddedLDAP> <BEA-171524> <Cannot determine the Listen address for the Admin server
3. Now run "installWLSFORMS_Service.cmd." The Service should be installed, it will have a name like "beasvc %DOMAIN_NAME%_%SERVER_NAME%" (e.g. beasvc ClassicDomain_WLS_FORMS). The Service "Startup Type" will be "Automatic." Start the Service. The Service will come back fairly quickly to say it is started. The actual time taken for the managed server to start and reach a state of 'RUNNING' will be longer - perhaps two or three minutes. The state of the server can be monitored by reviewing the stdout txt file.
Configuring the Windows service to restart upon failure
As with any Windows Service, it is possible to configure the service to restart itself upon failure. These are standard options available when configuring a Windows Service in the context of Windows Services Manager. However, it is important to understand that Windows Services Manager only monitors the JVM process. If the JVM process fails (shuts down), then Windows Services Manager will attempt to restart it. But there are some scenarios where the Admin Server or Managed Server may go into an unhealthy or failed state but the JVM is still running. The Windows Service will not know to restart the process in these cases, whereas if the Admin Server and Managed Server had been started using Node Manager, Node Manager would recognize such a state and restart the process accordingly. So it may be desirable to start Node Manager with a Windows Service and then start the Admin Server and Managed Servers with Node Manager to take advantage of this monitoring feature. Below you will find one such example of how to do this.
Example of starting the Admin Server and a Managed Server using Node Manager
1. Create a batch script similar to this:
Myscript.cmd
call D:\Product\Oracle\Middleware\user_projects\domains\base_domain\bin\setDomainEnv.cmd
java weblogic.WLST D:\Product\Oracle\Middleware\user_projects\domains\base_domain\ServerStart.py
2. Create a Python script similar to this:
ServerStart.py
nmConnect('weblogic', 'welcome1', '192.168.0.101', '5556', 'base_domain','D:\Product\Oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1','ssl')
nmStart('AdminServer')
connect ('weblogic','welcome1','t3://192.168.0.101:7001')
nmstart('myserver','Server','t3://192.168.0.101:7002')
If you want this to happen automatically on boot up, you can run the script (myscript.cmd) from the Windows Scheduler. You must configure the scheduler to run the script on system startup. This will execute the script without requiring an interactive login to Windows (unattended).
Some Additional Information to Remember
The startup.properties file for the Admin and Managed servers must have "AutoRestart=true." This can be set in the "Health Monitoring" tab for each respective server in the WLS console.
The boot.properties file must be configured and present for each server that you plan to start automatically so that you are not prompted for the user name and password each time. If you are not currently prompted when you start the servers then it is already done.
The nodemanager.properties file must have "StartScriptEnabled=true" and "StartScriptName=StartWeblogic.cmd" in place.

How to deploy config files to managed servers

We have several configuration files that are used by our EJB application at
startup. Is there a way to automatically deploy these configuration files
to the managed servers. Right now, we are forced to FTP to files over to
the managed servers as part of the deployment process. It would be nice if
there were an easier way.
Randy Ott

why cant you include them inside your ejbjar as resource files ?
prasen
Nitin Shenoy wrote:
>
Guess no one replied!!
"Randy Ott" <[email protected]> wrote in message
news:3b67022e$[email protected]..
We have several configuration files that are used by our EJB applicationat
startup. Is there a way to automatically deploy these configuration files
to the managed servers. Right now, we are forced to FTP to files over to
the managed servers as part of the deployment process. It would be niceif
there were an easier way.
Randy Ott

9iAS R2 Automatic Startup at Boot time on Windows

How to successfully start the 9iAS R2 Application Server at boot time.
Many of you are still struggling with the problem of 9iAS R2 not automatically starting up properly when your system is restarted. I've been fighting this issue for several weeks and have found the problems, and pitfalls, involved with fixing it. It really is a race condition of things trying to start up before something it depends on is fully functioning, or some application starting out of sequence.
There is a bug associated with this problem; BUG 2511270 ( 9IASV2 Need Ability to Restart All Components in Instance After a Reboot). The bug report itself has very little useful information in it other than to say it doesn't work, and manually starting the components is the only known fix. If you're like me. this isn't a good enough answer.
Your mileage may vary.
My configuration has a 9.2.0.1 customer database, and a 9.0.1.3.1 infrastructure database that is also the application server database, including portals, all installed on the same system which is a Pentium 4, Windows 2000 machine, with 1.5GB of memory. I only use a single LISTENER, which runs out of the 9.2 DB ORACLE_HOME.
Chapter 5 (Starting and Stopping the Application Server) of the Oracle9i Application Server Administrator's Guide shows all of the commands necessary, in the proper order, to manually start the infrastructure and application server. Unfortunately, there is also some incorrect information in this document.
Part 1c in the section Starting an Infrastructure Using Commands on Windows, using SQLPlus to connect to and start the database, does not work unless oracle.exe is already running (which means that you recently shutdown the database by command, not with "services>stop"). If your system is rebooting, oracle.exe is not running. This exact same information is documented in the Database Administrators Guide, Chapter 4, Starting a Database. If you don't have these manuals handy the offending commands are as follows:
ORACLE_HOME\bin\sqlplus /nologsql> connect sys/password_for_sys as sysdba
sql> startup
sql> quit
Since we can't put some variant of the above in a command script to manually start the databases and wait for it to open, the only option left is to let the databases come up in "automatic" mode when the system boots, and run the remaining commands when they are open. If your system is like mine, that can take several minutes, even after you've logged on and gotten your first cup of coffee.
If you set up a command script to run at startup, you don't have any control over when the script gets run, more than likely, in this case, before the databases are open. Unfortunately, Microsoft does not have anything resembling a sleep (timer, wait, delay, etc) command that can be used in a script. There may be something somewhere, but I can't find it. So I wrote one in Perl, which does have a sleep command. You can use anything you have available to you that will function as needed. We obtained our Perl distribution from http://aspn.activestate.com/ASPN/Perl.
The next issue has to do with starting the Oracle Internet Directory. The documentation shows two commands to execute, but in reality, only the first one is required, it automatically takes care of the second one. Refer to the command file below for the correct one.
The last issue deals with running the dcmctl commands. If you run these commands one at a time in a command window, you won't notice anything askew. If you run them, as shown, in a script, they will stop execution of the script when they complete, and there will be no indication that anything wrong has happened. The CMD.exe still exists, it just isn't running. They must be run in there own cmd command as shown below.
Now, let's review the steps necessary to get all this to work.
Put the two scripts shown below in there target directories and edit any necessary changes for your system.
In Start>Settings>Control Panel>Administrative Tools>Services set the OracleServiceSID's and the OracleOraHomeTNSListener to Automatic Startup Type. All other Oracle* services should be set to Manual.
In Start>Programs>Accessories>System Tools>Scheduled Tasks double click on the Add Scheduled Task item,
select Next,
Browse to where your startup script resides,
double click the file name,
select "When my computer starts",
select Next,
Enter a user name and password (that has ORA_DBA privileges)
select Next, then Finish.
Uncomment the first exit in the iasStartup.cmd script.
Reboot your system.
Compare the database open time stamp in each database alert log to the time recorded in the iasStartup.log file to determine you first time delay. Add 10-20 seconds or more to this difference just to be safe. If you add services at a later time, this number may need to be increased.
Edit the iasStartup.cmd file to include this time delay for the first sleep command and comment out the first exit command.
Reboot your system.
After several minutes, all infrastructure and application server processes should be up and running. You can check this in several ways; Look at the log file to see if all commands were run, Look at the Windows Task Manager to see if all expected tasks are running, Look at Services to see what is running. Finally, you can look at the Infrastructure Enterprise Manager Website and click on each instance to determine the current status of each system component. On mine, the component Portal:portal:7779 always shows as down but in reality it is functioning.
The following command script only starts the minimum set of processes that I require. Your requirements may be different so refer to the documentation for additional commands.
Enjoy.
******** iasStartup.cmd ********
REM # iasStartup.cmd
REM # Command script to start the infrastructure and application server at system boot
REM # Mike Bukaty
REM # Sandia National Laboratories
REM # [email protected]
REM # set default directory that contains the log and sleep.pl files.
cd E:\Oracle\admin
echo Starting iasStartup.cmd > iasStartup.log
time /t >> iasStartup.log
REM # Uncomment the following command to determine the time delay for your system
REM # exit
REM # This delay is determined by looking at the times from the alert logs
REM # for when the database was opened and the time recorded above.
REM # SLEEP is a perl script to do just that (in seconds) since Windows doesn't have one.
sleep.pl -delay=120
time /t >> iasStartup.log
REM #Start the infrastructure first
REM #The SID for the infrastructure must be set
set ORACLE_HOME=E:\Oracle\as9inf
set ORACLE_SID=iasdb
echo Starting as9inf oidmon >> iasStartup.log
%ORACLE_HOME%\bin\oidmon start
echo Starting as9inf EMWebsite >> iasStartup.log
net start Oracleas9infEMWebsite
REM # Have to wait for all of the website process to finish
sleep.pl -delay=40
REM # All calls to dcmctl must be in there own CMD environment,
REM # or they will halt this one when they complete
echo Starting as9inf dcmctl ohs >> iasStartup.log
cmd /c %ORACLE_HOME%\dcm\bin\dcmctl start -ct ohs
sleep.pl -delay=5
echo Starting as9inf dcmctl OC4J_DAS >> iasStartup.log
cmd /c %ORACLE_HOME%\dcm\bin\dcmctl start -co OC4J_DAS
REM # Start the application server
set ORACLE_HOME=E:\Oracle\ora9ias
echo Starting ora9ias webcachectl >> iasStartup.log
%ORACLE_HOME%\bin\webcachectl start >> iasStartup.log
echo Starting ora9ias dcmctl ohs >> iasStartup.log
cmd /c %ORACLE_HOME%\dcm\bin\dcmctl start -ct ohs
sleep.pl -delay=10
echo Starting ora9ias dcmctl OC4J >> iasStartup.log
cmd /c %ORACLE_HOME%\dcm\bin\dcmctl start -ct OC4J
REM # The above command starts all existing OC4J processes.
REM # You can now stop any that aren't necessary.
echo Stopping ora9ias dcmctl OC4J_Demos >> iasStartup.log
cmd /c %ORACLE_HOME%\dcm\bin\dcmctl stop -co OC4J_Demos
time /t >> iasStartup.log
echo Finished iasStartup.cmd >> iasStartup.log
exit
******** sleep.pl ********
#!/usr/local/bin/perl
## Author: Mike Bukaty
## Sandia National Laboratories
## [email protected]
## Program: sleep.pl
$| = 1;
use strict;
use Getopt::Long;
Getopt::Long::Configure("no_ignore_case");
GetOptions(
"delay=s" => \ my $delay,
# Set default options
if( not defined($delay) ) { $delay = 1; }
sleep $delay;
exit 1;

New information:
When I originally wrote this, the command script worked as advertised. That was yesterday. I've since had to add the following lines just BEFORE the call to start the oidmon.
echo Starting as9inf oidctl >> iasStartup.log
%ORACLE_HOME%\bin\oidctl server=oidldapd configset=0 instance=1 start
Sometimes me thinks that Oracle reconfigures itself at night when I'm not watching.
Enjoy.

Unable to start managed servers from Admin Console "FAILED_NOT_RESTARTABLE"

I recently installed WebLogic 10.3.5, JRockit, and ECM 11.1.1.5. I'm to the point where I am trying to get Nodemanager configured so I can stop/start managed servers through the admin console. I have the following listed in Environment > Servers:
AdminConsole - running
IBR_server1 - FAILED_NOT_RESTARTABLE
managedServer1 - FAILED_NOT_RESTARTABLE
UCM_server1 - FAILED_NOT_RESTARTABLE
I followed the tutorial at http://blogs.oracle.com/jamesbayer/entry/weblogic_nodemanager_quick_sta to get to the point where the AdminServer starts when the server reboots, so I think Nodemanager is working there. If I view Machines > Monitoring, it says Nodemanager "Reachable." However, when I go to restart IBR_server1, managedServer1, or UCM_server1, I get the FAILED_NOT_RESTARTABLE status. I am using the weblogic server's IP for the machine name/host because our DNS is still screwed up. Would that have any affect on this?
I'm completely unsure what to do now. The Nodemanager log shows:
INFO - <Loading domains file: E:\oracle\MIDDLE~1\WLSERV~1.3\common\nodemanager\nodemanager.domains>
WARNING - <Domains file not found: E:\oracle\MIDDLE~1\WLSERV~1.3\common\nodemanager\nodemanager.domains>
INFO - <Loading identity key store: FileName=E:/oracle/MIDDLE~1/WLSERV~1.3/server\lib\DemoIdentity.jks, Type=jks, PassPhraseUsed=true>
WARNING - <Node manager configuration properties file 'E:\oracle\MIDDLE~1\WLSERV~1.3\common\nodemanager\nodemanager.properties' not found. Using default settings.>
So I'm confused why it's saying the properties file and domains file are not found... I've checked and they exist at
E:\oracle\middleware\wlserver_10.3\common\nodemanager\nodemanager.properties
and
E:\oracle\middleware\wlserver_10.3\common\nodemanager\nodemanager.domains
The domains file contains
base_domain=e\:\\oracle\\middleware\\user_projects\\domains\\base_domain
Which is correct.
Any idea what I'm missing here? I can provide more detail if needed. Thank you.
EDIT: I should add that I can start the UCM and IBR managed servers using the start up scripts on the server, but that's not what I'm after. I want everything controlled through the AdminConsole and want to be sure that when the server reboots, all the managed servers come back up correctly.
Edited by: user5824683 on Oct 5, 2011 5:04 PM
Edited by: user5824683 on Oct 5, 2011 5:09 PM

I did a bit of digging, and it seems I have an issue with -Xnohup... I've verified this arugment exists in all of my managed servers properties files, yet it still bombs when I try to restart from the webLogic console. I should note that if I start fresh from the server, I can start all my manager servers using WLST nmStart().
starting weblogic with Java version:
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
Oracle JRockit(R) (build R28.1.3-11-141760-1.6.0_24-20110301-1430-windows-x86_64, compiled mode)
Starting WLS with line:
E:\java\JROCKI~1.1\bin\java -jrockit -Xms256m -Xmx512m -Dweblogic.Name=IBR_server1 -Djava.security.policy=E:\oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=E:\oracle\middleware\user_projects\domains\base_domain\servers\IBR_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xnohup -Xverify:none -da -Dplatform.home=E:\oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=E:\oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=E:\oracle\MIDDLE~1\WLSERV~1.3\server -Dcommon.components.home=E:\oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1 -Djrockit.optfile=E:\oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\FMWCON~1\servers\IBR_server1 -Doracle.domain.config.dir=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\FMWCON~1\carml -Digf.arisidstack.home=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\servers\IBR_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=E:\oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,E:\oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Ducm.oracle.home=E:\oracle\MIDDLE~1\ORACLE~2 -Dem.oracle.home=E:\oracle\middleware\oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=false -Dweblogic.management.server=http://138.126.180.177:7001 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=e:\oracle\MIDDLE~1\patch_wls1035\profiles\default\sysext_manifest_classpath weblogic.Server
Exception in thread "Main Thread" java.lang.NoClassDefFoundError: –Xnohup
Caused by: java.lang.ClassNotFoundException: –Xnohup
     at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
     at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
     at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
Could not find the main class: â€“Xnohup. Program will exit.
<Oct 6, 2011 12:38:13 PM> <FINEST> <NodeManager> <Waiting for the process to die: 4252>
<Oct 6, 2011 12:38:13 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Oct 6, 2011 12:38:13 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>

Automatic startup of managed servers

Similar Messages

Maybe you are looking for