Zheng Tech Blog

Mobilizing Your Portal Strategy [CON8944] Nediljko Bilkic - IT Manager, Ross Stores, Inc. JayJay Zheng - Solution Architect, Aurionpro Solutions, Inc. Ashish Agrawal - Sr. Director, Product Management, Oracle Mobile portals must deliver much of the same capability available to desktop users and also provide unique capabilities pertinent to users on the move, all in a form that leverages mobile device capabilities and context signals. Although mobility raises new challenges for portal initiatives, it also brings a world of new opportunities to improve user engagement and business value. Attend this session to learn how Oracle WebCenter Portal is delivering mobile content creation, infrastructure, and collaboration to keep you connected on the go. Additional Information Conference: Oracle OpenWorld Products and Services: MIDDLEWARE: Portal, Content Management, Web

A navigation link can be opened in the current window or a new window. By default it would open ni the current window. There are a number of the predefined URL attribute for a navigational resource. For a complete list of the URL attributes, please refer to here . One of the attribute is " Target". As per the description,  it's the location on the container page where the resource is displayed when it is selected, either in the same browser window ( _self ), a new window ( _blank ), or a popup ( _popup ), or any other location supported by the navigation UI. Is that it? Not really, if you have custom developed your navigation UI. The "target" attribute is nothing special here, as it's just an attribute with a meaningful name. The navigation UI needs to specifically evaluate the attribute and handle it. Here are the two steps to do: 1. apply a swticher on the navigation model node. If the target is "_blank", use the golink component.

Update : The Oracle Patch on the bug has been released: Patch 17328920 : CONTENT PRESENTER THROWS STUCK THREAD AND OOM WHEN UCM RETURNS MANY PROFILES.  In this fix, a system parameter "contentTypeLazyCaching=true" is requested to be added on the JVM startup. Custom code has been added into the ContentTypeFactory.class in the two places: %ORACLE_HOME%/webcenter/modules/oracle.webcenter.content.integration_11.1.1/ucm_spi.jar/oracle/webcenter/content/integration/spi/ucm/factory/ContentTypeFactory.class %ORACLE_HOME%/webcenter/modules/oracle.webcenter.content.integration_11.1.1/content-app-lib.ear/APP-INF/lib/ucm_spi.jar/oracle/webcenter/content/integration/spi/ucm/factory/ContentTypeFactory.class The directory could be either on your local Jdev folder or on the remote WebCenter portal server. The added custom code is a new method getMinimalContentTypes():   public synchronized List<ContentType> getMinimalContentTypes()     throws RepositoryException   {    

Background : It's well documented in the Oracle documentation that Resource Catalog can be filtered at the resource level and catalog level ( link here). Let me re-iterate the details a little bit. Resource level: there is a "visible" property that takes expression language as a value, which are evaluated at the run time as boolean value to determine whether the particular resource should be displayed or not. The value can be "#{true}", "#{false}" or any other valid EL. Catalog level: we can define a Java Bean (a filter class) implementing CatalogDefinitionFilter to apply on a catalog.xml file. In this Java file, we need to implement the API includeInCatalog() which takes two arguments: catalogElement and hashtable objects. The filter class is triggered when the catalog is instantiated.  Although not documented in the Oracle documentation, we could apply the same resource level and catalog level filtering on the navigation model. For any EL based