Preferred portlet implementation approach in 10.3

what should i use to implement portlets in WL Portal 10.3: struts, page-flow, jsf? i need something which is stable, time-tested and reliable.

In my opinion page-flow was the best suited and most easily maintained. But Oracle has killed it and so new work probably shouldnt use it. The same should apply for struts, what works today will probably continue working , but dont expect to see too much new stuff here.
JSF is recommended by Oracle. There is a whitepaper by Peter Laird which explains some stuff. There are also only a couple of supported frameworks if I recollect correctly. I detest JSF , but thats just my opinion :), if you are familiar with JSF you should probably go for it.
JSR286 is probably reasonable, but not supported yet. JSR168 is an extremely crippled spec (again my opinion).
So in summary , probably JSF.

Similar Messages

BW Implementation Approach

Hi Guys,
I am looking for the ASAP Paper on BW Implementation Approach. Which details at length how do we go about implementating it. With R/3 implementation together or after R/3. Cant find it on Sapnet though.
Can anyone help me with the link please ?
Cheers
Kirk

Hi Kirk,
As for the timing, BW in itself can function without a SAP environment all together as it could be implemented into any Landscape. With or After R3? Well with is always a better approach seeing that MasterData issues could be resolved at an early stage. Another reason is for modeling purposes. There are so many variables to consider that depending on the landscape and the future development and modules that you will be implementing it could go any route.
Personal suggestion based on experience is to do it with the R3 implementation, but in rythm with the implementation. Keep in mind that the whole architechture of BW Modelling needs to adapt to all the different source systems - you probably know this - and that this could really influence the decission on when what will be done.
If you do find that ASAP papare you are looking for, plz drop me a msg...
Regards,
Caz

Implementation approach/Guidelines for MDS.

Hi Team,
I am looking for a document which can give me the implementation approach or guidelines for Master Data Services(MDS).
Appreciate your quick help in this.
Thanks
Arsa.

Arsa,
There is a paper: Implementing
a Phased Approach to Master Data Management from SQL Server 2008 R2 but is still relevant.
The complete series is here: Organizational Approaches to Master Data Management
I would also recommend is the: Master Data Services Support Site
Hope this helps.
Reeves
Denver, CO

GRC 10 implementation approach

Hi All,
Am in the process of implementing GRC 10 with the following components for a pharma client.
Access Risk Analysis (ARA)
Access Request Management (ARM)
Emergency Access (Firefighter)
Business Role Management (BRM)
I just wanted to know your views on what kind of approach is better?. Please comment your views with your best approach.
My view is to first implement ARA and EAM together and then go ahead with ARM and BRM packed together.
Thank You for your idea.

Hello Mani,
Apart from technical details provided by Madhu and Plaban,some more additional information
As per my understanding any successful implementation will follow the ASAP methodology,check the below link for information on ASAP methodology
Basic understanding on ASAP Methodology for beginners
You need to define resources and time line before start the project,check the below link
What is the ideal composition of an implementation team
also check the below threads which gives additional information
Implementation of GRC AC 10.1
GRC 10 implementation | SCN
While implementing if any issues Forum will help you.
All the best!!!
Regards
Baithi

Portlet Implementation

I currently work for an ASP that uses a non-Oracle infrastructure (Vignette) to serve our product.
We are looking into serving our app. as a portlet in Oracle Portal Server. I've looked through quite a bit of documentation and am not quite sure what I need to do on our side to allow our application to be viewed as a portlet within Oracle Portal server. Any help would greatly be appreciated. Thanks in advance.

Jason,
To expose your content to Oracle Portal, you need to create a Web Provider - see the Java Portal Development Kit (JPDK) which is distributed as part of the Portal Development Kit (PDK) - available via download from http://technet.oracle.com/
The JPDK defines a framework for creating and managing portlets. In the simplest case, you need to create an xml file (provider.xml) that defines the set of portlets belonging to a provider. For each portlet the minimum you need to do is provide code to render your portlet - this could be a static html file, a JSP, a servlet or a java method.
Once you have downloaded the JPDK, look at the samples. There are plenty of them ranging from the simplest hello world portlet to mini applications. If you have more questions once you have looked through the samples, post another message

Planning implementation approach

