...
| Info |
|---|
If you do not see the service deployed, wait for a while for the deployment engine of Axis2 to pick up the newly added |
Running the
...
service
From the terminal go to
<AS_HOME>\samples\CommodityQuotedirectory.Execute one of the following commands to run the client:
OS Command MS Windows run-client.bat [ -qos (rm|secure|securerm)] [ -e CommodityQuoteServiceURL] Unix/Linux run-client.sh [ -qos (rm|secure|securerm)] [ -e CommodityQuoteServiceURL]
Terms Used
- -e : is the Endpoint Reference (EPR) of the CommodityQuote service. You can find the endpoints in the AS Management Console.
To find endpoints:- On the Menu, under Services, click List.
The Deployed Services page will appear. - Click on the CommondityQuote service.
This will open up the service dashboard, where you can find its endpoints.
For this sample the default URLs for the standalone distribution and the embeddable version are as follows:
The default EPRs for http and https will be available in:
<AS_HOME>/samples/CommodityQuote/conf/default_epr.propertiesfile.
In addition to this, the SSL connection ( https://127.0.0.1:9443/services/CommodityQuote or https://127.0.0.1:9443/wso2appserver/services/CommodityQuote ) is needed for security scenarios. This is discussed later.
- -qos : This represents rm, secure or securerm options that eventually engage respective modules to the CommodityQuote service. These modules can be easily engaged from the AS Management Console. To run the sample with these QoS functions, you must engage the respective module for the CommodityQuote service in the WSO2 Application Server.
- rm - Sandesha2
- secure - Rampart/Rahas: WSO2 Application Server distribution is compliant with fifteen security scenarios. *# UsernameToken
Provides Authentication. Clients have Username Tokens
- On the Menu, under Services, click List.
...