Best Practices for running Multiple Browser Macros

Discussions and Tech Support related to automating the iMacros Browser or Internet Explorer from any scripting and programming language, such as VBS (WSH), VBA, VB, Perl, Delphi, C# or C++.
Forum rules
Before asking a question or reporting an issue:
1. Please review the list of FAQ's.
2. Use the search box (at the top of each forum page) to see if a similar problem or question has already been addressed.
3. Try searching the iMacros Wiki - it contains the complete iMacros reference as well as plenty of samples and tutorials.
4. We can respond much faster to your posts if you include the following information:CLICK HERE FOR IMPORTANT INFORMATION TO INCLUDE IN YOUR POST
Post Reply
overdaedge
Posts: 10
Joined: Wed Mar 09, 2011 12:19 am

Best Practices for running Multiple Browser Macros

Post by overdaedge » Mon Apr 25, 2011 6:35 pm

Hey - I was curious if you could provide me with some insight on the best practice for running multiple browsers. Currently I'm logging on to one website with multiple login's - because the site is the same I can only run one login script at a time. An obvious solution would be to run each script with it's own proxy. I'm assuming the best way to do this would be to create a Firefox profile for each script and link the a proxy to that profile this way they can all run at the same time. Does this seem possible? Anyone have any experience with this?

Thanks in advance
User avatar
Tech Support
Posts: 4948
Joined: Tue Sep 20, 2005 7:25 pm
Contact:

Re: Best Practices for running Multiple Browser Macros

Post by Tech Support » Wed Apr 27, 2011 8:24 am

... best practice for running multiple browsers
You are correct. Using multiple profiles is the best way to do this with Firefox. We have the -fxProfile switch for this. For Internet Explorer, it is even easier: You can separate instances using the "Inprivate" mode. There is the -iePrivate switch in iimInit for this.

Both options are described here in more detail: http://wiki.imacros.net/iimInit()#Separ ... _Instances

These options work if the cookie is the limiting factor. If the site also checks for the IP address (rare!) you need to combine this approach with the PROXY command (as you suggested).
Post Reply