Oracle EBS 12.2.4与ADF集成：OAF嵌入Hierarchical Viewer无显示问题

Hey there, let's dig into why your ADF Hierarchical Viewer isn't showing up in the OAF RichContent component—especially since you're not getting any error messages to go on. I'll walk through the most likely fixes based on your setup (EBS 12.2.4, JDev 10.1.3.5 for OAF, JDev 11g R2 for ADF):

1. First, Validate Your Destination Function Output #

Your MyOwnDestinationFunction is responsible for generating the content that the RichContent component renders. If it's not outputting the right HTML structure, nothing will show up:

• Test with basic content first: Modify the function to return a simple snippet like <h2>Test RichContent Rendering</h2> and refresh the OAF page. If this doesn't display, the problem is with the function itself (not the ADF integration).
• Ensure proper ADF embedding markup: When you switch back to embedding the Hierarchical Viewer, make sure the function outputs an iframe (or the correct container) that points to your ADF page, and includes EBS session context (like SSO tokens) so the ADF app recognizes the logged-in user.

2. Check EBS-ADF Session & Cross-Domain Compatibility #

EBS 12.2.4 has stricter session handling, so broken integration here can silently block content:

• Verify SSO integration: Confirm your ADF app is set up to accept EBS's single sign-on context. If the ADF page requires a separate login, the iframe will fail to load without throwing a visible error.
• Inspect browser dev tools: Hit F12 to open the developer console, go to the Network tab, and look for requests related to your RichContent component. Check if the ADF page request returns a 200 status, or if there are hidden CORS/frame-blocking errors in the Console tab.

3. Double-Check RichContent Component Properties #

Even small misconfigurations here can cause silent failures:

• Confirm Rendered status: Make sure the component's Rendered property is set to true—it's easy to accidentally toggle this or have a conditional logic hiding it.
• Content Type alignment: Since you're using Content Type: Others, ensure you haven't missed any dependent properties (like Content Source if required for your setup). Some OAF versions expect explicit hints for non-standard content types.

4. Address EBS 12.2.x Content Security Policies (CSP) #

EBS 12.2.x introduced stricter CSP rules that can block embedded content by default:

• Check CSP settings: Look up the FND: CSP Enabled profile option. If it's enabled, you'll need to add your ADF app's domain to the allowed frame sources in the CSP configuration.
• ADF app headers: Ensure your ADF app returns appropriate X-Frame-Options or Content-Security-Policy headers that allow embedding from your EBS domain.

5. Verify the ADF Hierarchical Viewer Works Standalone #

Before blaming the OAF integration, confirm the ADF component itself is functional:

• Directly access the ADF page: Open the ADF Hierarchical Viewer's URL in your browser (logged into EBS) and make sure it renders correctly. If it doesn't, fix the ADF app first before troubleshooting the OAF embedding.
• Check required parameters: If the ADF page needs specific parameters (like a record ID), ensure your MyOwnDestinationFunction is passing these correctly in the embedded URL.

内容的提问来源于stack exchange，提问作者Harry47