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
Leave a comment

2 Comments

  1. LaskaB

     /  November 24, 2011

    I have an issue similar to this one.
    I have one domain with SOA and OSB. When i run it normaly with startWebLogic – everything is fine and working.
    But I installed the domain as a windows service using the modified version of the installSvc.cmd. The windows service is turning everything on – wsl console, enterprise manager and osb… but soa-infra is marked as failed in enterprise manager :/

    I found that that the server is missing some jars in the classpath for bpm, bpel and so on…

    I think I have a StartScriptEnabled = true and i have restarted both the nodemanager and SOA+OSB domain… but still soa-infra is down ;/

    Got any advice?

    Reply
    • Hi Laska,

      You could check the soa-infra deployment and see where the target is pointing to. A second check you could perform is to re-target the deployment and see if any errors come up in the console or logging.
      I found the best way in setting-up the classpath manualy in the server-start of each managed server. This will make you more adaptable in future releases on you SOA-suite or OSB regarding library’s and memory settings.

      succes!

      regards,

      Thomas

      Reply

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: