Reg: node and node manager

Hi to all
iam new to this forum, iam new administrator in weblogic plese help me.....
what is diference between node and node manager?
Thanks & Regardes
Ashok

Hi Ashok,
Node term usually we use for a Physical Box.
Nodemanager is a WebLogic Specific Java program which can be used to Manage a Remote Manage Server. Every Machine (Machine is a Logical name which represents a Physical box where Managed server is running) must have a NodeManager. AdminServer usually interacts with NodeManager to give start or stop Servers instructions to the Nodemanager, NodeManager program runs & resides in the same Managed Server Box...so it actually follows AdminServer's Instructions.
Nodemanager gets the Latest Configuration files from AdminServer while starting a Server in the physical box. or if AdminServer is not running at the time of starting a Managed Server then ... nodemanager uses the "msi-config.xml" file to provide to managed Servers while starting them.
Please refer to the below Post: http://weblogic-wonders.com/weblogic/2010/04/28/weblogic-clustering-in-remote-boxes/ to know what is the need of NodeManager and how to configure it.
To know in-depth about Nodemanager please refer to James Bayers....Post: http://blogs.oracle.com/jamesbayer/2010/01/weblogic_nodemanager_quick_sta.html
Thanks
Jay Sensharma

Similar Messages

Reg: Downgrading and data management

Hello all,
I've been experiencing some performance issues with my Mac Book Pro lately (I've been having trouble using more than 5-6 tabs in safari or chrome while using itunes and Microsoft Word); I've bought this notebook in mid 2010. It's the 13-inch 2.4 Core 2 Duo with 4GB 1067 MHz DD3 ram. Now I've been running OS X Lion for a long time and to be honest I haven't experienced any major improvement on the performance aspect of the operating system (functionality probably went up) but never thought of going back to SL bevause I never actually tried to backup my data.
I had to make a fresh installation after my hard drive failed me so I went again from SL to Lion trying to give it another go but keeping a backup this time of all data in time machine. So my questions are the following :
1) I was informed that Lion does not fit oldest models quite well and Snow Leoppard might be a better option for a Core 2 Duo rather than the newest OS. Any feedback on that?
2) I'm leaning towards downgrading. I know I can simply go back by finding my first backup on the time machine. If I do that do I also loose all data stored up to this point? Is there an option of copying from Lion backups to SL OS ?
3) Should i be experiencing this level of performance? I mean I'm I just asking too much from the notebook to handle (given I only have 4 GB or memory)?
4) would you suggest rolling back or waiting for the next major update in a couple of months ?
Thanks a lot.

Well initially I was thinking my hard drive was the issue (faulty) thus I've run the diagnostics apple requested and I did change the drive as they suggested. (quite funny process as my disk would oscillate between 20Gb of free space and 0Gb in t=3 seconds)
After that I simply stopped trying to sort anything out, looked into using alterntive software ( have been trying out chrome for the best part of the past 2 weeks ) and I eventually shut down the mac-book as soon as I'm done with any major job i need to finish. I simply couldn't afford any time on playing arround (other than running the normal disk utility repairs) as I'm in the middle of something rather too important to try on reinstalling everything.
I'm not a hard-core user. The MBP is left on sleep most time and it's used on word processing, safari itunes and in worst case scenarions fm2012. (definately not all in parallel). Is there a normal diagnostics procedure I could follow to dig something up ?

Incentive and Commission Management / Contract Management

Hi friends,
Could some one send me the documents reg- Incentive and Commission Management / Contract Management other then library or like for best practices where I can get info to configure above concepts .
my E mail id [email protected]
Thanks in advance and regards,
Padma

Hi friends! I´m in the same truble... how to implement ICM. If some one have any information to help, please send it to [email protected]
Thanks in advance.
Marina.

Multiple Node Manager Instances and servers sharing the same domain home.

