Subject: Web retriever was discontinued in Domino 7
If you are really looking for the Domino Web retriever task (NWEB.EXE) this was discontinued in Domino 7. The Web server task is NHTTP.EXE, as Carl mentioned.
Sticking with NWEB.EXE, I can’t imagine that you were using this for client access to Internet content, as it really can’t handle most modern web sites.
If you were using NWEB.EXE for agent-based access to HTTP content, then there are various alternative approaches. Search for Web retriever in the Notes/Domino 6 and 7 forum.
The web retriever is still available in the Domino 8.0.1 32bit installation. I’ve just regressed to that this morning as an instant fix.
I’ve searched the Dominno 6/7 forum but cannot find anything that talks about replacements/options. Can you be a little more specific if you have a moment to help?
If you’re not using db.getDocumentbyURL, or those solutions won’t work for you, then I think we’ll need some more details about what you’re using the Web retriever for at present.
Subject: Doesn’t getdocumentbyURL still work in 8? The documentation needs updating if it does not
The Designer Help doc on the getdocumentbyURL does not state this method will not work on certain releases… Does this work or not work in 8 (I did not try it.)
If it does not work or is being deprecated than it should be documented in Help.
I use web retriever for two processes/clients, both of which involve getting an HTML webpage, and then scraping that webpage for data/tags/etc, parsing it and extracting what I need from that webpage.
Both of the processes are LS agents presently and carry out reasonably complex processing.
Subject: Should be good info for a developer to assist / maybe raise a PMR also
That explains much more clearly why you need this functionality. And as you have demonstrated, it’s still present in the W32 code.
Perhaps a developer who has coded similar screen-scraping logic can suggest some alternative mechanisms.
Also, I don’t have a W64 server to check the absence of nweb.exe, but I couldn’t find any mentions of this in a quick support search. I suggest you open a support call with IBM to find out if this has definitely been dropped from the 64-bit code stream, and what workarounds they can suggest.
My take would be that this might be a good opportunity to change your screen scraping approach into web service consumption of some sort. But that’s the admin talking!
That’s what I’m thinking might be the way forward! Connect to the site using the Microsoft XMLHTTP object (so will only work on Windows boxes). That can retrieve the response as XML … or the whole responsetext shebang
I don’t know how to open a support ticket with Lotus actually?