Publishing a repository enables the Oracle BI Server to load the repository into memory upon start-up and makes the repository available for queries.
Publish repository in distributed mode or shared mode:
When you upload a repository file for publishing, you provide the name and location of the repository to upload and the current repository password.
The published repository is available to all Oracle BI Server clients, not just to Oracle BI Presentation ServicesPublish repository in distributed mode or shared mode:
- In distributed mode, each Oracle BI Server instance loads the repository from its default local directory. Repositories uploaded through Fusion Middleware Control are uploaded to each default local directory. Any changes made to the repository using the Administration Tool affect only the Oracle BI Server component that is associated with the changed repository file.
- In shared mode, each Oracle BI Server instance loads the repository from the shared network location designated as the repository publishing directory. Note that repositories uploaded through Fusion Middleware Control are uploaded to both the shared location and the default local directory for each Oracle BI Server. You typically publish the repository in shared mode when you have multiple Oracle BI Server components in your deployment.
Like the Oracle BI repository, the Oracle BI Presentation Catalog can be published in shared mode, or distributed mode. Each Presentation Services instance loads the Oracle BI Presentation Catalog from the catalog location specified in Fusion Middleware Control.
Login to Fusion Middle ware Enterprise console (http://localhost:7001/em) goto Business Intelligence overview page and click on Deployment
Click on Lock and Edit configuration to release the lock
You can see your rpd name next to the Default RPD : your_rpd_name,if you want to deploy a Shared Repository click on Shared Repository( shared mode)
For distributed mode you need to upload the rpd by clicking on "Browse" button and give the
respective credentials(password)
Next, give the catalog location of Presentation Service for repository.
Click on "Activate Changes" which will save the changes and restart all BI services.
Open the rpd in online mode or check the NQSConfig.ini and instanceconfig.xml file for the newly updated rpd and catalog folders.
Note: See the Nico comments
Hy saichand thanks again.
ReplyDeleteAre you sure that you have to stop the services ?
The repository get a version number incremented each time that the repository is uploaded.
You just need to restart after changes, no ?
Cheers
Nico
hi Nico,
ReplyDeleteThank you so much for your comment
Its my mistake i should mention the error that what i received when i am trying to restart my services
----------------------
Message ID: EM-02694
Message Level: 1
Argument 1: DOMAIN;FAILED_TO_SAVE_CREDENTIALS
Component: AdminServer
Module: oracle.sysman.emai.view.bi.impl.ProgressDialogHelper
Message: Supplementary information regarding operation: DOMAIN;FAILED_TO_SAVE_CREDENTIALS
-----------------------
At this stage i stopped all the services from EM and again did the same procedure it works fine...
Is this the correct process? I agree with you on Version number but what about my error message when i am restarting?
Btw,after restarting the services i did google on error message to find any reference from oracle but some one already posted/faced the same in one thread
http://forums.oracle.com/forums/thread.jspa?threadID=1131390
Once,again thanks for visiting my blog and comments/suggestions on my posts
I think that it says that it can't create a credential entry in the credential store.
ReplyDeleteHere:
http://gerardnico.com/wiki/dat/obiee/credential
In this windows, you enter all password and you can see that you have an entry for the repository (on the picture repository.sampleApp_B001). It contains the password of the repository to start the BI Server.
"Why it fails" is the question. You can try to create them via a WLST script to have more information.
But as the repository name gets a incremental unique number, normally you can't get this error.
Cheers
Nico
Great...missed the credentials entry i will change my post.
ReplyDeleteAppreciate your inputs!
Hi,
ReplyDeleteI guess the reason it fails originally is because of the release configuration step which I guess is missed.
When loading the new RPD a. lock b. change the rpd (provide the correct pwd) c. release the lock. d. then activate the changes... e. Then restart to apply the changes.
If the third step is missed then I guess the error is seen.
Thanks
AnnaRR
Hi Saichand,
ReplyDeleteInstead of placing the catalog in the path and giving the path details, Can we browse the catalog from our local and upload just like we upload the RPD?
Hi,
ReplyDeleteI am getting the below error while uploading the RPD ,am trying to commit the upload action.
Traceback (innermost last):
File "", line 1, in ?
File "", line 609, in invoke
File "", line 1848, in raiseWLSTException
WLSTException: Error occured while performing invoke : Error while doing an invoke. : SEVERE: Element Type: DOMAIN
Element Id: null
Operation Result: FAILED_TO_SAVE_CREDENTIALS
Detail Message: null SEVERE: Element Type: DOMAIN
Element Id: null
Operation Result: FAILED_TO_SAVE_CREDENTIALS
Detail Message: null
Use dumpStack() to view the full stacktrace
Can you pleas help.
Thanks
Mahesh
is there any automatic script not via em that i can use to change the rpd and catalog locations?
ReplyDeletemaybe a detailed explanation to which files should i change?
i found that after the change the admin user don't see the new catalog,
anyone know why? it will help alot.
thanks
Mirit