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
<b><a class="jive-link-external" href="http://www.togotutor.com">http://www.togotutor.com</a> (Learn Programming and Administration for Free)</b><</td>

Similar Messages

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)

Creation of Managed servers using WLST on two different machines

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

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

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

What is the use of Node Manager?

OBIEE Oracle Business Intelligence 11.1.1.5
I have started up the WebLogic server which delivers the WL Server Admin Console as well as the Fusion Middleware Control.
I have ignored NodeManager. It hasnt been started.
What is the use of NodeManager?
Oracle tells us:
Note: In order to start the Managed Server using the WebLogic Server Administration Console, the Node Manager must be running.
http://download.oracle.com/docs/cd/E21043_01/bi.1111/e10541/components.htm
But my Manged Server is running ok - I can check http://<host>:7001/console and its ok.
So why do I need to bother with NodeManager?
I only have WLS and OHS installed - no BI instance.
DA

Answers inline:
As I have installed weblogic server 10.3.5 on windows. while am starting it using cmd am getting two ips as
1**.*.... for weblogic server one is (channel default 4... .. and one is default 1) kindly explain.
- It doesn't generate any IP. If you have installed successfully, weblogic will run on your system and it's ip will remain same. You can access it using your systems'IP:portnumber
Also tell as I have to use cmd for starting servers how can i use unix commands for the same??
- You have installed on windows so unix command won't work for you. You can either start by going into services window in windows or start using command by going to path weblogichome\domains\domainname\bin. Execute startWebLogic.cmd
Also explain what is the use of node manager and weblogic scripting tool which are also installed in the system.
- Node manager is used for communication bentween two or more servers in a domain.
As am looking to install OIM 11g so kindly tell what are all the things I need to know about weblogic so that i can learn OIM easily.
- To install OIM, install weblogic, install oracle database. Use RCU utilities to create database and then install SOA, OIM and configure them. You can get all kinds of guides and steps for OIM 11g r2 here:
http://docs.oracle.com/cd/E27559_01/index.htm
regards,
GP

Java.io.IOException when to use WLST to connect admin server

Hello experts,
I am following this article to use wlst to connect to admin server from remote, but failed with below error.
Oracle WebLogic Server 12c: Configuring and Using Node Manager
>java weblogic.WLST
wls:/offline> connect('superadmin', 'agile9', 't3://myadminserver.company.com:7001')
Connecting to t3://myadminserver.company.com:7001 with userid superadmin ...
The CompatabilityMBeanServer is not initialized properly.
This might happen if the CompatabilityMBeanServer is
disabled via the JMXMBean.
To view the root cause exception use dumpStack()
WLST detected that the RuntimeMBeanServer is not enabled. This
might happen if the RuntimeMBeanServer is disabled via the JMXMBean.
Please ensure that this MBeanServer is enabled. Online WLST cannot
function without this MBeanServer.
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 22, in connect
File "<iostream>", line 648, in raiseWLSTException
WLSTException: Error occured while performing connect : "Cannot connect to WLST."
Use dumpStack() to view the full stacktrace
wls:/offline> dumpStack()
This Exception occurred at Tue Jul 22 20:45:53 PDT 2014.
java.io.IOException
java.io.IOException
wls:/offline>
I checked CompatabilityMBeanServer is already enabled in Admin Console
Does anybody has any idea how to resolve?
My Environment:
weblogic 12.1.1.0
OS: REL 6.0
Java: 1.7.0_21
Thanks
Jie

Hi,
Thanks for the reply. There was some problem with the input parameters to the automated activity. That error is resolved now.
I try to view the output of the automated activity, i.e, response of the web service call. I do an output mapping from the automated activity to a data object. But once I start the process and the automated activity executes, I could not see the output data in the context data in 'Operation Management --> Manage Processes'. The data object doesn't have any value.
The default trace doesn't have any error. I doubt if the web service is called at all!
Any suggestions?
Thank you.

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.

Can i set a node manager serve for 2 domain on one machin??

