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 messaging. Before this role, Mark was an Architect in the Enterprise Cloud-Native Java Team, the Verrazzano Enterprise Container Platform project, worked on Wercker, WebLogic and was a senior member of the A-Team since 2010, and worked in Sales Consulting at Oracle since 2006 and various roles at IBM since 1994.
This entry was posted in Uncategorized and tagged , , . Bookmark the permalink.

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

  1. Pingback: End-to-end installation of WebCenter and BPM 11g (64-bit) | RedStack

Leave a comment