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

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):

$SOA_HOME/oracle_common/common/bin/setNMProps.sh

About Mark Nelson

Mark Nelson is a Developer Evangelist at Oracle, focusing on microservices and AI. Mark has served as a Section Leader in Stanford's Code in Place program that has introduced tens of thousands of people to the joy of programming, he is a published author, a reviewer and contributor, a content creator and a lifelong learner. He enjoys traveling, meeting people and learning about foods and cultures of the world. Mark has worked at Oracle since 2006 and before that at IBM since 1994.

View all posts by Mark Nelson →