Configure a WebLogic Server Background Serviceserver running in the background which is very much required in Production and Test Environments where your operating platform is Windows NT based. Whenever the Windows server is rebooted the WebLogic Admin server or Managed servers running on it are going to started automatically, when they are configured with windows ‘services’.
- Use WebLogic existing Domain or Create a Domain for testing
- Create a installation Script per WebLogic server such as AdminServer or Managed Server
- Create a .cmd let us workout per AdminServer with the following
Open notepad or any editor to write the following Windows batch Script
echo off SETLOCAL set DOMAIN_NAME=demoDomain set USERDOMAIN_HOME=F:\irfan\demoDomain set SERVER_NAME=AdminServer call "F:\Oracle\wlserver\server\bin\installSvc.cmd" ENDLOCAL
Write the above code and SAVE it with ‘AdminServerSrv.cmd’ in your domain\bin
- open a new CMD prompt with Admin permissions.
- Window button + R will give you program that to run “Services.msc”
Upto the WebLogic 10.3.6 it was beasvc binary now it is changed in the WebLogic 12c it is wlsvc file. This will be invoked by installSvc.cmd file. Once the WebLogic server is started in the Operating system services then it will be give access through the Admin Console that you usually use http://adminhost:adminport/console.
Uninstalling the WebLogic server from windows ServiceStep 1: Open one more edit window or notepad write the following script commands using “unintallSvc.cmd”
echo off SETLOCAL set DOMAIN_NAME=demoDomain set USERDOMAIN_HOME=F:\irfan\demoDomain set SERVER_NAME=AdminServer call "F:\Oracle\wlserver\server\bin\uninstallSvc.cmd" ENDLOCAL