Provisioning location of End-Users when using impersonate()

From my customer:

What works:

1. Changed Oracle BI to use the BI Publisher Security Model
2. Had to add users via the analytics application (e.g. user01)
3. Also had to add the same users on WLS console
4. Impersonate now works
5. Impersonate userid/passwd is stored in the bi_auth table (custom table in our database)
6. Code that calls the impersonate function first does a query to get the impersonate user/passwd from the table (This is the admin user/password)
7. Rather than have the userid hard coded in the java class that does the query, it should be stored as a property in a property file so that it can be changed if needed so query to db is not needed.