first of all, thanks for the selenium nodes! Together with the palladian nodes they are really my most used KNIME feature!
My problem is, i log into a backend of a webpage and grab some information (just some numbers) for several accounts. Each account has several profiles for which i have to get 5 different numbers from 5 different urls. So i have to visit many different urls in the backend for each login.
Is there a way to parallelize that process? Can i login and start five tabs for those five urls and grab the numbers and close the tabs again and repeat for the next profile?. Or start a new Webdriver that "remembers" the login?
Thanks for your help.
great to hear you feedback :)
Currently, there is no support for tab management, but I'll add this to the wishlist and see what solutions we can provide in the future. I would recommend you subscribe to the Selenium Nodes newsletter (on seleniumnodes.com), where we usually keep users informed about recent changes.
In the meantime, I would probably go for the following solution: Use one WebDriver per account, which you keep open and sequentially visit the URLs from which you can extract data. You can navigate to new URLs conveniently by using the "Navigate" node. You would repeat that procedure for each account you need to process.
Does that make sense?
thanks for your answer. I tried to use the knime parallel execution to open one WebDriver per account, but that does not seem to work reliable. For now i will execute everything sequentially because the workflow is planed to run at night.
I tried to use the knime parallel execution to open one WebDriver per account, but that does not seem to work reliable.
thanks for the details; I have to admit that I never used the parallel execution nodes until now, so I'm not fully aware of potential issues in conjunction with the nodes. Would it be possible to share some details of your concrete workflow, that I can get an idea and see, where improvements could be made? (you can also contact me via e-mail email@example.com -- a screenshot to get a general overview over your workflow's structure should also be sufficient).