Hi guys,
I'm curious about a peculiar approach for designing planning application, by simply making all members (accounts, entities,...) -regardless of their number or any other criteria, as "NeverShare" as oppose to using Dynamic Calc/Store etc (the normal way I'd say).
Have you seen this before? if so what do you think?
This is not a technical issue, just need to know what do you think.
Cheers,

When the storage type of members is Never Share or Store (Dont want to dig into Dynamic Calc and Store) Essbase reserve storage space, less is the block size faster is the calculations, My general take If Account is dense, few of them:
1. Will Identify the members which are actually not needed to store values: Ex:
Ratios:
- Sales Ratio
- Margin Ratio
In such type of cases we can make Ratio as Label only.
2. Dynamic Calc: Rest of the parents can be Dynamic Calc (Though Exceptions are there),
3. Will use Shared Members Instead of Member formula to make calculations faster,
4. There shouldn't be a Stored or Never Share Parent of Dynamic Calc Members.
If you want to understand more then for the outline you are taking about, click on that outline in EAS console and click on Optimize. Though not a perfect way but this will optimize the outline up to a certain extant then perform customer specific changes.
Cheers..!!

Announcing: Developing JSF Portlets with WebLogic Portal Whitepaper

Just Released: Developing JSF Portlets with WebLogic Portal Whitepaper
A supplemental developer's guide has been published to help guide WLP 10.x customers that wish to use JSF as the web framework for building portlets on WebLogic Portal. This is a sizable document (150 pages) that covers a large number of topics. It also coaches developers on best practices and common pitfalls.
Important: It also clarifies the supported configuration of JSF within Portal Web Projects. Workshop for WebLogic by default configures a web project in a configuration that is not supported by WebLogic Portal. The guide explains how to address this:
* Change from the unsupported MyFaces JSF implementation to the supported Sun Reference Implementation (RI)
* Change from the unsupported "client" STATE_SAVING_METHOD to the supported "server"
The guide can be downloaded here:
http://download.oracle.com/technology/products/weblogic/portal/weblogic-portal-jsf-whitepaper.pdf
To help internet searches locate this document, the table of contents is reproduced below:
Introduction
1.1. Prerequisites...................................................................... 8
1.2. Applicable Versions............................................................ 8
1.3. Native Portlet Bridges and Standard Portlet Bridges .......... 8
1.4. JSF Portlet Support Roadmap ........................................... 9
1.5. Whitepaper Structure ....................................................... 10
1.6. Look Before You Leap ..................................................... 10
1.7. For More Information........................................................ 10
Part 1: Converting JSF Applications into Portlets
2. IDE Support for JSF Portlets Chapter ...................................... 12
2.1. Workshop for WebLogic – WebLogic Portal's Supported IDE 12
2.2. Workshop Features for JSF Support in WebLogic Portal.. 12
3. Introduction to JSF Portlets Chapter ........................................ 18
3.1. Creating Your First JSF Portlet......................................... 18
3.2. Essentials of JSF Portlet Views........................................ 21
3.3. WebLogic Portal Artifacts................................................. 22
4. Configuring JSF within WebLogic Portal Chapter..................... 24
4.1. JSF Library Modules in WebLogic Server ........................ 24
4.2. Installing the JSF Libraries into a Portal Web Project ....... 25
4.3. JSF Configuration Settings............................................... 27
4.4. Configuring JSF 1.2 ......................................................... 29
4.5. Building an Unsupported JSF Implementation Library Module 31
4.6. Faces Configuration is Web Application Scoped.............. 31
5. Navigation within a JSF Portlet Chapter................................... 33
5.1. Navigating within a Portlet with the JSF Controller ........... 33
5.2. Redirects.......................................................................... 34
6. Namespacing Chapter ............................................................. 35
6.1. Namespacing Managed Bean Names.............................. 35
6.2. Client ID Namespacing with the View and Subview Components 35
6.3. Client ID Namespacing with the WLP NamingContainer .. 36
7. Logging, Iterative Development, and Debugging Chapter ........ 39
7.1. Logging............................................................................ 39
7.2. Iterative Development ...................................................... 39
7.3. Debugging ....................................................................... 40
8. Custom JavaScript Chapter ..................................................... 42
8.1. DOM Manipulation within a JSF ....................................... 42
8.2. Form Validation within a JSF Portlet ................................ 45
9. Preparing JSF Portlets for Production Chapter ........................ 46
9.1. Configuration.................................................................... 46
9.2. Performance and Scalability............................................. 47
9.3. Security............................................................................ 49
9.4. Localization...................................................................... 50
Part 2: Interacting with the Portal Environment
10. Native Bridge Architecture Chapter ...................................... 54
10.1. Container Architecture Overview.................................. 54
10.2. Container Architecture.................................................. 54
10.3. Container Interactions .................................................. 55
11. Interportlet Communication Chapter .................................... 56
11.1. Using Session and Request Attributes for IPC (Anti-pattern) 56
11.2. Using the WLP Event Facility for IPC with JSF Portlets 56
11.3. Notifications ................................................................. 60
11.4. Comparison of the IPC Approaches ............................. 60
12. Scopes Chapter ................................................................... 62
12.1. Conceptual Scopes for Standard JSF Applications ...... 62
12.2. Conceptual Scopes for Portal Applications................... 63
12.3. Implementation Patterns for Portal Scopes .................. 63
13. State Sharing Patterns Chapter ........................................... 66
13.1. State Sharing Concepts ............................................... 66
13.2. HttpSession Versus HttpServletRequest ...................... 66
13.3. Base Code for HttpSession Patterns ............................ 67
13.4. Single Portlet Pattern ................................................... 68
13.5. Multiple Portlet Patterns ............................................... 69
14. Rendering Lifecycles Chapter .............................................. 77
14.1. WLP and JSF Lifecycles .............................................. 77
14.2. Invocation Order of WLP and JSF Lifecycle Methods... 77
14.3. Accessing WLP Context Objects from JSF Managed Beans 78
15. Portal Navigation Chapter .................................................... 80
15.1. Programmatically Constructing JSF Portlet URLs ........ 80
15.2. Changing the Active Portal Page.................................. 80
15.3. Redirects within a Portal............................................... 83
16. Ajax Enablement Chapter .................................................... 85
16.1. Ajax in JSF Portlets...................................................... 85
16.2. Partial Page Rendering Pattern.................................... 85
16.3. Stateless API Request Pattern ..................................... 86
16.4. Portlet Aware API Request Pattern .............................. 87
16.5. Controlling the WLP Ajax Framework........................... 91
17. Additional WLP Features Chapter........................................ 93
17.2. Portlet Container Features ........................................... 93
17.3. Portal Container Features ............................................ 98
18. Example: Implementing a Login Portlet Chapter .................. 99
18.1. Login Portlet Motivation................................................ 99
18.2. Login Portlet Design..................................................... 99
18.3. Login Portlet Implementation...................................... 101
Part 3: Integrating Third Party Libraries
19. Integration Overview Chapter............................................. 111
19.1. Types of Libraries....................................................... 111
19.2. Roadmap for MyFaces Trinidad and ADF Faces Rich Client 111
20. Using the Facelets View Technology Chapter.................... 113
20.1. Introduction to Facelets .............................................. 113
20.2. Configuring Facelets Support ..................................... 113
21. Using the Apache MyFaces Tomahawk Component Library Chapter 115
21.1. What is Apache MyFaces Tomahawk? ...................... 115
21.2. Support for Tomahawk in WLP................................... 115
21.3. Tomahawk Component List........................................ 116
21.4. Installing and Configuring Tomahawk......................... 119
21.5. Resolving the Duplicate ID Issue................................ 120
21.6. Referring to Resources .............................................. 120
21.7. forceId Attribute.......................................................... 124
21.8. File Upload................................................................. 125
22. Using the Apache Beehive Navigation Controller Chapter . 126
22.1. Apache Beehive Page Flow ....................................... 126
22.2. JSF and Page Flows .................................................. 126
22.3. Configuring the JSF Integration with Page Flows ....... 127
Appendices
23. Appendix 1: Consolidated List of Best Practices ................ 130
24. Appendix 2: Known Issues and Workarounds.................... 132
24.1. CR383659, CR383662 Inconsistent failures with JSF portlets 132
24.2. CR342124: IllegalStateException due to duplicate client-id 132
24.3. CR384916: IllegalStateException due to duplicate client-id when using certain components such as Tomahawk and Trinidad...... 133
24.4. CR361477 Problems with the integration of JSF portlets with Apache Beehive Page Flows.................................................................. 133
24.5. CR377945 JSF 1.2 suffers from a memory leak during iterative development .............................................................................. 134
25. Appendix 3: The JSFPortletHelper Class ........................... 135
26. Appendix 4: The CleanupPhaseListener Class .................. 147

