Difference between revisions of "Wizard Proxy Web Service"
F.albanese (talk | contribs) (→Wizard Proxy Web Service) |
|||
| Line 8: | Line 8: | ||
In the second page you can select the operations that are described in WSDL file. | In the second page you can select the operations that are described in WSDL file. | ||
| − | In the third page you can select the following parameters of the | + | In the third page you can select the following parameters of the Web Service call: |
*[[System]] | *[[System]] | ||
*[[Participant]] | *[[Participant]] | ||
*[[Channel]] | *[[Channel]] | ||
*[[Data provider]], used to adapt the workflow input to the Web service input | *[[Data provider]], used to adapt the workflow input to the Web service input | ||
| − | *Return type, used to choose what must be | + | *Return type, used to choose what must be passed as output to the workflow: |
**context : the [http://axis.apache.org/axis2/java/core/api/org/apache/axis2/context/MessageContext.html MessageContext] | **context : the [http://axis.apache.org/axis2/java/core/api/org/apache/axis2/context/MessageContext.html MessageContext] | ||
**envelope : the envelope as XML serialized string | **envelope : the envelope as XML serialized string | ||
| Line 31: | Line 31: | ||
In the last page you can set the following parameters of the publishing Web Service: | In the last page you can set the following parameters of the publishing Web Service: | ||
| − | *Input type, used to choose what must be | + | *Input type, used to choose what must be passed as input to the workflow: |
**context : the [http://axis.apache.org/axis2/java/core/api/org/apache/axis2/context/MessageContext.html MessageContext] | **context : the [http://axis.apache.org/axis2/java/core/api/org/apache/axis2/context/MessageContext.html MessageContext] | ||
**envelope : the envelope as XML serialized string | **envelope : the envelope as XML serialized string | ||
| Line 44: | Line 44: | ||
*Choose if Web Service should be forced to HTTPS | *Choose if Web Service should be forced to HTTPS | ||
*Choose if target namespace to be used is the one in the xsd | *Choose if target namespace to be used is the one in the xsd | ||
| − | |||
== Example == | == Example == | ||
Revision as of 17:49, 7 February 2012
Wizard Proxy Web Service
"Wizard Proxy Web Service" is a wizard that, from a service's WSDL, publishes the same service on GreenVulcano® ESB, therefore it is only a Proxy. In practice, it creates the Web Service call to the service indicated in WSDL file, defines a GreenVulcano® ESB service that makes the Web Service call and exposes this GreenVulcano® ESB service as Web Service.
In the first page you can choose the WSDL file.
In the second page you can select the operations that are described in WSDL file.
In the third page you can select the following parameters of the Web Service call:
- System
- Participant
- Channel
- Data provider, used to adapt the workflow input to the Web service input
- Return type, used to choose what must be passed as output to the workflow:
- context : the MessageContext
- envelope : the envelope as XML serialized string
- body : the body as XML serialized string
- body-element : the first child of body as XML serialized string
- header : the header as XML serialized string
- envelope-om : the envelope as SOAPEnvelope object
- body-om : the body as SOAPBody object
- body-element-om : the first child of body as OMElement object
- header-om : the header as SOAPHeader object
In the fourth page you can choose your preferred transport protocol between:
- SOAP
- SOAP12
- REST Transport
- JMS Transport
In the last page you can set the following parameters of the publishing Web Service:
- Input type, used to choose what must be passed as input to the workflow:
- context : the MessageContext
- envelope : the envelope as XML serialized string
- body : the body as XML serialized string
- body-element : the first child of body as XML serialized string
- header : the header as XML serialized string
- envelope-om : the envelope as SOAPEnvelope object
- body-om : the body as SOAPBody object
- body-element-om : the first child of body as OMElement object
- header-om : the header as SOAPHeader object
- Data provider, used to adapt the workflow output to the Web service output
- Choose if Web Service should be forced to HTTPS
- Choose if target namespace to be used is the one in the xsd
Example
| Web Service name | Operation | Description | |
|---|---|---|---|
| Credit Card | withdrawal | This operation............................................................. | Example 1 |
| Credit Card | Balance | This operation............................................................. | Example 2 |
