Oracle SOA Suite managed server $CLASSPATH challenges

Once you installed Oracle SOA Suite en created your domain with or without scripts you will see that the installer(default) creates a separate managed server for the SOA suite, soa_server1 (default). You can start this server in two ways:

  1. Trough the admin console
  2. With the “startManagedWeblogic.sh” script

Most administrators and developers would like to start this beast with the admin console. So you have to configure and start the nodemanager. If  you start the server without setting up the correct classpath in the “server start” tab of the managed server. All the SOA suite deployments will be on status “failed“. Now you have two choices:

1. Fill the tab below and figure out the classpath

2. Alter the nodemanage.properties StartScriptEnabled flag to value “true”

DomainsFile=/opt/oracle/middleware/wlserver_10.3/common/nodemanager/nodemanager.domains
LogLimit=0
PropertiesVersion=10.3
DomainsDirRemoteSharingEnabled=false
javaHome=/opt/oracle/middleware/jrockit_160_24_D1.1.2-4
AuthenticationEnabled=true
NodeManagerHome=/opt/oracle/middleware/wlserver_10.3/common/nodemanager
JavaHome=/opt/oracle/middleware/jrockit_160_24_D1.1.2-4/jre
LogLevel=INFO
DomainsFileEnabled=true
StartScriptName=startWebLogic.sh
ListenAddress=
NativeVersionEnabled=true
ListenPort=5556
LogToStderr=true
SecureListener=true
LogCount=1
DomainRegistrationEnabled=false
StopScriptEnabled=false
QuitEnabled=false
LogAppend=true
StateCheckInterval=500
CrashRecoveryEnabled=false
###########
StartScriptEnabled=true
###########
LogFile=/opt/oracle/middleware/wlserver_10.3/common/nodemanager/nodemanager.log
LogFormatter=weblogic.nodemanager.server.LogFormatter
ListenBacklog=50

The result is a beautifull “Active” state of all our SOA deployments:

Advertisements