I have to install a BCA machine using an account with a password that I am not allowed to know. Somebody who knows the password will sit with me and fill in the blanks at the appropriate junctures. When the server is made live the only access I will have to it will be via the BO Services Administrator app on my PC.
Can I have a second account on the server which I can use purely to login to BO Services Administrator - even though this account will not be the one that BCA is using to run its services? I think not…but would welcome thoughts and constructive suggestions
Have you guessed at “sa” or “change_on_install” yet Nick?
Seriously, if the password is an issue, play the game, raise the issue and state the reasons for needing the password. As in, if somebody is off, what do I do? Turnaround time will be jeopardised. Usual sort of support and development risks.
If you are using SQL Server, there may be a problem creating a second user - they may be unwilling, or worried about the access that this would provide you with. You may also hit problems depending upon the levels of access granted to that user, be it a database username or a server username. Things like, if the user is read only or not an administrator of the machine, you won’t be able to perform certain tasks.
Better option is to convince them of your need for the password. Assuming that you are on that site in a contract/consultancy/short term role, suggest that they could change the password once you leave.
The immediate response from our local support is that you can’t solve this problem with two accounts as the second account will simply not be recognised by BO Services Administrator. Updates to follow.
I spoke too soon…support came back to me and stated that this IS possible, simply by having a second account with the 6 OS rights as a member of the local admin group on the server.
One caveat they mentioned was that changing from one user to another can be a bit kludgy - I’ll soon find out.
Just for info, we’ve always used a separate account for logging on to BO Services Administrator. In fact, if I remember right, I set the account up in the local admin group on each server and that was it - nothing special was needed. We don’t usually touch the account that runs the webi/BCA services. (webi 2.6.3 on NT, cluster managers only - no nodes)
We had this problem with WebI as we need a domain user to access an OLAP server, but we could not have the password for this user. We could however have the password for a local user with admin rights. Therefore the setup is as follows:
User to launch the application (the user you see when you launch servconf.exe) = Domain user (with local admin rights on the server including the required WebI rights)
User for OLAP (an IIS Setting) = The above Domain user again.
User to run the two WebIntelligence Services( WebIntelligence Manager and WebIntelligence Orb) = Local user (with admin and the required WebI rights)
This means that we can use the administrator module, and also the infrastructure people can keep the user with a hidden password.
The same could well work for BCA. But, if I understand the situation correctly, it comes down to having the password to the user that runs the services if you want to be able to support without continuous hassle.
(BOB member since 2002-08-15)
(BOB member since 2002-08-15)