Click Logout. Implementing Portlet Security

7-48 Oracle Fusion Middleware Developers Guide for Oracle Portal JNDI variable and is therefore less secure and not the recommended method to use. For example: title = UrlUtils.escapeStringdata.getPortletTitle;

7.2.8 Controlling the ExportImport of Portlet Personalizations

The exportimport facility of Oracle Portal is a multi-purpose tool for moving your portal objects, such as portlets, between instances of Oracle Portal. For example, you might use exportimport to move objects from a development environment to a stage environment and then, finally, to a production environment. You might also use exportimport to move pages and page groups between Oracle Portal instances, or to move Web providers from one machine to another. For more information about exportimport in general, please refer to the Oracle Fusion Middleware Administrators Guide for Oracle Portal. Because portlet default settings can be set by the administrator and then changed by the user, they require some special consideration when you import and export them. To simplify the transport process, Oracle Portal provides default functionality that handles administrator personalization data that is, data created using Edit Defaults mode for you. When a portlet is exported, the default personalization data stored using PDK-Javas PreferenceStore mechanism is exported with the portlet by default. Hence, when the portlet is imported into a target instance of Oracle Portal, this data is imported along with it. As a result, the portlet instances default settings are maintained when the portlet is moved from one portal instance to another. 1 The aforementioned behavior is provided to you as a convenience and it requires no action on your part to leverage. You might, however, want to exercise more granular control over the export of personalization data than that provided by the default functionality. To implement your own requirements for exportimport, you can make use of the programming interface to augment or override the default handling of personalizations. If you use the PDK-Java preference store mechanism, the exportimport of your Edit Default personalizations is built-in and requires no additional effort on your part. This default exportimport of administrator personalizations relies on the PDK-Java preference store. If you have created your own preference store mechanism for example, a file or database preference storage system, then you also must implement your own exportimport support that performs the following functions: ■ Exports personalizations. This functionality must at least export administrator personalizations, but it could optionally include user personalizations, too. ■ Imports personalizations. Note that this functionality must reflect whatever you implemented for export. For example, if you allow the export of both administrator and user personalizations, then the import functionality must support both as well. The exportimport functionality for personalizations requires that your Oracle Portal instance and provider are on Release 10.1.2. Exportimport of personalizations behaves the same regardless of the location of your provider, which can be either of the following: ■ in the default Oracle Containers for Java EE of the Oracle Application Server, where the Oracle Portal instance is different. 1 User personalization data for Oracle Portal objects is never exported. This restriction applies to portlets as well as other objects, such as pages.