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.

Similar Messages

Automatically start a Managed Sever after a reboot

I have been tasked with getting some Managed servers to start automatically after reboot, usually when Windows patches are installed. Starting the Managed servers through the GUI works just fine, but I would like for these to start on their own without someone getting involved. The server is Windows 2003 SP2, and the weblogic install should be 8.1.4. Nodemanager is installed as a service on the same server as the Admin servers and the Managed servers. I will try to provide as much info as I can but this is the first time I have worked with weblogic.
When the server reboots, all services are started and the Admin server is running, but the Managed Server's status is unknown until I manually start it.
I notice this warning in the Managed server log after the machine reboots and the Managed server status is unknown:
<Warning> <NodeManager> <QA-WEB01> <ManagedServer1> <Thread-5> <<WLS Kernel>> <> <BEA-300038> <The node manager is unable to monitor this server. Could not create an SSL connection to the node manager. Reason : Connection refused: connect>
From what I have read about this warning, hostname verification should be turned off. I can confirm that hostname verification is set to none. If anyone could point me in the right direction it would be very much appreciated.

Hi,
To overcome this you can create windows services for the managed servers as well.
Also, a good practice for windows hosts is to implement the graceful shutdown.
Cheers,
Vlad
Give points - it is good etiquette to reward an answerer points (5 - helpful; 10 - correct) for their post if they answer your question. If you think this is helpful, please consider giving points

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

Unable to start the Managed servers OIM and SOA after starting the Weblogic

Hi,
We are unable to start the any manager servers after starting the weblogic Admin Server.
We are getting the below error after trying to start the OIM or SOA managed servers.
Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 5555; nested exception is:
java.net.BindException: Address already in use
We have also cross verified that the port 5555 is listening after starting the weblogic Admin server.
Please help us to start the managed servers in the weblogic 10.3.5.
Thanks.

We are getting the below errors after starting the Admin server and Managed servers.
Admin Server:
<Jan 11, 2012 7:15:06 AM EST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Jan 11, 2012 7:16:02 AM EST> <Error> <org.apache.beehive.netui.pageflow.internal.AdapterManager> <BEA-000000> <ServletContainerAdapter manager not initialized correctly.>
Managed Server:
Starting WLS with line:
/opt/jdk1.6.0_27/bin/java -client -Xms1024m -Xmx4096m -XX:PermSize=512m -XX:MaxPermSize=1024m -Dweblogic.Name=oim_server1 -Djava.security.policy=/ama/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.security.SSL.trustedCAKeyStore=/ama/Oracle/Middleware/wlserver_10.3/server/lib/cacerts -Xverify:none -da -Dplatform.home=/ama/Oracle/Middleware/wlserver_10.3 -Dwls.home=/ama/Oracle/Middleware/wlserver_10.3/server -Dweblogic.home=/ama/Oracle/Middleware/wlserver_10.3/server -Dcommon.components.home=/ama/Oracle/Middleware/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=/ama/Oracle/Middleware/user_projects/domains/base_domain -Djrockit.optfile=/ama/Oracle/Middleware/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.server.config.dir=/ama/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig/servers/oim_server1 -Doracle.domain.config.dir=/ama/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig -Digf.arisidbeans.carmlloc=/ama/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig/carml -Digf.arisidstack.home=/ama/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig/arisidprovider -Doracle.security.jps.config=/ama/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig/jps-config.xml -Doracle.deployed.app.dir=/ama/Oracle/Middleware/user_projects/domains/base_domain/servers/oim_server1/tmp/_WL_user -Doracle.deployed.app.ext=/- -Dweblogic.alternateTypesDirectory=/ama/Oracle/Middleware/Oracle_IDM1/server/loginmodule/wls,/ama/Oracle/Middleware/oracle_common/modules/oracle.ossoiap_11.1.1,/ama/Oracle/Middleware/oracle_common/modules/oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol|oracle.fabric.common.classloaderurl.handler|oracle.fabric.common.uddiurl.handler|oracle.bpm.io.fs.protocol -Dweblogic.jdbc.remoteEnabled=false -DXL.HomeDir=/ama/Oracle/Middleware/Oracle_IDM1/server -Djava.security.auth.login.config=/ama/Oracle/Middleware/Oracle_IDM1/server/config/authwl.conf -Dorg.owasp.esapi.resources=/ama/Oracle/Middleware/Oracle_IDM1/server/apps/oim.ear/APP-INF/classes -da:org.apache.xmlbeans... -Dsoa.archives.dir=/ama/Oracle/Middleware/Oracle_SOA1/soa -Dsoa.oracle.home=/ama/Oracle/Middleware/Oracle_SOA1 -Dsoa.instance.home=/ama/Oracle/Middleware/user_projects/domains/base_domain -Dtangosol.coherence.clusteraddress=227.7.7.9 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=/ama/Oracle/Middleware/wlserver_10.3/server/lib/DemoTrust.jks -Dem.oracle.home=/ama/Oracle/Middleware/oracle_common -Djava.awt.headless=true -Dums.oracle.home=/ama/Oracle/Middleware/Oracle_SOA1 -Dweblogic.management.discover=false -Dweblogic.management.server=http://127.0.0.1:7001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/ama/Oracle/Middleware/patch_wls1035/profiles/default/sysext_manifest_classpath:/ama/Oracle/Middleware/patch_ocp360/profiles/default/sysext_manifest_classpath weblogic.Server
Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 5555; nested exception is:
java.net.BindException: Address already in use
We have to find out why the port 5555 is in listening mode after starting the Admin server.

