BEA Weblogic Portal

View: [ 2009 | 2008 | 2007 | 2006 | 2005 | 2004 | 2003 | 2002 ]

Articles
  

Articles:
  • Sharing Data among Federated Portals: Using WebLogic Portal, Tangosol Coherence and WSRP by Jason Howes   - [Clicks: 61]
    Learn how to combine BEA WebLogic Portal's WSRP extensions with Tangosol's Coherence product to efficiently share data between a Producer and its Consumers.
    http://dev2dev.bea.com/pub/a/2005/11/federated-portal-cache.html - Nov, 2005
  • Portal Menus and Windowed Controls by Gerald Nunn   - [Clicks: 106]
    In Internet Explorer (IE), dynamically positioning HTML elements in an overlapping fashion can lead to some elements hiding others. Unfortunately, this can occur in BEA WebLogic Portal 8.1 when multilevel menus are used on a portal page that contains specific HTML entities such as the SELECT element or ActiveX controls. The undesirable result is that the menu is partially hidden. This article shows an HTML technique that eliminates this problem by ensuring that menus are rendered above all other elements on the portal page.
    http://dev2dev.bea.com/pub/a/2005/04/portal_menus.html - Apr, 2005
  • Inside WSRP by Subbu Allamaraju   - [Clicks: 182]
    BEA WebLogic Portal 8.1 lets portals consume remote portlets by using the Web Services for Remote Portlets (WSRP) protocol. In most cases, portlets originally built and deployed for use by local portals will function the same when you move those portlets to remote WSRP Producers. WebLogic Portal and its WSRP Consumer and WSRP Producer capabilities are designed to shield portlets from the location of the portal. However in some cases, you may find that certain portlets behave differently or incorrectly. The most common cause of such behavior is implicit or explicit assumptions such portlets might have made about the location of the portal. In this article, I discuss some of the most common assumptions, and why such assumptions can interfere with the WSRP protocol in undesirable ways. My goal is to highlight best practices that you can employ to make portlets WSRP-friendly without necessarily compromising functionality.
    http://dev2dev.com/products/wlportal81/articles/inside_wsrp.jsp - Mar, 2005
  • Application Architecture for Applications Built on BEA WebLogic Platform 8.1 by Bob Hensle   - [Clicks: 217]
    This article provides architecture and application best practices for software applications built using the BEA WebLogic Platform 8.1. The technologies discussed include BEA WebLogic Server, WebLogic Portal, WebLogic Integration, WebLogic Workshop, and Liquid Data for WebLogic. This article is intended for enterprise architects and application architects and uses the 4+1 View Model to describe the architecture of an application built with the WebLogic Platform 8.1.
    http://dev2dev.bea.com/products/wlplatform81/articles/application_architecture.jsp - Feb, 2005
  • URLs in WebLogic Portal 8.1: A Tutorial by Subbu Allamaraju   - [Clicks: 188]
    One of the core responsibilities of the BEA WebLogic Portal 8.1 framework is to create URLs consistently and correctly so users can interact with various portlets within the context of a portal page. The purpose of this article is to show you the plumbing behind the URL creation process in WebLogic Portal. In this article, I will discuss how WebLogic Portal creates URLs, the different kinds of URLs that can be created, the APIs and layers behind URLs, and what happens to URLs when you offer or consume portlets using Web Services for Remote Portlets (WSRP). As we walk through the URL creation process, I will also highlight some best practices. After reading this article, you will be able to avoid most of the common pitfalls with URLs and be able to provide a consistent user experience with your portlets.
    http://dev2dev.bea.com/products/wlportal81/articles/urls_in_portal.jsp - Feb, 2005
  • Portlet Caching by Gerald Nunn   - [Clicks: 112]
    WebLogic Portal 8.1 includes a number of features that enable developers to maximize the performance of their site. One of these features is the caching of portlet content through the use of the Render Cacheable property. While a basic description of the property can be found in the help documentation, this feature is often misunderstood. The purpose of this article is to provide a detailed examination of this property and discuss when it should and should not be used.
    http://dev2dev.bea.com/products/wlportal81/articles/portlet_caching.jsp - Jan, 2005

[Top]