We have recently noticed something very interesting about Oracle’s services were absconding (means not to be seen) from Services listing, however the Oracle products are intact in all other means.
Earlier we shared a post explaining recreating the missing database services. Today we will try to explain how you can recreate missing Weblogic services. You MUST have Administrative access to the box, and en elevated command prompt (right click, start as administrator)
Assuming you have installed the Weblogic 10.3.6 server in the folder “D:\WebLogic\Middleware>” let us start
Start an elevated command prompt. Switch to “D:\WebLogic\Middleware>”
Let us do an old DOS trick to print all the .cmd files available with the repository
D:\WebLogic\Middleware>dir *.cmd /s > D:\weblogic_cmd_files.txt
Double click open the weblogic_cmd_files.txt file you just generated. The file must have following entries
Directory of D:\WebLogic\Middleware\modules\org.apache.ant_1.7.1\bin
04/04/2013 09:04 AM 2,857 ant.cmd
04/04/2013 09:04 AM 3,410 antenv.cmd
04/04/2013 09:04 AM 4,315 envset.cmd
04/04/2013 09:04 AM 1,817 runrc.cmd
4 File(s) 12,399 bytesDirectory of D:\WebLogic\Middleware\oracle_common\bin
02/09/2011 04:39 AM 2,002 copyBinary.cmd
02/09/2011 04:39 AM 1,995 copyConfig.cmd
11/23/2010 11:40 AM 2,071 extractMovePlan.cmd
02/09/2011 04:39 AM 3,237 pasteBinary.cmd
02/09/2011 04:39 AM 1,985 pasteConfig.cmd
5 File(s) 11,290 bytesDirectory of D:\WebLogic\Middleware\oracle_common\common\bin
01/20/2010 04:11 PM 663 config.cmd
04/02/2010 03:36 PM 596 getproperty.cmd
01/20/2010 04:11 PM 661 pack.cmd
01/20/2010 04:11 PM 783 setHomeDirs.cmd
11/08/2010 10:30 AM 2,143 setNMProps.cmd
12/13/2011 03:41 PM 5,066 setOjbstEnv.cmd
12/13/2011 03:41 PM 315 setWasConfigEnv.cmd
01/20/2010 04:11 PM 62 setWasHome.cmd
12/13/2011 03:41 PM 93 setWlstEnv.cmd
11/08/2010 10:30 AM 1,593 setWlstEnvExtns.cmd
12/13/2011 03:41 PM 5,490 setWsadminEnv.cmd
01/20/2010 04:11 PM 663 unpack.cmd
05/09/2011 04:51 PM 5,865 was_config.cmd
01/20/2010 04:11 PM 1,684 wlst.cmd
05/09/2011 04:51 PM 5,903 wsadmin.cmd
15 File(s) 31,580 bytesDirectory of D:\WebLogic\Middleware\oracle_common\rda
09/16/2011 05:40 PM 7,266 rda.cmd
1 File(s) 7,266 bytesDirectory of D:\WebLogic\Middleware\Oracle_FRHome1\BIN
10/12/2012 03:22 PM 2,408 shortenPaths.cmd
1 File(s) 2,408 bytesDirectory of D:\WebLogic\Middleware\Oracle_FRHome1\common\bin
01/20/2010 04:11 PM 663 config.cmd
01/20/2010 04:11 PM 661 pack.cmd
01/20/2010 04:11 PM 851 setHomeDirs.cmd
01/20/2010 04:11 PM 663 unpack.cmd
01/20/2010 04:11 PM 558 was_config.cmd
01/20/2010 04:11 PM 1,388 wlst.cmd
01/20/2010 04:11 PM 655 wsadmin.cmd
7 File(s) 5,439 bytesDirectory of D:\WebLogic\Middleware\Oracle_FRHome1\opmn\bin
05/01/2008 05:27 PM 228 opmnassociate.cmd
1 File(s) 228 bytesDirectory of D:\WebLogic\Middleware\Oracle_FRHome1\rda
09/16/2011 05:40 PM 7,266 rda.cmd
1 File(s) 7,266 bytesDirectory of D:\WebLogic\Middleware\user_projects\domains\appsdomain
04/05/2013 11:39 AM 381 InstallWindowsService_AdminServer.cmd
04/05/2013 11:50 AM 534 InstallWindowsService_WLS_FORMS.cmd
04/05/2013 12:43 PM 524 InstallWindowsService_WLS_REPORTS.cmd
04/04/2013 09:57 AM 319 startWebLogic.cmd
4 File(s) 1,758 bytesDirectory of D:\WebLogic\Middleware\user_projects\domains\appsdomain\bin
04/04/2013 09:57 AM 22,511 setDomainEnv.cmd
04/04/2013 09:57 AM 3,348 startManagedWebLogic.cmd
04/04/2013 09:57 AM 5,945 startWebLogic.cmd
04/04/2013 09:57 AM 2,525 stopManagedWebLogic.cmd
04/04/2013 09:57 AM 1,989 stopWebLogic.cmd
5 File(s) 36,318 bytesDirectory of D:\WebLogic\Middleware\user_projects\domains\appsdomain\bin\server_migration
04/04/2013 09:55 AM 6,521 wlsifconfig.cmd
1 File(s) 6,521 bytesDirectory of D:\WebLogic\Middleware\utils\bsu
04/04/2013 09:05 AM 330 bsu.cmd
1 File(s) 330 bytesDirectory of D:\WebLogic\Middleware\utils\clone
04/04/2013 09:04 AM 338 clone.cmd
04/04/2013 09:04 AM 311 restore.cmd
2 File(s) 649 bytesDirectory of D:\WebLogic\Middleware\utils\config\10.3
04/04/2013 09:05 AM 182 setHomeDirs.cmd
1 File(s) 182 bytesDirectory of D:\WebLogic\Middleware\utils\quickstart
04/04/2013 09:05 AM 735 quickstart.cmd
1 File(s) 735 bytesDirectory of D:\WebLogic\Middleware\utils\uninstall
04/04/2013 09:05 AM 811 uninstall.cmd
1 File(s) 811 bytesDirectory of D:\WebLogic\Middleware\wlserver_10.3\common\bin
04/04/2013 09:05 AM 9,132 commEnv.cmd
04/04/2013 09:05 AM 2,079 config.cmd
04/04/2013 09:05 AM 1,512 config_builder.cmd
04/04/2013 09:05 AM 1,666 pack.cmd
04/04/2013 09:05 AM 1,422 setPatchEnv.cmd
04/04/2013 09:05 AM 4,873 startDerby.cmd
04/04/2013 09:05 AM 3,909 startManagedWebLogic.cmd
04/04/2013 09:05 AM 1,851 stopDerby.cmd
04/04/2013 09:05 AM 1,780 unpack.cmd
04/04/2013 09:05 AM 3,288 upgrade.cmd
04/04/2013 09:04 AM 773 wlsifconfig.cmd
04/04/2013 09:05 AM 580 wlst.cmd
12 File(s) 32,865 bytesDirectory of D:\WebLogic\Middleware\wlserver_10.3\common\derby\bin
04/04/2013 09:05 AM 206 startNetworkServer.cmd
04/04/2013 09:05 AM 104 stopNetworkServer.cmd
2 File(s) 310 bytesDirectory of D:\WebLogic\Middleware\wlserver_10.3\common\quickstart
04/04/2013 09:05 AM 243 quickstart.cmd
1 File(s) 243 bytesDirectory of D:\WebLogic\Middleware\wlserver_10.3\server\bin
04/04/2013 09:05 AM 3,275 installNodeMgrSvc.cmd
04/04/2013 09:05 AM 6,309 installSvc – Backup.cmd
04/22/2013 09:16 PM 6,468 installSvc.cmd
04/05/2013 12:11 PM 6,269 installSvc_WLS_REPORTS.cmd
04/04/2013 09:05 AM 3,882 setWLSEnv.cmd
04/04/2013 09:05 AM 5,085 startNodeManager.cmd
04/04/2013 09:05 AM 701 uninstallNodeMgrSvc.cmd
04/04/2013 09:05 AM 992 uninstallSvc.cmd
8 File(s) 32,981 bytesDirectory of D:\WebLogic\Middleware\wlserver_10.3\uninstall
04/04/2013 09:05 AM 226 uninstall.cmd
1 File(s) 226 bytesTotal Files Listed:
75 File(s) 191,805 bytes
0 Dir(s) 97,695,387,648 bytes free
If you really know where exactly the .cmd files are, you may go ahead with the rest of the exercises. So the Node manager installer script is residing under D:\WebLogic\Middleware\wlserver_10.3\server\bin folder. Switch to the folder and execute the .cmd file
D:\WebLogic\Middleware>cd wlserver_10.3\server\bin
D:\WebLogic\Middleware\wlserver_10.3\server\bin>installNodeMgrSvc.cmd
Executing the .cmd file should create a new service and available to start within services console.
So once we created the Node Manager Service, we can start re-creating the optional service(s). We will limit ourselves to Weblogic Admin Console service, which is the maximum for our exercises. You may refer to our other post about installing & Configuring Weblogic 10.3.6 for details about creating individual services for Forms and Reports services.
Based on the application domain(the directory export will clearly give you an idea of the folders where components are installed) you have chosen during the installation, switch to the domain folder now
D:\WebLogic\Middleware\user_projects\domains\appsdomain
Here is where you will find the scripts you have modified earlier during an installation cycle (following our earlier posts)
D:\WebLogic\Middleware\user_projects\domains\appsdomain>InstallWindowsService_Ad
minServer.cmdD:\WebLogic\Middleware\user_projects\domains\appsdomain>echo off
…………
…………
D:\WebLogic\Middleware\user_projects\domains\appsdomain>ENDLOCAL
D:\WebLogic\Middleware\user_projects\domains\appsdomain>
Check your Windows Services console, and you must find a new service “beasvc appsdomain_AdminServer” listed
Bravo, let us check whether the newly created services are REALLY working once after they were freshly created.
Weblogic Admin Console
So we are done, let us start the Forms & Reports Servers now.
We hope this helps :)
for Windows7bugs
raj