What I've noticed is that on Windows the SOAP (Jetty) server runs as an instance of javaw.exe. When you create the server and start it using Web Services Developer, you can check the U2 SOAP Server log in the bottom pane to ensure it started. By default it will listen using port 8181. You change that when you create or edit the server.
You can see the port and status by running something like netstat -an from a DOS command window. When you close Web Services Developer, you should still see it listing on that port. If all is well, you can deploy the SOAP server to another Windows host by first exporting it, then deploying it. The instructions are in the Web Services Developer manual under chapter 7. After completing the deployment process, you can use the runsoapserver.bat and stopsoapserver.bat batch files to manage it. If you don't need to deploy it on a separate host, then simply use the batch files as required on the local Windows host. Regards, LeRoy On 2/23/11 4:28 PM, "Lettau, Jeff" <[email protected]> wrote: >I just noticed a potentially bad thing. The soap service will only run >if you run it manually after logging into the server. If I log off of >the server the soap service stops running. >I'm guessing the problem is that it is not actually running as a service, >but I don't see how to make it run as a service. > >Does anyone have any suggestions on how to enable a soap server to run on >startup? > >Jeffrey Lettau >ERP Systems Manager >polkaudio _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
