cnc__guy
Well Known Member
Friends,
I am attempting to create my JAS Services as Windows Services using WASSERVICE and I am having a "dilly" (yes, that is a technical term) of a time.
I am using the following command from my \websphere\appserver\bin directory and having no luck:
wasservice -add AS_JS_81 -profilePath "d:\websphere\appserver\profiles\appsrv01" -serverName AS_JS_81
or
wasservice -add AS_JS_81 -profilePath "d:\websphere\appserver\profiles" -serverName AS_JS_81
or
wasservice -add AS_JS_81 -profilePath "d:\websphere\appserver\profiles" -serverName jdeweb01
none of the above allow my windows service to stay running. When I start the service after entering the above commands the service will die and no logs get created in the logs directory. I have done this before but I am missing something now.
All services load and run successfully using the batch files but this creates issues when the user that logs in and runs the batch files logs out.
Thanks,
James
I am attempting to create my JAS Services as Windows Services using WASSERVICE and I am having a "dilly" (yes, that is a technical term) of a time.
I am using the following command from my \websphere\appserver\bin directory and having no luck:
wasservice -add AS_JS_81 -profilePath "d:\websphere\appserver\profiles\appsrv01" -serverName AS_JS_81
or
wasservice -add AS_JS_81 -profilePath "d:\websphere\appserver\profiles" -serverName AS_JS_81
or
wasservice -add AS_JS_81 -profilePath "d:\websphere\appserver\profiles" -serverName jdeweb01
none of the above allow my windows service to stay running. When I start the service after entering the above commands the service will die and no logs get created in the logs directory. I have done this before but I am missing something now.
All services load and run successfully using the batch files but this creates issues when the user that logs in and runs the batch files logs out.
Thanks,
James