General enquiry regarding starting the managed servers in weblogic

Hi,
Is there any sequence do we need to follow while bringing up the managed server? like in our set up we do have SOA,OSB & BAM managed servers.
So during maintainance activities, we have to start in sequence like SOA(managed server1),OSB(managed server 2) then BAM(managed server3).
In case if we change the above mentioned order the servers are not coming up.
So, we would like to know what might be cause & is there a sequence do we need to go thru to start the servers? if Yes, please give us the justification.
Thanks,
Sudhir.

In order to diagnostic the problem, you should post the error you're getting when trying to start the managed servers on a different order. Also, which mservers exactly are causing you problems?
Regards,
Franco.

Scripts for starting/stopping managed servers

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

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

Getting JMS Exception while starting the managed servers

Hi ,
I have Savvion BPM tool hosted on WebLogic server 10.3 version.Before the manage servers coming to Running state its throwing the below mention warning message.Can anybody help me to identify what could be the reason the managed server the below exceptions.
Thanks in advance...
<Jun 19, 2012 3:54:32 AM EDT> <Notice> <Cluster> <BEA-000142> <Trying to download cluster JNDI tree from server sbmejb2.>
<Jun 19, 2012 3:54:33 AM EDT> <Notice> <Cluster> <BEA-000164> <Synchronized cluster JNDI tree from server sbmejb2.>
<Jun 19, 2012 3:54:34 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Jun 19, 2012 3:54:34 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
*<Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLServiceMDB is unable to connect to the J*
MS destination: jms/BLAdminTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:34 AM EDT> <Notice> <Cluster> <BEA-000162> <Starting "async" replication service with remote cluster addres
s "sbmejb1,sbmejb2">
<Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLCacheSyncMDB is unable to connect to the
JMS destination: jms/BLCacheSyncTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLSessionMDB is unable to connect to the J
MS destination: jms/SBMTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:34 AM EDT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 10.177.16.126:16103 for pr
otocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Jun 19, 2012 3:54:34 AM EDT> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "sbmejb1" for domain "sb
m76" running in Production Mode>
<Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLBizStoreMDB is unable to connect to the
JMS destination: jms/SBMTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLCheckDueMDB is unable to connect to the
JMS destination: jms/SBMTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:41 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLEmailMDB is unable to connect to the JMS
destination: jms/SBMTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:41 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLResumeWSMDB is unable to connect to the
JMS destination: jms/SBMTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:41 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: MConsoleServiceMDB is unable to connect to
the JMS destination: jms/SBMTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:41 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: EPServiceMDB is unable to connect to the J
MS destination: jms/SBMTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:42 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: EventReaderBean is unable to connect to th
e JMS destination: jms/BPAdminTopic. The Error was:
weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
<Jun 19, 2012 3:54:42 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Jun 19, 2012 3:54:42 AM EDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>

Hi Rohit,
Thanks for your response..
Below is the BLAdminTopic configuration.Please let me know if you need any further info.
Topic:BLAdminTopic
Type:Distributed Topic
JNDI:jms/BLAdminTopic
Sub Deployment :N/A
Target:N/A
BLAdminTopic@jmsnode1BL Topic jms/BLAdminTopic@jmsnode1BL BLAdminTopic@jmsnode1BL jmsnode1BL
BLAdminTopic@jmsnode2BL Topic jms/BLAdminTopic@jmsnode2BL BLAdminTopic@jmsnode2BL jmsnode2BL
Regards,
Jyotiranjan

Empty initial replica exception while starting up managed servers

Hi,
I am doing what should be a fairly straight forward installtion/configuration of the weblogic portal 10.3.2.
I have installed the portal, created a new domain with one admin server and two managed servers in it. I also have a cluster on which I have both my managed servers and finally I have a machine on which I have all the 3 of my servers.
I am able to successfully startup the nodemanager and then the admin server. But when I try to start up the managed servers from the admin console, I get this exception -
####<Feb 11, 2011 12:39:37 PM IST> <Critical> <WebLogicServer> <XXXXXXXX> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1297408177691> <BEA-000386> <Server subsystem failed. Reason: weblogic.ldap.EmbeddedLDAPException: Empty initial replica
weblogic.ldap.EmbeddedLDAPException: Empty initial replica
     at weblogic.ldap.EmbeddedLDAP.getInitialReplicaFromAdminServer(EmbeddedLDAP.java:1301)
     at weblogic.ldap.EmbeddedLDAP.start(EmbeddedLDAP.java:221)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Any idea what could be the reason for this?
Regards,
Kunal
Edited by: kunal. on Feb 11, 2011 1:34 AM

Hi,
anybody got any solution to this?
Regards,
Kunal

Cannot start the managed servers because of this error.