Hi Peter!
First, I wish to thank you for the great work.
We followed your whitepaper and managed to deploy a JSF portlet on WLS.
But we are not able to register it (consume it) as remote portlet in Oracle Portal 10.1.4. The error log is as follows:
An error occurred while trying to refresh the provider. (WWC-43190)
An error occurred during the call to the WSRP Provider:
java.rmi.RemoteException: serialization error: serialization error:
unexpected null value for literal data; nested exception is:
serialization error: serialization error: unexpected null value for literal data
com.sun.xml.rpc.encoding.SerializationException: serialization error:
serialization error: unexpected null value for literal data
com.sun.xml.rpc.encoding.SerializationException: serialization error:
unexpected null value for literal data
Java stack trace from root exception:
unexpected null value for literal data
at
oracle.webdb.wsrp.RegistrationContext_LiteralSerializer.doSerialize(RegistrationContext_LiteralSerializer.java:107)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalSerialize(LiteralObjectSerializerBase.java:119)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.serialize(LiteralObjectSerializerBase.java:70)
at
oracle.webdb.wsrp.GetServiceDescription_LiteralSerializer.doSerialize(GetServiceDescription_LiteralSerializer.java:88)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalSerialize(LiteralObjectSerializerBase.java:119)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.serialize(LiteralObjectSerializerBase.java:70)
at
com.sun.xml.rpc.client.StreamingSender._writeRequest(StreamingSender.java:473)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:62)
at
oracle.webdb.wsrp.WSRP_v1_ServiceDescription_PortType_Stub.getServiceDescription(WSRP_v1_ServiceDescription_PortType_Stub.java:63)
at
oracle.webdb.wsrp.client.design.v1.OraWSRP_v1_ServiceDescription_PortType.getServiceDescription(Unknown
Source)Do you have any idea why this happens? Or you can provide some useful links to WLP -Oracle Portal federation?
Thank you and best regards,
PaKo

