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.
We are predominantly a Microsoft shop, however we can be flexible. What is best to use for our coming AJAX backend services. We can write ASP.NET based pages in any of their varies forms, but also might we consider technologies such as PHP or Node.js? Do any of these pose possible technology conflicts with WebFocus (ie. will setting them up screw up WebFocus)? I see a lot of Javascript front end examples and this is not a problem, but we need reassurance that altering our currently 8.1 and coming 8.2 servers will not cause trouble and conflicts in our servers.This message has been edited. Last edited by: FP Mod Chuck,
WebFOCUS 8.2.04 (and climbing) Windows 10, AppStudio
So far we just do reports. What's the web related content? It sounds interesting. Can you point me at a primer? Anyway, what's the recommended backend tech for Windows boxes?
I should reiterate, there is concern about installing things on our WebFocus server. Because of javascript's sandbox restriction, the chosen technology must sit benignly next to WebFocus under IIS.This message has been edited. Last edited by: mbondr,
WebFOCUS 8.2.04 (and climbing) Windows 10, AppStudio
We need to reload some backend data and then refresh the page to see the results. WCF seems to kill WebFocus, at least enabling HTTP Activation does. So now I'm thinking Node.js, but I saw a mention of using a servlet stationed within the WebFocus directory tree.
WebFOCUS 8.2.04 (and climbing) Windows 10, AppStudio
It's how Microsoft does deamons. It's a bit like a Java service in that it has stubs, WSDL's, and SOAP wrappers. Lately they've been pitching a REST'ive version that just emits JSON or XML.
WebFOCUS 8.2.04 (and climbing) Windows 10, AppStudio
I'd look into ASP.NET Core 2.1 and Signal R for sockets. We're working to implement a .NET Core backend ourselves among the rest of our new stack. Looking very promising.
8.2.02M (production), 8.2.02M (test), Windows 10, all outputs.
Posts: 1113 | Location: USA | Registered: January 27, 2015
Our problem is that we can't enable HTTP Activation. It kills WebFocus. So no web service projects. And our system manager won't turn on ASP.NET without IBI approval, which is essentially impossible to get.
If you're using raw sockets, then almost anything will do.
WebFOCUS 8.2.04 (and climbing) Windows 10, AppStudio
Not sure. Everyone doing development suddenly got up and complained that it wasn't working. It was a crisis. Turning off HTTP Activation and restarting IIS restored the status quo.
WebFOCUS 8.2.04 (and climbing) Windows 10, AppStudio