Web Service Development in TIBCO is one of the key topic that becomes a prime focus when you go for an Interview for a TIBCO developer position in any organization. Keeping that in mind, I am writing this post that covers TIBCO Web services related top interview questions with their answers.
Q: What are the transport types we can use for TIBCO SOAP web services?
Ans: In TIBCO, we can create SOAP web services using HTTP or JMS as transport.
Q: What is the difference between Concrete and Abstract WSDL?
Ans: Abstract WSDL is used on the server side which contains all details about a service including its operations, messages and port type details without any transport details. On the other hand, Concrete WSDL is used in the client side in order to access the web service and consume its operations and It contains transport details along with that information which is available in the Abstract WSDL.
Q: What are the ways to create SOAP web service in TIBCO Designer?
Ans: In TIBCO designer, there are two ways to create a SOAP Web service:
1. Contract first: In this approach, first abstract WSDL is created using WSDL palette and then web service is generated from the WSDL.
2. Code first: In this approach, processes are first developed/designed and then web service is generated from the processes.
Q: What is the difference between RESTful and SOAP web services?
Ans: SOAP Web services are based on XML structure while REST based services are URI and Method based implementation. SAOP Web Services expose operations in the form of a WSDL while RESTful web services doesn’t have any standard specification.
Q: Which SOAP activity is used to consume a web service in TIBCO?
Ans: SOAP Request Reply activity is used to consume a web service operation in TIBCO BW.
Q: What are the three types of messages that can be part of a WSDL Operation?
Ans: Following are the three types of messages for a Web Service Operation:
1. Input Message
2. Output Message
3. Fault Message
Q: How can we retrieve Concrete WSDL from a deployed web service EAR?
Ans: We can retrieve concrete wsdl from a deployed service by setting retrieveresource.enabled to true in the advanced configuration of par. Then we can access the wsdl by following URL: