Best Practices from Oracle Development's A‑Team

Additional configuration to allow SOA managed server to be started from Node Manager

Mark Nelson


Before starting Node Manager for the first time, run the setNMProps.sh script, which is located in the ORACLE_COMMON_HOME/common/bin directory, to set the StartScriptEnabled property to 'true.

Main Article

I usually don’t start my managed servers from the Node Manager, as I like to have easy access to the console while I am developing and debugging.  But today, I needed to get it working as a prerequisite for another product.

When I simply started the Node Manager and attempted to start my SOA managed server using it, I got a bunch of ClassNotFoundExceptions and it sat there keeping one CPU busy for a long time, with nothing happening.

Turns out there is one additional piece of configuration that needs to be done to enable the managed servers to be started from the Node Manager, you need to run this script (once):


For more information, please visit Oracle Fusion Middleware Administrator's Guide

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.Captcha