Full Set of WebLogic Portal 9.2 Samples Now Available
Josh Lannin's Blog |
August 13, 2006 7:59 PM
|
Comments (12)
The WebLogic Portal CodeShare on Dev2Dev has been updated with a set of samples that exercise a range of new capabilities introduced with the 9.2 release. These samples leverage everything from advanced WSRP features to a very capable set of Content Management portlets with RSS feed production. We hope that these samples help jump-start your 9.2 development efforts and look forward to more contributions from the WLP community.
Note, some of these samples are authored by BEA employees; but there is no official BEA product support for the samples themselves.
The samples include:
Portal Framework:
- Adrenaline Sample – Adrenaline is a new feature available in WebLogic Portal 9.2 that allows developers to quickly embed portlets within any JSP. This allows developers of non-portal web applications (i.e., without a portal based navigation scheme) to add either local portlets or federated WSRP portlets to any place in their page. Communication to and from the server is handled through AJAX (default) or IFRAMEs, so that there is no need to refresh the entire JSP when interacting with a specific portlet.
Content Management:
- Content Management Sample – This sample allows the user to login, browse the repository, create, display and edit content, modify content’s security settings, search for content (using metadata and full-text search functionality), publish repository content to an RSS feed and manipulate the application’s cache settings.
WSRP:
- User Profile Sample– Demonstrates using remote user profiles for both JSR 168 and other portlet types.
- Username Token Sample – Showcases leveraging the Username Token (UNT) to authenticate the user on a WSRP producer, which may be used to interop with 3rd party producers and consumers that don’t support SAML.
- IPC / JSF Sample – This sample demonstrates interportlet communication between federated (WSRP) JavaServer Faces portlets.
- Interceptors Sample – This sample demonstrates how to author your own interceptor for caching, form encoding, and text replacement.
Security:
Communities and Search:
- Search Controls Sample -Groupspace searchControls are the beehive control implementation of the CM search API's. These samples demonstrate the ability to perform three types of searches: 1) Search GroupSpace content 2) Search all or selected non-Groupspace BEA Repositories. 3) Search files systems and web pages.
- Community Sample – This community sample is intended to demonstrate how communities work within the portal framework by demonstrating easy exploration of community functionality in the sample. The sample includes portlets for making changes to any community's settings, inviting users to a community, community registration, new desktop and community templates creation from existing streamed desktops and communities, and provides a listing of all communities.
- GroupSpace Versioning Sample – This sample explores an approach to adding very simple versioning to GroupSpace. Out of the box, GroupSpace does not provide a version history for the artifacts (Issues, GroupNotes, Documents, etc.) it manages but simply reports the date/time and author of the original creation and the most recently modification. If you have a need to maintain a version history for each item, this sample can give you some ideas for how to implement this functionality on top of GroupSpace with minimal changes.
- Dynamic Content Tags Sample – The Dynamic Content tags provide the ability to update a small part of a JSP page within a PageFlow-based portlet using an AJAX request. This allows for parts of the page to be updated without the need to perform a full portal request. These AJAX requests are both smaller and quicker than full portal requests, and therefore provide a much more responsive user experience when interacting with a portal application. A sample application is included along with a description of each tag and an explanation of how it is used.
Comments
Comments are listed in date ascending order (oldest first) | Post Comment
-
Do you have any sample code that demonstrates how to use the DragDrop tag library? I have not been able to find any examples in BEA's documentation. Please help.
Posted by: divinedsa on May 14, 2007 at 12:15 PM
-
Have you reviewed this page ?
Posted by: jlannin on May 16, 2007 at 8:16 AM
-
Yes, I have. But I am not able to figure out how to access the draggable resources and drop zone in my controllers. Basically, how can I do the actual drag process in code.. that is, to move my resource from one place to another. I am looking for sample code to do that. Thank you.
Posted by: divinedsa on May 16, 2007 at 8:42 AM
-
The User Profile sample does not contain complete installation instructions. Can someone update the install instructions with more detail?
Posted by: barrym on July 18, 2007 at 4:49 PM
-
Are federated user profiles supported if I use a wsrp-enabled WLS 9.2 producer domain?
Posted by: barrym on July 18, 2007 at 4:54 PM
-
Hi mdiaz,
Thanks for your response. Actually, I'm asking about WL*S* domains, not portal domains and the answer turns out to be "No". You have to use custom data transfer to pass the user profile parameters from a WLP 9.2/consumer to a WLS 9.2/producer via a backing file/preRender on the consumer. One little nuance of this is that it appears that both the producer and consumer must be deployed in an EAR file. However, the docs don't really make this clear and I did not test it extensively to verify.
Posted by: barrym on July 24, 2007 at 11:57 AM
-
Barry - apologies - I missed the point that you were asking about WLP to WLS only domains. And just to elaborate a bit - in a WLS only domain what is implemented is what WLP calls the WSRP Simple Producer. In the WLP 9.2 Federation guide it says:
A simple producer supports only some basic features of the WSRP protocol. These basic features
do not require the producer to be deployed in a full WebLogic Portal domain. You can, for
example, deploy a simple producer in a basic WebLogic Server domain.
A simple producer:
Does not depend upon WebLogic Portal features - A simple producer cannot take
advantage of WebLogic Features features such as user management and personalization.
Does not depend on WebLogic Portal APIs - Again, a simple producer cannot rely on
any WebLogic Portal dependencies.
Does not support registration - Registration allows a producer to associate portlets and
any portlet customization data with the consumer that is interacting with it. The producer
can also use the registration to tailor the scope of the portlets offered to specific consumers.
Does not support event handling - You cannot use the event handling API with a simple
producer.
So - yes as you said you are absolutely correct that it is not possible to transfer WLP user profile properties (UUP) to a WLS only domain - because this would rely on WLP api's that are not available in the simple producer. Others have done what you did to expand the capabilities of the simple producer via custom data transfer. Just watch out for the other limitations as well. I will try and update the edocs the documentation to be clearer about these limitations around UUP and a WLS only domain
regards - Marcus
Posted by: mdiaz on July 25, 2007 at 9:24 AM
-
I have .war file. I request you to please guide me how to deploy this in Weblogic Portal 9.2.
Thanks in advance only.
Posted by: prasoon23 on September 11, 2007 at 2:07 AM
-
Hi all, we actually are in a project with WLP 10.0 and would urgently need JSF IPC (inter portlet communication) samples based on WLP 10.0
If any of you has successfully done or an good idea how to we would appreciate very much your tipps and recommendations.
#Peter
Posted by: ppoess on September 12, 2007 at 9:41 AM
-
can any one tell me the url of the portal administration iam not able to get that url i tried with sum urls but not worked .
i have installed the portal v 9.2.2 my workshop is working properly but iam not able to get the weblogic portal administration page.
please help thanks in advance .
Any Help regarding this will be appriciated
Posted by: mchokkakula1 on January 7, 2008 at 6:18 AM
-
Mchokkakul1- this is a good question to put on our forums (or checking with support) rather than a blog post comment: http://forums.bea.com/forum.jspa?forumID=2044
I would generally suggest that in Workshop you highlight the enterprise application in the project view then use the workshop command to run the portal admin tools.
Posted by: jlannin on January 10, 2008 at 9:26 AM
|
