Conver weblogic Admin server to a windows service

Question

I used the following scripts to conver weblogic Admin server to a windows service :
SETLOCAL
set DOMAIN_NAME=Sayesaman
set USERDOMAIN_HOME=C:\jdev11.1.1.6\user_projects\domains\Sayesaman
set SERVER_NAME=Sayesaman
set WL_HOME=C:\jdev11.1.1.6\wlserver_10.3
set WLS_USER=weblogic
set WLS_PW=weblogic110
set PRODUCTION_MODE=false
set MEM_ARGS=-Xms512m –Xmx512m
call "C:\jdev11.1.1.6\wlserver_10.3\server\bin\installSvc.cmd"
ENDLOCAL
after running these scripts the windows service created successfully and running properly .
but the state of all web application is failed and even I can't deploy any web application and I get the following error :
Class Not Found : oracle.dms.wls.DMSServletFilterr
Please help me to conver weblogic Admin server to a windows service correctly .
Edited by: 950222 on Aug 1, 2012 2:46 AM

Answer 1

Request you to share the entire stack of error.
Meanwhile,I would recommend that you deleet the existing service created and re-create the service by following the below steps:-
1. Create a text file
%MIDDLEWARE_HOME%\user_projects\domains\servers\AdminServer\security\boot.properties
Add the following lines
username=weblogic
password=
Important to Note:
a. If this step is not performed you will see the following generic error when the Admin Server is started in " background mode " via an MS Windows Service.
BEA-090403 Authentication for user weblogic denied
This error occurs because, by default, startup of Admin Server interactively prompts for the weblogic username and password. If the password is not supplied the error is thrown.
b. As soon as you start the Admin Server the username and password values in this file will be encrypted. Be sure to stop / start the Admin Server as soon as possible to ensure the credentials are not exposed for longer than necessary.
2. Create a command script called installAdmServer_Service.cmd which has lines like
SETLOCAL
set DOMAIN_NAME=ClassicDomain
set USERDOMAIN_HOME=C:\middleware\FMW11g\user_projects\domains\ClassicDomain
set SERVER_NAME=AdminServer
set PRODUCTION_MODE=true
cd %USERDOMAIN_HOME%
call %USERDOMAIN_HOME%\bin\setDomainEnv.cmd
call "C:\middleware\FMW11g\wlserver_10.3\server\bin\installSvc.cmd"
ENDLOCAL
3. For troubleshooting / debugging purposes it is helpful to redirect standard out and error to a text file. Although most information is captured in the AdminServer server log files, you will not see all standard out and error when the server is started via a MS Windows Service (unlike when you start an AdminServer from the command prompt using startWebLogic.cmd). To redirect standard out to a text file, backup and edit installSvc.cmd and change the line at the bottom of the file so it include the -log parameter e.g
"%WL_HOME%\server\bin\beasvc" -install
-svcname:"%DOMAIN_NAME%_%SERVER_NAME%"
-javahome:"%JAVA_HOME%" -execdir:"%USERDOMAIN_HOME%"
-extrapath:"%WL_HOME%\server\bin" -password:"%WLS_PW%"
-cmdline:%CMDLINE%
-log:"C:\Middleware\FMW11g\user_projects\domains\ClassicDomain\%SERVER_NAME%-stdout.txt"
4. Now run "installAdmServer_Service.cmd". The Service should be installed, it will have a name like ""beasvc %DOMAIN_NAME%_%SERVER_NAME%" e.g
beasvc ClassicDomain_AdminServer
The Service "Startup Type" will be 'Automatic'. Just like any other MS Windows Service you can change the 'Startup Type' to 'Manual'.
Start the Service. The Service will come back fairly quickly to say it is started. The actual time taken for AdminServer to start and reach a state of 'RUNNING' will be longer - perhaps two or three minutes. The state of the server can be monitored by reviewing the stdout txt file.
Notes:
An alternative to the boot.properties approach to specifying the Admin Server weblogic username / password is to add the following environment variables to your wrapper cmd script - installAdmServer_Service.cmd
set WLS_USER=weblogic
set WLS_PW=manager11g
The beasvc utility encrypts the login credentials and stores them in the Windows registry.
This is one of two possible methods for avoiding the username/password prompt when a server instance starts. The disadvantage to this method is that changing the username or password for the server instance requires you to delete the Windows service and set up a new one with the new username and password. Instead of this method, you can use a boot identity file. With a boot identity file, you can change the login credentials without needing to modify the Windows service.
Create a MS Windows Service for a Managed Server e.g WLS_FORMS
Important to Note:
1. The ADMIN_URL value should reference the AdminServer hostname and listen port.
2. The SERVER_NAME value is case sensitive. For example, if you are creating a MS Windows service for a different managed server such as 'wls_ods1' then the value needs to match the case of the server name otherwise the startup of the server via the MS Windows service will fail.
3. Be careful that there are no trailing spaces after each line in the command file - trailing spaces will cause the managed server to fail at startup. For example a trailing space in the ADMIN_URL value will result in the error
<Error> <EmbeddedLDAP> <BEA-171524> <Cannot determine the Listen address for the Admin server
3. Now run "installAdmServer_Service.cmd". The Service should be installed, it will have a name like ""beasvc %DOMAIN_NAME%_%SERVER_NAME%" e.g
beasvc ClassicDomain_AdmServer
The Service "Startup Type" will be 'Automatic'. Just like any other MS Windows Service you can change the 'Startup Type' to 'Manual'.
Start the Service. The Service will come back fairly quickly to say it is started. The actual time taken for the managed server to start and reach a state of 'RUNNING' will be longer - perhaps two or three minutes. The state of the server can be monitored by reviewing the stdout txt file.
Hope this helps!
-Sandeep