It is often seen that when implementing custom security we face this issue below are the few useful steps for debugging.
->Check if the user has the acess to bipulisher in the privilages.
->Check it the SOAP acess is granted to BISystem users.
->Check if OBIPS and java Host are up and running.
->If SSL is enabled make sure BIP server protocol is also https instead of http.
Furthur debugging also possible by checking the bipublisher.log file in
$FMW\user_projects\domains\bifoundation_domain\servers\AdminServer\logs\bipublisher.log
For enterprise installation please look for the bipublisher.log in managed server logs instead of admin server logs.
$FMW\user_projects\domains\bifoundation_domain\servers\bi_Servern\logs\bipublisher.log
We can also view this log from the em.
->Check if the user has the acess to bipulisher in the privilages.
->Check it the SOAP acess is granted to BISystem users.
->Check if OBIPS and java Host are up and running.
->If SSL is enabled make sure BIP server protocol is also https instead of http.
Furthur debugging also possible by checking the bipublisher.log file in
$FMW\user_projects\domains\bifoundation_domain\servers\AdminServer\logs\bipublisher.log
For enterprise installation please look for the bipublisher.log in managed server logs instead of admin server logs.
$FMW\user_projects\domains\bifoundation_domain\servers\bi_Servern\logs\bipublisher.log
We can also view this log from the em.
No comments:
Post a Comment