As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
The answer to your Q2 is yes... Webfocus can interact to other webapps through webservices...
As said in product manual, It can be through a Java/J2EE or a .NET call.
quote:
Features of the WebFOCUS Web Service Enablement Option : 1) Full support of all key Web-services standards to ensure interoperability
2) User extensible – empowering developers to build new functions that can then be published as new J2EE or .NET calls
3) Utility for automatic generation of Web Services Description Language (WSDL) to expedite application development
4)Exposed functionality for more efficient Web-services development, including security, report execution, application management, user administration, and delivery and scheduling
All depends on whether WebFocus will be consuming web services that have been published using other platforms (java, ,NET, etc.), or if WebFocus will be providing services to other platforms. WebFocus and ReportCaster both have support in either case.
We've been using WebFocus with .NET-generated SOAP web services for years. All our web services interactions have WebFocus as the consumer, not the producer of services. But the .NET implementation of SOAP and other web service standards has changed dramatically with the Windows Communications Foundation (WCF). WCF is now Microsoft's comprehensive solution for interoperability. WebFocus version 7.7 added support for WCF services--see http://documentation.ibi.com/m...nfhilit/snfhilit.pdf and search for "WCF").
Its worth noting that if you're using a later version of Visual Studio or Visual Studio Express that you now use a "Service Reference" rather than a "Web Reference".
As a result this changes the syntax slightly for the connection, since it adds to the end of the name "SoapClient".
e.g. Rather than the following which shows in the WebFOCUS web services manual when you name the service reference "MR": Dim wfs As New MR.WebFocus
You would have the following: Dim wfs As New MR.WebFocusSoapClient
The rest of the example code from the manual should be able to be copied and pasted out of the manual without modification.