Standard Web Services
Integration Web Services 253
T Can use a Java Message Service (JMS) queue (asynchronous process) or
bypass the JMS queue (synchronous process).
Enterprise Web services that are processed in a JMS queue do not support
the Query operation and do not provide any response content to the caller.
Enterprise Web services that are configured with the Query or Create
operations provide XML content in the service response.
Standard Web Services
You can create a standard Web service from methods that are annotated in
application services. In order to be available as Web services, annotated methods
such as ChangeStatus, must exist within an application. A single standard Web
service is created for each application service and all annotated methods within
the service are the Web service operations. The system links the input and output
parameters of the methods to the input and output parameters for the standard
Web service.
Web Service Deployment Actions
You deploy a Web service through the Deploy Web Service action. When you
deploy a Web service, the following events occur:
T Schemas are generated and regenerated for existing service schemas.
T The Web Services Description Language file is generated for the service
interface.
T The Web service is deployed for the selected service.
T If UDDI registry properties are configured, the Web service is registered in
the UDDI registry.
The deployed Web service is available at the following URL:
http://hostname:port/meaweb/services/web service name
T host:port/meaweb is the value of the Integration Web Application URL
property.
T web service name is the name of the service for which the Web service is
deployed.
Web services are deployed on the Axis Server that is based on the IsDeployed flag
in the service definition. When you restart the application server, all Web services
are redeployed based on the registry.
The list of deployed Web services is available in the Web Services Library
application.
To Next Page
Loading...