What's the best way to implement LOVs in OBIEE?

Hi All,
Does anyone have any good ideas on how to go about implementing LOVs in OBIEE?
At the moment we have created reports and dashboard prompts from the relevant SQL views which report off an Oracle EBS database. Our problem is that when we create a dashboard prompt from this view, that the generation of the LOV will take an extremely long time as it would need to run the whole query and do a distinct on the relevant column, before the LOVs are returned to the user.
I'd like to find out what possible solutions exist to implement and manage LOVs in OBIEE, and which is the preferred and recommended approach?
Thanks,
Lance

Hi Lance,
I can think about two things which are indexing and using a dimensional model rather than OLTP.
Are the views based on huge transaction tables? Are the LOVs based on transactional dates.
Thanks,
Manoj.

PI 7.11 mapping lookup - data enrichment - appropriate approach?

Hi guys,
we just upgraded from PI 7.0 to PI 7.11.
Now I´m facing a new scenario where an incoming order have to be processed.
(HTTP to RFC)
Furthermore each item of the order have to be enriched by data looked up in a SAP ERP 6.0 system.
the lookup functionality could be accessed during RFC or ABAP Proxy
With the new PI release we have several possibilities to implement this scenario, which are ...
(1) graphical RFC Lookup in message mapping
(2) ccBPM
(3) using of the lookup API in java mapping
(4) message mapping RFC Lookup in a UDF
Because of performance reason I prefer to make use of the Advanced Adapter Engine, if this is possible.
Further there should only one lookup request for all items of the order instead of each order item.
I tried to implement possiblity (1), but it seems to be hard to fill the request table structure of the RFC function module. All examples in SDN only uses simple (single) input parameters instead of tables. Parsing the result table of the RFC seems to be tricky as well.
Afterwards I tried to implement approach (3) using an SOAP adapter as Proxy with the protocol XI 3.0.
(new functionality in PI 7.11)
But this ends up in a crazy error message so it seems that SOAP adapter could not used as proxy adapter in this case.
ccBPM seems also be an good and transparent approach, because there is no need of complex java code or lookup api.
So the choice is not so easy.
What´s the best approach for this scenario??
Are my notes to the approach correct or do I use/interpret it wrong?
Any help, ideas appreciated
Kind regards
Jochen

