Hi,
Our System landscape:
- We have 2 BW systems each in a different domain. (one in .sap domain and the other in .hr domain)
- Our Enterprise portal & Business Objects are all in .sap domain.
- Both the BW systems are configured to accept Single sign on tickets and are trusted systems with the portal.
- All involved URLs use the full qualified domain names of the involved systems.
- SAP Authentication is configured on our BusinessObjects Enterprise system.
Single signon works flawlessly when the iview to be integrated is based on the BW system in the .sap domain (same domain as EP & Business Objects). But when the iview is based on the BW system in hr domain, Business Objects throws a "Request Processing failed (XLS 000009). Cannot connect to OLAP Source" error. This indicates that the SAP Logon token passed by the portal is invalid and cannot be used to login to the BW system in the hr domain.
The system connection test in portal to the hr BW system comes back successfully. We actually have visual composer iviews directly based on the hr BW system (without Business Objects) and SSO works fine.
After further investigation, we know that the portal is only passing a SAP Logon ticket based on the BW system in the .sap domain. I found this because we did an alias in Business Objects for an id which exists in both the BW systems and then SSO works for both iviews. But aliasing always doesnot work because the users in both the systems are different in most cases.
Trying to figure out if there is any other way to do it without aliasing. We only use SAP Logon tickets for Portal authentication.
Any help or pointers in the right direction are highly appreciated.
Thanks & Regards
Spoorthy