Hi,
We have a 8 man server weblogic cluster spread over 4 machines. Each machine runs 2 man servers each.
Each of the machine is configured to run node manager.
We use shared storage accessible to all 8 servers and all 8 man servers have the same domain_home.
Lets call it W:/domain
Now the problem we are facing is that node manager running on 1 machine is trying to access/control a managed server on a different machine after a machine restart.
eg.
ManServer1 Home : W:/domain/servers/server1 ====> runs on Machine 1
ManServer2Home : W:/domain/servers/server2 ====> runs on Machine 2
Problem is node manager on machine 1 is trying to restart man server 2. The path W:/domain/servers/server2 is accessible to Machine 1.
After a restart, what I assume is happening is that the nodemanager is checking all servers folder under Domain_Home/Servers and trying to restart servers instead of restarting only those which it should start. The config file has the server and machine assignment done correctly. Is there a way to make this configuration towork. Or do we need to create different domain_home's for different man servers like
Domain_Home for MS1: W:/domain/MS1 ( Server Home would be : W:/domain/MS1/servers/MS1)
Domain_Home for MS2: W:/domain/MS2 ( Server Home would be : W:/domain/MS2/servers/MS2)
Regards,
Atheek
Edited by: atheek1 on 03-May-2010 00:27

Thanks - We have tried putting 2 dad entries in file, but not sure how you connect. You only specify a port number, so how does it connect that to a db???

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.

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

Oracle HTTP Server and Node Manager

Hi,
I installed Oracle HTTP Server with Node Manager. I set "CrashRecoveryEnabled=true" in the nodemanager.properties. It works fine when I reboot the machine, but when I kill the root process (kill -9), the new process can not be started as the previous process does not have enough time to die and still uses the ports. I tried to run "nmGenBootStartupProps" in wlst, or set the
RestartMax=2
RestartDelaySeconds=5
variables in "[domain_name]/servers/[server_name]/data/nodemanager/startup.properties" - no success.
Any ideas, how to set the number of retries and the delay between restarts?
Versions:
Oracle HTTP Server: version="12.1.3.0.0"
java version "1.7.0_79"
OHS log:
[2015-05-04T11:43:48.0653+02:00] [OHS] [NOTIFICATION:16] [OHS-9999] [mod_weblogic.c] [host_id: dev-oep-soalb-1] [host_addr: 192.168.0.226] [pid: 18651] [tid: 140166670751552] [user: app] [VirtualHost: main] WebLogic Server Plugin version 12.1.3 <WLSPLUGINS_12.1.3.0.0_LINUX.X64_140421.1459>
[2015-05-04T11:43:48.0854+02:00] [OHS] [NOTIFICATION:16] [OHS-9999] [core.c] [host_id: dev-oep-soalb-1] [host_addr: 192.168.0.226] [pid: 18651] [tid: 140166670751552] [user: app] [VirtualHost: main] Oracle-HTTP-Server-12c/12.1.3.0.0 (Unix) mod_ssl/12.1.3.0.0 OtherSSL/0.0.0 mod_plsql/11.1.1.0.0 configured -- resuming normal operations
[2015-05-04T11:48:53.9584+02:00] [OHS] [INCIDENT_ERROR:32] [OHS-9999] [worker.c] [host_id: dev-oep-soalb-1] [host_addr: 192.168.0.226] [pid: 18838] [tid: 140103489120064] [user: app] [VirtualHost: main] (98)Address already in use: make_sock: could not bind to address 192.168.0.226:80
[2015-05-04T11:48:53.9585+02:00] [OHS] [INCIDENT_ERROR:20] [OHS-9999] [worker.c] [host_id: dev-oep-soalb-1] [host_addr: 192.168.0.226] [pid: 18838] [tid: 140103489120064] [user: app] [VirtualHost: main] no listening sockets available, shutting down
[2015-05-04T11:48:53.9585+02:00] [OHS] [ERROR:32] [OHS-9999] [core.c] [host_id: dev-oep-soalb-1] [host_addr: 192.168.0.226] [pid: 18838] [tid: 140103489120064] [user: app] [VirtualHost: main] Unable to open logs
Node Manager log:
<May 4, 2015 11:37:50 AM CEST> <INFO> <Loading domains file: /opt/app/soalb_domain/nodemanager/nodemanager.domains>
<May 4, 2015 11:40:18 AM CEST> <INFO> <Loading identity key store: FileName=/opt/app/soalb_domain/security/DemoIdentity.jks, Type=jks, PassPhraseUsed=true>
<May 4, 2015 11:40:18 AM CEST> <INFO> <Loaded NodeManager configuration properties from '/opt/app/soalb_domain/nodemanager/nodemanager.properties'>
<May 4, 2015 11:40:18 AM CEST> <INFO> <Node manager v12.1.3 #1604337>
<May 4, 2015 11:40:18 AM CEST> <INFO> <soalb_domain> <soalb_server1> <Startup configuration properties loaded from "/opt/app/soalb_domain/servers/soalb_server1/data/nodemanager/startup.properties">
<May 4, 2015 11:40:19 AM CEST> <INFO> <Secure socket listener started on port 5556, host localhost/127.0.0.1>
<May 4, 2015 11:43:53 AM CEST> <INFO> <soalb_domain> <soalb_server1> <The server 'soalb_server1' is running now.>
<May 4, 2015 11:48:53 AM CEST> <INFO> <soalb_domain> <soalb_server1> <The server 'soalb_server1' with process id 18672 is no longer alive; waiting for the process to die.>
<May 4, 2015 11:48:53 AM CEST> <INFO> <soalb_domain> <soalb_server1> <Server failed so attempting to restart (restart count = 1)>
<May 4, 2015 11:48:54 AM CEST> <SEVERE> <soalb_domain> <soalb_server1> <Unexpected error while monitoring server>
java.io.IOException: Failed to start the server soalb_server1
Check log file /opt/app/soalb_domain/system_components/OHS/ohs_nm.log
Check log file /opt/app/soalb_domain/servers/soalb_server1/logs/soalb_server1.log
 at oracle.ohs.plugin.nodemanager.OhsProcessManagementPlugin$ProcessImpl.buildIoException(Unknown Source)
 at oracle.ohs.plugin.nodemanager.OhsProcessManagementPlugin$ProcessImpl.start(Unknown Source)
 at weblogic.nodemanager.server.DecoratedSystemComponentManager$DecoratedProcess.start(DecoratedSystemComponentManager.java:129)
 at weblogic.nodemanager.server.ServerMonitor.startProcess(ServerMonitor.java:441)
 at weblogic.nodemanager.server.ServerMonitor.runMonitor(ServerMonitor.java:406)
 at weblogic.nodemanager.server.ServerMonitor.run(ServerMonitor.java:295)
 at java.lang.Thread.run(Thread.java:744)
