WLST without Node Manager

We are not using node manager to start|stop the servers. But we are monitoring the servers, getting the runtime values of the servers remotely using WLST. Can we also use WLST to automatically start and stop the managed servers without node manager, when the server status is failed. Also, can we do that remotely?
Please advise me where I can find the documentation on it.

No, you cannot start and stop servers via WLST without a Node Manager running.
-satya
BEA Blog: http://dev2dev.bea.com/blog/sghattu/

Similar Messages

Stop managed server without node manager and admin server

What are the commonly used ways to stop managed Weblogic server without node manager running and without administration server running?
(I have only one solution: on the managed server startup dump process ID to a file, and then when I want to stop it, send a signal to this process ID and kill JVM. But it seems not very clean way.)
(The managed server is started when both node manager and admin server are down, and I provide boot.properties of admin server to the managed server to start.)
UPDATED: And I don't want to start neither admin server, nor node manager even temporarily.
Edited by: user12163080 on Jun 24, 2010 4:40 AM

Hai,
I read the Oracle weblogic wlst script document without Admin server you cannot connect the managed server through the WLST script. see the below lines
"The start command starts Managed Servers or clusters in a domain using Node Manager.
To use the start command, WLST must be connected to a running Administration Server.
To start Managed Servers without requiring a running Administration Server, use the
nmStart command with WLST connected to Node Manager."
"You shut down a server to which WLST is connected by entering the shutdown command
without any arguments.
When connected to a Managed Server instance, you only use the shutdown command to shut
down the Managed Server instance to which WLST is connected; you cannot shut down another
server while connected to a Managed Server instance.
WLST uses Node Manager to shut down a Managed Server. When shutting down a Managed
Server, Node Manager must be running.
In the event of an error, the command returns"
They are two option if you are using adminserver then we can stop the any Managed server.
The option is if you are using the nodemanager without admin server we can stop the any Managed server.
The last final solution to kill the particular Managed server pid.
Regards,
S.vinoth babu

Installing weblogic without node manager

Hi
I installed weblogic 9.2 on windows 64 bit env. My machine is a VM.
I installed the admin server and managed server on different ports both on the same machine.
So i dont think there is a need for node manager in this context since there are no multiple machines involved.
I start the admin server and then try to start the managed server from the admin console . This is the error its giving me
The server dev_01 does not have a machine associated with it.
All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager. No action will be performed.
where dev_01 is the name of the managed server.
However, i am able to start the managed server thorugh script
startManagedWebLogic.cmd dev_01 http://localhost:7001
I would not prefer to have the node manager . so how would i start the managed server from the admin console?
Any help much appreciated

Hi,
Starting a ManagedServer from AdminConsole requires Nodemnager should be associated with the ManagedServer.
NodeManager is a Utility which is used to remotely start, stop Servers. If you try to start a ManagedServer from AdminConsole , in this case also it is called as *"Remote Start"* even if the ManagedServer is located in the Same Physical Box.

It means without associating the NodeManager to your ManagedServer you cannot start that ManagedServer from the AdminConsole. Because as soon as u try to start the ManagedServer from AdminConsole the AdminServer tries to pass the Start Instructions to the NodeManager Associated with That ManagedServer. If NiodeManager is associated with the ManagedServer then it performs all the prework before starting the Server and then issues the ManagedServer Start command.
 
Thanks
Jay SenSharma
http://weblogic-wonders.com/weblogic (WebLogic Wonders Are here)

Starting manged server without node manager

Hi All
I know that we can start managed servers from admin console but for that we have to have node manager on that machine running.
But I want to know,if I dont want to use node manager,can i start some how managed servers from admin console.That is if my node manager is not running,can i start the managed servers using admin console.
Please let me know if it is possible or not.
Thanks in advance.
DJ

Without the node manager running, you cannot start the managed servers from the admin console.
There are other options you can use to start the managed servers though, which i guess you might be aware of.
Just in case you don't, it's nicely documented by Atul @ http://onlineappsdba.com/index.php/2008/08/03/oracle-weblogic-server-startupshutdown/
Hope this helps.
Thanks,
Patrick

