When running a Weblogic server and its managed servers I have heard at multiple projects that there is a need of automatic startup of these server processes. There is not default an options to create a windows service when installing Weblogic and for example SOA Suite. The one option that is available is to create a windows service for the node manager.
This small guide will show how to create a windows service for the Weblogic AdminServer, the node manager and the Managed server and setting up the evironment settings. For creating the Windows services a tool called NSSM (the Non-Sucking Service Manager) is used.
Weblogic as a windows service
Scroll to: Change DomainEnv script | AdminServer start script | Windows Service | Node manager | Managed Servers | Delayed Start.
Change SOADomainEnv script
First we are going to change the setSOADomain.env
script. The reason for this is we want to be in control about the
memory settings of the JVM just like we can with the node manager. The
node manager uses the settings which can be configured via the Weblogic
console, but when starting a managed server with the OS start script it
won’t pick those up. We want to be in control by setting the environment
variable USER_MEM_ARGS in advance. Read the full article here.
WebLogic Partner Community
For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.