ohs_nm.log:
<2015-05-04 11:48:53> <INFO> <OHS-0> <The server 'soalb_server1' with process id 18672 is no longer alive; waiting for the process to die.>
<2015-05-04 11:48:53> <INFO> <OHS-0> <Server failed so attempting to restart (restart count = 1)>
<2015-05-04 11:48:53> <INFO> <OHS-4018> <Starting server soalb_server1>
<2015-05-04 11:48:53> <INFO> <OHS-0> <Running /opt/app/ohs12c/wlserver/../ohs/bin/httpd.sh httpd.worker -k start -f /opt/app/soalb_domain/config/fmwconfig/components/OHS/instances/soalb_server1/httpd.conf>
<2015-05-04 11:48:53> <INFO> <OHS-0> <[Mon May 04 11:48:53 2015] [warn] Errors will be logged into /opt/app/soalb_domain/servers/soalb_server1/logs/soalb_server1.log>
<2015-05-04 11:48:54> <INFO> <OHS-0> </opt/app/ohs12c/wlserver/../ohs/bin/httpd.sh httpd.worker -k start -f /opt/app/soalb_domain/config/fmwconfig/components/OHS/instances/soalb_server1/httpd.conf: exit status = 1>
<2015-05-04 11:48:54> <INFO> <OHS-4005> <Check the instance log file for more information: /opt/app/soalb_domain/servers/soalb_server1/logs/soalb_server1.log>
<2015-05-04 11:48:54> <SEVERE> <OHS-0> <Failed to start the server soalb_server1>
<2015-05-04 11:48:54> <SEVERE> <OHS-0> <Unexpected error while monitoring server>
Node Manager properties:
#Wed Apr 29 18:31:26 CEST 2015
#Node manager properties
#Wed Apr 29 17:18:21 CEST 2015
DomainsFile=/opt/app/soalb_domain/nodemanager/nodemanager.domains
LogLimit=0
PropertiesVersion=12.1.3
AuthenticationEnabled=true
NodeManagerHome=/opt/app/soalb_domain/nodemanager
JavaHome=/opt/app/jdk1.7.0_79
LogLevel=INFO
DomainsFileEnabled=true
StartScriptName=startWebLogic.sh
ListenAddress=localhost
NativeVersionEnabled=true
ListenPort=5556
LogToStderr=true
SecureListener=true
LogCount=1
StopScriptEnabled=false
QuitEnabled=false
LogAppend=true
StateCheckInterval=5000
CrashRecoveryEnabled=true
StartScriptEnabled=true
LogFile=/opt/app/soalb_domain/nodemanager/nodemanager.log
LogFormatter=weblogic.nodemanager.server.LogFormatter
ListenBacklog=50
Startup properties:
#SSLArguments=-Dweblogic.security.SSL.ignoreHostnameVerification\=false -Dweblogic.ReverseDNSAllowed\=false
RestartMax=2
RestartDelaySeconds=5
FileTimeSpan=24
RestartInterval=3600
FileTimeSpanFactor=3600000
RotatedFileCount=7
RotationType=bySize
#AdminURL=http\://192.168.0.224\:7001
NumberOfFilesLimited=true
AutoRestart=true
RotationTimeStart=00\:00
FileSizeKB=500
Regards,
András