Unable to start SOA server through Node Manager

Hi All,
I am trying to install AIA 11.1.1.6.0 on the top of SOA Suite 11.1.1.6.0.
I was able to install successfully the weblogic server, rcu, soa and osb servers. Now, before installing the AIA, the document i am following it says, make sure to start the soa server through the node manager.
Now i start the admin server, then the node manager, to make sure i have checked that the node manager is up, i logged in to the weblogic console, went to Machines, and i can see that it is up and reachable.
Now using the WLST commands, first i connected to the node manager using command nmConnect(), then i am trying to start the soa server through node manager using the command start('soa_server1') command.
I am getting an error while trying to start soa server with nmStart() command, below is the error message...
"Error starting server soa_server1: weblogic.nodemanager.NMException: Exception while starting server 'soa_server1'"
I executed the dumpStack() command, and i am getting the output as "No stack trace available"
If i am able to start the soa server through the node manager, i can go ahead and install the AIA pack but this is not letting me go forward.
I also tried to start the soa server through the weblogic console., go to servers tab, select the soa_server1 and start, the soa server state is going to "FAILED_NOT_RESTARTABLE".
I followed some of the blogs like...
http://neeraj-soa-tips.blogspot.com/2010/06/starting-admin-and-managed-servers.html
http://www.javamonamour.org/2011/09/nmconnect-nmstart-nmkill.html
Experts, please give your advice.
Many Thanks,
N

Hi Narsing,
I'm assuming that you've followed the required Pre-config steps. If it is not working, I'd suggest to start the Admin and SOA server without node manager first. Then start your node manager and see if it is reachable from the WLS console. Then shut down your SOA server from command prompt and restart your SOA server from WLS console.
Verify the Listen Address of your Node Manager and start your node manager from command prompt by explicitly specifying the same address and port.
As WLS console internally uses node manager only to start your server, you would not need to use WLST scripts to do the same and only SOA server needs to be started using node manager.
Regards,
Neeraj Sehgal
Hi Neeraj,
I made sure that in the weblogic console, in the machines tab, local machine-->configuration--->Node Manager, I have given the correct Listen Address (Narsing-PC) and the listen port 5556.
I have made sure the property StartScriptEnabled= true.
I have started the admin server through startWebLogic.cmd command, now i start the node manager by going to the C:\Oracle\Middleware\wlserver_10.3\server\bin and running the command startNodeManager.cmd, then i go to the weblogic console--->servers--->control--->soa_server1--->start , it is going to FAILED_NOT_RESTARTABLE status.
If i see the log messages in the nodemanager.log, this is the below message...
<Jun 28, 2012 11:25:09 PM> <INFO> <soa_domain> <soa_server1> <Server output log file is 'C:\Oracle\Middleware\user_projects\domains\soa_domain\servers\soa_server1\logs\soa_server1.out'>
<Jun 28, 2012 11:25:11 PM> <INFO> <soa_domain> <soa_server1> <Server failed during startup so will not be restarted>
<Jun 28, 2012 11:25:11 PM> <WARNING> <Exception while starting server 'soa_server1'>
java.io.IOException: Server failed to start up. See server output log for more details.
 at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:196)
 at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
 at weblogic.nodemanager.server.Handler.handleStart(Handler.java:609)
 at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
 at weblogic.nodemanager.server.Handler.run(Handler.java:71)
 at java.lang.Thread.run(Thread.java:662)
