View Full Version : Starting webMethod as a Windows Service
I can start Webmethod with server.bat from bin. But I want to know the steps and changes that I need to make in order to start Integration Server as a Windows service. Any feedback on this will be highly appreciated.
vinodravi
05-08-2003, 12:45
While installing the webmethods server, you are given an option whether to install the server as a windows service or not. You can either chose this for installing as a windows service. The other option is to run the installSvc program under IntegrationServer/support/win32.
Good Luck!
Thanks Vinod for your valuable input. I have seen that option availbale in WebMethod 6.0 where you can give your choice to install it as service. I tried to re-install my 4.6 IS and carfully observe the sequence. There is no option anywhere where I can instruct to install it as a service.Can you confirm me if 4.6 has a option to install it as a service ??
vinodravi
05-08-2003, 13:14
Yes, 4.6 has an option available where it lets you install as a Windows NT Service.
You can specify the "type of set up you prefer" to be custom and click the check box that says "Yes, install as an NT service".
I am yet to upgrade to wM6.0. So not sure about that.
Thanks and good luck!
Thanks Ravi. It did work. I appreciate your time and effort.
Just a caution on running wM4.6 as windows service...
Did anyone face problems while running wM4.6 as windows service? We faced a problem related to record creation. The OS was windows 2000. While creating a record (fairly big with cross-reference) from schema, it was throwing Out of Memory exception. But it went through well when the wM server is run from a command prompt. I could recreate this issue by trying it again by running as a windows service as well as from command prompt. But there was no issues with creating smaller size records.
Second issue is, the wM server will not stop even if you stop the service by selecting the properties from right-click menu (from Services window) and pressing the stop button. Though the service window says the service is stopped. You should stop the server through the Administrator screen. I think, this issue is fixed in wM6.0.
The problem of starting IS 4.6/Windows 2000 as a windows service is right and is unavoidable, correct me if I am wrong. Our Production environemnt is Windows clustered(not WM clustered) and in a fail over situtation the fail over server has to resatart as it switches. This left with no option other than starting it as a windows service. How does it sounds to community ? Any feedback >>>>>>
Steve Grody (Unregistered Guest)
05-12-2003, 12:30
V601 as a service will stop correctly using the services panel.
Just a note on using MS for IS clustering: It is only useful for externally initiated connections, and will not help with inflight transactions failover. (We used to use BigIP) If you use reverse invoke, and the V601 broker communications, there are no connections normally made to your internal IS boxes. Does your license restrict you from IS clustering? We had that at one point also, but we were allowed to keep both servers running, as long as we weren't directing the failover server to handle any traffic, unless it saw the primary was down (scheduled ping service).