Changing Administrator Password in OBIEE
(3 votes, average: 5.00 out of 5)
Loading ...
Sorry for the delay as I was busy in some assignments of mine which had to be taken up on priority. Today we changed the Administrator Password for OBIEE, BI Publisher and Scheduler so, thought to share the same with you.
We can change the Administrator password by using the following steps:
1) We need to create a superuser in BI Publisher so that we can log into the application using the Superuser credentials and change the Administrator password.
2) Take a backup of the file “c:\OracleBI\xmlp\XMLP\Admin\Configuration\xmlp-server-config.xml”.
3) Log into BI Publisher and navigate to Admin > Security Center > Security Configuration
4) Enable a Local Superuser and put in the Superuser name and password(eg: Username-admin Password-admin1) and click apply.
5) Now restart the oc4j services.
6) Try Signing into BI Publisher(standalone application) as admin/admin1(superuser) and you should be successfully logged into the application.
7) Navigate to Admin > Security Center > Security Configuration and change the Administrator Password in the Security Model to the new password ( eg: admin123)
8 ) Navigate to Admin/JDBC Connection and click the Oracle BI EE link.Change the password for the Administrator user there and write the new password(admin123). This is used because when we use Oracle BI EE as source for the reports then, it establishes the connection with OBIEE using these credentials.
9) Also navigate to Admin/Integration/ Oracle BI Presentation Services and change the Administrator password there also(admin123).
10) Open the OBIEE Repository in Online mode and change the password for the Administrator to the new password eg: admin123.
11) Shut down the servers and oc4j.
12) Run the cryptotools utility which will modify the credentialstore.xml for BI Publisher and Scheduler(As required for Administrator user).
Cryptotools just a general purpose utility for the manipulation of the credential store XML file (OracleBIData/web/config/credentialstore.xml). The credentialstore.xml is used by the Presentation Services to communicate with other BI Components (BI Scheduler [aka Delivers] and BI Publisher). Once the Presentation Services contacts the other BI Component, the BI Component will use the credentials provided by the Presentation Services to authenticate the user against the BI Server. The reason this was implemented this way it’s due to the fact that in most large installations the Presentation Services will reside on a different box than the BI Scheduler [aka Delivers] or BI Publisher hence the connection between the services needs to be authenticated.
13) Configure the scheduler using the ‘schconfig’ on UNIX box.
1 – Configure Scheduler
>>> Enter Choice: 1
***** Scheduler Configuration *****
1 – Database
2 – General
3 – Advanced
0 – Quit
>>> Enter Choice: 2
***** Scheduler General Configuration *****
10 – Administrator Name : Administrator
11 – Administrator Password : *****
0 – Quit
>>> Enter Choice: 10, then 11
0 – Quit
0 – Quit
0 – Quit
14) Now, start all the servers and oc4j so that the changes can take effect.
15) Try logging into the application using the new Administrator credentials. it should log in successfully.
16) Try to navigate to BI Publisher from OBIEE and it should navigate without any errors.
Follow the above mentioned steps in the defined order. Hope it works fine for you.
Post your comments in case you face nay issues…
cool!!!!
Hi ,
I like your explanation way.Your way is very simple, that anyone who are new to this can understand like me.
I really appreciate you.I have a request recently i took training, now i want to study and prepare, will you guide me and pls provide some good materials at my email.
Will you give some comment on BI APPS and DAC.
Thanks
Sunia
Hi Sunitha,
Thank you for reading the posts. Sorry i cant take out much time to write frequently but i try to write when i get time. Please let me know what are you preparing for and what all material you require for the same.
I had worked on DAC prviously and also have some docx on the same.
Let me know what all you want.
hi
you are providing very good information.can u provide material how to implement security in obiee?
Hi Ramadevi.
Thanks for the appreciation….
Will also write about security also in upcoming posts…
Thanks and keep posting….
Nice Blog Man ..Keep up the Good Work !!
Hi,
I have a query on OBIEE and Siebel application.
Whenever I click on segment screen in Siebel marketing application, It shld navigate and open
OBIEE application directly without asking for OBIEE credentials.
But, it is asking for the credentials to enter. PLease let me know wat can be the reason.
Hi Chitra..
As per my understanding it should log in without asking for the credentials but if it asks for the credentials then then chek that whether your password for OBIEE application is same or have u changed it.
Also check your credentialstore.xml file. Sometimes you need to configure it accordingly as this file is responsible for interaction between BI Server and other components.
Hope this helps.
Hi Rohit, very good post thanks a lot for sharing it with us. I saw that you have a worked with DAC as well and i have a question. I have 3 environments dev qa and prod which are pulling etls form a Siebel DB. Since dev and qa and not in use very much i want to sync the data every month or so. Do i just need to change the physical source in DAC or some other steps are involved . Please let me know if you had any experience with this or some documentation.
Thanks,
Vas
Hi Vas,
Thanks a lot for reading the posts.
Yes, I have worked on DAC and what I understand from your scenerio is that your Source DB is Siebel DB and it doesnt get updated that frequently. So you want your to sync up your target DB monthly or so with the Prod Source DB.
This can be achieved by changing the Connections in the DAC and point it to Prod Source DB keeping the target DB to Dev or QA.
But the thing you need to keep in mind is that if you are doing this then what will happen to the Ids in your tables. What is your data load strategy, is it a full truncate load or is it Update/Insert. Because the Ids in Source DB in Prod and Dev may differ and based on them you might be populating your Ids in Target DB, in this case some issues can creep in.
Try having a truncate load if you don’t have to maintain history in Dev and QA and want the latest data from Prod.
Hope this helps.
Thanks for the input Rohit. I am going to try sometimes this week and keep you posted on my progress.
Again many thanks,
Vas
HI Rohith,
Very good posts. I like your way of explanations. I have ideo on DAC and BIAPPS. As replied above if you have any documents regarding DAC and BIAPPS can you share it, that is like tutorial documents how will be it implemnted in projects, configuration and installation.
Hi Rohit,
Happened to see your blog for the first time. Nice way of presenting.
Keep up all the good work (ofcourse a kind of social work
Thanks,
Sarat
Thanks Sarat….. This is the first time somebody is terming it as Social work
very very nice
Hi..I am sudhakar..I have good knowledge on core DBA concepts and i am bit intrested in OBI ADMINISTRATION too. Can u suggest me, is it gud thing to learn OBI too or shall i continue with core DBA?
Hi Sudhakar,
As I am working on OBIEE I would always suggest its a good thing but frankly speaking its on individual’s interest. Still if you want to know I would suggest you to read about it(start with the basics) and if you find it interesting you can go ahead with it. According to market situation, I would say it has nice future prospects but I would also like to say that learn OBIEE but at the same time don’t loose your core DBA skills.
Moreover, as you said that you have a good knowledge on core DBA concepts, I would definitely like to learn somethings from you. So, please feel free to post material on the DBA concepts so that our readers can also gain something from it.
Leave your response!
Recent Posts
Categories
Archives
Tags
Most Commented
Most Viewed