The log message in the soa_server1.out file is as below...
Starting WLS with line:
C:\Oracle\MIDDLE~1\JDK160~1\bin\java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=soa_server1 -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=C:\Oracle\Middleware\user_projects\domains\soa_domain\servers\soa_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xverify:none -da:org.apache.xmlbeans... -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dcommon.components.home=C:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1 -Djrockit.optfile=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\servers\soa_server1 -Doracle.domain.config.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\servers\soa_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\ORACLE~1\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 -Doracle.security.jps.policy.migration.validate.principal=false -da:org.apache.xmlbeans... -Dbpm.enabled=true -Dsoa.archives.dir=C:\Oracle\Middleware\Oracle_SOA1\soa -Dsoa.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dsoa.instance.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1 -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=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks -Dem.oracle.home=C:\Oracle\Middleware\oracle_common -Djava.awt.headless=true -Dbam.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dums.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dweblogic.management.discover=false -Dweblogic.management.server=http://localhost:7001 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1036\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_oepe180\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_ocp371\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_adfr1111\profiles\default\sysext_manifest_classpath weblogic.Server
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
<Jun 28, 2012 11:25:11 PM> <FINEST> <NodeManager> <Waiting for the process to die: 4808>
<Jun 28, 2012 11:25:11 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Jun 28, 2012 11:25:11 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
Someone please help, if i am able to start the soa manged server, i can go ahead and install the AIA Foundation pack...
Many Thanks.

Not able to start SOA managed server first time with node manager by WLST

Hi all,
I have created a SOA11g domain. Then using WLST utility I have started the Node Manager.
Then from WLST prompt I have connected to the Node Manager & started the Admin Server successfully.
But when ever I am starting the SOA manager server using WLST it's throwing the following error in WLST page : -
Error Starting server soa_server1: weblogic.nodemanager.NMException: Exception while starting server 'soa_server1'
In server log file I am getting the following error : -
Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user denied
weblogic.security.SecurityInitializationException: Authentication for user denied
I am getting this problem only when I am trying to start the domain for the first time after domain creation using WLST/nodemanager.
If I start & stop the SOA managed server from EM console & then try to start it aging from WLST/NodeManager then it's work fine.
Can anyone please tell me what can be the issue?
Thanks in Advance!!!
Edited by: 008 on Dec 6, 2012 7:53 PM

Hi,
I am getting this problem only when I am trying to start the domain for the first time after domain creation using WLST/nodemanager.
If I start & stop the SOA managed server from EM console & then try to start it aging from WLST/NodeManager then it's work fine.When you a server for the first time by using console or startManagedWeblogic.cmd, a file boot.properties is created under %DOMAIN_HOME%\servers\soa_server2\data\nodemanager...
The WLST/Nodemanager approach doesn't create the file so it won't work for the first start... But it will work just fine from the second on...
I've never tried, but you can try and create the boot.properties manually in your script with the following content... Password should be encrypted after the first successful start...
username=type-the-username-here
password=type-the-password-here
Cheers,
Vlad

Enable Node Manager debug using WLST

Hi,
I would like to enable debug for node manager using WLST instead of using the Admin console - by selecting the check box for "Debug Enabled" property under Environment > Machine > Configuration > Node Manager in the Admin console.
I could locate the MBean name to 'NodeManagerMBean' and the property to 'DebugEnabled', but I'm not sure how to script it.
Can anybody please guide me?
Thanks in advance
Edited by: vikascv on Apr 29, 2009 9:23 AM

Here you go
Enable Node Manager debug using WLST
<a class="jive-link-external" href="http://www.togotutor.com">http://www.togotutor.com</a> (Learn Programming and Administration for Free at Togotutor)
def connection_to_Admin():
try:
connect(username, password, URL)
except wlst.WLSTException, ex:
print "Caught exception while connecting: %s" % ex
else:
print "------- Connected successfully! ---------"
connection_to_Admin() #Calling the connect Function
edit()
startEdit()
cd('/Machines/MS1/NodeManager/Machine_1')
cmo.setDebugEnabled(true)
activate()
Thanks
Togotutor
<a class="jive-link-external" href="http://www.togotutor.com">http://www.togotutor.com</a> (Learn Programming and Administration for Free)<</td>

WLST - Failing to run nmConnect() command / node manager becomes unreachabl

