Difference between revisions of "Top-down development method"
(→Top-down development method) |
(→Top-down development method) |
||
| Line 10: | Line 10: | ||
*Operation name, the operation name present in the WSDL file | *Operation name, the operation name present in the WSDL file | ||
*Service, choose {{GVESB}} service to invoke. | *Service, choose {{GVESB}} service to invoke. | ||
| − | In the last page User sets the | + | In the last page User sets the following parameters: |
*[[Data provider]], used to adapt the workflow output to the Web Service output | *[[Data provider]], used to adapt the workflow output to the Web Service output | ||
*Input type, used to choose what must be passes as input to the workflow: | *Input type, used to choose what must be passes as input to the workflow: | ||
Latest revision as of 08:34, 28 February 2012
Top-down development method
Wizard Top-down development method guides user step by step with the Web Service creation. Prerequisites to use this wizard is the WSDL file. If you don't know how build a WSDL file visit this link. Right click on GVServices-->Services label and select Wizard Top-Down Web Service.... New WebService Wizard window will be shown.
In the first Wizard page user selects the WSDL file. The Wizard on the second page proposes the operations that are described in the WSDL file. User selects one or more operations. In the next page user sets the following parameters:
- Create Services, if this radio button will be checked the Service parameters are enabled
- Use existing services, if this radio button will be checked the Service parameters are disabled
- System
- Participant
- Channel
- Operation name, the operation name present in the WSDL file
- Service, choose GreenVulcano® ESB service to invoke.
In the last page User sets the following parameters:
- Data provider, used to adapt the workflow output to the Web Service output
- Input type, used to choose what must be passes 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
- Input xsd name: the name of your XSD file, defined in the xsds folder
- Output xsd name: the name of your XSD file, defined in the xsds folder
- 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 | Saldo | This operation............................................................. | Example 2 |
