Difference between revisions of "Bottom-up development method"
F.albanese (talk | contribs) (→Wizard bottom-up development method) |
F.albanese (talk | contribs) (→Wizard bottom-up development method) |
||
Line 17: | Line 17: | ||
*JMS Transport | *JMS Transport | ||
− | If you choose Rest Transport, you must additionally select the verb for the operation. | + | If you choose Rest Transport, you must additionally select the verb for the operation. |
If you choose JMS Transport, you must additionally: | If you choose JMS Transport, you must additionally: | ||
*Select the JMS connection factory | *Select the JMS connection factory |
Revision as of 11:09, 2 February 2012
Wizard bottom-up development method
Wizard bottom-up development method helps user to create a GreenVulcano® ESB service as a Web Services. Right click on GVServices-->Services label and select "Wizard New WebService...". New WebService Wizard window will be open. Fill the window fields as following:
- In the "WebService name" field set the WebService name that you want to publish
- In the "target namespace" field you can change the default operation target namespace proposed
- In the "Operation" field choose the operation to bind from list proposed
On the second page you can change:
- 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.
On the third page you can choose your preferred transport protocol. Properties indicate 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.
- Soap Transport
- Soap12 Transport
- Rest Transport
- JMS Transport
If you choose Rest Transport, you must additionally select the verb for the operation. If you choose JMS Transport, you must additionally:
- Select the JMS connection factory
- Set the JMS destination name
- Set JMS destination type
- Reply destination: Destination where a reply will be posted
- Content Type: This property is similar to the Content-Type header found in an HTTP message and is used to describe the content type of the message
- ByteMessage
- TextMessage
On the last page you must choose:
- The Web Service input type
- The Data provider name
And optionally:
- The input XSD name
- The output XSD name
Lastly check the preferred Radio Button for:
- HTTP or HTTPS
- Web Service's target namespace is in the XSD or it is that proposed by default
- Use the original wsdl or not
Example
Web Service name | Operation | Description | |
---|---|---|---|
Credit Card | withdrawal | This operation............................................................. | Example 1 |
Credit Card | Saldo | This operation............................................................. | Example 2 |