PCUI - portal event - webDynpro Abap

Hello,
From standard PCUI, which used to create partner, I want to get a value partner and send it to a view that content Webdynpro Abap through portal Event.
Is it possible? How?
Thanks.

Hello,
Could you please clarify your question?
Thanks and Regards
Francisco

Similar Messages

Calling Portal event from ABAP class

Hi Experts,
I need a following clarificatrion, Please help,
1. Is it possible to call a webdynpro method from a normal ABAP class?
2. If no, we need a functionality of a class 'CL_WDR_HTTP_EXT_MIME_HANDLER' having method 'DO_DOMAIN_RELAX_HTML'.
Is there any alternative method which can be used in ABAP having the same functionality.
3. Is there any ways with which we can call portal event from ABAP class?
Thanks,
Shabir

>1. Is it possible to call a webdynpro method from a normal ABAP class?
I wouldn't necessarily recommend this approach. You shouldn't try to trigger events or any of the standard WDDO* methods from outside the WD Component itself. That said, you can pass the object reference (like the WD_COMP_CONTROLLER object reference or the View Object Reference) into methods of normal classes. Be careful if you are finding yourself calling a lot of your added methods from outside WD. This is probably a sign that these methods should be in the Assistance Class or some other Class functioning as a Model Object.
>2. If no, we need a functionality of a class 'CL_WDR_HTTP_EXT_MIME_HANDLER' having method 'DO_DOMAIN_RELAX_HTML'.
Is there any alternative method which can be used in ABAP having the same functionality.
What exactly do you want to do here? Do you just want to get the relaxation script? For what purpose? You should never need to inject the relaxation script into WDA.
>3. Is there any ways with which we can call portal event from ABAP class?
To what purpose. Do you just want to delegate the triggering of the event that is inside WD Component to be called from a class? If so you can pass the portal API object reference into a class from the WD Component. However this only works while running within WD.
How is this class used? Are you running in WD? Are you trying to generate some HTML code that runs in the portal independent of WD?

Settings Portal eventing - WebDynpro for Abap iView communication

To connect two WD4A's using portal eventing; what work is to be done inside the portal environment.
All manuals on SDN provide information action to be done within WD4A, Do we need to configure/set values in the Portal environment at al...

