on 06-23-2006 12:31 PM
Hello,
I am trying to send portal events between VC- and WebDynpro-iViews (both NW2004s) on a portal page.
I am using Signal-In/Out elements in VC and wrote two small WD apps to send/receive arbitrary events, i.e. namespace, event name and a string value to be transferred can be entered.
After playing around a bit I eventually managed to raise a portal event in the VC-iView and received the same (after first subscribing to it) in a WD-iView. I found that the name of the Signal-out element itself becomes the portal event name and the string entered for "EPCM event" is prefixed with the string "urn:" and becomes the portal event namespace. The data entered (in an input field in the VC-iView) the payload of the event - was in a way actually received with the event in the WD-iView, but surrounded by some strange <Params>..-strings: when entering foobar e.g. I received (literally) <i><Params><param name="dataObject" value="foobar"/></Params></i>
Given these mechanics I thought the other way around raising an event in a WD-iView and receiving it in a VC-iView should work as well. However nothing happens, I just cant get it to function!? So my questions are:
1) How can one get rid of the surrounding <Params>-strings when going VC -> WD (I mean obviously they are needed for VC <-> VC communication, but what does this mean for VC <-> WD exchange)?
2) What could be the reason that WD -> VC does not work, any ideas what could be wrong?
Regards,
Sebastian
I actually wrote a how-to guide on how to integrate BEx WEb Templates and Visual Composer using events
You can do something very similar with Webdynpro as well. XSL and XML Dom are the two most common ways to change this XML doc format.
Also, one thing to keep in mind is that this format is changing with SPS8.
Examples:
SPS7:
<Params><Param name="F0FISCPER" value="2002001" name="F0CALYEAR" value="2002" name="F0COMP_CODE" value="1000"/></Params>
SPS8:
<Params version="2"><Row F0FISCPER="2002001" F0CALYEAR="2002" F0COMP_CODE="1000" /></Params>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Prakash (or anybody else),
problem 1) is solved. I used the javax.xml.parsers package to parse the received string, build a dom document and extract the attribute value - my actual data.
However I can't get the communication WD->VC to work. I use the exact format of the event data as sent by a VC sender (which I display in my WD receiver) and reuse it (copy&paste) to raises an event in the WD iView. All four iViews WD sender/receiver, VC sender/receiver reside on one single page. I also tried to encode the spaces and other special characters (such as '>') with %2E etc. but that doesn't help either.
In your Document you seem to send the value 'raw' as such (i.e. no xml document). Anyway, raw or xml, I tried both and I don't see any difference between your and my scenario.
So, if anybody had an idea that'd be great.
Regards,
Sebastian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Use the flash debugger in Visual Composer. Build a VC model that has 2 iViews (one with signal out and one with signal in) both within a page. Build a button that triggers the event. Deploy the model with the flash debugger on. Trigger the event at runtime. Look at the format of the parameter that is being passed. Now add the WD iView to that page in a portal page. Trigger the event and compare the signal within the flash debugger.
Hi,
I am also trying to use portal eventing between a VC and webdynpro application. I am able to get the singal to work and getting an encoded string. The string is as below:
%3CParams%20version%3D%222%22%20%3E%3CRow%20STR1%3D%22Aamod%22%20/%3E%3C/Params%3E
The paramter Name is "SRT1" and the value is "Aamod". Can you please give me the code on how you used the parser package to get the value of the attributes.
Thanks in advance,
Aamod.
Hi Prakash,
thanks for your note, I read your paper and it helped understanding the <param..>-tags. However, I still don't understand why sending an event within WD (i.e. the payload data providing the <param..>-tags in a syntactically correct way) and receiving the same in VC doesn't work. How does a VC-iView subscribe to a certain event/namespace? How come the event raising/subscribing mechanism is not symmetrical (as described before VC->WD functions)?
Regards,
Sebastian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Make sure that you specify the correct namespace and event name within Visual Composer. If it still doesn't work, turn on the flash debugger as I describe in the paper. The XML document format must be EXACT for VC to interpret the signal... If you need, send an event out from VC and consume it in WD and print out the value to the screen...
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.