Hello guys,
I'm facing some issues to setup some configurations of one application that I've deployed on weblogic 10.3.3.0.
One of the needed steps in order to configure this applications is open the WLST in offline mode an run 2 commands:
*/bea/mytrack/wlserver_10.3/common/bin/wlst.sh*
Then I try to connect in the nodemanager:
* wls:/offline> nmConnect('admin30800','weblogic_password',port='30801',domainName='track30800')*
The following error returns:
Connecting to Node Manager ...
<Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 123, in nmConnect
File "<iostream>", line 646, in raiseWLSTException
WLSTException: Error occured while performing nmConnect : Cannot connect to Node Manager. : Access to domain 'track30800' for user 'admin30800' denied
I did some research and found this thread here: http://kr.forums.oracle.com/forums/thread.jspa?threadID=788163
that solves the initial problem, however after I performed the nmConnect and a storeUserConfig() command, I exit() from the WLST and restart the node manager with success, the node manager becomes unreachable.
I used the WL adm console and access -> appdomain -> environments -> machines -> monitoring -> node manager status to check the unreachable status.
Thanks in advance,
Davinod

Nice it worked!!
However when I try to start the servers controlled by this node manager I got this error:
-sh-3.2$ <Jul 14, 2011 8:43:42 AM> <WARNING> <Exception while starting server 'track30800-01'>
java.io.FileNotFoundException: /u01/track30800/user_projects/domains/track30800/servers/track30800-01/data/nodemanager/boot.properties (Permission denied)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
at weblogic.nodemanager.server.ServerManager.saveBootIdentity(ServerManager.java:495)
at weblogic.nodemanager.server.ServerManager.saveStartupConfig(ServerManager.java:438)
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:301)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:619)
Jul 14, 2011 8:43:42 AM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'track30800-01'
java.io.FileNotFoundException: /u01/track30800/user_projects/domains/track30800/servers/track30800-01/data/nodemanager/boot.properties (Permission denied)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
at weblogic.nodemanager.server.ServerManager.saveBootIdentity(ServerManager.java:495)
at weblogic.nodemanager.server.ServerManager.saveStartupConfig(ServerManager.java:438)
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:301)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:619)
<Jul 14, 2011 8:43:42 AM CDT> <Error> <NodeManager> <BEA-300048> <Unable to start the server track30800-01 : Exception while starting server 'track30800-01'>
Edited: Should I change the chmod for 777 for this file in order to check that all users have write permission?
-rw-r--r-- 1 root iluser 193 Jun 24 11:05 boot.properties
Did I miss a step?
Thanks,
Davinod
Edited by: davinod on Jul 14, 2011 6:58 AM

Start node manager using WLST

I am trying to start node manager using WLST with following command
wls:/offline> nmConnect('weblogic','weblogic123','localhost','5556','FirstDomain','C:\Oracle\Middleware\user_projects\domains\FirstDomain','plain')but getting below exception
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 123, in nmConnect
File "<iostream>", line 618, in raiseWLSTException
WLSTException: Error occured while performing nmConnect : Cannot connect to Node
Manager. : Connection refused: connect. Could not connect to NodeManager. Check
that it is running at localhost:5,556.
Use dumpStack() to view the full stacktrace
wls:/offline>
I am using weblogic 11g.
Can anybody let me know how to fix this issue.

You can use something like this:
beahome = '/home/oracle/soasuite';
pathseparator = '/';
adminusername = 'weblogic';
adminpassword = 'magic11g';
domainname = 'base_domain';
domainlocation = beahome + pathseparator + 'user_projects' + pathseparator + 'domains' + pathseparator + domainname;
nodemanagerhomelocation = beahome + pathseparator + 'wlserver_10.3' + pathseparator + 'common' + pathseparator + 'nodemanager';
print 'START NODE MANAGER';
startNodeManager(verbose='true', NodeManagerHome=nodemanagerhomelocation, ListenPort='5556', ListenAddress='localhost');
print 'CONNECT TO NODE MANAGER';
nmConnect(adminusername, adminpassword, 'localhost', '5556', domainname, domainlocation, 'ssl');
print 'START ADMIN SERVER';
nmStart('AdminServer');
nmServerStatus('AdminServer');More information can be found here: http://middlewaremagic.com/weblogic/?p=6040
in particular the "Starting the SOA environment" section

