When integrating content that uses the client to store its state like Adobe Flash or an Iframe connecting to a legacy backend inside a portlet the problem arises that when you navigate away from the page and come back the client side state is lost. The portlet and its contents just re-render and an end user could potentially lose work he has performed with those applications.
The article describes how to adjust the theme Server side aggregation mode to render an iframe or flash or another external resources when the page is selected instead of rendering content. It keeps the backend content hidden in an invisible frame and shows and hides it accordingly. Frame technology was used to store the other applications and the theme renders itself as well as those frames. The article lists the steps to implement the customization.
If you want to use Client Side aggregation please see the following article:
Integrating iframes, flash and other applications into Portal without losing the client side state using Client Side Aggregation
High level architecture:
- Theme will be adjusted to load frameset and load itself inside the first frame - this frame would be visible by default
- Client side content (flash, iframes, ...) will be rendered inside the other frames
- If certain pages or are selected or other actions are triggered the Portal content area is hidden and the content of the frameset is displayed
- If a Portal page is selected the other frame is hidden and the Portal content area is made visible again
Steps to integrate: