You might have noticed that for Oracle SOA 12c Weblgic domain when you start Admin server, a derby server gets started automatically as separate java process which could be bit annoying and resource consuming if you are not intended to use derby server, which mostly the case for everyone.
You can follow below instruction to permanently stop derby
server process running -
This is how derby process can be identified as per below
snap-
Now, update setDomain.sh with aserver, mserver location,
also replicate the same change to other nodes if you have multiple copy of
domain files.
Before setDomainEnv.sh snap -
After setDomainEnv.sh snap -
Restart the Adminserver and derby server will not start not
again -
No comments:
Post a Comment