Configuring Node Manager for machine (wlst offline setup)

Good morning,
I'm trying to configure a machine's underlying node manager to have plain as NMType:
machine1 = create("Machine1", "Machine")
cd("Machine/Machine1/NodeManager/Machine1");
set("NMType", "plain");
WLST always complains as follows:
" No Machine!NodeManager object with name Machine1!Machine1"
I can't even navigate to the node manager: cd("Machine/Machine1/NodeManager")
leads to "No nested element NodeManager is found"
Any clue what I'm doing wrong? Thanks in advance!

Hi,
After you create a MachineMBean (machine1) , you must create a NodeManagerMBean (nm) :
machine1 = create('Machine1', 'Machine')
cd ('Machine/Machine1')
nm = create('Machine1', 'NodeManager')
After you set the value of ListenAddress and ListenPort, on NodeManagerMBean (nm)

Node Manager not starting UCM Server automatically

Hi All,
I have configured Node Manager to start and stop UCM 11g server.
But whenever, I am restarting the host OS - Windows server 2003 64 bit, it does not start the UCM managed server, automatically.
I am running two managed servers on the same host OS, the first UCM manages server, starts automatically on every restart.
The second managed UCM server, does not start. I need to then manually start the managed server. There are no errors logged, and the manual start of the managed server happens without any issues.
As a workaround, I tried starting the managed server from Windows scheduler, but it does not start the server as well. I wrote a script like -
Myscript.cmd
call E:\..\user_projects\domains\prod_domain\bin\setDomainEnv.cmd
java weblogic.WLST c:\start....\ServerStart.py
scheduled the script (myscript.cmd) to run from the Windows Scheduler.
Any pointers would be very helpful. Are there any known issues, if there are two managed servers, and one starts automatically, which affects the starting of the second managed server?
I see the following error in the log file -
<14/10/2011 6:35:22 PM EST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<14/10/2011 6:35:33 PM EST> <Info> <Management> <BEA-141223> <The server name PRD_UCM_Server1 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {PRDAdminServer,PRD_UCM_server1,PRD_IBR_server1}.>
<14/10/2011 6:35:33 PM EST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.management.ManagementException: [Management:141223]The server name PRD_UCM_Server1 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {PRDAdminServer,PRD_UCM_server1,PRD_IBR_server1}.
at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:149)
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:41)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:881)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:568)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
at weblogic.Server.main(Server.java:71)
Regards
Avi

Hi Avi,
Give a cross check to your ServerStart.py
As the error states The server name PRD_UCM_Server1 specified with -Dweblogic.Name does not exist
In your ServerStart.py you might have specified as follows
sh start MAnagedWeblogic.sh server=PRD_UCM_Server1
While these are the list of Server you have in your weblogic
PRDAdminServer,
PRD_UCM_server1,(You have Specified in your command PRD_UCM_Server1
PRD_IBR_server1
The Command should be as follows
sh start ManagedWeblogic.sh server=PRD_UCM_server1
This should help
Regards
Fabian

Node Manager not starting UCM Server

Hi All,
I have configured Node Manager to start and stop UCM 11g server.
But whenever, I am restarting the host OS - Windows server 2003 64 bit, it does not start the UCM managed server, automatically.
I am running two managed servers on the same host OS, the first UCM manages server, starts automatically on every restart.
The second managed UCM server, does not start. I need to then manually start the managed server. There are no errors logged, and the manual start of the managed server happens without any issues.
As a workaround, I tried starting the managed server from Windows scheduler, but it does not start the server as well. I wrote a script like -
Myscript.cmd
call E:\..\user_projects\domains\prod_domain\bin\setDomainEnv.cmd
java weblogic.WLST c:\start....\ServerStart.py
scheduled the script (myscript.cmd) to run from the Windows Scheduler.
Any pointers would be very helpful. Are there any known issues, if there are two managed servers, and one starts automatically, which affects the starting of the second managed server?
Regards
Avi

Hi All,
Add to my initial post , the error which is getting logged is -
<14/10/2011 6:35:22 PM EST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<14/10/2011 6:35:33 PM EST> <Info> <Management> <BEA-141223> <The server name PRD_UCM_Server1 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {PRDAdminServer,PRD_UCM_server1,PRD_IBR_server1}.>
<14/10/2011 6:35:33 PM EST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.management.ManagementException: [Management:141223]The server name PRD_UCM_Server1 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {PRDAdminServer,PRD_UCM_server1,PRD_IBR_server1}.
 at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:149)
 at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:41)
 at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
 at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
 at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:881)
 at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:568)
 at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
 at weblogic.Server.main(Server.java:71)
