OpenEdge Management and OpenEdge Explorer: Configuration
OpenEdge Management and OpenEdge Explorer: Configuration
OpenEdge Management and OpenEdge Explorer: Configuration
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Configuring <strong>OpenEdge</strong> Web Services<br />
6–18<br />
Deploying a Web service to a Web Services Adapter<br />
instance<br />
You can deploy a Web service to the context of any available WSA instance using the Web<br />
Service Mapping (WSM) file generated using ProxyGen. For more information on generating<br />
a WSM file, see <strong>OpenEdge</strong> Development: Web Services.<br />
A deployed Web service receives its initial property values from the default.props file for the<br />
WSA instance. You can either change these default values before you deploy the Web service,<br />
or you can change the deployed Web service property values after you deploy the Web service.<br />
A Web service always deploys with a disabled status to prevent premature or unintended client<br />
access.<br />
To deploy a Web service:<br />
1. Click Resources in the management console menu bar. The main resource types appear in<br />
the list frame.<br />
2. Exp<strong>and</strong> the Web Services Adapter folder, <strong>and</strong> select the instance where you want to<br />
deploy the Web service. The Details page for that instance appears.<br />
3. Click Deploy.<br />
4. Type the path <strong>and</strong> name of the WSM file for the Web service that you want to deploy.<br />
5. Click Submit. Verify that the deployment information shown (<strong>and</strong> which is based on<br />
information in the WSM file) is correct. You can modify information in the following<br />
fields:<br />
• WSM Filename — The path <strong>and</strong> name of the WSM file.<br />
• Name — The name used to identify the Web service in the management console <strong>and</strong><br />
to name the Web service files that are deployed to the WSA instance.<br />
• Web Service Namespace — Any value you choose to uniquely qualify the names<br />
for operations <strong>and</strong> parameters used to define the Web service.<br />
• SOAP Action — A string that the client application is required to place in the<br />
SOAPAction HTTP header when accessing a Web service hosted by the WSA<br />
instance. The SOAPAction HTTP header is required for all HTTP messages that<br />
carry SOAP messages <strong>and</strong> is used by intervening security servers (such as firewalls)<br />
to determine if each HTTP message is allowed to pass through to its destination. The<br />
default is a blank string, but it can be any string required by the intervening security<br />
servers on the network.
Change language