|
|
Techniques for surfacing UI components into WLP
Bangaly Traore's Blog |
April 21, 2008 6:14 AM
|
Comments (0)
There are many ways to surface UI components into your portal. The table below list the pros and cons of various approaches I've used on site.
As with all architecture, there are pros and cons to an approach. Ultimately, it's the architect's role to weigh these pros and cons and deliver
an optimal solution.
In the near future, I will be discussing the role that WLP plays in delivering presentation services and how to integrate WLP into your company's SOA fabric.
| Primary Objective |
WSRP |
Shared Library |
Web Clipping |
Adrenaline
Portlet Publishing |
Native
(running in portal container) |
Runtime Independence:
- If you require the ability to deploy new portlets at runtime.
- Deploying producer to fast cluster w/ zero downtime architecture can ensure that performance and availability requirements are met
- WSRP deployment requires more detailed strategy when migrating between environments and to ensure display of static resources (images/buttons)
- Developing Ajax functionality (RIA) w/i portlets prior to WLP92 can be a little tricky. Since 92, support is better but still not as easy as with the other approaches
- Performance is less than shared lib and native options assuming that portlet processing on consumer hardware is less than latency introduced by network and SOAP overhead
- Portlet producer can be deployed to WLS domain
|
X |
|
|
X |
|
Performance:
- Shared (Optional) libraries are defined in the J2EE 1.4 specification
- Shared Library and Native portlets offer the highest performance.
- The advantage of shared library is that portlet code is not bundled in portal EAR therefore updates can be provided w/o updates to EAR.
- Adrenaline is ideally suited to surface portlets deployed remotely in Portal consumer. This is faster than WSRP however doesn't support:
IPC, runtime independence, injection, identity propagation, sharing data between consumer and producer
- Any updates to native or shared library portlets will require redeploying portal EAR which will cause downtime.
|
|
X |
|
X |
X |
Surfacing portlets (new functionality) into legacy applications:
- All new functionality can be implemented in the portal. The benefit is that this new functionality can be exposed through the portal or legacy web application thus ensuring that new functionality is only written once.
|
|
|
|
X |
|
Ajax support:
- If you wish to use Ajax within a portlet to interact w/ server
|
\ (better in WLP10x) |
X |
\ (Ajax or any heavy JS page may be problematic because clipping engine may remove JS from head) |
X |
X |
Integrating Legacy application:
- Assumes that legacy UI conforms to consuming portal Look and Feel/style guide
|
|
|
X |
|
|
WSRP catch all:
|
X |
|
|
|
|
Comments
Comments are listed in date ascending order (oldest first) | Post Comment
|
|
