Sunday, October 9, 2016

Overview of Web Services in TIBCO BW

     An Organization can offer its application services to other organization by using the standards-based model of web services. Web services can be used within a business to integrate various critical applications, or web services can be made available to other businesses or individuals.

     Web services rely on a variety of published standards for communication, security, data exchange and so on. Standards-based technology enables businesses and individuals to use each other’s web services, regardless of the underlying applications or implementations of the service.

Most web services comply with the following standards:

• HyperText Transfer Protocol (HTTP) or Java Message Service (JMS) – HTTP and JMS are transports that are mechanisms for relaying information. Web services use a transport mechanism such as a Web server or JMS server to store and relay messages. TIBCO ActiveMatrix BusinessWorks supports HTTP and JMS as transport for web service messages.

• Simple Object Access Protocol (SOAP) – SOAP is the communications protocol for web services. SOAP defines message structure and bindings to the underlying transports.

• Extensible Markup Language (XML) – XML is used to define data schemas for SOAP message content.

• Web Service Definition Language (WSDL) – WSDL describes the interface to a web service. A web service provider publishes a WSDL file that describes the offered service. A client uses the WSDL file to determine the appropriate input, output and fault messages for the service.

• Web Service Security (WS-Security) – WS-Security specification defines the standards-based approach to message-level security. Unlike transport-level session security (such as HTTPS), message-level security allows you to secure messages that may travel through multiple hops on a distributed transport channel. Message-level security is important for organizations that require trusted, secure communication between web services and clients.

• Universal Description Discovery and Integration (UDDI) – UDDI is an XML based standard for describing, publishing and finding web services. In simple terms, UDDI is a directory service where companies can register and search for web services.

NOTE: The World Wide Web Consortium (W3C) maintains the standards upon which web services are based. Refer for more information about the currently supported web services standards.

A typical Web Service creation Involves below Steps :

1) Define Types - XSDs
2) Define the Transport (HTTP/JMS)
3) Create Abstract WSDL from XSDs
4) Create the service and configure Endpoint bindings like transport details etc.
5) Operation Implementation
6) Publish Concrete WSDL

A typical interaction between web service client and server is as follows :

As described in above diagram :

1) Service Provider :
       i) Defines XSDs and then abstract WSDL which contains the service definition
       ii) Implement the service (business functionality)
       iii) Adds bindings(transport to be used) and service (where it is exposed)

2) Service Provider - Publish ConcreteWSDL to UDDI Service Registry.

Info :
Abstract WSDL - Service definition (Types, Messages, PortType)
Concrete WSDL - Service definition + (Bindings(how) + Service(where))

3) Service Consumer - Look up UDDI registry to get Concrete WSDL.

4) Service Consumer :
       i) will make use of Concrete WSDL and invokes web service by sending SOAP message.
       ii) Receives SOAP response message as success or fault.

You can also check the below ways of creating and exposing web services in TIBCO BW:

Creating Web Service by using Service Activity
Creating Web Service by using SOAP Event Source Activity

No comments:

Post a Comment

back to top