Siebel integrated Obi report

Business Requirements:

1. The report interface of obiee needs to be displayed in Siebel, so that the current user SSO To Obi can

2. Implement Data Security Control Based on login users in Bi

3. view security control similar to user responsibilities is implemented for each report in Siebel, refined to the user, and the visibility control of the job on the report

4. Report Classification Management in Siebel

5. About 100 reports

 

Solution design:

1. SSO Bi and Siebel use OAM to achieve single-point login is troublesome. Considering that bi user authentication can be customized through the database, Siebel user data is synchronized to the Bi User table every day.

Including username and password. Use the Bi password field bisecpwd associated with the Siebel user for the password (the Encryption Policy can be set freely)

2. Use symbolic URL for report Integration

When designing a report, each bi report corresponds to a specific URL path. The report path and symbolic URL string are stored as BC objects, and the access group mvg is added to the report BC,

Add the type field and import the report URL path and category in batches.

 

The symbolic URL ARGs is designed as follows:

Configure Bi report Applet in tools, Applet Class = cssframelistweb, Applet webtemplate = analytics Applet

Configure BC:

 

3. Configure the directory tree and report applet to load reports based on nodes.

This function requires the isrecordsensitive = true parameter to be added to the symbolic URL ARGs to refresh the interface, that is, to select a directory node and reload the report.

Configure the tree applet, copy the Organization tree applet, and modify the BC and Applet corresponding to the Tree node without recursion.

Final effect:

 

4. The integration of Bi can have ended, but a product bug has been found.

The official description is as follows:

"In Siebel view integrated on any external webpage, if isrecordsensitive parameter is used, clicking mvg, pick applet, or popup applet such as record will cause sessionwarning and component crash"

This bug has QF for 8.0.0.5 or above and is included in 8.1.1.5 patchset.

Engineering developed quick fix for this issue on top of 8.0.0.5.
The fix details:
Bug ID: 13113684
Platform available: Linux, Solaris, Windows
Product Certified: Sia
Ages certified: Lang independent
Base required: Fix Pack 8.1.1.5 [1, 21229]
Patch Abstract:
8.1.1.5 21229 SIA limit 0540 sebl_aru
Qf install doc:
Doc is named readme.html and is located under
P13111_4_811_linux_1of2.zip
P13111_4_811_solaris64_1of2.zip
P13111_4_811_winnt_1of2.zip

However, if the project is stable, I don't want to upgrade it. I plan to continue using version 8114. So Oracle gave workaround, which is to write browser script on the directory tree applet, to simulate reaching the refresh view without isrecordsensitive ARGs:

 

// In the applet_load event:
Function applet_load ()
{
Applet =This;
}
// In the applet_changerecord event:
Function applet_changerecord ()
{
SetTimeout ("Refresh ()", 10 );
}
// And added the following function to the General Declaration:
Function refresh ()
{
Applet. invokemethod ("Toggleto");
}
 

The results can indeed be achieved, but it seems that this workaround itself has a bug, and it actually has a QF, and you can see MetalinkArticle[ID 1072082.1]

However, this is not the case currently, so this patch is still unavailable.

 

In the end, there is a problem with page integration, but workaround can also solve the problem. It converts the view security of Bi reports to the security of path records of Bi reports, this solution is very good, at least I think so.