We would like to use the advanced login strategy so that we can use
the user's BO login as the login to the database (Oracle v7.3). In
the Universe connection we use @variable('BOUSER') as the login user
name. This works fine if the BO User Name is in upper case.
The problem is when the BO User Name is in lower case it doesn't match
the database id. Oracle database ids must be upper case. I'd rather
not change all our BO User Names from lower to upper case. I tried
modifying the connection to something like @variable(Upper('BOUSER'))
without success. Has anyone solved this problem? Tech Support says
it can't be done, but perhaps someone knows of a creative workaround.
Christopher Jeter
HIMCO (Hartford Investment Management Company)
Hartford, CT USA
chris.jeter@thehartford.com
> we use @variable('BOUSER') as the login user name. This works
> fine if the BO User Name is in upper case. The problem is when
the > BO User Name is in lower case it doesn’t match the database id.
> Oracle database ids must be upper case.
Are you sure that the not being recognized is due to the lower-case
userID’s in BO?
We also have an oracle database (v7.3.2.3.0 on OpenServer) and use
advanced login strategy with no problem at all.
All our BO userID’s are in lower case (completely), Oracle userID’s are
in uppercase and oracle just verifies them OK (middleware SQL*net 2.2).
We do however fill in a password as well (same as the userID).
Hope you can figure out the difference, because the problem must reside
somewhere else then in BO.
We would like to use the advanced login strategy so that we can use
the user's BO login as the login to the database (Oracle v7.3). In
the Universe connection we use @variable('BOUSER') as the login user
name. This works fine if the BO User Name is in upper case.
The problem is when the BO User Name is in lower case it doesn't match
the database id. Oracle database ids must be upper case. I'd rather
not change all our BO User Names from lower to upper case. I tried
modifying the connection to something like @variable(Upper('BOUSER'))
without success. Has anyone solved this problem? Tech Support says
it can't be done, but perhaps someone knows of a creative workaround.
Normally, ORACLE does not care about the case of login IDs. BUT wher you use other
databases this might be an issue.
There are also variables called BOUSER_UPPER and BOPASS_UPPER (undocumented?)
available, which give you excatly what you want
You can test this with the following example script (c) BusinessObjects:
Sub main
dim var as BOVariable
dim I as integer
for I = 1 to Application.Variables.Count
set var = Application.Variables.Item(I)
MsgBox var.Name & " " & var.Value
next
End Sub
Hope this helps.
DI Walter Muellner
Delphi Software GmbH, Vivenotgasse 48, A-1120 Vienna / Austria
Tel: +43-1-8151456-12, Fax: +43-1-8151456-21
e-mail: w.muellner@delphi.at, WEB: http://www.delphi.at
A little conceptual question about Advanced Login Strategy.
The connection with the database using BOUSER and BOPASS is possible
with the data.
But what about the connection with the repository?
I think it’s not possible because you must connect with the repository
before having the bo username and password.
In pure BO, I think that the solution reside in creating a bomain.key
for each user.
But with Webintelligence???
I work with WebIntelligence 2.0 and after some little problem of
installation I need to go deeper in the product. So I need to connect
with the same Nt user and BO user (easy with administrator). I changed
the dll’s to log with the current user in BO (easy) but I can’t made a
link between Webi and the BO instance when you refresh a BO 4.1.3
document. I think I must work with servconf.exe but the only working way
is to log with a particular user.
Can somebody help me?
If you need info about my installation problem contact me.
Bruno FAUCON
Three-i
GD Luxembourg: T. +352 29 92 501 - F. +352 29 92 51
Belgium: T. +32 2 332 35 32 - F. +32 2 332 34 31
There is a way to do Advanced Login for the repository.
You follow the same steps and use the same variables. It’s outlined in pg.
24 of the Supervisor’s Guide. You’ll simply get a warning that Supervisor
will not try to validate the account, as it normally does when it “pings”
the server with hard-coded account information.
As for your WebIntelligence/BusObj question, I don’t think there is a way to
do it. The BusObj.exe runs on the NT server under a given account with
certain rights and privileges. I really don’t think you want all kinds of
users running executables on the server. Besides, any login strategy is
followed in the same way by WebIntelligence as it is by BusinessObjects.
