Reg: Closing and Opening Web Dynpro Application in same browser

Dear Experts
In my webdynpro application when i click a button another web dynpro application is opened in another window(another browser) .
But i want to open the second web dynpro application inside the same browser in which closing the first applicaiton and opening the second web application in same browser window .
Please guide me to do this.
Regards
Arun

hi ,
Exit plugs have the special property that they use the defined URL parameter. After you have created the URL parameter in the parameter list on the Outbound Plugs tab page in the window editor, you can specify a value for this parameter in the method that calls the exit plug.
ref
link:[http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/ca3351508f04e7e10000000a42189c/content.htm]
it would help u
regards,
amit

Similar Messages

Difference between mobile web dynpro and simple web dynpro application

Hi Everyone,
Can anyone pls let me know what's the difference b/w mobile web dynpro application and an offline or simple web dynpro application.
Thank U!!
Ravi Aswani

Hi ,
Mobile WebDynpro
The SAP Web Application Server allows direct online access to Web Dynpro applications using mobile devices. As part of the SAP Web Application Server, Web Dynpro provides a development and runtime environment with which you can quickly and simply create professional user interfaces for desktop PCs or for mobile devices. An appropriate infrastructure and renderer classes are provided for developing mobile Web Dynpro applications for Pocket PCs as well as for BlackBerry Wireless Handhelds and Nokia Series 80 devices.
http://help.sap.com/erp2005_ehp_03/helpdata/EN/fa/100d4113eff16fe10000000a1550b0/frameset.htm
WebDynpro Java
Web Dynpro is a client-independent programming model of the SAP NetWeaver technology platform for developing user interfaces for professional business applications. It is based on the model view controller paradim which ensures that the business logic is separated from the presentation logic. This architecture is visible in the Web Dynpro perspective of the SAP NetWeaver Developer Studio (NWDS).
Web Dynpro helps you with the development of Web applications by:
·        Ensuring platform-independence with the meta model approach
·        Minimizing the implementation effort through declarative programming
·        Supporting a structured design process by applying the model view controller paradigm
·        Providing reuse and better maintainability by using components
·        Providing graphical support with tools in the Web Dynpro perspective
·        Providing the SAP NetWeaver Java Development Infrastructure (NWDI) which supports team work with different services such as source code versioning and the Central Build Service.
http://help.sap.com/erp2005_ehp_03/helpdata/EN/fa/100d4113eff16fe10000000a1550b0/frameset.htm
Thanks
Suresh
Edited by: Suresh Mandalapu on Sep 2, 2008 11:07 AM

Closing window of web dynpro application with exit-plug don't run in the EP

Hi everybody,
I want to close a window that contains a Web Dynpro with a close button, because it's used and create as a popup from an other iView (that's not created with web dynpros) in the EP. I read the different threads how to close a window in web dynpro, like JavaScript in WD
I create a HTML file with the javascript code to close the window and it works fine, when I start the application separately.
If I used it in the portal and click the close button I get the following error message:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!
I tried also: ...wdFirePlugExit("javascript:self.parent.close();") or some other javascript code, but got the same error message.
Then I tried:
WDPortalNavigation.navigateAbsolute(url,WDPortalNavigationMode.SHOW_INPLACE,(String) null, (String) null,(String) null);
instead of fireing the outbound plug in the action of the close button
(...InterfaceViewController().wdFirePlugExit(url);)
but than a new window with the EP open and the old is still there!
We use the NWDS2004s an the EP 7.00.
It must be possible to close a (this) window!
Thanks for any hint
christian

Hi,
This is what you can do:
1. You have already created the HTML file with the necessary javascript in the foloowing folder structure :
src->Mimes->Components-><your component name>-><fileName.html>.
2. Create a new iView of type URL in your portal.
3. Get the absolute URL of this HTML file inside your project. This will be in the following format:
http://<server>:<port>/webdynpro/resources/sap.com/<development ComponentName>/Components/<namespace>/<fileName>.html
You can find it thus:
try {
String u = WDURLGenerator.getAbsoluteWebResourceURL(wdComponentAPI.getDeployableObjectPart(),"filename.html");
wdComponentAPI.getMessageManager().reportSuccess(u);
} catch (WDURLException e) {
// TODO Auto-generated catch block
e.printStackTrace();
4. Now enter this URL string as the URL for the iview.
5. Do a normal portal navigation to this iview on-click of the button.
Regards,
Satyajit.

How to destroy and restart Web Dynpro application by triggering an action?

I try to implement a screen flow that when user click on "Reset" button, it will restart the application (screen flow) again.
Said, when the user processed till Screen 3, he/she decide to "Reset" and restart again, all the context in all controllers (view, custom and component) will be destroy (bind() to new element , or clean up), then start from the first screen again.
I figure out that the best way to do this is to destroy the current application session, and restart a new one . In this case, you don't have to worry about clean up the context , then navigate to the first screen when you click "Reset button".
I am thinking is it a good idea by trigger the exitPlug() then navigate to the URL of the same WD application again?
Please advise.
Thanks a lot.
Kent

Hi Kent,
I have tried the method of creating the exit plug from the interface view of the controller, and then returning to the same URL of the application.
It works fine and all the contexts, their values and controller contexts are cleared.
For my application it is working great....
Regards,
Alka

Short dump when trying to open FPM for Web Dynpro Application

Hi,
I am receiving a short dump while trying to open a Web Dynpro Application in FPM. I go to SE80 and open the Web Dynpro component 'FPM_OIF_COMPONENT'. I then choose the application '/sapsrm/wda_l_fpm_oif'. I then click Web Dynpro Application -> Test -> Execute in Administration Mode. A new IE browser is opened and I then receive a short dump. The name of the short dump runtime error is 'OBJECTS_OBJREF_NOT_ASSIGNED_NO' and the exception is 'CX_SY_REF_IS_INITIAL'.
I have not used FPM before. I would like to use it to remove the 'Close' button from this application. Do I need to initialize FPM before using it?
Please help.
Thanks,
Jeff

>
Chinnu wrote:
> Hello Jeffery Andersen,
>
> If I understand correctly, you are trying to preview FPM_OIF_COMPONENT.
>
> I think this component can not be executed as it just is a template for creating a FPM applications. In other words, it is an interface that can be used to created a WD ABAP application from work bench.
>
> This [Floor Plan Manager - ABAP|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/90f3cfd2-46d0-2b10-b3ab-eabf3452cc50&overridelayout=true] can help you understand better.
>
> Best regards,
> Chinnu
Hi Chinnu,
Your understanding is not correct, he is trying to execute the application /sapsrm/wda_l_fpm_oif'.
Hallo Jeff,
everyone have suggested lots of possibilities. Nothing works for you. I would suggest the following.
Go and execute any other FPM application which uses FPM_OIF_COMPONENT,does it work ?
If it works then you can narrow down that /sapsrm/wda_l_fpm_oif is not working and you can raise a OSS ticket.
If it is not working then you have to see if you have right BASIS versions to use FPM.
Edited by: Baskaran Senthivel on Dec 6, 2010 1:09 PM

Exchanging data between a Web Dynpro application and SAP Web Shop

I'll try to keep this as clear as possible:
1) We have the SAP Internet Sales system running, which has a series of Business Object classes and corresponding Backend Layer objects that can return data from several sources.
2) We are able to create our own Backend Layer objects that would return data from a component called IPC, which is a Java component.
3) I would like a Web Dynpro application to retrieve data from this backend layer object, but I am not experienced enough with Java to know if what I want to do is possible. I don't think that I can use JCo, because I am trying to get a Java component (class?) in Web Dynpro to access a Java class remotely.
4) I think I am asking is this: is there a way for a Java to Java connection to be created, much like Web Dynpro can use JCo to connect Java to ABAP systems?
If this is a glaringly obvious question to Java programmers, my apologies!
- Tony.