To deploy your FMX you need AS 10.1.2 Forms installed, and then you can use AS control or Forms server configuration file.
For more information regarding FMX deployment, refer to http://download.oracle.com/docs/cd/B14099_19/web.1012/b14032/toc.htm
Regards,
Preet

Steps to setup and configure Node Manager on local and remote machine

Hello,
I am using WLS 10.3 on Windows.
I have two machines, One cluster and two managed servers (one on each machine) created under a domain. I have used configuration wizard to create the domain.
I have gone through documents on Node Manager and found what to configure. But I have not found when to configure. In other words I want to know what is the sequence of steps if I have to set Node Manager on my local machine (in which domain exists) and on remote machine.
Please let me know the sequence of steps I need to follow to set and configure the Node Manager on local and remote machine. I want to use Java Node Manager (not the Script node manager).
Thanks,
Sanjay

Hello,
Ok, let me tell you what I have done till now.
1) Installed WebLogic 10.3 on machine A (local machine, on which I have created domain and my Admin Server is running. Also Managed Server 1 is created on this machine).
2) Installed WebLogic 10.3 on machine B (remote machine, on which Managed Server 2 will be created).
3) On machine A I used the configuration wizard and create a domain. While creating the domain I did the following:
i) Created two managed servers.
ii) Created a cluster
iii) Assigned Servers to cluster.
iv) Created two machines.
v) Assigned servers to machines (Admin Server and MS_1 to machine A and MS_2 to machine B).
4) Sarted Admin Server.
5) On the Admin Console I made some configurations for the Node Manager on Machines -> Machine A -> Node Manager. Assigned the values:
i) Type (SSL)
ii) Listen Address (IP_Address of machine A)
iii) Listen Port (5556)
6) Similarly did for Machine B.
So till now phsically the managed server (MS_2) directory and configuration is not there on Machine B (its only configured on machine A because I created the domain on Machine A).
Now I want install/configure/setup NM on both the machines. Start my both the managed servers using Admin Console (which will use the node managers).
What are the sequence of steps I need to follow my task?
Any help and suggestions are welcome with warm regards.
Thanks,
Sanjay

Query regarding the Node manager configuration(WLS and OAM Managed server)

Query regarding the Node manager configuration(WLS and OAM Managed server):
1) In the nodemanager.properties I have added the ListenAddress:myMachineName and ListenPort: 5556
My setup : One physical Linux machine(myMachineName) has : WLS admin server, managed server(OAM 11G) and nodemanager.No clustered environment.
2) nodemanager.log has the following exception when I start the oam_server1 using EM(Enterprise Manager11g):
Mar 23 2012 1:39:55 AM> <SEVERE> <Fatal error in node manager server>
java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:336)
at java.net.ServerSocket.bind(ServerSocket.java:336)
at javax.net.ssl.impl.SSLServerSocketImpl.bind(Unknown Source)
at java.net.ServerSocket.<init>(ServerSocket.java:202)
at javax.net.ssl.SSLServerSocket.<init>(SSLServerSocket.java:125)
at javax.net.ssl.impl.SSLServerSocketImpl.<init>(Unknown Source)
at javax.net.ssl.impl.SSLServerSocketFactoryImpl.createServerSocket(Unknown Source)
Default port on which node manager listen for requests is localhost:5556.I have changed it to point to my machine. The port should be of WLS admin server or it should be the managed server port?
3) I have started the NodeManager using the startNodeManager.sh script.
4) The admin server port is 7001 and the oam managed server port is 14100.
Any inputs on what might be wrong in the setup will be helpful.Thanks !