Regards,
Avi

Problem starting Admin Server using Node Manager

I have configured the Node Manager to run as a windows service. I want it to start the Admin Server when it is started. This is not working. The Node Manager starts without problem but does not appear to even attempt to start the Admin Server. No error message is written to the nodemanager.log. I have configured the following properties as described in the documentation:
StartScriptEnabled=true
StartScriptName=startWebLogic.cmd
Starting the Admin Server using wlst works. As does starting and stopping a Managed server using the Admin console. This leads me to conclude that the Node Manager configuration is ok.
WLS version is 9.2.
All suggestions as to what could be the issue here would be greatly appreciated.
Cheers!

Ok, I just wasted a whole day before I found the tricks.
First, you don't need to do that StartScriptEnabled stuff, unless you have important things to add there.
Ok, and now what I found:
- You must make sure you have installed the NodeManager as a service
- Next, make sure the admin server is assigned to the right machine. Since you can do the WLST trick, that should be fine. If not, tough luck, because the docs say you cannot re-assign an admin server.
- In nodemanager.properties (...\weblogic92\common\nodemanager) make sure CrashRecoveryEnabled is set to true
- In nodemanager.domains (same dir) make sure your domain is mentioned with its path
- For each of the servers to be auto-started, make sure that a startup.properties (in <your-domain-dir> \servers\<server-name> \data\nodemanager) contains Arguments=-Xnohup (for JRockit, for Sun JDK its -Xrs)
Make sure they are started through the nodemanager, et voila, they'll be restarted after a reboot.
Why this works? At reboot, the OS ask all processes to die, nicely. Those that don't, get killed forcibly. Without the -Xnohup/rs, the WebLogic servers respond to the nice request, and the nodemanager immediately tries to restart them. Unfortunately, the OS refuses to do that, and the server process is marked as failed, and won't be restarted after reboot. With the option given, the servers ignore mr nice guy, and get killed after the nodemanager has disappeared.
What can go wrong? A lot. I was playing with the nodemanager username and password, and that took some time to clean up. I probably have to redo the entire setup just to make sure I have a repeatable experience now...
Cheers,
Bert

Accessing an EJB 3.0 Enterprise Bean and Node Manager