Somebody on another forum recommended using RMI. Which would be the better option in terms of ease of implementation?
- Tony

Problem in Closing a web dynpro application

Hi experts,
I wanted to close the application when the user clicks on the close button.
I created a out bound plug "EXIT" of type 'EXIT' in my window.
I also created a parameter "CLOSE_WINDOW" of type "WDY_BOOLEAN" for the outbound plug
Now in action of the close button i have done the below code:
DATA: l_ref_ywd_maintain_catalog TYPE REF TO ig_ywd_maintain_catalog .
l_ref_ywd_maintain_catalog = wd_this->get_ywd_maintain_catalog( ).
l_ref_ywd_maintain_catalog->fire_exit_plg( CLOSE_WINDOW = 'X'
where ywd_maintain_catalog is my window name.
when i check the program i am getting the below error:
get_ywd_maintain_catalog_ctr is unknown or protected or private.
I refered the standard web dynpro component "WDR_TEST_EXIT_PLUG" to implement the logic
Pls help
Regards,
Vinod

Hi all,
This is my requirement when i click on a close button the application should close.
i refered to a web dynpro component "WDR_TEST_EXIT_PLUG" where they have explained the way to use exit plug.
They have created a outbound plug in the window called "EXIT" of type exit. and in the action of the button they have used the below code to fire the outbound plug.
method onactionfire_exit .
data: l_ref_wdr_test_exit_plug type ref to ig_wdr_test_exit_plug .
l_ref_wdr_test_exit_plug = wd_this->get_wdr_test_exit_plug_ctr( ).
l_ref_wdr_test_exit_plug->fire_exit_plg(
url = 'http://www.google.de/'
endmethod.
I followed the similiar approach in my code:
I created a out bound plug "EXIT" of type exit in my window.
then in the action of the close button i have done the below code:
DATA: l_ref_ywd_maintain_catalog TYPE REF TO ig_ywd_maintain_catalog .
l_ref_ywd_maintain_catalog =wd_this->get_ywd_maintain_catalog_ctr( ).
l_ref_ywd_maintain_catalog->fire_exit_plg( CLOSE_WINDOW = 'X'
The problem i am facing is i am getting the error "method get_ywd_maintain_catalog_ctr is unknown or public or private"
I am referred to the below URL to do it :
link: [Exiting a Web Dynpro Application by pressing a button on a Web Dynpro View]
Regards,
Vinod

Reg Simple Web Dynpro Application

Hello Gurus,
I am developing a simple Web Dynpro Application that displays just Purchase Header Details.
It says the runtime Error, "The exception CX_WD_CONTEXT" was raised but was not caught at any stage in Call Hierarchy.
Any Suggestions would be rewarded.....
Regards
Jay

Hi,
I have pasted the short dump....
===========================================================
Runtime Errors UNCAUGHT_EXCEPTION
Except. CX_WD_CONTEXT
Date and Time 27.02.2007 11:48:17
 ShrtText
 An exception that could not be caught occurred.
 What happened?
 The exception 'CX_WD_CONTEXT' was raised but was not caught at any stage in the
 call hierarchy.
 Since exceptions represent error situations, and since the system could
 not react adequately to this error, the current program,
 'CL_WDR_CONTEXT_NODE_VAL=======CP', had to
 be terminated.
 What can you do?
 Print out the error message (using the "Print" function)
 and make a note of the actions and input that caused the
 error.
 To resolve the problem, contact your SAP system administrator.
 You can use transaction ST22 (ABAP Dump Analysis) to view and administer
 termination messages, especially those beyond their normal deletion
 date.
 is especially useful if you want to keep a particular message.
 Error analysis
 An exception occurred. This exception is dealt with in more detail below
 . The exception, which is assinged to the class 'CX_WD_CONTEXT', was not
 caught,
 which led to a runtime error.
 The reason for this exception is:
 Die Anzahl der Elemente der Kollektion des Knotens INDEX.1.EKKO_ITAB verletzt
 die Kardinalität.
 How to correct the error
 You may able to find an interim solution to the problem
 in the SAP note system. If you have access to the note system yourself,
 use the following search criteria:
 "UNCAUGHT_EXCEPTION" CX_WD_CONTEXTC
 "CL_WDR_CONTEXT_NODE_VAL=======CP" or "CL_WDR_CONTEXT_NODE_VAL=======CM001"
 "CHECK_COLLECTION"
 If you cannot solve the problem yourself and you wish to send
 an error message to SAP, include the following documents:
 1. A printout of the problem description (short dump)
 To obtain this, select in the current display "System->List->
 Save->Local File (unconverted)".
 2. A suitable printout of the system log
 To obtain this, call the system log through transaction SM21.
 Limit the time interval to 10 minutes before and 5 minutes
 after the short dump. In the display, then select the function
 "System->List->Save->Local File (unconverted)".
 3. If the programs are your own programs or modified SAP programs,
 supply the source code.
 To do this, select the Editor function "Further Utilities->
 Upload/Download->Download".
 4. Details regarding the conditions under which the error occurred
 or which actions and input led to the error.
 System environment
 SAP Release.............. "640"
 Application server....... "diamond"
 Network address.......... "64.72.230.131"
 Operating system......... "Windows NT"
 Release.................. "5.2"
 Hardware type............ "4x Intel 801586"
 Character length......... 8 Bits
 Pointer length........... 32 Bits
 Work process number...... 0
 Short dump setting....... "full"
 Database server.......... "DIAMOND"
 Database type............ "MSSQL"
 Database name............ "ECC"
 Database owner........... "ecc"
 Character set............ "English_United State"
 SAP kernel............... "640"
 Created on............... "Nov 21 2005 00:50:16"
 Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
 Database version......... "SQL_Server_8.00 "
 Patch level.............. "101"
 Patch text............... " "
 Supported environment....
 Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
 SAP database version..... "640"
 Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
 Memory usage.............
 Roll..................... 8112
 EM....................... 12543552
 Heap..................... 0
 Page..................... 0
 MM Used.................. 11868848
 MM Free.................. 672136
 SAP Release.............. "640"
 User and Transaction
 Information on where terminated
 The termination occurred in the ABAP program "CL_WDR_CONTEXT_NODE_VAL=======CP"
 in "CHECK_COLLECTION".
 The main program was "SAPMHTTP ".
 The termination occurred in line 12 of the source code of the (Include)
 program "CL_WDR_CONTEXT_NODE_VAL=======CM001"
 of the source code of program "CL_WDR_CONTEXT_NODE_VAL=======CM001" (when
 calling the editor 120).
 Source Code Extract
 Line SourceCde
 1 method CHECK_COLLECTION .
 2
 3 data:
 4 path_name type string,
 5 lines type i.
 6
 7 lines = lines( me->collection ).
 8
 9 if ( lines = 0 and abap_true = me->node_info->is_mandatory ) or
 10 ( lines > 1 and abap_false = me->node_info->is_multiple ).
 11 path_name = me->if_wd_context_node~get_path( ).
 >>>>> raise exception type CX_WD_CONTEXT exporting textid = CX_WD_CONTEXT=>COLLECTION_ILLEGAL_
 13 endif.
 14
 15 lines = lines( me->selection ).
 16
 17 if ( lines = 0 and abap_true = me->node_info->is_mandatory_selection ) or
 18 ( lines > 1 and abap_false = me->node_info->is_multiple_selection ).
 19 path_name = me->if_wd_context_node~get_path( ).
 20 raise exception type CX_WD_CONTEXT exporting textid = CX_WD_CONTEXT=>SELECTION_ILLEGAL_C
 21 endif.
 22
 23
 24 endmethod.
 Contents of system fields
 Name Val.
 SY-SUBRC 0
 SY-INDEX 1
 SY-TABIX 1
 SY-DBCNT 12919
 SY-FDPOS 34
 SY-LSIND 0
 SY-PAGNO 0
 SY-LINNO 1
 SY-COLNO 1
 SY-PFKEY
 SY-UCOMM
 SY-TITLE HTTP Control
 SY-MSGTY
 SY-MSGID
 SY-MSGNO 000
 SY-MSGV1
 SY-MSGV2
 SY-MSGV3
 SY-MSGV4
 Active Calls/Events
 No. Ty. Program Include Line
 Name
 22 METHOD CL_WDR_CONTEXT_NODE_VAL=======CP CL_WDR_CONTEXT_NODE_VAL=======CM001 12
 CL_WDR_CONTEXT_NODE_VAL=>CHECK_COLLECTION
 21 METHOD CL_WDR_CONTEXT_NODE_VAL=======CP CL_WDR_CONTEXT_NODE_VAL=======CM01B 34
 CL_WDR_CONTEXT_NODE_VAL=>IF_WD_CONTEXT_NODE~BIND_TABLE
 20 METHOD /1BCWDY/MXAJIDSD2PZXCNSR7DDN==CP /1BCWDY/B_UXWMB4OI2PW6SWO6N6KC 1058
 CL_INDEX_CTR=>WDDOINIT
 Web Dynpro Component ZJAY_WEBDYN1
 Web Dynpro Controller INDEX
 19 METHOD /1BCWDY/MXAJIDSD2PZXCNSR7DDN==CP /1BCWDY/B_UXWMB4OI2PW6SWO6N6KC 167
 CLF_INDEX_CTR=>IF_WDR_VIEW_DELEGATE~WD_DO_INIT
 Web Dynpro Component ZJAY_WEBDYN1
 Web Dynpro Controller INDEX
 18 METHOD CL_WDR_DELEGATING_VIEW========CP CL_WDR_DELEGATING_VIEW========CM003 3
 CL_WDR_DELEGATING_VIEW=>DO_INIT
 17 METHOD CL_WDR_CONTROLLER=============CP CL_WDR_CONTROLLER=============CM00Q 3
 CL_WDR_CONTROLLER=>INIT_CONTROLLER
 16 METHOD CL_WDR_VIEW===================CP CL_WDR_VIEW===================CM00K 5
 CL_WDR_VIEW=>INIT_CONTROLLER
 15 METHOD CL_WDR_CONTROLLER=============CP CL_WDR_CONTROLLER=============CM002 12
 CL_WDR_CONTROLLER=>INIT
 14 METHOD CL_WDR_VIEW_MANAGER===========CP CL_WDR_VIEW_MANAGER===========CM008 58
 CL_WDR_VIEW_MANAGER=>GET_VIEW
 13 METHOD CL_WDR_VIEW_MANAGER===========CP CL_WDR_VIEW_MANAGER===========CM005 23
 CL_WDR_VIEW_MANAGER=>BIND_ROOT
 12 METHOD CL_WDR_VIEW_MANAGER===========CP CL_WDR_VIEW_MANAGER===========CM00B 21
 CL_WDR_VIEW_MANAGER=>INIT
 11 METHOD CL_WDR_INTERFACE_VIEW=========CP CL_WDR_INTERFACE_VIEW=========CM004 5
 CL_WDR_INTERFACE_VIEW=>INIT_CONTROLLER
 10 METHOD CL_WDR_CONTROLLER=============CP CL_WDR_CONTROLLER=============CM002 12
 CL_WDR_CONTROLLER=>INIT
 9 METHOD CL_WDR_CLIENT_COMPONENT=======CP CL_WDR_CLIENT_COMPONENT=======CM003 46
 CL_WDR_CLIENT_COMPONENT=>DISPLAY_TOPLEVEL_COMPONENT
 8 METHOD CL_WDR_CLIENT_APPLICATION=====CP CL_WDR_CLIENT_APPLICATION=====CM00I 30
 CL_WDR_CLIENT_APPLICATION=>INIT
 7 METHOD CL_WDR_WEBDYNPRO_MAIN_TASK====CP CL_WDR_WEBDYNPRO_MAIN_TASK====CM008 29
 CL_WDR_WEBDYNPRO_MAIN_TASK=>IF_WDR_CLIENT_TASK~EXECUTE
 6 METHOD CL_WDR_CLIENT_MANAGER=========CP CL_WDR_CLIENT_MANAGER=========CM004 18
 CL_WDR_CLIENT_MANAGER=>PROCESS_TASK_LISTS
 5 METHOD CL_WDR_CLIENT_MANAGER=========CP CL_WDR_CLIENT_MANAGER=========CM002 99
 CL_WDR_CLIENT_MANAGER=>DO_PROCESSING
 4 METHOD CL_HTTP_EXT_WEBDYNPRO=========CP CL_HTTP_EXT_WEBDYNPRO=========CM001 77
 CL_HTTP_EXT_WEBDYNPRO=>IF_HTTP_EXTENSION~HANDLE_REQUEST
 3 METHOD CL_HTTP_SERVER================CP CL_HTTP_SERVER================CM00D 645
 CL_HTTP_SERVER=>EXECUTE_REQUEST
 2 FUNCTION SAPLHTTP_RUNTIME LHTTP_RUNTIMEU02 879
 HTTP_DISPATCH_REQUEST
 1 MODULE (PBO) SAPMHTTP SAPMHTTP 13
 %_HTTP_START
 Chosen variables
 Name
 Val.
 No. 22 Ty. METHOD
 Name CL_WDR_CONTEXT_NODE_VAL=>CHECK_COLLECTION
 ABAP_TRUE
 X
 5
 8
 ME->NODE_INFO->IS_MANDATORY
 X
 5
 8
 LINES
 12919
 7300
 7200
 %_DUMMY$$
 2222
 0000
 SYST-REPID
 CL_WDR_CONTEXT_NODE_VAL=======CP
 4455455444545554444554433333334522222222
 3CF742F3FE4584FEF45F61CDDDDDDD3000000000
 ABAP_FALSE
 2
 0
 ME->NODE_INFO->IS_MULTIPLE
 2
 0
 SY-REPID
 CL_WDR_CONTEXT_NODE_VAL=======CP
 4455455444545554444554433333334522222222
 3CF742F3FE4584FEF45F61CDDDDDDD3000000000
 ME
 O:167*=CL_WDR_CONTEXT_NODE_VAL
 5000A000
 80007000
 RSJOBINFO
 00000000000000 ####
 222222222222222222222222222222223333333333333322222222222222222222222222222222220000
 000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 PATH_NAME
 INDEX.1.EKKO_ITAB
 44445232444454544
 9E458E1E5BBFF9412
 SY
 ########################################w2##"#################################################
 0000000000000000000000000000000000000000730020000000000000000000000000000000000000000000000000
 1000000010001000000000000000000000000000720020001000000010000000000000000000800000000000000000
 %_EXCP
 O:13087*=CX_WD_CONTEXT
 E0001300
 0000F300
 SPACE
 2
 0
 CX_WD_CONTEXT=>COLLECTION_ILLEGAL_CARDINALITY
 B5CA499B9D5CBA47B8D4664C56B3A97C
 43443334343444334343333433434334
 25314992945321472844664356231973
 ME->SELECTION
 Table[initial]
 ME->NODE_INFO->IS_MANDATORY_SELECTION
 2
 0
 ME->NODE_INFO->IS_MULTIPLE_SELECTION
 2
 0
 No. 21 Ty. METHOD
 Name CL_WDR_CONTEXT_NODE_VAL=>IF_WD_CONTEXT_NODE~BIND_TABLE
 NEW_ITEMS
 Table IT_325[12919x492]
 POOL=/1BCWDY/MXAJIDSD2PZXCNSR7DDN=CL_INDEX_CTR=WDDOINIT=ITAB_EKKO
 Table reference: 153
 TABH+ 0(20) = C8E8E33CD0C4E73C000000009900000045010000
 TABH+ 20(20) = 77320000EC010000FFFFFFFF04C30000801B0000
 TABH+ 40( 8) = 10000000C1308000
 store = 0xC8E8E33C
 ext1 = 0xD0C4E73C
 shmId = 0 (0x00000000)
 id = 153 (0x99000000)
 label = 325 (0x45010000)
 fill = 12919 (0x77320000)
 leng = 492 (0xEC010000)
 loop = -1 (0xFFFFFFFF)
 xtyp = TYPE#000116
 occu = 16 (0x10000000)
 access = 1 (ItAccessStandard)
 idxKind = 0 (ItIndexNone)
 uniKind = 2 (ItUniqueNon)
 keyKind = 1 (default)
 cmpMode = 8 (cmpManyEq)
 occu0 = 1
 collHash = 0
 groupCntl = 0
 rfc = 0
 unShareable = 0
 mightBeShared = 0
 sharedWithShmTab = 0
 isShmLockId = 0
 gcKind = 0
 isUsed = 1
 >>>>> Shareable Table Header Data <<<<< tabi = 0xF8C9E33C
pghook = 0x08E9E33C
idxPtr = 0x00000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16368 (0xF03F0000)
lineAlloc = 12944 (0x90320000)
store_id = 202 (0xCA000000)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<< regHook = 0x80EFFE3C
hsdir = 0x00000000
ext2 = 0x00000000
>>>>> 2nd level extension part <<<<< tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
SET_INITIAL_ELEMENTS
X
5
8
ELEMENT
O:13086*=CL_WDR_CONTEXT_ELEMENT
E0001300
1000E300
ELEMENT->NODE
O:167*=CL_WDR_CONTEXT_NODE_VAL
5000A000
80007000
ME
O:167*=CL_WDR_CONTEXT_NODE_VAL
5000A000
80007000
ME->COLLECTION
Table IT_330[12919x8]
O:167*=CL_WDR_CONTEXT_NODE_VAL=COLLECTION
Table reference: 157
TABH+ 0(20) = 78F2FE3C00000000000000009D0000004A010000
TABH+ 20(20) = 7732000008000000FFFFFFFF04D10000E0030000
TABH+ 40( 8) = 10000000C1288000
store = 0x78F2FE3C
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 157 (0x9D000000)
label = 330 (0x4A010000)
fill = 12919 (0x77320000)
leng = 8 (0x08000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000008
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 4 (cmpSingleEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<< tabi = 0xE8F1FE3C
pghook = 0x18B8D83C
idxPtr = 0x00000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 15408 (0x303C0000)
lineAlloc = 13360 (0x30340000)
store_id = 207 (0xCF000000)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<< regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<< tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
SY-TABIX
1
0000
1000
%_SPACE
2
0
ME->LEAD_SELECTION_INDEX
1
0000
1000
ME->LEAD_SELECTION
O:168*=CL_WDR_CONTEXT_ELEMENT
5000A000
70008000
ME->NODE_INFO->IS_MANDATORY_SELECTION
2
0
ME->SELECTION
Table[initial]
ME->NODE_INFO->IS_INITIALIZE_LEAD_SELECTION
X
5
8
ME->IF_WD_CONTEXT_NODE~NO_SELECTION
-1
FFFF
FFFF
ME->ELEMENTS_SUPPLIED
2
0
No. 20 Ty. METHOD
Name CL_INDEX_CTR=>WDDOINIT
IF_WDR_APPLICATIONAPPLICATION_INFO->STARTUP_PLUG->IF_WD_RR_PARAM_FEATUREPARAMETERS
 Table[initial]
 State Dump for Thread Id 1488
 eax=00000001 ebx=00000103 ecx=fffffffe edx=003c0000 esi=00000000 edi=00000000
 eip=7c82ed54 esp=0589feb0 ebp=0589fef4 iopl=0 nv up ei pl zr na po nc
 cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
 function : KiFastSystemCallRet
 7c82ed54 c3 ret
 7c82ed55 8da42400000000 lea esp,[esp] ss:0589feb0=7c821514
 7c82ed5c 8d642400 lea esp,[esp] ss:098bd47f=00000000
 FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
 0589fef4 00ff70c7 000006c4 00000000 00000000 044bed68 ntdll!KiFastSystemCallRet
 0589ff84 7c349565 00000000 00000000 00000000 044becd0 disp+work!SigIMsgFunc
 0589ffb8 77e6608b 044becd0 00000000 00000000 044becd0 MSVCR71!endthreadex
 0589ffec 00000000 7c3494f6 044becd0 00000000 00000000 kernel32!GetModuleFileNameA
 List of ABAP programs affected
 Index Ty. Program Group Date Time Size Lang.
 0 Prg SAPMHTTP 0 06.11.2003 20:57:21 6144 E
 1 Prg SAPLHTTP_RUNTIME 1 12.11.2004 04:12:18 152576 E
 2 Typ ICFHANDLST 0 21.11.2003 11:40:58 13312
 3 Prg %_CIHTTP 1 12.11.2004 03:26:38 36864 E
 4 Typ ICFSERVICE 0 21.11.2003 11:41:18 13312
 5 Typ ICFATTRIB 0 06.11.2003 20:36:18 4096
 6 Typ ICFLOGIN 0 12.11.2004 03:26:38 9216
 7 Prg CL_HTTP_SERVER================CP 7 12.11.2004 04:13:34 154624 E
 8 Typ ICFRECORDER 0 06.11.2003 20:36:19 12288
 9 Typ IOPROP 0 29.03.2001 16:07:43 2048
 10 Typ ICFSTAT 0 09.11.2000 14:08:22 2048
 11 Prg CL_HTTP_UTILITY===============CP 11 12.11.2004 03:48:49 15360 E
 12 Prg CL_ABAP_TRACE=================CP 12 06.11.2003 21:53:44 6144 E
 13 Prg CL_ICF_RECORDER===============CP 13 12.11.2004 03:26:45 8192 E
 14 Prg CL_HTTP_SERVER_NET============CP 14 12.11.2004 04:13:34 101376 E
 15 Typ ICFRECODER_LOGON 0 06.11.2003 20:28:45 3072
 16 Prg CL_ABAP_RUNTIME===============CP 16 06.11.2003 20:59:29 8192 E
 17 Prg CL_HTTP_REQUEST===============CP 17 12.11.2004 03:48:50 20480 E
 18 Prg CL_HTTP_ENTITY================CP 18 12.11.2004 03:48:50 41984 E
 19 Prg CL_HTTP_RESPONSE==============CP 19 12.11.2004 04:13:34 24576 E
 20 Typ ICFALIAS 0 21.11.2003 11:41:17 13312
 21 Typ ICFVIRHOST 0 19.01.2001 18:13:06 2048
 22 Typ ICFBUFFER 0 21.11.2003 11:41:18 16384
 23 Prg SAPLSHTTP 23 12.11.2004 03:49:05 166912 E
 24 Typ ICFAPPLCUST 0 21.11.2003 11:41:17 2048
 25 Prg CL_HTTP_USER_CONTEXT==========CP 25 12.11.2004 03:48:50 9216 E
 26 Typ BAPIALIAS 0 09.12.1999 13:47:51 1024
 27 Prg SAPLLANG 27 06.11.2003 20:53:03 8192 E
 28 Typ T002 0 14.02.1998 10:24:58 2048
 29 Typ ABAPTEXT 0 16.03.1993 18:19:31 1024
 30 Prg SAPLSCP2 30 23.11.2004 18:49:18 126976 E
 31 Prg SSO2GETPARAM 1 06.11.2003 20:57:30 15360 E
 32 Prg SAPLSSFG 32 09.12.2003 11:41:04 116736 E
 33 Typ SSFARGS 0 19.11.2001 15:50:14 5120
 34 Typ PARMVALUES 0 03.01.1996 15:26:26 2048
 35 Prg SAPLSPFC 35 12.11.2004 03:38:48 239616 E
 36 Typ MOD_FIELDS 0 16.07.1997 14:42:34 2048
 37 Typ SSF_PSE_H 0 15.11.2000 17:54:53 4096
 38 Typ ICFRECSTRU 0 06.11.2003 20:28:45 2048
 39 Prg SAPLSAUTHTRACE 39 16.03.2004 20:07:17 43008 E
 40 Typ IHTTPNVP 0 29.03.2001 16:07:42 2048
 41 Prg CL_HTTP_EXT_WEBDYNPRO=========CP 41 12.11.2004 03:49:03 49152 E
 42 Prg IF_HTTP_EXTENSION=============IP 7 29.03.2001 17:03:40 5120 E
 43 Prg CL_HTTP_EXT_1X1_GIF===========CP 43 12.11.2004 03:48:51 11264 E
 44 Prg IF_HTTP_HEADER_FIELDS_SAP=====IP 43 06.06.2001 13:26:02 5120 E
 45 Prg CL_WDR_CLIENT_MANAGER=========CP 45 12.11.2004 03:48:52 47104 E
 46 Prg CL_WDR_TASK===================CP 46 12.11.2004 03:49:04 46080 E
 47 Prg CL_WDR_EVENT_QUEUE============CP 47 06.11.2003 21:11:25 10240 E
 48 Prg CX_WDR_RT_EXCEPTION===========CP 48 06.11.2003 21:15:08 15360 E
 49 Typ SCX_SRCPOS 0 09.11.2000 14:12:15 2048
 50 Prg CX_WD_EXCEPTION===============CP 50 06.11.2003 21:15:11 10240 E
 51 Prg CX_NO_CHECK===================CP 51 06.11.2003 21:33:04 8192 E
 52 Prg CX_ROOT=======================CP 52 06.11.2003 21:56:05 9216 E
 53 Prg CL_WDR_CLIENT_SSR=============CP 53 12.11.2004 04:21:19 121856 E
 54 Prg CL_WDR_CLIENT_ABSTRACT_HTTP===CP 54 12.11.2004 03:48:52 58368 E
 55 Prg CL_DYNP_GLOBAL_CONTROL========CP 55 06.11.2003 21:02:15 7168 E
 56 Prg CL_WDR_CLIENT_INSPECTOR=======CP 56 12.11.2004 03:48:49 39936 E
 57 Typ WDR_CLIENTS 0 06.11.2003 20:38:42 2048
 58 Typ WDR_CLIENT_DATA 0 06.11.2003 20:33:21 2048
 59 Prg CL_WDR_CLIENT_CONSTANTS=======CP 59 06.11.2003 21:11:17 12288 E
 60 Prg CL_WDR_CLIENT_CSF=============CP 60 12.11.2004 03:48:50 103424 E
 61 Prg IF_WDR_CLIENT_DESCRIPTION=====IP 56 06.11.2003 21:34:13 3072 E
 62 Prg CL_WDR_CLIENT_CSF_COND========CP 62 12.11.2004 03:26:52 32768 E
 63 Prg CL_WDR_CLIENT_ABSTRACT_COND===CP 63 12.11.2004 03:26:52 32768 E
 64 Prg IF_WDR_CLIENT_CONDITION=======IP 56 06.11.2003 21:34:13 29696 E
 65 Prg IF_WDR_CLIENT_INFO_OBJECT_HDL=IP 56 06.11.2003 21:34:13 29696 E
 66 Prg CL_WDR_CLIENT_XML=============CP 66 12.11.2004 03:48:49 80896 E
 67 Prg CL_WDR_CLIENT_XML_COND========CP 67 12.11.2004 03:48:49 32768 E
 68 Prg CL_WDR_VIEW_ELEM_ADAPTER_MNG==CP 68 06.11.2003 22:00:29 49152 E
 69 Prg CL_WDR_UIEL_ADAPTER_MANAGER===CP 69 16.03.2004 19:57:19 13312 E
 70 Prg CL_WDR_ABSTRCT_ADAPTER_MANAGERCP 70 06.11.2003 21:11:15 9216 E
 71 Typ WDY_MD_CHANGE_INFORMATION 0 06.11.2003 20:33:22 2048
 72 Typ WDY_UI_LIBRARY 0 06.11.2003 20:38:47 3072
 73 Prg CL_EXITHANDLER================CP 73 12.11.2004 03:49:03 27648 E
 74 Prg CL_ABAP_TYPEDESCR=============CP 74 07.11.2003 13:01:59 26624 E
 75 Prg CL_ABAP_ELEMDESCR=============CP 75 06.11.2003 22:11:36 33792 E
 76 Prg CL_ABAP_DATADESCR=============CP 76 06.11.2003 22:10:04 16384 E
 77 Prg CL_ABAP_REFDESCR==============CP 77 07.11.2003 13:01:58 20480 E
 78 Prg CL_ABAP_STRUCTDESCR===========CP 78 21.11.2003 11:42:45 34816 E
 79 Prg CL_ABAP_COMPLEXDESCR==========CP 79 06.11.2003 22:10:04 14336 E
 80 Prg CL_ABAP_TABLEDESCR============CP 80 06.11.2003 22:11:36 21504 E
 81 Prg CL_ABAP_CLASSDESCR============CP 81 06.11.2003 22:11:36 25600 E
 82 Prg CL_ABAP_OBJECTDESCR===========CP 82 06.11.2003 22:11:36 29696 E
 83 Prg CL_ABAP_INTFDESCR=============CP 83 06.11.2003 22:11:36 20480 E
 84 Prg CL_ABAP_SOFT_REFERENCE========CP 84 06.11.2003 20:41:10 8192 E
 85 Prg CL_ABAP_REFERENCE=============CP 85 06.11.2003 20:52:43 6144 E
 86 Prg IF_EX_WDR_UIE_LIBRARY=========IP 77 09.12.2003 11:45:52 4096 E
 87 Prg %_CABAP 83 06.11.2003 22:07:49 25600 E
 88 Typ SXS_INTER 0 30.11.1998 15:55:16 2048
 89 Prg SAPLSEXV 89 16.03.2004 20:14:01 108544 E
 90 Prg CL_BADI_FLT_DATA_TRANS_AND_DB=CP 90 12.11.2004 03:49:03 35840 E
 91 Typ SXS_ATTR 0 20.08.2001 12:23:27 4096
 92 Typ V_EXT_ACT 0 09.11.2000 14:27:05 2048
 93 Typ SXC_EXIT 0 09.11.2000 14:23:43 2048
 94 Prg SAPLSEXE 94 12.11.2004 03:49:05 78848 E
 95 Typ TADIR 0 09.11.2000 14:14:40 4096
 96 Prg SAPLPA_PACKAGE_SERVICES 96 12.11.2004 04:12:26 121856 E
 97 Typ SXS_MLCO 0 04.12.2000 14:59:55 2048
 98 Prg CL_EX_WDR_UIE_LIBRARY=========CP 98 09.12.2003 11:43:56 24576 E
 99 Prg CL_WDR_EVENT_ADAPTER_MANAGER==CP 99 06.11.2003 22:00:29 35840 E
 100 Prg CL_WDR_CLIENT_SSR_COND========CP 100 12.11.2004 03:48:49 33792 E
 101 Prg CL_WDR_SERVER_SESSION=========CP 101 09.12.2003 11:39:43 39936 E
 102 Prg CL_WDR_CLIENT_INFO_OBJECT=====CP 102 06.11.2003 21:11:17 12288 E
 103 Prg CL_WDR_CLIENT_USER============CP 103 06.11.2003 21:11:19 34816 E
 104 Prg SAPLISOC 104 06.11.2003 20:53:02 26624 E
 105 Prg CL_WDR_LOCALE=================CP 105 06.11.2003 21:11:28 7168 E
 106 Prg CL_WDR_CLIENT_SESSION=========CP 106 06.11.2003 21:11:18 36864 E
 107 Typ WDR_NAME_VALUE 0 06.11.2003 20:33:21 2048
 108 Prg CL_WDR_CLIENT_WINDOW==========CP 108 06.11.2003 21:11:19 40960 E
 109 Prg IF_WDR_CLIENT=================IP 56 06.11.2003 21:34:13 30720 E
 110 Prg CX_SY_MOVE_CAST_ERROR=========CP 110 06.11.2003 20:41:23 9216 E
 111 Prg CX_DYNAMIC_CHECK==============CP 111 06.11.2003 21:33:04 8192 E
 112 Prg CL_WDR_REC_PLUGIN_MANAGER=====CP 112 06.11.2003 22:00:29 50176 E
 113 Typ WDR_REC_PLUGIN 0 06.11.2003 20:38:42 2048
 114 Prg SAPLSPLUGIN 114 06.11.2003 21:28:25 6144 E
 115 Prg CL_WDR_WEBDYNPRO_MAIN_TASK====CP 115 12.11.2004 03:49:04 60416 E
 116 Prg IF_WDR_CLIENT_TASK============IP 45 06.11.2003 21:34:13 4096 E
 117 Typ WDR_EVENT_ADAPTER 0 09.12.2003 11:37:55 2048
 118 Prg CL_WDAL_URD2_DYNPRO_CONVERSIONCP 118 12.11.2004 04:21:19 263168 E
 119 Prg CL_WDR_SYSTEM_EVT_HANDLER_REG=CP 119 06.11.2003 21:11:35 33792 E
 120 Prg CL_WDR_ABSTRACT_SRV_EVTHDL_REGCP 120 06.11.2003 21:11:15 34816 E
 121 Prg CL_WDR_CLIENT_APPLICATION=====CP 121 12.11.2004 03:48:49 67584 E
 122 Prg CL_WDR_CLIENT_COMPONENT=======CP 122 09.12.2003 11:39:43 64512 E
 123 Prg CL_WDR_RR_RUNTIME_REPOSITORY==CP 123 16.03.2004 19:57:19 27648 E
 124 Prg CL_WDR_RR_APPLICATION=========CP 124 06.11.2003 22:00:29 29696 E
 125 Typ WDY_APPLICATION 0 06.11.2003 20:38:43 3072
 126 Prg CX_WDR_RR_EXCEPTION===========CP 126 09.12.2003 11:39:45 15360 E
 127 Typ WDY_RT_OBJECT_MAP 0 06.11.2003 20:33:24 2048
 128 Prg CL_WDR_RR_COMPONENT===========CP 128 12.11.2004 03:49:04 73728 E
 129 Typ WDY_RR_COMPONENT 0 27.01.2004 13:51:32 2048
 130 Typ WDY_RR_VIEW 0 06.11.2003 20:33:24 2048
 131 Typ WDY_RR_VIEW 0 06.11.2003 20:33:24 2048
 132 Typ WDY_RR_WINDOW 0 06.11.2003 20:33:24 2048
 133 Typ WDY_RR_WINDOW 0 06.11.2003 20:33:24 2048
 134 Typ WDY_RR_COMPO_USAGE 0 06.11.2003 20:33:23 2048
 135 Typ WDY_RR_COMPO_USAGE 0 06.11.2003 20:33:23 2048
 136 Typ WDY_RR_CONTROLLER 0 06.11.2003 20:33:23 2048
 137 Typ WDY_RR_CONTROLLER 0 06.11.2003 20:33:23 2048
 138 Typ WDY_RR_VUSAGE 0 06.11.2003 20:33:24 3072
 139 Typ WDY_RR_VUSAGE 0 06.11.2003 20:33:24 3072
 140 Typ WDY_RR_VCA_INFO 0 06.11.2003 20:33:23 2048
 141 Typ WDY_RR_VCA_INFO 0 06.11.2003 20:33:23 2048
 142 Typ WDY_RR_NAV_LINK 0 06.11.2003 20:33:23 2048
 143 Typ WDY_RR_NAV_LINK 0 06.11.2003 20:33:23 2048
 144 Typ WDY_RR_NAV_TARGREF 0 06.11.2003 20:33:23 2048
 145 Typ WDY_RR_NAV_TARGREF 0 06.11.2003 20:33:23 2048
 146 Typ WDY_SUBSCRIBED_EVENT 0 06.11.2003 20:33:24 2048
 147 Typ WDY_SUBSCRIBED_INBOUND_PLUG 0 06.11.2003 20:33:24 2048
 148 Typ WDY_RR_CTLR_COMPO 0 06.11.2003 20:33:23 3072
 149 Typ WDY_RR_CTLR_COMPO 0 06.11.2003 20:33:23 3072
 150 Typ WDY_RR_UI_EVT_BIND 0 06.11.2003 20:33:23 2048
 151 Typ WDY_RR_UI_EVT_BIND 0 06.11.2003 20:33:23 2048
 152 Typ WDY_RR_UI_VIEW_CONT 0 06.11.2003 20:33:23 2048
 153 Typ WDY_RR_UI_VIEW_CONT 0 06.11.2003 20:33:23 2048
 154 Typ WDY_RR_IOBOUND_PLUG 0 06.11.2003 20:33:23 2048
 155 Typ WDY_RR_IOBOUND_PLUG 0 06.11.2003 20:33:23 2048
 156 Typ WDY_RR_PARAMETER 0 06.11.2003 20:33:23 2048
 157 Typ WDY_RR_PLUG_PARAMS 0 06.11.2003 20:33:23 3072
 158 Typ WDY_RR_PLUG_PARAMS 0 06.11.2003 20:33:23 3072
 159 Typ WDY_RR_UI_ELEM_DEFS 0 06.11.2003 20:33:23 3072
 160 Typ WDY_RR_UI_ELEM_DEFS 0 06.11.2003 20:33:23 3072
 161 Typ WDY_RR_UI_ELEM 0 06.11.2003 20:33:23 3072
 162 Typ WDY_RR_UI_ELEM 0 06.11.2003 20:33:23 3072
 163 Typ WDY_RR_CLUSTER 0 27.01.2004 13:51:32 21504
 164 Prg CL_WDY_MD_PARAM_FEATURE=======CP 164 16.03.2004 20:12:30 25600 E
 165 Typ WDY_MD_OBJECT_DESCRIPTION 0 09.12.2003 11:37:56 2048
 166 Prg CL_WDY_MD_OBJECT==============CP 166 06.11.2003 22:00:30 12288 E
 167 Prg CL_WDR_RR_DB==================CP 167 16.03.2004 20:12:30 82944 E
 168 Typ WDY_COMPONENT 0 06.11.2003 20:38:43 3072
 169 Typ WDY_RR_TEXT 0 06.11.2003 20:33:23 2048
 170 Typ SOTR_KEY 0 09.12.1999 13:48:20 2048
 171 Typ SOTR_TERM 0 15.11.2000 17:54:28 3072
 172 Prg SAPLSOTR_DB_READ 172 12.11.2004 04:15:08 39936 E
 173 Typ SOTR_CNTXT 0 09.12.1999 13:48:20 2048
 174 Typ SOTR_ADMIN 0 09.12.1999 13:48:20 2048
 175 Typ SOTR_TEXT 0 06.11.2003 20:31:14 5120
 176 Typ SOTR_HEAD 0 15.11.2000 17:54:28 4096
 177 Prg CL_WDR_RR_EMPTY_VIEW==========CP 177 06.11.2003 21:11:32 28672 E
 178 Prg CL_WDR_RR_ABSTRACT_VIEW=======CP 178 06.11.2003 22:00:29 35840 E
 179 Prg CL_WDR_RR_INBOUND_PLUG========CP 179 06.11.2003 21:11:32 32768 E
 180 Prg CL_WDR_RR_INCOMING_EVENT======CP 180 06.11.2003 21:11:32 26624 E
 181 Prg CL_WDR_RR_PARAM_FEATURE=======CP 181 06.11.2003 21:11:33 28672 E
 182 Prg CL_WDR_RR_COMPONENT_INTF_IMPL=CP 182 06.11.2003 21:11:31 29696 E
 183 Prg CL_WDR_RR_COMPONENT_INTERFACE=CP 183 06.11.2003 21:11:30 31744 E
 184 Prg CL_WDR_RR_CONTROLLER==========CP 184 06.11.2003 22:00:29 36864 E
 185 Prg CL_WDR_RR_WINDOW==============CP 185 06.11.2003 22:00:29 43008 E
 186 Prg CL_WDR_RR_VIEW_USAGE==========CP 186 06.11.2003 22:00:29 54272 E
 187 Prg CL_WDY_MD_ABSTRACT_VIEW=======CP 187 19.07.2004 03:41:57 96256 E
 188 Typ WDY_VIEW 0 06.11.2003 20:38:47 4096
 189 Prg CL_WDR_RR_VIEW================CP 189 06.11.2003 22:00:29 39936 E
 190 Prg CL_WDR_RR_INTERFACE_VIEW======CP 190 06.11.2003 21:11:32 30720 E
 191 Prg CL_WD_TODO====================CP 191 06.11.2003 21:12:50 24576 E
 192 Prg CL_WDR_CONFIGURATION_CONSTANTSCP 192 06.11.2003 21:11:20 6144 E
 193 Prg CL_WDR_SERVER_CONSTANTS=======CP 193 06.11.2003 21:11:34 6144 E
 194 Prg CL_WDR_UI_ELEMENT_FACTORY=====CP 194 06.11.2003 21:11:36 31744 E
 195 Prg /1BCWDY/MXAJIDSD2PZXCNSR7DDN==CP 195 24.02.2007 13:45:21 89088 E
 196 Prg IF_WDR_CLASSLOADER============IP 122 06.11.2003 21:34:13 27648 E
 197 Prg CL_WDR_DELEGATING_COMPONENT===CP 197 06.11.2003 21:11:24 46080 E
 198 Prg CL_WDR_COMPONENT==============CP 198 06.11.2003 22:09:16 60416 E
 199 Prg CL_WDR_CONTROLLER=============CP 199 06.11.2003 22:00:29 45056 E
 200 Prg IF_WDR_CONTEXT================IP 197 06.11.2003 21:34:13 27648 E
 201 Typ WDR_CONTEXT_ATTR_VALUE 0 06.11.2003 20:33:21 2048
 202 Typ WDR_CONTEXT_ATTR_VALUE 0 06.11.2003 20:33:21 2048
 203 Typ WDR_CONTEXT_ATTRIBUTE_INFO 0 06.11.2003 20:33:21 3072
 204 Typ WDR_CONTEXT_MAPPING_INFO 0 06.11.2003 20:33:21 2048
 205 Prg CL_WDR_CONTEXT_NODE_INFO======CP 205 09.12.2003 11:39:43 29696 E
 206 Prg CX_WD_CONTEXT=================CP 206 06.11.2003 21:15:10 12288 E
 207 Prg CL_WDR_CONTEXT_NODE===========CP 207 09.12.2003 11:39:43 45056 E
 208 Typ WDR_CONTEXT_CHILD 0 06.11.2003 20:33:21 2048
 209 Prg CL_WDR_CONTEXT_NODE_VAL=======CP 209 09.12.2003 11:39:43 66560 E
 210 Prg IF_WDR_COMPONENT_DELEGATE=====IP 195 16.03.2004 20:12:31 27648 E
 211 Prg IF_WD_CONTROLLER==============IP 197 09.12.2003 11:46:03 27648 E
 212 Prg CL_WDR_MESSAGE_MANAGER========CP 212 09.12.2003 11:39:43 74752 E
 213 Prg CL_WDR_DATA_CONTAINER=========CP 213 09.12.2003 11:39:43 69632 E
 214 Typ WDY_RT_DATA_CONT_ATTR_MAP 0 06.11.2003 20:33:24 3072
 215 Typ WDY_RT_DATA_CONT_CNTL 0 06.11.2003 20:33:24 2048
 216 Prg CL_WDR_APPLICATION_WINDOW=====CP 216 06.11.2003 21:11:15 44032 E
 217 Prg CL_WDR_WINDOW=================CP 217 06.11.2003 22:00:29 50176 E
 218 Prg IF_WDR_APPLICATION============IP 101 06.11.2003 22:07:12 29696 E
 219 Typ WDR_EVENT_PARAMETER 0 06.11.2003 20:33:21 2048
 220 Typ WDR_VIEWMAN_LINE 0 06.11.2003 20:33:21 2048
 221 Prg CL_WDR_VIEW_MANAGER===========CP 221 12.11.2004 03:49:04 70656 E
 222 Prg IF_WDR_VIEW_MANAGER===========IP 221 06.11.2003 22:07:12 27648 E
 223 Typ WDR_CONTROLLER_LINE 0 06.11.2003 20:33:21 2048
 224 Prg CX_WDR_BAD_STATE==============CP 224 06.11.2003 21:15:06 9216 E
 225 Prg CX_WDR_RUNTIME================CP 225 06.11.2003 21:15:08 10240 E
 226 Typ WDR_CLIENTCOMP_LINE 0 06.11.2003 20:33:21 2048
 227 Prg CL_WDR_WINDOW_MANAGER=========CP 227 06.11.2003 21:11:39 37888 E
 228 Prg CL_WDR_DELEGATING_IF_VIEW=====CP 228 06.11.2003 21:11:24 45056 E
 229 Prg CL_WDR_INTERFACE_VIEW=========CP 229 06.11.2003 21:11:28 43008 E
 230 Prg CL_WDR_VIEW===================CP 230 06.11.2003 22:00:29 62464 E
 231 Prg IF_WDR_VIEW_DELEGATE==========IP 195 16.03.2004 20:12:31 27648 E
 232 Prg IF_WD_CONTEXT_NODE============IP 228 09.12.2003 11:46:03 31744 E
 233 Prg IF_WD_CONTEXT_NODE_INFO=======IP 228

Weblog for Simple way to debug ESS and MSS Web Dynpro Java applications

Here is the link to the new Weblog topic "Simple way to debug ESS and MSS Web Dynpro Java applications"
/people/yugandhar.reddy/blog/2011/03/26/simple-way-to-debug-ess-and-mss-web-dynpro-java-based-applications--very-useful-technique

Thanks Siddharth. I was trying as you suggested, I was trying to add the link to the FAQ's but looks like the wiki is locked or I dont have permission to create a page in it. Is there any other way to do it?
Edited by: Yugandhar Reddy on Mar 28, 2011 5:04 PM

Close External Window in Web Dynpro Application

Hi Folks,
I am working on a development in Web Dynpro and I am pretty new to this topic, so I seek your help.
The scene is:
I have created a Web Dynpro application in which I open an URL using CREATE_EXTERNAL_WINDOW method of the Window Controller. I am able to open the window but not able to close it.
I tried using methods,
CLOSE()
and
SET_CLOSE_IN_ANY_CASE()
but no success.
Please guide me if anything more needs to be done for closing the opened window.
Thank you.
Sud.

Thank you Thomas,
You correctly pointed out, I was trying to close the external window from my source window.
More precisely, I have a WD application which has a button (Search) on one of its views. On click of 'Search' button, I open a new window using 'CREATE_EXTERNAL_WINDOW' passing the URL 'www.google.com'.
Till this point its fine, but now I want to close this newly opened window. As you said now these are 2 different sessions and cannot communicate anymore, so any guidance how to close this new window?.
OR
Is this the only way to call an URL i.e using CREATE_EXTERNAL_WINDOW? Is there any other way to call an URL without closing my current running WD application?
Request your help......
Thanks.
Regards,
Sud....

Error when web dynpro application is deployed

Hi,
I get this error when i deploy the web dynpro application
Could you please help to know wat it is about ? my application is extremely simple hello world application.
java.lang.ClassNotFoundException: helloworld.wdp.InternalHelloworld -
Loader Info -
ClassLoader name: [local/helloworld] Parent loader name: [Frame ClassLoader] References: common:service:http;service:servlet_jsp service:ejb common:service:iiop;service:naming;service:p4;service:ts service:jmsconnector library:jsse library:servlet common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl library:ejb20 library:j2eeca library:jms library:opensql common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore interface:resourcecontext_api interface:webservices interface:cross interface:ejbserialization sap.com/tcwddispwda sap.com/tcwdcorecomp service:webdynpro service:sld library:tcddicddicservices library:com.sap.aii.proxy.framework library:tcgraphicsigs library:com.sap.mw.jco library:com.sap.lcr.api.cimclient library:sapxmltoolkit library:com.sap.aii.util.rb library:com.sap.util.monitor.jarm library:tcddicddicruntime library:com.sap.aii.util.xml library:com.sap.aii.util.misc library:tc~cmi Resources: D:\usr\sap\ID6\DVEBMGS00\j2ee\cluster\server0\apps\local\helloworld\webdynpro\public\lib\app.jar Loading model: {parent,references,local} -
thanks......

Hi Murtuza,
I have done it.
Reload means I closed and opened the project
but still i get the error
this time it also says negative cache
The initial exception that caused the request to fail, was:
java.lang.ClassNotFoundException: helloworld.wdp.InternalHelloworld Found in negative cache -
Loader Info -
ClassLoader name: [local/helloworld] Parent loader name: [Frame ClassLoader] References: common:service:http;service:servlet_jsp service:ejb common:service:iiop;service:naming;service:p4;service:ts service:jmsconnector library:jsse library:servlet common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl library:ejb20 library:j2eeca library:jms library:opensql common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore interface:resourcecontext_api interface:webservices interface:cross interface:ejbserialization sap.com/tcwddispwda sap.com/tcwdcorecomp service:webdynpro service:sld library:tcddicddicservices library:com.sap.aii.proxy.framework library:tcgraphicsigs library:com.sap.mw.jco library:com.sap.lcr.api.cimclient library:sapxmltoolkit library:com.sap.aii.util.rb library:com.sap.util.monitor.jarm library:tcddicddicruntime library:com.sap.aii.util.xml library:com.sap.aii.util.misc library:tc~cmi Resources: D:\usr\sap\ID6\DVEBMGS00\j2ee\cluster\server0\apps\local\helloworld\webdynpro\public\lib\app.jar Loading model: {parent,references,local} -

How to get User Id in Web dynpro application

Hi Experts,
I am running web dynpro application with authentication checkbox set. I want to display user id of the user in my application. I am using following code in Init method of component controller.
IWDClientUser wdUser = WDClientUser.getCurrentUser();
WdContext.currentContextElement().setUserName           (wdUser.getClientUserID());
Here I am getting some integer value as userId.
I am not using Portals, so solutions suggested for portal are not useful for me .
Is there any way to get this uset id.
Thanks in advance

hi
try this piece of code
          IWDClientUser wdUser = WDClientUser.getCurrentUser();
          IUser user = wdUser.getSAPUser();
          if (user != null)
                    IUserAccount[] acct = user.getUserAccounts();
                    if(acct[0] != null)
                              String strUserid = acct[0].getLogonUid();
wdContext.currentZtms_Fm_Regupdate_InputElement().setAssoid(new String(strUserid));
Note: Defining the IUser will show an error. To resolve this, within the properties of
the project, choose Java build path -> Libraries -> Add external jars ->
com.sap.securities -> lib -> com.sap.security.api. Open this file and retype the code.

Errors in While trying to Deopy Web Dynpro Application

Hi,
I have NetWeaver 2004S in My local System. I am facing one problem while deploying that Web Dynpro Application from NWDS. Error is pasted below. But i can deploy EP Application. I am facing the same problem when i tried to Deploy from Remote GUI.
Can anyone help me in fixing this problem.
Thanks,
Sridhar
Exception i got while deploying.
Starting Deployment of SampleWD
Aborted: development component 'SampleWD'/'local'/'LOKAL'/'0.2006.06.05.11.29.10':
Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [H1B-2F241-HMY] with user name: [Administrator] Check your login information. Exception is: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.]
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)
Deployment of SampleWD finished with Error (Duration 2473 ms)

Hi Sridhar,
Please follow the steps below:
1. Open ConfigTool ( drive:\usr\sap\J2E (your instance)\JC01\j2ee\configtool
2. Go to Secure Store and change the password for the property admin/password/J2E (This password should same as the one you are trying to login to portal)
3. Click Add
4. Click Save and restart your server.
Should be able to deploy your components.
Happy deploying
Best Regards,
Shiva

The Web Dynpro Application 'Explorer' has expired

hi,
when I am trying to open the deployed content in the
Content Administrator in the sap portal I am getting the following error
"500 Internal Server Error The Web Dynpro Application 'Explorer' has expired. Restart the application using the Refresh button or via the following link Explorer.
Details:
No details available"
what can I do?
I have read here at sdn that I should increase the expiration time but where can I do this?

Hi Thorsten,
Close your explorer, open a new explorer and run the application from the new browser.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b52de690-0201-0010-c5a6-b4bde0a12e44
<a href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_ep_sys/~form/handler">SAP Note Number: 519191</a>
<a href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_fes/~form/handler">SAP Note Number: 856741</a>
Regards,
Mithu

The Web Dynpro Application 'WebUI' has expired,

Hi experts,
We are using Netweaver 7.01 portal , I have done some change to the portal for configuring idle timeout .
Now currently we are not using that in portal ,so i removed all the configurations
When i am using the all the other portal applications it is working fine, but when i am using webdynpro java applications it is giving the following error in a couple of mins (less then 5 mins)
The Web Dynpro Application 'WebUI' has expired. Restart the application using the Refresh button or via the following link WebUI.
Please let me know how to resolve this is issue .
Thanks & Regards,
Pavan Marla

Hi,
Check this link and below settings
DefaultExpirationTime
=================
http://help.sap.com/saphelp_nw04s/helpdata/en/43/8a1a8ece230c8ce10000000a11466f/content.htm
Check the time for session timeout by the following steps:
1. Open the visual admin tool.
2. Navigate to Server -> Services -> Web Container -> Properties.
3. Check the value of the property 'SessionTimeout'.
Regards,
Nivas209
Edited by: Nivas209 on Feb 8, 2012 12:50 PM
Edited by: Nivas209 on Feb 8, 2012 12:51 PM
Edited by: Nivas209 on Feb 8, 2012 1:03 PM
Edited by: Nivas209 on Feb 8, 2012 1:06 PM

Reg: Closing and Opening Web Dynpro Application in same browser

Similar Messages

Maybe you are looking for