Difference between revisions of "Top-down development method"

From GreenVulcano Wiki
Jump to: navigation, search
(Created page with " == Top-down development method == Wizard Top-down development method help user to create a Web Service . Right click on GVServices-->Services label and select "Wizard Top-Down W...")
 
(→‎Top-down development method)
 
(20 intermediate revisions by 5 users not shown)
Line 1: Line 1:
 +
== Top-down development method ==
 +
Wizard Top-down development method guides user step by step with the [http://en.wikipedia.org/wiki/Web_service Web Service] creation. Prerequisites to use this wizard is the WSDL file. If you don't know how build a WSDL file visit this  [http://www.w3.org/TR/wsdl link]. Right click on ''GVServices-->Services'' label and select ''Wizard Top-Down Web Service...''. New WebService Wizard window will be shown.
  
−
== Top-down development method ==
+
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:
−
Wizard Top-down development method help user to create a Web Service . Right click on GVServices-->Services label and select "Wizard Top-Down Web Service...".
+
*Create Services, if this radio button will be checked the Service parameters are enabled
−
New WebService Wizard window will be open.
+
*Use existing services, if this radio button will be checked the Service parameters are disabled
−
Fill the window fields as following:
+
*[[System]]
−
*In the "WebService name" field set the WebService name that you want to publish
+
*[[Participant]]
−
*In the "target namespace" field if you want you can change the default operation target namespace proposed
+
*[[Channel]]
−
*In the "Operation" field choose the operation to bind from list proposed.
+
*Operation name, the operation name present in the WSDL file
−
[[File:ws2.png|thumb|WebService Wizard second window ]]
+
*Service, choose {{GVESB}} service to invoke.
−
On the second page you can change:
+
In the last page User sets the following parameters:
−
*Soap Action and the mapped operation name to the WebService-This optional property is set on an outgoing SOAP/JMS request message to indicate the soapAction value associated with the Web services request. This property is similar to the SOAPAction HTTP header used when transporting Web service requests over an HTTP transport. The value of the soapAction property is a URI identifying the intent of the SOAP request. If the soapAction property is specified, it is used by the server component to determine the target of the request. The SOAP specification places no restrictions on the format or specificity of the URI or that it is resolvable. Typically, this property is set to the soapAction value from the WSDL document.
+
*[[Data provider]], used to adapt the workflow output to the Web Service output
−
[[File:ws3.png|thumb|WebService Wizard third window]]
+
*Input type, used to choose what must be passes as input to the workflow:
−
On the third page you can choose your preferred transport protocol. The properties indicates the version number of the protocol used by the client and server.If the SOAP request message represents a two-way request, the client component must set the JMS message.
+
**context        : the [http://axis.apache.org/axis2/java/core/api/org/apache/axis2/context/MessageContext.html MessageContext]
−
*Soap Transport
+
**envelope        : the envelope as XML serialized string
−
*Soap12 Transport
+
**body            : the body as XML serialized string
−
*Rest Transport
+
**body-element    : the first child of body as XML serialized string
−
*JMS Transport
+
**header          : the header as XML serialized string
 +
**envelope-om    : the envelope as [http://ws.apache.org/axiom/apidocs/org/apache/axiom/soap/SOAPEnvelope.html SOAPEnvelope] object
 +
**body-om        : the body as [http://ws.apache.org/axiom/apidocs/org/apache/axiom/soap/SOAPBody.html SOAPBody] object
 +
**body-element-om : the first child of body as [http://ws.apache.org/axiom/apidocs/org/apache/axiom/om/OMElement.html OMElement] object
 +
**header-om      : the header as [http://ws.apache.org/axiom/apidocs/org/apache/axiom/soap/SOAPHeader.html 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 ==
 +
{| class="gvtable"
 +
|-
 +
! Web Service name
 +
! Operation
 +
! Description
 +
!
 +
|-
 +
| Credit Card
 +
| withdrawal
 +
| This operation.............................................................
 +
| [[Example 1]]
 +
|-
 +
| Credit Card
 +
| Saldo
 +
| This operation.............................................................
 +
| [[Example 2]]
 +
|}

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
Retrieved from "https://gvwiki.greenvulcano.com/gvwiki/index.php?title=Top-down_development_method&oldid=2764"