By using netstat -anp|grep 5556 you can check which process on your machine is using the 5556 port.

Running OSB and SOA Suite as Windows Services? Node Manager

Hi,
Based on our current hardware configuration, we need to deploy our SOA Managed Server and Admin Server on the same machine as our OSB. Currently for development we just start the servers using the start scripts and keep a window open for them (3 of them: 1 - admin, 1 - soa_server1, and 1 - OSB.) We want to be able to run these as services and allow the admins to log out of the box. It seems like the Node Manager would allow us to do that but can we configure our Windows server to have a Node Manager running for the OSB and another for the SOA stuff on the same box? Do we even need to do that? Can we have a single Node Manager manage all three on port 5556?
I hope this makes sense. Thanks in advance for any quick responses.
Jeremy

Definitely you can (should) have a single node manager. You may refer below links -
http://blogs.oracle.com/jamesbayer/2010/01/weblogic_nodemanager_quick_sta.html
WLS 10.3.2 Adminserver startup failed when trying to run as Windows Service
Regards,
Anuj

Reg: Configuration of Managed Server through Node Manager

Hello:
I have a question Regarding the System properties (-Dname= value
pairs) that are passed when starting the Managed Servers.
In the managed Server script I am passing below two name value pairs
when starting the managed server
-Dorg.omg.CORBA.ORBClass=com.inprise.vbroker.orb.ORB
-Dorg.omg.CORBA.ORBSingletonClass=com.inprise.vbroker.orb.ORB
I am able to see these variables as <java System variabales > in the
weblogic.log corresponding to managed server.
Next is starting managed server through the node manager. Now in this
case the Node managed recives the configuration
of the managed server from the Administration server and he then
starts the managed server.
Now my question is though I have changed the startup scripts of
the Managed server to include the above two name value pairs. But I am
not able to see them in the congfiguration file in NodeManagerLogs
corresponding to the Managed Server. Also even in weblogic.log
corresponding to the Managed Server.
Can any one clarify this. Also How to define the new system variables
for the Managed Server so that I can see them in the configuration
file that Adminitration Server sends to the Node Manager.
Thanks,
Vijay

Thanks Anand.
"Anand Byrappagari" <[email protected]> wrote:
Vijay,
When you say managed server scripts do you mean startWeblogic.cmd ?
If you are using the node manger to start the managed servers then these
scripts are not executed. You should set the properties in the console.
Goto YourDomain>Servers>YourManagedServer in the console.
Select "Configuration" tab.
Then select "Remote Start" tab.
In the "Remote Start" tab enter the properties in the "Arguments" field.
-- Anand
"Vijay Kumar" <[email protected]> wrote in message
news:[email protected]..
Hello:
I have a question Regarding the System properties (-Dname= value
pairs) that are passed when starting the Managed Servers.
In the managed Server script I am passing below two name value pairs
when starting the managed server
-Dorg.omg.CORBA.ORBClass=com.inprise.vbroker.orb.ORB
-Dorg.omg.CORBA.ORBSingletonClass=com.inprise.vbroker.orb.ORB
I am able to see these variables as <java System variabales > in the
weblogic.log corresponding to managed server.
Next is starting managed server through the node manager. Now in this
case the Node managed recives the configuration
of the managed server from the Administration server and he then
starts the managed server.
Now my question is though I have changed the startup scripts of
the Managed server to include the above two name value pairs. But Iam
not able to see them in the congfiguration file in NodeManagerLogs
corresponding to the Managed Server. Also even in weblogic.log
corresponding to the Managed Server.
Can any one clarify this. Also How to define the new system variables
for the Managed Server so that I can see them in the configuration
file that Adminitration Server sends to the Node Manager.
Thanks,
Vijay

Domain wide administration port and node manager

