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,

I think this all depends on what you are going todo with WebFOCUS.

Just call reports, or use the use Web related content.

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,

This is where things get complicated.

Do you need to log into WebFOCUS to run the fexes ?

If so, then I think you need to check out RESTful Web Services

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.

Whats WCF ?

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.

Found a mention of using servlets in the WebFocus directory tree itself to catch the socket connections.

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.

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.

How does it kill WebFOCUS ?

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.

I wonder if you need to debug that.

Sounds like its going to make too many waves.