Hi Marco,
Check the url:
[help.sap.com - Client-Side Eventing|http://help.sap.com/saphelp_nw70/helpdata/EN/ce/3e98408d953154e10000000a1550b0/frameset.htm]
Best regards,
G. Leurs

How to handle unsaved data in portal through webdynpro ABAP ?

Hi Experts ,
     I need to handle unsaved data in SAP Enterprise Portal through webdynpro for ABAP . I got a sdn link which explained some code for this..
http://help.sap.com/saphelp_nw70/helpdata/EN/45/b76f4169e25858e10000000a1550b0/frameset.htm
I tired to implement this in EXIT method of the view. but im not able to get this . Can any one help me in this ? .
Regards ,
Kalpana .

Hi ,
Yes i have checked the code . But the example itself not working when i linked the same with portal . If EXIT is not the right method , Can you help in placing the code in right method ? The code i pasted in EXIT method is
data L_COMPONENTCONTROLLER type ref to IG_COMPONENTCONTROLLER .
data L_API_COMPONENTCONTROLLER type ref to IF_WD_COMPONENT.
data L_PORTAL_MANAGER type ref to IF_WD_PORTAL_INTEGRATION.
L_COMPONENTCONTROLLER =   WD_THIS->GET_COMPONENTCONTROLLER_CTR( ).
L_API_COMPONENTCONTROLLER = L_COMPONENTCONTROLLER->WD_GET_API( ).
L_PORTAL_MANAGER = L_API_COMPONENTCONTROLLER->GET_PORTAL_MANAGER( ).
call method L_PORTAL_MANAGER->SET_APPLICATION_DIRTY_FLAG
exporting
    DIRTY_FLAG = ABAP_TRUE .

Portal event webdynpro

hi can u tell me how event can be triggered of portal with screen sot with example

Hello,
Could you please clarify your question?
Thanks and Regards
Francisco

Webdynpro ABAP called from IView JAVA works over http but doesn't over http

Hello gurus, like I said in the subject, we have integrated inside our JAVA portal a WebDynpro ABAP and it's working good over http protocol (http://<servername>:<http_port>/irj/portal), but when you browse the portal over https protocol (https://<servername>:<https_port>/irj/portal), everything works fine exept the WebDynpro ABAP, is like if the javascript components didn't be loaded completly, because the buttons doesn't make anything, and only half of the table that is supossed to be loaded is showed.
Do you know what kind of configuration I'm missing?
Thanks and best regards

You have to note here that for webdynpro ABAP applications, the http/https request is actually served by the backend server.
So, while accessing your webdynpro ABAP application, the request will be like:
https://<mybackendserver>:<backendport>/bc/sap/.....
While creating a system object in your portal (System landscape), you will need to adjust the protocol to https and also set the appropriate https port of the backend server. Also, HTTPS/SSL communication should be enabled on your backend server.
Please check the definition of your system object.
You can find more information by turning on a HTTP trace and checking how the request is routed to the backend server upon accessing the WD4A application.
Thanks,
Shanti

Webdynpro ABAP not working from internet

Hello,
I´m new at webdynpro and portal...
We have a ess portal with webdynpro abap and java. Our employees may access it from intranet and all works fine, and from internet when they are in the outside.
From internet the webdynpro abap gives the message that the server cannot be reached. The server is our production backend and is not open to the exterior.
Is there a way to make this work, from inside and outside?
Teresa

Yes sure,
so you have to set the parameter wdisp/add_clientprotocol_header = 1 in the web dispatcher profile.
Good references are:
[http://help.sap.com/saphelp_nw04s/helpdata/en/de/89023c59698908e10000000a11402f/frameset.htm|http://help.sap.com/saphelp_nw04s/helpdata/en/de/89023c59698908e10000000a11402f/frameset.htm]
[http://wiki.sdn.sap.com/wiki/display/BSP/HandlingBinaryData|http://wiki.sdn.sap.com/wiki/display/BSP/HandlingBinaryData]
and this
[http://help.sap.com/saphelp_nw04s/helpdata/en/9a/53a2a4a45e244aa189c2b7065a0b78/frameset.htm|http://help.sap.com/saphelp_nw04s/helpdata/en/9a/53a2a4a45e244aa189c2b7065a0b78/frameset.htm]
Sergio

Java Portal Event not received correctly by ABAP Webdynpro

We have a page that contains 2 iviews.
iView 1 contains the MSS Employee Search that raises portal event:
Namespace: "urn:com.sap.mss.employeesearch"
Name: "selection_changed"
The second iview contains an ABAP Webdynpro program that subscribes to the Portal event.
The issue is that the event in the ABAP webdynpro is not being triggered. It does get triggered if we first fire the event from the Java program, unsubscribe the event in the ABAP program them subscribe to the event in the ABAP program. The event gets triggered at this time and the parameter can be retrieved.
If the event is fired a second time, nothing happens in the ABAP program.
The abap program works fine when another abap program triggers the same portal event.
Also, the portal event is being picked up correctly by other SAP delivered JAVA programs. I just cannot get a custom ABAP Webdynpro program to work...
Any ideas, comments?
Glenn

Hi Glenn,
Are you using https? Is your j2ee stack and abap stack in the same domain? In the past I have found that https can cause issues in the event communication between different applications.
Cheers,
Dion

Portal Eventing in Webdynpro ABAP

Hello,
I am trying to implement Eventing in Webdynpro ABAP using 2 components ,Com1 serving as the source component and Com2 serving as Target. In Com1 I created a Inputfield and a button ,and then tied an action to the button and called the FIRE method of the IF_WD_PORTAL_INTEGRATION and sent the value in the Inputfield as the eventing parameter.
In Com2, i subscribed to the event in the wddoinit() method and then defined an action for the same and got the parameter value sent in the Com1 and set the value in the context attribute in the Com2 which is bound to the inputfield.
But still the value sent in Com1 is not displayed in the Com2 Inputfield.
Any help would be highly appreciated.
Thanks.

>
SAPEPDeveloper wrote:
> Hello,
>
> I am trying to implement Eventing in Webdynpro ABAP using 2 components ,Com1 serving as the source component and Com2 serving as Target. In Com1 I created a Inputfield and a button ,and then tied an action to the button and called the FIRE method of the IF_WD_PORTAL_INTEGRATION and sent the value in the Inputfield as the eventing parameter.
>
> In Com2, i subscribed to the event in the wddoinit() method and then defined an action for the same and got the parameter value sent in the Com1 and set the value in the context attribute in the Com2 which is bound to the inputfield.
>
> But still the value sent in Com1 is not displayed in the Com2 Inputfield.
>
> Any help would be highly appreciated.
>
> Thanks.
Hi I assume the following, please correct me if my understanding is not correct.
1.First of all you try this in Portal.
2.The moment you fire the event, the comp-2 view is active and subscribed to the portal event.
If the above are true then tell me if the portal eventing enter into the action ?Have you checked in bebug that your action is triggerred on portal_event ?
If portal event is action handler is called then if you have a importing parameter portal_event_parameter then your input value should be there.

Portal eventing in WD ABAP

Hello ,
We have an requirment to pass values from one WD ABAP application iView to another in the Enterprise portal.Is there any configuration that needs be done in WD ABAP or is there any setting in EP that we need to do ??
Rahul

Rahul,
Though most of this stuff is of web dynpro for java. You can just replace java Code with ABAP.
You need to use eventing functionality.In the SAP Enterprise Portal, different application types in specific iViews can be arranged on one page. To communicate between the different iView types the portal provides the Enterprise Portal Client Framework (EPCF), also known as client-side eventing. This document describes how Web Dynpro applications can use EPCF.
http://help.sap.com/saphelp_nw04/helpdata/en/24/243ca46e1c334f8a6f8b0792656bc7/content.htm
The following code shows the signature of the subscribe method:
WDPortalEventing.subscribe(java.lang.String nameSpace, java.lang.String event, IWDAction action);
for example
WDPortalEventing.subscribe (urn:com.sap.tc.webdynpro.test.portal,
    TestEvent,
    wdThis.wdGetTestEventAction());
You have to define the events name and its namespace. The combination of these two names must be unique.
The third parameter is the Web Dynpro action, which should be mapped to the portal event. The action event handler is called if the Web Dynpro application receives the specified portal event on the client side. The mapping between a portal event and a Web Dynpro action is done automatically and it is completely transparent for the Web Dynpro application developer.
You can reuse a Web Dynpro action for several portal events. If you want to receive the portal events data you have to define the following parameters for your Web Dynpro action:
·        dataObject
The dataObject parameter contains the portal event parameter.
·        nameSpace
The namespace parameter contains the portal events namespace.
·        name
The name parameter contains the portal events name.
It is useful to add the nameSpace and nameparameters to the Web Dynpro action if the action is reused for several portal events because you can use this information to differentiate between the portal events.
Note: In the current version a portal event subscription is valid for a Web Dynpro view. Therefore you should add the required Java coding, for example in the wdDoInit() method of the generated view class. If you navigate between different views, you have to subscribe to every view for the portal event required.
Unsubscribe from a portal event
Unsubscribing from a portal event is very similar to subscribing. The following code shows the signature of the unsubscribemethod:
WDPortalEventing.unsubscribe(java.lang.String nameSpace, java.lang.String event, IWDAction action);
for example
WDPortalEventing.unsubscribe (urn:com.sap.tc.webdynpro.test.portal,
    TestEvent,
    wdThis.wdGetTestEventAction());
Note: You must unsubscribe every Web Dynpro view, because subscription and unsubscription is valid only for the current view.
Raise a portal event
The following example shows how to raise a portal event. The signature is:
WDPortalEventing.fire(java.lang.String nameSpace, java.lang.String event, java.lang.String parameter);
for example
WDPortalEventing.fire (urn:com.sap.tc.webdynpro.test.portal,
     TestEvent,
    AParameter);
You can fire a portal event anywhere in your Web Dynpro application. The event is sent to the client with the next response. You can also raise more than one portal event in a request-response cycle. Typically, you will fire a portal event in a Web Dynpro action event handler (for example, as a response to pressing a button).
The following step-by-step example shows how to carry out portal eventing within two simple Web Dynpro example applications.
Example Description
The user can enter an arbitrary string in an input field. If the user presses the pushbutton Click here in the sender view, the input string will be displayed in a TextView UI element of the listener application.
Prerequisites
You have built two Web Dynpro applications. How to build Web Dynpro applications is described in Creating a Simple Web Dynpro Application. In each application you have created a Web Component with a view that uses the portal eventing.
You can find the detailed procedure describing how to insert UI elements into a view in Creating a Simple Web Dynpro Application.
Further information about the integration of a Web Dynpro application into the SAP Enterprise Portal can you find under Running a Web Dynpro Application in SAP Enterprise Portal.
Procedure
Creating the Web Dynpro applications
       1.      Create the Web Dypro project. Call it webdynproexample_portal_eventing.
       2.      Create two Web Dynpro components. Call them:
                            a.      EventSenderComponent
                            b.      EventListenerComponent
       3.      Create two Web Dynpro applications. Call them:
                            a.      EventSenderApplication
                            b.      EventListenerApplication
Creating the necessary views:
Create the layout of the EventSenderView in the EventSenderComponent as follows:
Create the context structure of the EventingSender View:
The context value attribute Name must be of type String.
Create an action Show
Define the data binding of corresponding UI element properties:
The appropriate properties of the UI elements must be bound to the context that contains and displays the data.
       4.      Define a text, for instance, Enter a text: for the label UI element (ID: NameLabel) using the property text.
       5.      Bind the property value of the input field (ID: NameInputField) to the context attribute Name.
       6.      Bind onAction of the button (ID:ShowButton) to the corresponding action Show.
Implementation of the view controller
       7.      If you create an action declaratively within the SAP NetWeaver Developer Studio, the Web Dynpro framework automatically generates an onAction method in the controllers implementation. The generated method enables you to write code to fetch the input string and to fire the portal event. The fire method of WDPortalEventing passes the data and the name of the event that should be handled by the second application as parameters. The following code shows the implementation of onActionShow method:
public void onActionShow(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
    //@@begin onActionShow(ServerEvent)
   String name = wdContext.currentContextElement().getName();
    WDPortalEventing.fire("urn:com.sap.tc.webdynpro.example.portaleventing",
                       "Show",
                       name);
    //@@end
Create the layout of the EventListenerView in the EventListenerComponent as follows:
Create the context structure of the EventingListenerView:
The context attribute Name must be of type String.
Create an action, for example, ReactPortalEventing which should be mapped to the portal event.
       8.      Create an action ReactPortalEventing.
       9.      Add the parameter dataObject. It should have the type java.lang.String.
Define the data binding of the corresponding UI element properties:
The corresponding properties of the UI elements must be bound to the context that contains and displays the data.
10.      Define a text for the NameLabel for example, The entry is displayed in a TextView UI element:
   11.      Bind the property text of the TextView UI element (ID: TextViewShow) to the context attribute Name.
Implementation of the views controller
   12.      You have to subscribe to the event within the wdDoInit method. You have to define the namespaceof the event and the name of the event, for example Show. The third parameter is the Web Dynpro action, which should be mapped to the portal event.
   13.      You have to implement the action (ReactPortalEventing) that passes the dataObjectand fills the context with data. The following code shows the implementation of the wdDoInit and the reactPortalEventing methods:
public void wdDoInit()
    //@@begin wdDoInit()
    WDPortalEventing.subscribe("urn:com.sap.tc.webdynpro.example.portaleventing", "Show",
    wdThis.wdGetReactPortalEventingAction() );
    //@@end
public void onActionReactPortalEventing(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent, java.lang.String dataObject )
    //@@begin onActionReactPortalEventing(ServerEvent)
    wdContext.currentContextElement().setName(dataObject);
    //@@end
Deploying the Web Dynpro Application
Before you can call the Web Dynpro application, you have to build the Web Dynpro project and deploy the application on the J2EE Engine.
Simple Testing of the Portal Eventing and Calling the Web Application
   14.      Create two iViews in the newly-created example folder as described in Running a Web Dynpro Application in SAP Enterprise Portal.
   15.      Create a page and add the two iViews to the newly-created page.
To preview the Web Dynpro applications, choose the button Preview in the Portal Content Studio.
   16.      Enter your input and choose button Click here.
Result
A page preview will demonstrate portal eventing.
Also, Please refer to these links,
http://help.sap.com/saphelp_nw04/helpdata/en/c6/21fc3f82c2e469e10000000a155106/content.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webdynpro/portal integration of web dynpro applications.pdf
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cfb80249-0801-0010-3eaa-829afeac170f
Please let me know whether its useful.
Thanks,
Raj.

Webdynpro ABAP/Portal. Plugin HTTP connection issue on WaitingEventQueue.js

Hello,
We are experiencing a strange Portal Behavior with our Webdynpros. Our portal contains several iViews including some Webdynpro (ABAP) and some reporting transaction calls that use SAPgui for HTML.
When portal is called for the first time and a user logs in, two connections of type RFC can be seen for that user in SM04 in our ERP system. All iViews work as expected. For example, calling the Time Management webdynpro closes one of the RFC connections and starts a new Pluguin HTTP connection. We can go back and forth between the welcome page and this Webdynpro with no issues.
If we then select one of the reporting transaction codes, the portal launches the SAPGUI for HTML. Report retrieves and shows data, and then we close using the "Exit" button provided by the sapgui for HTML
Next we try again to launch any webdynpro (abap), but SM04 shows that the new Plugin HTTP session gets stuck and spinning mid way, and will stay there. Refreshing the Portal screen with F8, navigating back and forth, logging off and on again has no effect. The webdynpros will not launch again. Only webdynpros are affected, any of the reporting transactions can be called successfully over and over.
We have figured that deleting Temporary Internet files (we are using IE 7), and in particular by just deleting the WaitingEventQueue.js?XXXXXXXXXXX file, the system will break away from the spin loop and show the webdynpro again, but eventually it will get stuck again, and asking the users to delete their Temporary Internet Files every 5 minutes is not a workable solution
I have reviewed the contents of this javascript file at different points during the test, and the contents do not change, so deleting the file and the recreate process must be resetting somehow the queue and allowing for a new correct communication.
Is there a way to properly reset this event queue (for example from ABAP, when the webdynpros are reloaded) in order to avoid the spin loop?
Thanks for any help!
Andres

Well, we got the issue resolved, so here is what we did, in case anybody is interested:
Tested again our portal with multiple versions of Internet Explorer, in particular IE8 and IE6, the Webdynpro behavior was normal (no timeouts or locks). It even worked when we installed IE7 in a brand new machine and tried our portal.
So we started suspecting if maybe the particular IE7 that we install internally (with specific settings and policies) may be the culprit. We took a desktop that was producing the timeouts and used the following options in IE7:
Tools->Internet Options->Advanced(tab)-Reset Internet Explorer settings
and, voila! the next time we ran there, the portal did not create any timeouts.
We even asked our desktop support team to uninstall and reinstall IE7 in the same machine after we did the reset, and even after the re-install that the timeout problems did not re-appear.
One of the things that the "reset" option does is delete the Add-ons used by IE.
So as a last test, we took a machine that was presenting the problem and went to the Internet Options to disable all the add-ons (in the Programs Tab). The error disappeared.
And even after enabling back all the add-ons, the error would not return.
Conclusion:
Without being able to pinpoint the specific add-on (or combination) that causes the problem, we suspect that some of them conflicted, causing IE7 to behave abnormally. Disabling them all, restarting Internet Explorer, and enabling them again, makes the WaitingEventQueue.js work as it should

Debugging the webdynpro abap application from portal.

I developed a WebDynpro application and integrated in portal. I have to catch some portal events.For that i have written some code in my application. I tried to debug the application from portal by using all the available break-point types.but we could not .
Anybody have an idea how to debug a WebDynpro application from portal.
Thanks,
Kumar.

Hi
Few links to check:
External debugging is not working
Re: Debugging Abap webdynpro appln
Re: Unable to Debug WD ABAP application
Dedug is not working in Production Server.
a) Check on number of R/3 sessions opened at a time.
b) Check that user ID configured in portal using System Mapping Under 'Delegate User Administration' is the same user for which you are setting external breakpoint in backend system.

Apply custom themes to WebDynpro ABAP application in Portal

Hi,
We have just upgraded the E-Recruitment to EHP4. We have two instances of ECC in which one acts as HR instance and the other one for E-Recruitmet. We have created custom themes for portal and need to apply the same for the WebDynpro ABAP applications for E-REcruitment. I have downloaded the theme and from portal and uploaded the same in MIME folder using SE80 transaction. I have also added the parameter sap-cssurl=/sap/public/themes/<my custom theme folder name>.
Also tried giving the url in application parameter as
SAP-EP-THEMEROOT=http://<hostname>/irj/portalapps/com.sap.portal.design.portaldesigndata/themes/portal/customer/<custom theme>
Is there any other way to apply themes for WD ABAP applications. I dont want to customize the standard applications and just want to apply the themes.
Any suggession on this is highly appreciated.
Kind Regards,
Vivek.

Hi,
to create theme for webdynpro abap application, use Eclipse Plugin. Please remeber to check the version of theme file before using theme.
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/10d5ef40-465e-2c10-9ca9-f548bfc3f236
setup custom theme for webdynpro abap application.
FEATURED EVENTS
Regards
Baby

How to handle events in webdynpro abap

Hi,
can any body explain how to handle the events in webdynpro abap.
i want to know some concepts in general.
Thanks,

Hi Mahesh,
you can create event handlers under the actions tab in you view. evry event handler has an importing parameter wdevent of type ref to cl_wd_custom_event.
you can also create events in your component controller and they can be handled within your views
check cl_wd_custom_event class for details about what all information you get when an event occurs.
for further details you can check out the following links
http://help.sap.com/saphelp_nw04s/helpdata/en/eb/ed6f4169e25858e10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/a9/c751415e3b6532e10000000a1550b0/frameset.htm
also you can try the tutorial at the following link for further clarity
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2eb11b59-0a01-0010-dfa3-8292abdf9c4f
Regards,
Shweta
Message was edited by:
Shweta R Shanbhag

Javascript server events in webdynpro ABAP

I am migrating an existing BSP application to webdynpro abap. Few of sections, in existing BSP application, uses java script coding to trigger few server events. For example it uses a flash charts on click of which some filtering logic is written on table. Similar logic needs to be placed for webdynpro. I used Iframe to display this charts. Charts are rendered properly but I am not able to raise the actions or trigger events on server as I dont have access to parent.document object of my parent view.
I get access denied/ permission denied error.
Cant we trigger server action or event using JavaScript from child IFrame.
With Regards,
Nitesh Shelar.

Hi Nitesh,
Integrating custom java script is not supported. There are still a few benefits BSP has over WDA. Well, you could put the flash object inside of a BSP application and use portal eventing to communicate with WDA.
Best regards,
Thomas

PCUI - portal event - webDynpro Abap

Similar Messages

Maybe you are looking for