I need a little help understanding how to properly configure the domain-wide
administration port in a clustered domain using node manager. After I enabled
the port in my domain, node manager will no longer start the managed servers
running on the same box as the domain's admin server. I don't have problems
starting remote managed servers. I see the problem but I don't know how to
fix it.
<Error> <Configuration Management> <BEA-150019> <The address provided to
get to the admin server (https://<host>@port) resolves to a managed server
local address (host@port) rather than a remote address as expected, or the
local managed server port might already be in use if you have setup domain
wide admin port, please check the configuration and correct the problem.>
The host I'm specifying is the host of my admin server, the port is the domain-wide
administration port. I don't get this error when starting my remote managed
servers, only the managed servers running on the same box as the admin server.
Grant

Cause might The managed server was given a URL to boot from that resolves to a managed server address. If the managed server is running on the same machine as the admin server, this can be caused by a failure to specify a unique admin port.
Inspect the address:port provided to the managed server from which to boot. This address should be changed to reference the admin server rather than resolving to a managed server. If the managed server is running on the same machine as the admin server, you must differentiate them by providing a unique port number.
Now we log a clear message that prints something like ,
The address provided to get to the admin server x.x.x.x resolves to a m
anaged server local address x.x.x.x:nnnn rather than a remote address as
expected, or the local managed server port might already be in use if you
have setup domain wide admin port, please check the configuration and correct
the problem.
Regards,
Prasanna Yalam

Start the node manager and rerun the command

Seeing the following in weblogic server log. When will I get this error? And how to retun node manager ?
The node manager at host ....and port 5555 seems to be down. Start the node manager and rerun the command.

You will get this message when the machine's NodeManager was not started.
Take a look at the following links to see how to install and start the Node Manager:
http://e-docs.bea.com/wls/docs81/adminguide/nodemgr.html#1150128
http://e-docs.bea.com/wls/docs81/adminguide/confignodemgr.html#1142955

Registering with the WebEx Data Center and the Cisco WebEx Node Management System

Dear guys, ...
Please help,
i want to implement to webex node ASR1000, i have read in "Configuring the Cisco Webex Node for ASR 100.pdf", there is prerequisites to implement it, that is "Registering with the WebEx Data Center and the Cisco WebEx Node Management System"
Can someone tell how to "Registering with the WebEx Data Center and the Cisco WebEx Node Management System"
Are there any step by step documentation to "Registering with the WebEx Data Center and the Cisco WebEx Node Management System"?
Thank you
BR

You should have received a PAK Key with your order. Go to Cisco licensing and enter the PAK Key as this will start the process. Once the PAK Key is validated a screen will be displayed to enter your request for ASR 100 integration. It normally takes a few days to a couple of weeks to get the information back from WebEx needed to configure your ASR.
If you did not get a PAK Key contact your WebEx rep to get the process started to integrate your ASR to your WebEx site.
Hope this helps
John

Health Monitoring and Restart Configuration with Node Manager

We have a WL 9.2.2 instance setup using Node Manager to control it. It contains a JMS server with a persistant store that is in an oracle database. If the Oracle database becomes unavailable, the Weblogic server throws a number of errors eventually leaving the Managed Server in a "FAILED" state. I configuring/activated the following "Configuration - Health Monitoring" options for the managed server to have it automatically recover from this situation:
Health Check Interval: 180
Auto Kill If Failed: Checked
Auto Restart: Checked
Max Restarts Within Interval: 2
Restart Delay Seconds: 0
However it is not automatically restarting, even though the server shows in a "FAILED" state.
1st question: Do I need to restart the server with the settings above to have it react to the FAILED state? I would think that 3 minutes after I configured the above it would begin a restart on the FAILED server, but that does not happen
I also note on the "Configuration - OverLoad" page, there is a setting for "Failure Action:" that can be set to "Ignore, take no action" or "Force Immediate Shutdown of this server" I did configure/activate this for "Force immediate Shutdown..." but again the currently FAILED server does not restart.
2nd question: Does this "Configuration - Overload- Failure Action" setting override or effect in any way the configuration of restart on the "Configuration - Health Monitoring" page?
3rd question: Same as 1st question but for these Overload settings: Do they require a full restart of the managed server to somehow take effect?


Have you set the field : CrashRecoveryEnabled=true in file : ..\bea\weblogic92\common\nodemanager\nodemanager.properties ?

Reg: node and node manager

Similar Messages

Maybe you are looking for