Panel Customizable Changes Customizable Component Changes

Additional Oracle WebCenter Upgrade Details 16-5 Example 16–4 Show Detail Frame Code of a WebCenter 11g Application cust:showDetailFrame id=showDetailFrame1 text=showDetailFrame 1 displayActions=never showMoveAction=none showMinimizeAction=none contentStyle=background-color:rgb0,255,255 xmlns=http:xmlns.oracle.comadffacescustomizablehtml

16.1.2 External Application Changes

You can associate external applications with portlet producers. Oracle WebCenter Framework defines an external application as any application that implements its own authentication process. That is, an application that does not take part in the single sign-on process of Oracle WebCenter Framework. For more information, see the Working with External Applications section in Oracle Fusion Middleware Developers Guide for Oracle WebCenter. This section contains the following subsections: ■ Overview of External Applications Changes in Oracle Application Server 10g and Oracle Fusion Middleware 11g ■ External Application Upgrade Changes 16.1.2.1 Overview of External Applications Changes in Oracle Application Server 10g and Oracle Fusion Middleware 11g Compared to Oracle Application Server 10g, in Oracle Fusion Middleware 11g, external applications have undergone some changes. In Oracle Fusion Middleware 11g, external applications let you specify shared and public credentials. External applications also let you define an internal name that serves the purpose of external application identifier and cannot be changed after creation and a display name that can be changed. Another distinguishing feature is that in Oracle Application Server 10g, external applications use Metadata Services MDS to store metadata; in Oracle Fusion Middleware 11g, external applications are stored as connections similar to other services like content repository connections. Table 16–3 compares how the distinguishing attributes of external applications map between Oracle Application Server 10.1.3.x and Oracle Fusion Middleware 11g. The table shows sample values for the name, ExtAppId, and GUID attributes. Table 16–3 Distinguishing External Applications Attributes in Oracle Application Server 10.1.3.x and Oracle Fusion Middleware 11g External Application Attribute Sample Attribute Value in Oracle Application Server 10.1.3.x Sample Attribute Value in Oracle Fusion Middleware 11 g Name app1 app1 Also used as the display name of the external application extAppId oracleadfexternalApp sextApp921389557420089 8560.xml app1 SharedCredEnabled Attribute not supported False PublicCredEnabled Attribute not supported False 16-6 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF

16.1.2.2 External Application Upgrade Changes

If your WebCenter 10.1.3.x application relies on external applications, then when you upgrade that application, the associated external applications are also upgraded automatically. For example, when migrating a WebCenter 10.1.3.x application that uses PDK-Java producers dependent on external applications, the external applications are automatically upgraded. While upgrading a WebCenter application, the upgrade utility performs the tasks for an upgraded external application: ■ Uses the name of the 10.1.3.x external application as the internal name ExtAppId of the upgraded application. ■ Updates the producer metadata with the new external application ID. An external application is referenced in the portlet producer metadata through its ID. ■ Migrates the external application metadata from MDS store configured in the WebCenter applications adf-config.xml to connections.xml. ■ Adds the automated login configuration to the project that contains external application portlets. ■ Adds the new attributes, listed in Table 16–3 , to the upgraded external application. ■ Removes the credential provisioning page configured for the project containing external application portlets and the managed bean and navigation rule defined in each project. In Oracle Fusion Middleware 11g, the credential provisioning page is packaged in the external application library. ■ Configures external application libraries, WebCenter External Application Service, and WebCenter External Application Service View.

16.1.3 Portlet Component Changes

When you upgrade a WebCenter application that uses portlets, JDeveloper automatically makes various changes related to portlet tags in the upgraded application.

16.1.3.1 Portlet Tag Changes

In WebCenter 10.1.3.x applications, the adfp:portlet tag represents a portlet in the namespace http:xmlns.oracle.comadffacesportlet. In WebCenter 11g applications, portlet tags are converted to Trinidad HTML Portlet tags. The adfp:portlet portlet tag is migrated to adfph:portlet in the namespace http:xmlns.oracle.comadffacesportlethtml.

16.1.3.2 Attribute Changes

Table 16–4 lists the attributes that are renamed or removed from an upgraded WebCenter application containing portlets. loginEnabled Attribute not supported True GUID Attribute not supported ExtAppbc638395-2860-41ae-a9f f-edfc6b79110f Table 16–3 Cont. Distinguishing External Applications Attributes in Oracle Application Server 10.1.3.x and Oracle Fusion Middleware 11g External Application Attribute Sample Attribute Value in Oracle Application Server 10.1.3.x Sample Attribute Value in Oracle Fusion Middleware 11 g Additional Oracle WebCenter Upgrade Details 16-7

16.2 Content Integration Connections: Migration of Credentials to External Applications

Content integration capabilities of Oracle WebCenter enable you to integrate decentralized content located across various content repositories, such as Oracle Content Server, Oracle Portal, or your file system, into your WebCenter applications. This section describes the authentication methods supported in Oracle WebCenter 10.1.3.x and Oracle WebCenter 11g applications. It also describes how credentials are migrated to external applications for content repository connections when you upgrade a WebCenter 10.1.3.x application. To integrate content from a content repository into your WebCenter application, you need to create a connection to the required repository. In Oracle WebCenter 11g, while creating a content repository connection, you can set the authentication method to any of the following: ■ Identity Propagation : In this method, no credentials are passed to the content repository. Instead, the repository connector uses the current users identity as determined from the Java security context. This method is generally used when the application and the content repository use the same identity store to authenticate users. ■ External Application : This method can be used in all other cases where the current user’s identity should not be propagated directly to the content repository. Table 16–4 Attribute Changes in an Upgraded WebCenter Application Containing Portlets Attribute Change in the Upgraded Application isSeededInteractionAv ailable This attribute is renamed to displayActions. The upgrade utility migrates isSeededInteractionAvailable=false|true to displayActions=onHover|always, respectively. isMinimizable This attribute is renamed to showMinimizeAction. The upgrade utility migrates isMinimizable=false|true to showMinimizeAction=none|chrome, respectively. isMaximizable This attribute is renamed to showMaximizeAction. This change is applicable only for HTML portlets. The attribute is not available for rich-text portlets. The upgrade utility migrates isMaximizable=false|true to showMaximizeAction=none|chrome, respectively. isMovable This attribute is renamed to showMoveAction. The upgrade utility migrates isMovable=False|True to showMoveAction=none|menu, respectively. contentInlineStyle This attribute is renamed to InlineStyle. text This attribute is renamed to title. portletType This attribute is removed. isLinkModeAvailable This attribute is removed. showRemoveAction This attribute is removed from an HTML portlet. In Oracle WebCenter 11g, this attribute is available only for rich-text portlets. expansionMode In JDeveloper 11g, the values allowed for this attribute are normal and minimized. In a WebCenter 10.1.3.x application, if the value is set to maximized, then the attribute is removed from the upgraded application.