Hi,
I installed weblogic 10.3.6 and created admin and managed servers and node manager. I am able to startup and shutdown the admin and managed servers using the node managers but when i try to start/shutdown the managed servers from the command prompt using startManagedWeblogic.cmd, i get this error:
<Apr 27, 2012 3:42:57 PM EDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
java.net.UnknownHostException: XXXXXX.XXXX.XXXX : 7152
at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:849)
at java.net.InetAddress.getAddressFromNameService(InetAddress.java:1202)
at java.net.InetAddress.getAllByName0(InetAddress.java:1153)
at java.net.InetAddress.getAllByName(InetAddress.java:1083)
at java.net.InetAddress.getAllByName(InetAddress.java:1019)
at java.net.InetAddress.getByName(InetAddress.java:969)
at weblogic.rjvm.JVMID.setLocalID(JVMID.java:238)
at weblogic.rjvm.RJVMService.setJVMID(RJVMService.java:48)
at weblogic.rjvm.RJVMService.start(RJVMService.java:30)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
>
The WebLogic Server encountered a critical failure
Reason: Assertion violated
Exception in thread "main" java.lang.NoClassDefFoundError: Could not initialize
class weblogic.protocol.ServerIdentityManager$Initializer
at weblogic.protocol.ServerIdentityManager.findServerIdentity(ServerIden
tityManager.java:64)
at weblogic.protocol.URLManager.findAdministrationURL(URLManager.java:173)
at weblogic.server.ServerLifeCycleRuntime.getLifeCycleOperationsRemote(S
erverLifeCycleRuntime.java:1078)
at weblogic.t3.srvr.ServerRuntime.sendStateToAdminServer(ServerRuntime.java:429)
at weblogic.t3.srvr.ServerRuntime.updateRunState(ServerRuntime.java:415)
at weblogic.t3.srvr.T3Srvr.setState(T3Srvr.java:206)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:482)
at weblogic.Server.main(Server.java:71)
Can anybody help me out with this. I am stuck here.
Thanks,
Robert
Edited by: Robert J on Apr 27, 2012 12:57 PM

try using flag -Djava.net.preferIPv4Stack=true within the startManagedWeblogic.cmd file to start the managed server with the command prompt.
Thanks,
Sandeep

Clustered enviroments -Starting/Stopping Managed servers, NodeManager & Admin server from single node

Hi,
We have 5 node Weblogic cluster. At the time of some mass activities like patching we have to stop all our managed, Admin Servers and node manager and it takes a lot of time to do this by logging in to all 5 managed servers and stopping all components. Though we have node manager configured so we can stop managed servers from console itself, but still have to login to each server to stop NodeManager and Oracle Http Servers.
Things become worse when wee have to shutdown almost 15-20 instances.
Is there a way (using wlst or shell script) that we can do all these tasks from by logging in to just one server?
Thanks,
Suraj

The simple code below would shutdown all the running Servers. Some of the APIs for ex MBeanHome are deprecated..still work though..if your concerned about that..I am working on the same using JMX API..if you want I could share that too. And also as described in the below link..you can Cluster stop and start using WLST commands. Managing the Server Life Cycle - 12c Release 1 (12.1.1)
<This code is from Oracle Weblogic documentation>
import java.util.Set;
import java.util.Iterator;
import java.rmi.RemoteException;
import javax.naming.Context;
import javax.management.ObjectName;
import java.io.*;
import java.net.*;
import weblogic.jndi.Environment;
import weblogic.management.MBeanHome;
import weblogic.management.WebLogicMBean;
import weblogic.management.configuration.ServerMBean;
import weblogic.management.runtime.ServerRuntimeMBean;
import weblogic.management.runtime.ServerStates;
import weblogic.management.WebLogicObjectName;
public class ServerStopper {
public static void stop() throws Exception {
    MBeanHome home = null;
    //url of the Admin server
    String url = "t3://localhost:7001";
    String username = "weblogic";
    String password = "welcome1";
    ServerRuntimeMBean serverRuntime = null;
    Set mbeanSet = null;
    Iterator mbeanIterator = null;
    try {
      // Set ContextClassloader to prevent assertions
      URL[] urls = { new File("/").toURL() };
      Thread.currentThread().setContextClassLoader(new
         URLClassLoader(urls));
      Environment env = new Environment();
      env.setProviderUrl(url);
      env.setSecurityPrincipal(username);
      env.setSecurityCredentials(password);
      Context ctx = env.getInitialContext();
      home = (MBeanHome)
           ctx.lookup("weblogic.management.adminhome");
      mbeanSet = home.getMBeansByType("ServerRuntime");
      mbeanIterator = mbeanSet.iterator();
      while(mbeanIterator.hasNext()) {
        serverRuntime = (ServerRuntimeMBean)mbeanIterator.next();
        if(serverRuntime.getState().equals(ServerStates.RUNNING)){
            serverRuntime.shutdown();
    } catch (Exception e) {
      e.printStackTrace();

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.

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.

Starting managed servers

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

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

Starting managed servers after rebooting

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

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

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.

Automatically starting of Managed Servers

Similar Messages

Maybe you are looking for