Iterating a single server job over multiple schemes
Posted: Wed Sep 19, 2007 5:00 am
Hi.
We are trying to make a server job iterate over several shemes. Logging into a specific scheme is done by username and password alone. We have currently come up with the following methods.
1. One seqence where the job is calles 1 time per scheme with hardcoded username/passwords. Works but is not very good when wanting to add/remove/change a scheme.
2. Concatanate username/password in a comma seperated list using it in a StartLoop then use loop.counter$[a,b] to get the username/password substring. Works but might be easy to make errors. And the password must be a clear text or the whole comma seperated list treated as encrypted.
3. Storing username/passwords in a table and using a transformer to call the job with the appropriate parameters. Works but somewhat hides what is actually going on. Somehow feels like a hack.
We have tried having two loops, one with usernames and one with the passwords, but can not seem to find a way to make them both iterate once between each time the job is run.
Anyone have any other ideas? We do not really like any of method 1-3.
Would greatly appreciate any help![Smile :)](./images/smilies/icon_smile.gif)
We are trying to make a server job iterate over several shemes. Logging into a specific scheme is done by username and password alone. We have currently come up with the following methods.
1. One seqence where the job is calles 1 time per scheme with hardcoded username/passwords. Works but is not very good when wanting to add/remove/change a scheme.
2. Concatanate username/password in a comma seperated list using it in a StartLoop then use loop.counter$[a,b] to get the username/password substring. Works but might be easy to make errors. And the password must be a clear text or the whole comma seperated list treated as encrypted.
3. Storing username/passwords in a table and using a transformer to call the job with the appropriate parameters. Works but somewhat hides what is actually going on. Somehow feels like a hack.
We have tried having two loops, one with usernames and one with the passwords, but can not seem to find a way to make them both iterate once between each time the job is run.
Anyone have any other ideas? We do not really like any of method 1-3.
Would greatly appreciate any help
![Smile :)](./images/smilies/icon_smile.gif)