My question is simple.
I installed webcenter suite and soa suite in a machine using difference linux user and difference middleware home.
and I want to set a node manager server for two domains (soa_domain and webcenter_domain).
Is is possible?
When I tried to register domain list in node manager domain list using nmEnroll() of wlst, it failed.
please check following logs in 7101 is admin server port of soa domain and I ran node manager on webcenter domain.
Thanks in advance.
BmW.
~~~~~~~~~~~~~~~~~~
wls:/offline> connect()
Please enter your username :weblogic
Please enter your password :
Please enter your server URL [t3://localhost:7001] :t3://localhost:7101
Connecting to t3://localhost:7101 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'soa_domain'.
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
wls:/soa_domain/serverConfig> wls:/soa_domain/serverConfig> wls:/soa_domain/serverConfig> wls:/soa_domain/serverConfig> nmEnroll('/u02/app/soa11g/middleware/user_projects/domains/soa_domain', '/u02/app/wc11g/middleware/wlserver_10.3/common/nodemanager');
Enrolling this machine with the domain directory at /u02/app/soa11g/middleware/user_projects/domains/soa_domain ...
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 1447, in nmEnroll
File "<iostream>", line 1848, in raiseWLSTException
WLSTException: Error occured while performing nmEnroll : Problem enrolling the machine. : /u02/app/soa11g/middleware/user_projects/domains/soa_domain/config/nodemanager/nm_password.properties (Permission denied)
Use dumpStack() to view the full stacktrace
wls:/soa_domain/serverConfig> exit();

you might be victim of the "node manager starts WL Server with same Unix user id that was used to start Node Manager itself" problem
see here http://forums.oracle.com/forums/thread.jspa?threadID=2184607&tstart=89
I have been looking everywhere for a simple way to tell Node Manager to use a different Unix UID,
anybody any clue?
here http://download.oracle.com/docs/cd/E12840_01/wls/docs103/nodemgr/overview.html the Node Manager doc page

ALSB2.6/WLS9.2 Node Manager Monitoring Issue

Hi,
We have configured a java based node manager on weblogic 9.2 platform, using our customized scripts, for ALSB domain.
Node manager uses a customized server startup script to start the servers. This start-up script does some custom tasks and then starts the weblogic managed server with java options specified in this start-up script.
We are able to start / stop the managed servers from admin console but the node manager is not able to monitor the health of the managed servers. Node manager's log file also shows that server is in failed state whereas the managed servers log files show running state.
Can you please help how can we make the java based node manager (which uses a script to start the server) to monitor/check health of the managed server.
Also we've noticed a change in the way parameters are passed to server start-up script (which is called by the node manager ) between WLS8.1 and 9.2.
In 8.1 arguments were passed to the script in$1,$2,$3 and $4 ($4 pointing to the pid file of managed server). However these arguments are no longer available in 9.2.

I think when nodemanager.properties runs at the start of node manager, there is one line in it, i.e.
StartScriptName=startWeblogic.cmd
now there are few lines in the startWeblogic.cmd, those are:
@REM Set IP Mask.
if NOT "%NetMask%"=="" (
set IPMASK=%NetMask%
) else (
set IPMASK=
@REM Perform IP Migration if SERVER_IP is set by node manager.
if NOT "%SERVER_IP%"=="" (
call "%WL_HOME%\common\bin\wlsifconfig.cmd" -addif "%IFNAME%" "%SERVER_IP%" "%IPMASK%"
now I think that's why everytime the node manager tries to start the server the IP address is changed or masked to different one in startup.properties file, what I have mentioned in previous post...and what is indicated in log file...
any guru...plz

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

Passing arguments to Managed Server ServerStart when using Node Manager

Below is the procedure to pass arguments to Managed Server serverstart tab when using Node Manager to start and stop the Managed Server instance
For passing the JVM arguments we will have to use "-server" which is hotspot and then pass the arguments
for eg: "-server -Xms2048m -Xmx2048m -verbosegc"
For adding jar's to the classpath you will have to add weblogic.jar and weblogic_sp.jar from WL_HOME/server/lib directory as well along with the custom jar (In some cases we can ignore weblogic_sp.jar, just adding weblogic.jar will do).
for eg: "\home\user\debug.jar;\home\user\bea\wlserver_10.3\server\lib\weblogic.jar;\home\user\bea\wlserver_10.3\server\lib\weblogic_sp.jar;"
- - Tarun

Hi,
To me, if you don't wanna use the NodeManager, you won't be able to start your managed servers with WLST.
I guess the only ways are :
* through the console / WLST using the NodeManager
* using the startManagedWebLogic.[cmd/sh]
Regards

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

Starting Manage Server using node manager

Hi,
Hi,
I am using Weblogic server 11g and I have deployed Admin server in one of my unix machine(machine1) and i able to start my Admin server using node manager, and when i try to start my Managed server in another machine(machine2) using the node manager(that machine node manager) its throwing error;
Note: am able to start Managed server using Adminurl and able to connect to Managed server node manager successfully,
but not able to start Managed server using node manager
its giving exception as below;
error:- wls:/nm/webdomain> nmStart('ms1')
Starting server ms1 ...
Error Starting server ms1: weblogic.nodemanager.NMException: Exception while starting server 'ms1'
plz help me out in this
Thanks in advance

An example to start managed servers on different machine is provided here: http://middlewaremagic.com/weblogic/?p=6637
"By default, WebLogic is installed and configured with the DemoIdentity.jks keystore. This certificate and key are created by utils.CertGen with the default options of containing only the host name in the common name field (cn), and not the fully-qualified DNS name. As a result, attempts to establish SSL connections may fail in some situations due to a host name verification exception. When using the demo certificates in a multi-server domain, managed server instances will fail to boot if they cannot establish an SSL connection with the Admin Server and the a BAD_CERTIFICATE error is generated. This error occurs because the host name verifier, which is enabled by default in all WebLogic domains and which is used during the SSL handshake, compares the value of the cn field in the certificate with the fully-qualified DNS name of the SSL server that accepts the SSL connection. If these names do not match, the SSL connection is dropped."

Managed server CLASSPATH using Node Manager

Hi All,
I ve' created a clustered (WLS 10.3) environment with tow managed servers and Admin Server all in one machine and I use the Node Manager to start the managed Servers (by Admin Console or WLST), I want to set some jars to be loaded before WEBLOGIC_CLASSPATH actually (apache XMLbeans and SAXON jars) . I tried the setDomainEnv.cmd and placed my jars in the PRE_CLASSPATH variable but It is not working.Could u help me in this please?.
Thnx in advance

Here is the WLST online script to do what David Told, please make necessary changes to it.
connect(userName, passWord, URL)
clustHM = HashMap()
edit()
startEdit()
cd("/Servers/"+ManagedServer1+"/ServerStart/"+ManagedServer1)
print "setting attributes for mbean type ServerStart"
set("RootDirectory", domainDir)
set("Arguments","-jrockit -Xms256m -Xmx256m -Xss256k -da -Dplatform.home=/usr/local/bea10/weblogic10 -Dwls.home=/usr/local/bea10/weblogic10/server -Dweblogic.home=/usr/local/bea10/weblogic10/server -Dweblogic.management.discover=false -Dweblogic.management.server="+URL+" -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/usr/local/bea10/patch_wlw1001/profiles/default/sysext_manifest_classpath:/usr/local/bea10/patch_wls1001/profiles/default/sysext_manifest_classpath -Dweblogic.Stdout=/var/Domain_Logs/Public_Domain/serverlogs/stdout_ms1.log -Dweblogic.Stderr=/var/Domain_Logs/Public_Domain/serverlogs/stderr_ms1.log -Dlog4j.configuration=/usr/local/appstage/Publicdm/cluster_1/config/log4j/log4j.properties -Dconfig.location=classpath -Dconfig.filename=dev.config.xml -DweblogicName="+ManagedServer1+" -Djava.security.policy=/usr/local/bea10/weblogic10/server/lib/weblogic.policy")
set("SecurityPolicyFile", Security_Policy)
set("JavaHome", JAVA_HOME)
set("BeaHome", BEA_HOME)
set("ClassPath",CLASSPATH)
set("Username", userName)
set("Password", passWord)
Thanks
Togotutor
<b><a class="jive-link-external" href="http://www.togotutor.com">http://www.togotutor.com</a> (Learn Programming and Administration for Free)</b>

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

Enable Node Manager debug using WLST

Similar Messages

Maybe you are looking for