Hi to all
I have got a problem in using Local(Remote) EJB Interface in Weblogic. I use Node Manager.
I have two servers:
1. AdminServer (working on port 7001)
2. Server1 (working on port 7003 under node manager control)
I have one EAR application file. This file contains jars with ejb 3.0. One jar called jarnumber1.jar is deployed on AdminServer. Second jar called jarnumber2.jar id deployed on Server1.
jarnumber1.jar constains EJBBean1 class.
jarnumber2.jar constains EJBBean2 class.
I want call EJBBean2 from EJBBean1 but I can't. I got exception 'NamingException'.
Example source code:
@Stateless(mappedName = "EJBBean1")
public class EJBBean1implements EJBBean1Remote {
@EJB private EJBBean2Remote eJBBean2Remote ; //injection doesn't work
I also tried method described here: http://middlewaremagic.com/weblogic/?p=5665 but it doesn't work.
AminServer has own JNDI Tree and Server1 has own JNDI Tree. It's seems to be that EJBBean1 can't see EJBBean2 from second JDNI tree.
Pleas help me.
With Regards,
ZK

Please try the following code:
HelloEJBBean.java:
@Stateless(name="Hello")
@Remote(value={Hello.class})
public class HelloEJBBean implements Hello { ... }
hello.jsp:
Context ctx = new InitialContext();
Hello h = (Hello)ctx.lookup("ejb/Hello");
web.xml:
<ejb-ref>
<ejb-ref-name>ejb/Hello</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<remote>fi.kronodoc.test.model.Hello</remote>
</ejb-ref>
i think you should also define jndi mappings for the references in orion-ejb-jar.xml and orion-web.xml but for some reason it seems to be working also without these.

After I do Node Manager nmConnect(...) I can no longer start a managed svr

I am running 10.3.2 on both windown and redhat
I have a domain with AdminServer and one managed server.
I can start AdminServer from the shell with startWebLogic.cmd
I can log into the web based 'console'
I can go to Environment -> Servers and start/shutdown the managed server.
If I use WLST and...
connect('user', 'pass', 't3://localhost:7001')
nmEnroll('fullPathToDomainDir')
I am still OK, I can still use the console to start and stop the managed server and I can so WLST start('managedSever')
I stop running the AdminServer from the shell - it is no longer running.
Now, I want to start the AdminServer with Node Manager, so (with WLST)...
nmConnect('user','pass','localhost','5556','domainName)
I get the error...
'Cannot connect to Node Manager: Access to domain 'domainname' for user 'user' denied
As suggested elsewhere, I go and edit nm_password.properties and change the hashed user/pass to
username=user
password=pass
I go back to WLST, now nmConnect works!!!
I can then do..
nmStart('AdminServer')
The AdminServer start, I go to the web console, and I try to start the managed server, I get...
'For server managedServer, the Node Manager associated with machine machineName is not reachable'
So it looks like the re-hashed password from nmConnect(...), while it works for WLST, it no longer works for the console.
Bottom line, I can get either get the console to start the managed server (if I do WLST connect(...) + nmEnroll(...)) or I can get WLST to start the servers (if I reset nm_password.properties and do nmConnect), but I can not get WLST to start the AdminServer and have the AdminSever console start the managed server.
I know for a fact that others have run into this, but in the threads I found, the thread stops before a soluton is posted.
Anyone know about this issue?
Regards

There are a couple of things you need to keep in mind:
-- There is one and only one valid username / passwrod for connecting to the node manager.
-- When you use nmEnroll, the username / password placed in the nm_password.properties file is taken from the admin server, hashed an placed in the nm_password file.
-- When you edit the nm_password.properties, and place the line "enter in username=user / password='pass',", in clear text, you have over ridden the U/P \thje admin server knows.
That is why you have a situation, oen of the two works but never both at the same time.
What you need to do is:
-- Log in to the WL Console.
-- in the Domain Tree, click at teh root level, which is the domain name.
-- Under the security tab, under advanced there is a node manager username / password.
-- Click on "Lock and edit", and change those to match what you are using through WLST.
-- Activate changes.
-- Just to make sure all is well, use nmEnroll to re enroll the node manager again , this way the nm_password.properties file will be set up correctly.
Now, both the WL Console should be able to talk to the node manager as well as nmConnect('user','pass','localhost','5556','domainName) would succeed.
Also, if you want to use node manager to start /servers, make sure you edit the file ( $WL_HOME/common/nodemanager/nodemanager.properties) and change the line
StartScriptEnabled=false
to
StartScriptEnabled=true
This will ensure all the proper class paths and properties etc needed are set up when using the node manager.
You would need to bounce the node manager for this change t take effect
Hope this helps.

WLST without Node Manager

Similar Messages

Maybe you are looking for