My opinion, assuming you mean doing an Import within the UI, the import module will use the current server the user is logged into to take the imported data for processing.  This cannot be controlled by the Alliance UI application while you are using some NLB method to have multiple application servers as the rules for connection are maintained by the NLB.

What you could perhaps look into is using the import utility on the server itself to manage the importing process so it is only done on that server.  Of course, the average backend user does not have access to the server itself so this would have to be done by user who does have access such as yourself.

Thanks a lot Phil, that is a good idea.

Hi Torsten,

My suggestion may work for you for now but please be aware that the import utility hosted on the server itself may not be updated in the future and we encourage using the Web Employee Portal instead.

Therefore, the only way I can now recommend to make sure the import occurs only on a specific server is that you change your connection URL away from the NLB address and go direct to the web/app server to use the import from there.