Hi,
the error while trying to use the soap channel for proxy communication is ....
com.sap.aii.mapping.lookup.LookupException: Exception during processing the payload. Error when calling an adapter by using the communication channel SOAP_RCV_QMD_100_Proxy (Party: , Service: SAP_QMD_MDT100_BS, Object ID: 579b14b4c36c3ca281f634e20b4dcf78) XI AF API call failed. Module exception: 'com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: Unexpected length of element <sap:Error><sap:Code> = XIProxy; HTTP 200 OK'. Cause Exception: 'java.io.IOException: Unexpected length of element <sap:Error><sap:Code> = XIProxy; HTTP 200 OK'.
so this feature seems not to work for soap lookups, isn´t it.
Kind regards
Jochen

Problem with public pages having PL/SQL portlets

I am having problem with a public page which has PL/SQL portlets.
When I try to access that page without doing login, it displays everything but the portlets which are database driven.
Is this the way this public page should behave?
Is there anyway by which I can display data to my public pages from PL/SQL portlets without doing login?
FYI PL/SQL portlets are in portal30 schema.

Yes, it has is_runnable function and it looks like this :
function is_runnable
p_provider_id in integer
,p_reference_path in varchar2
return boolean
is
begin
If p_reference_path is null the caller may be the provider
framework (i.e. the Refresh operation of the Portlet
Repository).
if (p_reference_path is null) then
The following if statement is the security mechanism that
the portlet implements. It does not have any other semantic
meaning. Any portlet is expected to implement their own
security mechanism.
This security mechanism checks if the current user is logged
on or just accessing the portal through the public account.
if (wwctx_api.is_logged_on) then
return true;
else
return false;
end if;
else
If p_reference_path is not null the caller makes this call as
a security check against the portlet instance.
The security mechanism implemented by this portlet for portlet
instances is null so true is returned. Returning this value
indicates that all users have access to this portlet instance.
return true;
end if;
end is_runnable;
+++++++++++++++++++++++++++++++++++++++++++
What should I need to change with that function? And what exactly is its use?
FYI : The code which I wrote for my portlet is by doing some modification in downloaded service portlet. But I have not altered is_runaable function.

Creating Web Services using Java Implementation

Hi,
This is quite a general question on how to create a Web Service using Java Implementation that needs to conform to a client XML schema.
Here are my Version specs,
I am using Jdeveloper 10.1.3.4.0 and deploying onto OAS 10.1.3.
I will be creating a J2ee 1.4 (JAX-RPC) Web Service using Document/Wrapped style.
I have been provided an XML schema from the client which is quite complex.
Using a top-down approach, I can create my WSDL file and import the XML Schema for my type definitions.
The Web service aim is to accept some parameters and return some data from the Oracle Database. The
XML response from the web service must conform to the element, attribute definitions in the provided XML schema.
From a Java implementation approach, what is the best (simplest or quickest) way to retrieve data from the Oracle
tables and map each fields/column to the required XML output (defined in the XML schema).
I'm not too concerned with using Java to retrieve data from the Database, more with how I can map the data returned
to the required output. Can this mapping task be controlled within the Java program?
Thanks in advance.

Hi,
This is quite a general question on how to create a Web Service using Java Implementation that needs to conform to a client XML schema.
Here are my Version specs,
I am using Jdeveloper 10.1.3.4.0 and deploying onto OAS 10.1.3.
I will be creating a J2ee 1.4 (JAX-RPC) Web Service using Document/Wrapped style.
I have been provided an XML schema from the client which is quite complex.
Using a top-down approach, I can create my WSDL file and import the XML Schema for my type definitions.
The Web service aim is to accept some parameters and return some data from the Oracle Database. The
XML response from the web service must conform to the element, attribute definitions in the provided XML schema.
From a Java implementation approach, what is the best (simplest or quickest) way to retrieve data from the Oracle
tables and map each fields/column to the required XML output (defined in the XML schema).
I'm not too concerned with using Java to retrieve data from the Database, more with how I can map the data returned
to the required output. Can this mapping task be controlled within the Java program?
Thanks in advance.

Custom Expiry Implementation Advice Needed

