Hi there!
What version of Progress are you using? We've done lots of work on webservice generation and hosting here using v10.1A, and here's a quick run-down of the components involved:
1. Create and configure an appserver, connected to your host database.
2. You now need a webserver. We used a windows server 2008 PC with Tomcat as the webserver software.
3. Download Progress' Web Service Adapter (WSA) component, which is a java servlet. This is installed on the webserver machine, and configured to connect to the appserver in step (1).
4. Design a procedure with the required input/output parameters. We tend to use an input LONGCHAR and an output LONGCHAR which allows the calling routine to specify parameters via incoming XML rather than a set of static parameters. This avoids the constant regeneration of proxies due to changing signatures.
5. Use Progress' ProxyGen to generate a webservice proxy for your procedure defined in step (4). This will produce wsdl and wsm files which specify the webservice definition.
6. Upload the proxy files generated in step (5) to the WSA via Progress Explorer.
7. Enable the webservice using Progress Explorer.
8. Done! You can now call your webservice.
So, the basic approach is to give a traditional appserver a webserver "wrapper" using the WSA. The WSA receives the incoming webservice call and translates that out to an appserver connect and procedure call.
Obviously, there are options here (you could use IIS rather than Tomcat, etc). Also, some of these steps may need more detail if you're not familiar with the tech, so ask away!
Hope this helps,
Andy Smith.