Hi Guys,
I need help identifying best implementation approach. A requirement is to transitionally persist data that is getting expired from a cache to either MQ queue or a database. Here I need to make sure if persistence operation fails (ie database/mq is down), entry should be retained in cache until other systems are operational again.
Implementation Options:
1) Periodically scan all cached entries and manually identify which ones are ready for expiration. Then use coherence transactions and link it through XA with persistence operation.
2) Periodically scan all cached entries and manually identify which ones are ready for expiration. Remove entry only if persistence operation is successful.
3) Use Custom Eviction Policy? I didn't see a good way of plugging in there.
4) Extend LocalCache.Entry and override isExpired method. Not too sure if that is a good option or if that will even work.
5) ??
Thanks,
Dmitriy

Hi Dmitriy,
Personally I wouldn't do anything off of the back of Coherence's built in expiry. Going through your options...
1) While you are scanning the entries Coherence has probably evicted them. Whenever you do an action on a cache the first thing Coherence does is evict anything that has expired. So if you tried to scan a cache Coherence would evict the entries before you could scan them. A second point, I wouldn't use Coherence transactions for what you suggest as you will find they are too restrictive to be much use.
2) See, 1 above - again you will have trouble scanning the cache
3) Custom eviction policies are really just ways to tell Coherence if it can evict something
4) This could get tricky and trying to do some sort of persistence off of the back of isExpired is just wrong - methods should do what the name says, you have no idea how often Coherence will call your overriden method and if it is doing persistence you could have a big impact on performance of your cluster.
5) I would choose this option
I am pretty sure that triggers get fired when an entry is evicted so you could add a trigger to the cache that will do the persistence when an entry is evicted. When an entry is evicted you basically get a synthetic remove event which you can detect in the trigger (although is it not nice code as you need to use reflection to get to the isSynthetic() method). A trigger that looks like this might be workable...
import com.tangosol.util.MapTrigger;
import com.tangosol.util.ValueExtractor;
import com.tangosol.util.extractor.ReflectionExtractor;
public class MyTrigger implements MapTrigger {
    private static final ValueExtractor syntheticExtractor = new ReflectionExtractor("isSynthetic");
@Override
    public void process(Entry entry) {
        if (entry.isOriginalPresent() && !entry.isPresent() && isSyntheticEntryEvent(entry)) {
            // The entry is being evicted...
private boolean isSyntheticEntryEvent(Entry entry) {
        boolean isSynthetic;
        try {
            Object synthetic = syntheticExtractor.extract(entry);
            isSynthetic = (synthetic instanceof Boolean) ? (Boolean) synthetic : false;
        } catch (Throwable e) {
            isSynthetic = false;
        return isSynthetic;
JK

Problem with Database Portlets

I have installed the database provider starter examples. I have added two more database portlets to the starter provider. Some users can see them in the portlet repository and some cannot.
The following function is in the code:
function is_runnable
p_provider_id in integer
,p_reference_path in varchar2
return boolean
is
begin
If p_reference_path is null the caller may be the provider
framework (i.e. the Refresh operation of the Portlet
Repository).
if (p_reference_path is null) then
The following if statement is the security mechanism that
the portlet implements. It does not have any other semantic
meaning. Any portlet is expected to implement their own
security mechanism.
This security mechanism checks if the current user is logged
on or just accessing the portal through the public account.
if (wwctx_api.is_logged_on) then
return true;
else
return false;
end if;
else
If p_reference_path is not null the caller makes this call as
a security check against the portlet instance.
The security mechanism implemented by this portlet for portlet
instances is null so true is returned. Returning this value
indicates that all users have access to this portlet instance.
return true;
end if;
end is_runnable;
How do I know if the p_reference_path is null? What is the p_reference_path? In this code which I used from the starter examples, it looks like if the p_reference_path is not null the portlet won't be runnable.
Does anyone know what and where the p_reference_path is?
Thanks....JS

Hi Julie,
The reference_path is the unique identifier of the portlet instance. The reference path is assigned to the portlet when it's added to the portal page.
The code above simply checks whether the reference path exists to eliminate error messages. The reference path is undefined for instance in preview mode, when the portlet is displayed on a "non-portal-page".
If you want to learn more about the topic you may find useful the Guidelines for Parameter Passing in Portlets PDK article.
Regards,
Peter

Remote Inter Portlet Communication for JSR 168

Hi All,
We are stuck in a big problem using JSR 168 as remote portlets. We will be relieved if someone can suggest few ideas on this. I will provide the scenario which we are trying now.
We have two portlets namely portlet A and portlet B which are Java(JSR 168) type portlets. These two portlets are offered as remote and they reside in the producer application. We have consumed these two portlets in our consumer application.
The portlet A is triggering an event and portlet B is listening to the event triggered by portlet A. Currently we are trying to implement this functionality using Ajax. We tried to use customEventUrl tag in our jsp belonging to portlet A and we finally figured out that customEventUrl will not work in Remote portlets. We are not sure as how to pass the information from remote portlet A to remote portlet B. Please let us know your thoughts about this as whether the implementation is really possible when using Remote portlets.
IMPORTANT NOTE: The event handling and the configuration code that we have made in the above scenario is working perfectly for non-remote java portlets. The problem is occurring only when we consume them in the consumer application.
Thanks
Vijay

Hello Ashwin,
What version of WebLogic Portal are you using? And is this the same for both the consumer and producer?
If you are using WLP 10.3.2 I would highly recommend using JSR286 portlets (the next version of the Java Portlet (JSR168) specification) and the JSR286-standard eventing. The JSR286 eventing model is actually much cleaner and easier to understand than the WLP-proprietary support for events in JSR168 portlets.
However, if you are using a version of WLP prior to 10.3.2 and can't upgrade, JSR168-style events are your only choice. I can give you examples, but they all look very similar to the examples in the online documentation.
When events work between portlets locally, but not over WSRP, the usual problems are:
- There is one or more of "onlyIfDisplayed", "sourceDefinitionLabels" or "sourceInstanceLabels" attributes declared on the handle*Event element in the .portlet file. These attributes restrict when the portlet should receive an event, and they usually don't work the way you think when running over WSRP. It is best to not use these attributes for portlets which are going to be used over WSRP.
- A payload is being sent with the event which is not actually serializable. If serialization of the event payload (which is required for versions of WLP prior to 10.3.2 for WSRP) fails, the event will not be delivered to the portlet.
- The producer may be configured to not accept events. Check your producer's WEB-INF/wsrp-producer-config.xml file; the "service-config" element should either not have an "offer-extensions" attribute, or this attribute's value should be "true".
- The events may be getting sent during a portlet lifecycle other than processAction or handleEvent. There is no way for WSRP to handle events which have been sent during preRender or render, so it simply doesn't work.
- In the case of JSR168 portlets, if you have a backing file on the portlet (in addition to the portlet implementation as well), that may not work in some circumstances over WSRP. It is best to have the event handlers be in the portlet implementation class and avoid the use of backing files for JSR168 portlets.
If none of those things help you, my suggestion would be to post a sample .portlet file for one of the portlets that is supposed to be receiving the event, as well as the method signature in that portlet's implementation class that is supposed to be receiving the event, and the code which is sending the event that is supposed to be received.
Kevin

Difference between EDN-DB and EDN-JMS implementation

Experts,
Looking for a difference between EDN-DB and EDN-JMS implementation. We have EDN implementation going on, where multiple source systems will be publishing business events. Events can be published using SOA Suite or JMS Bridge from AQ and MQ. In this scenario which implementation approach is suited better ?

Oracle Apps Adapter can be used for many other products other than E-Business Suite (JD Edwards E1, OTM, and others). The apps adapter was mainly used in ERP systems and was strong when you needed have added functionality other than just polling a db for a status / calling a stored procedure... It could connect out to other business services, xml gateways and so-on.
From a technical aspect / development perspective I always thought of that the Oracle Apps Adapter simplifies the development but, may is not flexible. The App Adapter's strength is the services that are difficult to integrate with (business services, xml gateway). If you need to hook in to these types of services, use the APPS adapter. (Again like it is named the "Apps Adapter" its for interacting w/ other applications to enable real-time processing / functionality.
That being said the dbAdapter can be very powerful but, like it is named is database focused (to poll some table to know when to kick off other logic and enable real-time functionality through database interaction.
Looking at the Oracle 12C Roadmap I had heard that there is more planned for the Oracle Apps Adapter moving forward, especially as Anuj said in the "Financial Apps" side of the isle at Oracle. Who knows what is real and what isn't though =]
Hope this helps!
-Luke

Preferred portlet implementation approach in 10.3

Similar Messages

Maybe you are looking for