JCO Connection for web-dynpro tutorials (EP 6.0 SP9 downlaod from SDN)

Hello,
I have a question regarding JCO connections for web-dynpro example/tutorials. I have installed WAS 6.40 sneak preview from EP 6.0 SP9 download from SDN. Installation instruction says: Choose "No SLD available"
but the web-dynpro example/tutorial asks to create JCO connections by going to web-dynpro -> content admin..etc on http:<host>:50000..Here, all the tabs relating to creating JCO connections appear to be "protected" on my screen. so I can't do anything further. By going to http:<host>:50000/sld, I also tried to add SLD server..but that is not helping. There is some "import" button, but which CIM file (in which folder etc) am i supposed to import for a simple test system? What are the steps for a bare minimum setup so that I can use the WAS 6.20 system at work-place as my backend & try out the web-dynpro examples? Do I really need SLD setup? Where is documentation about all this after one installs the WAS 6.40 JAva? I was expecting it somewhere at least in the eclipse IDE help-documentation..None of the web-dynpro tutorials explain this !
thanks

Thanks everybody.
NagaKishore, after doing all the steps, when I goto
localhost:50000-> web dynpro -> content administartor, and try to "maintain JCO Destinations" I am getting this error: (full stack trace not included)
An error has occurred:
"Failed to process the request."
Please contact your system administrator.
Error stacktrace:
java.lang.NullPointerException
     at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:871)
     at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:485)
     at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.updateJCOClientStatus(JCOConnectionsDetails.java:438)
     at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:634)
     at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:598)
     at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.wdDoInit(JCOConnectionsDetails.java:120)
     at com.sap.tc.webdynpro.tools.explorer.wdp.InternalJCOConnectionsDetails.wdDoInit(InternalJCOConnectionsDetails.java:238)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)

Similar Messages

Creation of JCO Destinations for web dynpro

Hi all,
I read quite a lot of post concerning the subject but unfortunately I did not found a solution to my problem.
My goal is to create JCO Destinations to make my web dynpro to connect to an R3 system.
In order to realise this I followed these steps :
- Launch visual admin and set http settings, rfc settings, and cim client settings. I click on CIM client test and the result is a success so I assume this part is correct.
- In R3, I execute transaction smgw, go to remote gateway to get the gateway settings. I execute RZ70 and filled the parameters just checked. Then I activate and launch the data collect. I have no error message and everythings seemed to work fine.
- In the sld (<host>:<port>/sld) I configured my server settings, the I go to data bridge, set update local sld to true and fill RFC gateway info with the same values as in my R3 system. Then I restarted the sld.
- Finally I went to Web Dynpro content administrator to create my destinations and there I failed. After entering all settings (the message server appears in my technical landscape in SLD), when I click on finish I've got the following exception :
[code]
Failed to create new JCO client connection WD_FLIGHTLIST_RFC_METADATA_DEST:
com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
at
com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:140) at
com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection
(SystemLandscapeFactory.java:286) at
com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish
(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:252) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:100) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:299) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:641) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at
com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263) at
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318) at
com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:824) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37) at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at
com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162) Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for WD_FLIGHTLIST_RFC_METADATA_DEST at
com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestinaton(JCOClientConnection.java:664) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:508) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:247) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:221) at
com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:138) ... 30 more Caused by: java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:393) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestinaton(JCOClientConnection.java:558) ... 35 more[/code]
I tried to create a generic destination (no for the web dynpro tutorial) and failed again.
I do not undestand what I did wrong.
Does someone have an idea ?
Thanks for reading this !
Sylvain
Message was edited by: Sylvain

This thread helped me too because before reading it I didn't thought that I had to create a logon group "PUBLIC".
Anyway I succed in creating 'WD_FLIGHTLIST_MODELDATA_DEST' and the test is ok. The problem was that in sld / technical system / web as abap, my Central Application Server host was wrong. It is not possible to change it so I just add a secondary server with the right host and select this one when creating the destination.
The only pb remaining is now 'WD_FLIGHTLIST_RFC_METADATA_DEST'. I think the pb is my message server such this is the only difference between the two destinations
Thanks for your help
Message was edited by: Sylvain

JCO conn. for WAS 6.40 trial install (EP 6.0 SP9 download from SDN)

Hello,
I have a question regarding JCO connections for web-dynpro example/tutorials. I have installed WAS 6.40 sneak preview from EP 6.0 SP9 download from SDN. Installation instruction says: Choose "No SLD available"
but the web-dynpro example/tutorial asks to create JCO connections by going to web-dynpro -> content admin..etc on http:<host>:50000..Here, all the tabs relating to creating JCO connections appear to be "protected" on my screen. so I can't do anything further. By going to http:<host>:50000/sld, I also tried to add SLD server..but that is not helping. There is some "import" button, but which CIM file (in which folder etc) am i supposed to import for a simple test system? What are the steps for a bare minimum setup so that I can use the WAS 6.20 system at work-place as my backend & try out the web-dynpro examples? Do I really need SLD setup? Where is documentation about all this after one installs the WAS 6.40 JAva? I was expecting it somewhere at least in the eclipse IDE help-documentation..None of the web-dynpro tutorials explain this !
thanks

HI,
E:usrsap<SID>DVEBMGS30j2eeadmingo.bat
HERE IS VA and its Guide
Netweaver 6.4 Admin Manual for J2EE
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/webas620/administration manual for sap j2ee engine 6.20.pdf

Create iView for Web Dynpro Application

Hi guys,
I've created a Web Dynpro Application via NWDI and deployed to the j2ee server. Now, I'm trying to create an iView to link to that application. The steps I've done are:
1. Create iView for Web Dynpro Application
2. Select "Create iView from each application View"
3. Select my application.
That's when the error occurs at step 3. I select my application and click next, but an error msg keeps appearing telling me to "To continue, select at least one application" despite having already done so. Can anyone enlighten me on this? Thanks!
ZHenmin

Hi,
First make sure the applications runs fine standalone. Also the versions for WAS and EP are maintained correctly. Actually, this error seems to be occur for many users. Check this thread too.
Open new Web Dynpro iView in EP7
If nothing works, restart the server and try creating the iView again.
Regards,
Harini S

Problem in connecting JCO destination in web dynpro

HI all,
I was installed sneak preview of Net weaver 6.4,
I want to do some web dynpro (java) programs which connect to back end systems.(R/3 system).
The R/3 system which I want to connect is at remote place, i have connectivity to that R/3 system using VPN connectivity. With this I am not having any problem. Since I am able to connect using User name and password, and able to do some transactions like RZ70, etc.
I developed an application which calls COMPANY_CODE_GET_LIST (BAPI function).
for the above requirement what I did was
(1)I created SLD setting.
(a)Web as Java (I am not having any problem to
Create this.
(b) Web as ABAP.
When i am trying to create
This, there are some steps like i need to go to SAP log in and I need to run the transaction RZ70. For this i need to create an enter in visual administrator>JCO RFC Provider>runtime-->Bundles i need to create an entry for RFC destination as well as Repository.
under RFC destination there are some fields which i need to enter those are (a)Program ID as mySLD (b) Gateway Host as 10.10.10.125 (c)Gateway service as sapgw00 (d)Number of processes as 1
Under Repository (a) Application server host 10.10.10.125 (b)system number as 00 (c)Client number as 100 (d)Language as en (e)user as ABCD (f)password as 1234
I haven't choused the check boxes Local bundle and Unicode and pressed the set button. So like this i created the RFC destinations. under the properties tab there is a property called RFC_DEFAULT_DESTINATION by default it was false so i made it as true. .
I also went to SLD Data Supplier,under Runtime tab , HTTP Settings , I mentioned
(a)Host: pava-vis75
(b) Port: 50000
(c) user: administrator
(d) password: abcd1234
RFC Settings, I mentioned as
(a)Gateway Host: 10.10.10.125 (which is SAP R/3 system)
(b)Gateway Service/Host: sapgw00
CIM Client Generation settings, as
(a)Host: pava-vis75
(b)Port (http/https):50000
(c) user: administrator
(d) Password : abcd1234
I tested the CIMClient Test by click the the button. I got the successful message.
Then I came back to HTTP settings and clicked the button with tilted arrow mark [This triggers data transfer to system landscape directory], for this also I got a successfully message.[data transferred successfully]
Next I been to SAPLOGON and went to RFC Destinations by using sm59 transaction. There under TCP/IP connections i been to SLD_NUC , opened this by double clicking that and under Technical settings for Program ID I had given the ID which I created at visual administrator [JCO RFC Provider] which is mySLD , under gateway options for Gateway Host as 10.10.10.125and Gateway service as sapgw00 then i tested the connection, it was also successfully.
Then I opened the SLDAPICUST and i created a new entry for maintaining the SLD Access Data by giving some couple of entries as
(a)Alias: vissldtest
(b)Host Name: pava-vis75
(c)Port: 50000
(d) user: administrator
(e) password: abcd1234
Then saved it.
Next I created sapmsUV0 3600/tcp entry at
WINDOWS\system32\drivers\etc\services file, and also there are some required entries which are already existing those are sapgw00 3300/tcp to sapgw99 3399/tcp , another entry starts from sapdp00s 4700/tcp to sapdp99s 4799/tcp , next entry starts from sapgw00s 4800/tcp to sapgw99s 4899/tcp and sapmsJ2E 3601/tcp .
I restarted the system, as well as server.
Now my problem is when I was trying to create JCO destination at web dynpro content administrator. For that I navigated as create JCO Destination Deployed Contentlocal-local/CompanyCodeGetList-Applications CompanyCodeGetList
I Choosed the JCO Connections tab- there are 2 entries those are
(1) COMPANY_CODE_MODEL
(2) COMPANY_CODE_RFC_METADATA
So I started creating connection for COMPANY_CODE_RFC_METADATA.
First one is
General data Name : COMPANY_CODE_RFC_METADATA
Client : 100
I didnt changed any default JCo pool configuration.
J2EE Cluster
There is a check box called Use Local J2EE engine J2E on pava-vis75 so I choosed that.
Connection Type
Dictionary Meta Data and application Data
I choosed the first one.
Then
Msg. Server Connection
Security
After these, I tried to test the connection by clicking the Test Connection.
It is saying the error as
First time
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=v011 GROUP=DEFAULT R3NAME=UV0 MSSERV=sapmsUV0 PCS=1 ERROR service 'sapmsUVO' unknown TIME Fri Jul 01 07:20:41 2006 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -3 COUNTER 1
second time
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=v011 GROUP=DEFAULT R3NAME=UV0 MSSERV=sapmsUV0 PCS=1 ERROR service '?' unknown TIME Fri Jul 01 07:20:41 2006 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -3 COUNTER 1
Can any body please help me to solve this problem.
From past 1 week on wards I have been trying to resolve this. But in vain.

It does not necessarily mean that you have to change that parameter. I read that blog as I had a similar problem, and after reading it and understanding the reasons and possible causes for the error, I found that my particular problem was that I was using "PUBLIC" as the logon group in my JCO destinations, but such a group does NOT exist at my backend. I went to transaction SMLG, had a look at Logon Groups, noted that there were none other than SPACE, figured out that I had to include that information in SLD (Web AS ABAP tech. system --> Message Server --> Logon Groups), put it there. Voilá. It works.
Edit: That SPACE logon group is the one I had to use at JCO destinations. Sorry I forgot to mention that one...
Regards,
Eduardo.
Message was edited by: Jesus Cil

LDAP connectivity in web Dynpro

How to do LDAP connectivity in web dynpro to make use of UME

After installing the LDAP go to configtool UME
Select the option from the dropdown
then
Provide the server name : The server in which you have installed the LDAP
port :389/636
username=cn=<the username>,o=<context name>
password=<the passsword provided by you while installing>
browse to find the data for the path below
userpath
grouppath
After this the UME in portal can be configured in the LDAP

JCO connection for Meta Data fails

Hi,
I have installed the WebAS Preview version with SP9. I had installed it once and had succesfully configured the JCo connection to my R/3 system. After I re-installed the WebAS after a system format, I have configured the JCo for both model & metadata. Both are configured to connect to the same R/3 sytem with the same user/password combination. But the JCo connection for model data pings and test come OK. But the one for metadata fails (ping as well as test).
I have tried creating more JCo connections with different names, but again the model one works, but not the metadata one.
Can anyone figure out why this is happening?
Regards,
Sumith.

Hi,
The error that I get when testing the JCo connection is:
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=ltilsap GROUP=PUBLIC R3NAME=LTI MSSERV=sapmsLTI PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR service 'sapmsLTI' unknown TIME Fri Jan 21 16:37:40 2005 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -3 MODULE ninti.c LINE 494 DETAIL NiPGetServByName2: service 'sapmsLTI' not found SYSTEM CALL getservbyname_r COUNTER 1
and when I ping it gives:
Failed to ping JCo destination 'LTI_WDMETADATA_DEST'.
But the connection for model data works perfectly for the same set of configuration.
Thanks & Regards,
Sumith

Want docs for Web Dynpro ABAP

Hi All ,
Can anyone please send me the Docs or link for Web Dynpro ABAP .
Thanks in advance
Rahul

Hi,
Web Dynpro ABAP
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/db22242d-0701-0010-28a2-aeaa1fefd706
Also, I have the official Web Dynpro for ABAP documentation. Please let me know if I should send it to you.
Hope that the following also helps you.
Web Dynpro for ABAP (WD4A, WDA) is the SAP standard UI technology for developing Web
applications in the ABAP environment. It consists of a runtime environment and a graphical
development environment with special Web Dynpro tools that are integrated in the ABAP
Workbench (SE80).
Web Dynpro offers the following advantages for application developers:
? The use of declarative and graphical tools significantly reduces the implementation
effort
? Web Dynpro supports a structured design process
? Strict separation between layout and business data
? Reuse and better maintainability by using components
? The layout and navigation is easily changed using the Web Dynpro tools
? Stateful applications are supported that is, if the page is changed and the required
data remains intact so that you can access it at any time throughout the entire
application context.
Note that stateless applications are not possible.
? Automatic data transport using data binding
? Automatic input check
? Automatic operation of the Web Dynpro application using the keyboard
? User interface accessibility is supported
? Full integration in the reliable ABAP development environment
Web Dynpro Architecture
Definition
Web Dynpro is the SAP NetWeaver programming model for user interfaces (UIs).
The Web Dynpro model is based on the Model View Controller paradigm, and has the
following features that build on the classic dynpro model:
? Clear separation of business logic and display logic
? Uniform metamodel for all types of user interfaces
? Execution on a number of client platforms.
? Extensive platform independence of interfaces
Structure
Metamodel Concept
Web Dynpro provides support for developing Web representation of a business application.
You use specific tools to describe the properties of a Web Dynpro application in the form of
Web Dynpro metadata. The necessary source code is then generated automatically and
executed at runtime. In addition to the events offered by the framework, you can also define
your own events for a Web Dynpro application. However, the event handling must always be
programmed in separate source code areas which are executed automatically when the event
is triggered at runtime.
In Web Dynpro, each user interface is always made up of the same basic elements. These
elements of the metamodel can be statically declared using Web Dynpro tools.
It is also possible to implement elements of the metamodel at runtime and to change them or
reintegrate them at runtime. Using these implementations, you can make any changes or
enhancements to a user interface that has been created by declarative methods by
generating new interface structures at runtime.
This means that you can combine declarative processes and the implementation of source
code.
Graphical Development Tools
To support this declarative concept, both the SAP NetWeaver Developer Studio and the
ABAP Workbench contain a range of Web Dynpro tools. You can therefore generate a large
proportion of a Web Dynpro application using the tools provided, without having to create your
own source code. This applies to the following parts of the application:
? Data flow between the front end and back end
? Layout of the user interface
? Properties of user interface elements
The Web Dynpro tools enable you to create source text areas manually within generated
source texts. These areas are not changed if the source code is regenerated.
Separation of Business and Application Logic
Using Web Dynpro enables a clear separation of business logic and display logic. A Web
Dynpro application runs on the front end and has local or remote access to the back end
system via a service. This means that the display logic is contained in the Web Dynpro
application, while the business logic and the persistence of the business objects run in the
back end system. The following options are currently available for connecting Web Dynpro
applications and the back-end system:
? An interface generated using adaptive RFC, through which BAPIs of an SAP system
can be called
? An interface for calling Web services
? A self-generated interface
The source code required for connecting the Web Dynpro application can be generated
from a UML definition of the Web Dynpro interface. A UML definition can be imported
into the Web Dynpro tools as an XML file.
Conversion of the Model-View-Controller
Conversion of the Model-View-Controller Programming Model
Every Web Dynpro application is structured according to the Model View Controller
programming model:
? The model forms the interface to the back end system and thus enables the
Web Dynpro application access to data.
? The view is responsible for the representation of the data in the browser.
? The controller lies between the view and the model. The controller formats
the model data to be displayed in the view, processes the user entries made by the
user, and returns them to the model.
/people/thomas.jung/blog/2006/06/20/web-dynpro-abap-demonstration-videos
http://help.sap.com/saphelp_nw04s/helpdata/en/77/3545415ea6f523e10000000a155106/frameset.htm
Reward points if useful
Regards
Anji

Links for WEB DYNPRO

PLease send me links for web dynpro,also if anyone interested in selling books for technical SAP please reply.

Hi,
Please refer the below links.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sapportals.km.docs/library/web-application-server/a-c/creating%20your%20first%20web%20dynpro%20application.pdf
Web Dynpro for ABAP: Tutorials for Beginners [original link is broken]
http://sappro.com/downloads/WebDynproJava.pdf
www.slideshare.net/Naresh007/web-dynpro-for-abap-tuto-1
Hope this helps you.
Kind Regards,
Ravi Sankar.Z

CAS connect to Web Dynpro

Hallo All,
I want to connect my Web Dynpro application with a CAS Project.
I have include the Cas-Model with "add Model" and I see it.
But I can't see the CAS application services and Entity Service under
the model.
Regards,
Philipp

Hello,
I have seen the case where people have coded switches into their reports (hidden parameters) that allow the report to be run and instead of exporting the results to an ALV table, have exported the results to a memory address. Then these memory areas have been read and exported to a WD. (there are standard SAP pieces of logic that used to do this in ESS and MSS in the old ITS days)
You can just execute the report from inside the WD code and retrieve the result...
Personally I don't like this approach! I don't like using global memory area for a start! I also have tried to replace any web based reporting with POWLs - which have a different approach to selections - i.e. knowing this before the user runs the report.
I think you would be better off modularising your report so it applied the MVC paradigm - the code for the report should be broken up so that the display and selection logic (view) is separated from the extraction logic (Model) the controller logic is pretty much the report code itself - and where I have built this approach (eg a backend report and a WD report that use the same logic) I have merged the view and controller logic in the report and pretty much also done this in the WD too - but the Model is identical in both cases.
Hope this helps,
Chris

Want documents for   Web Dynpro ABAP

Hi All ,
Can anyone please send me the Docs or link for   Web Dynpro ABAP .
Thanks in advance
Rahul

Hi Rahul,
   Welcome to the interesting world of Web Dynpro ABAP !
For Web dynpro ABAP you will require SAP ECC 6.0 onwards and WAS 7.0
is a must. It has very good future propspects as this is best UI technology.
In web dynpro ABAP we follow MVC(Model View Controller) architecture.
In this object oriented ABAP is used to provide background functionality. Here, your ABAP skills can be utilized to the fullest. Programming in web dynpro ABAP is different than conventional ABAP programming. Here we strictly follow MVC architecture in terms of controller interface. Also there are many wizards available so that we can directly pick the code from wizards.
e.g We can call BAPI through a service call in web dynpro application. Thus automatically backgroud code for BAPI execution will be generated.
To start with Web dynpro ABAP you can try following tutorial:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a282c952-0801-0010-1eb5-87953e036712
You can start with tutorials and all. There are around six tutorials in SDN library.
Web Dynpro for ABAP
http://help.sap.com/saphelp_erp2005/helpdata/en/a5/1a1e3e7181b60ae10000000a114084/frameset.htm
best tutorials in wbdynpro for ABAP to start with :
https://www.sdn.sap.com/irj/sdn/developerareas/webdynpro?rid=/webcontent/uuid/fed073e5-0901-0010-4eb4-c9882aac7b11 [original link is broken]
Have a look at the following SDN WDA Wiki . There you can find all relevant information.
https://wiki.sdn.sap.com/wiki/display/WDABAP/Main
First of all start doing SAP SDN tutorials .
Create some compenents with BAPI , Component usage and ALV .
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/02e1fa45-0801-0010-10a0-f1cf47e8c943
/people/marilyn.pratt/blog/2005/12/20/web-dynpro-for-abap
Try to Download demo tutorials from SDN library & Try to search WebDynpro ABAP WebLogs .
Wait not just that SAP has provided you with ample demo example of WD ABAP already bundled with SAP . Just Try out Components starting with WDR . I can tell you few like WDR_TEST_EVENTS ( It shows how every UI elments to use )
See packages like SWDP_DEMO , SALV_WD_DEMO
there are many more .
/people/marilyn.pratt/blog/2005/12/20/web-dynpro-for-abap
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a282c952-0801-0010-1eb5-87953e036712
The specified item was not found.
Also you can search weblogs on web dynpro ABAP.
Hope this will help you.
Cheers,
Darshna.

Web Dynpro tutorials

Hi everybody!
Long time ago the last time I was programming Webdynpro for Java I had found many tutorials how to create my Webdynpros. There was also a matrix where I could choose the different tutorials (about 20 tutorial). Unfortunately I can not find them any more on SDN.
Pretty sure that someone can help me. Of course I will award.
Bye Markus

Hello singer,
you could check in sdn aswell if not that matrix tutorials look at individual ones you will find all those individually ....
these documents have sample applications and study materials too....
https://www.sdn.sap.com/irj/sdn/nw-wdjava
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/49f2ea90-0201-0010-ce8e-de18b94aee2d
Tutorials & Samples for Web Dynpro Java
http://www.vogella.de/articles/SAPWebDynpro/article.html
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/60e5add3-8349-2a10-9594-bcb7d1b4bd2d
http://help.sap.com/saphelp_nw04/helpdata/en/80/c12041aa7df323e10000000a155106/frameset.htm
New Web Dynpro Java Tutorial - Component Interface Definitions in Practice
/thread/330020 [original link is broken]
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6d599690-0201-0010-12bb-b9ea3ea32d22
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a788fda2-0c01-0010-f5a3-b1445014369e
Pradeep

How to configure SSO for web dynpro ABAP (not web dynpro Java)

Hi Experts,
 I am testing SSO in IDES for web dynpro ABAP (Not for web dynpro Java / not for portal). When I am entering url of web dynpro application in web browser like internet explorer, then it should ask for user id and password first time, after login whenever user would access that url, it must not ask for user ID and password (url would be access web browser in mobile). For this I select to configure single sign-on for web dynpro ABAP. I have done below works:
1). I have created a web dynpro application having url: http://susws076.sap.swk:<port>/sap/bc/webdynpro/sap/zadb_hello_world2
2). I run TCode SICF and access service node to "Zadb_hello_world2". Double click on it, hit change. pressed "logon data" tab, select "Alternative logon
 procedure"
 Then deleted all logon procedure other than "SSO Authentication" and saved.
3). Go to "STRUST" and create certificate, choosed "Environment==> Logon Ticket" fill the required parameters and execute. It is OK (no red traffic
 signal).
4). Execute TCode "RZ10" to change profile parameter, insert new parameter (indicated by red arrow)
After all this settings I opened a browser enter above URL and hit enter but there is an error
There is no login page. It directly showed this error page. No cookies is saving.
Can anyone tell me what all the settings/configuration other than this I have to do. And is there any wrong setting done by me?
How to set the for single sign-on?
Thanks in Advance
Regards
Piyush

Hi Piyush,
Pls refer below links,
Single Sign On with ABAP WebDynpro
http://help.sap.com/saphelp_nw70ehp2/helpdata/en/5e/6c85c3edf942f39349a1e337434d29/content.htm
Regards
K.N

Error while creating jco connection for metadata?

Hi all,
we are using ep 6 sp 16.
I could create the JCO connection for application data but i am not able to create the jco connection for metadata for the same r3 server .
while creating the the connection
system name and logon group and disable
and when i click finish
it is giving following error
Failed to create new JCO client connection testmetadata: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection. at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:150) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:180) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for testmetadata at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:670) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:486) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:252) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:226) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:180) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Caused by: java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:606) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:564) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:486) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:252) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:226) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:180) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Thanking.
Rajendra

Hello Rajendra,
Good to hear from u. Let me try to give a soln for this problem of yours.
I think probably the logon group has not been specified in the backend.If thats the case then do the following:
Connect to the backend server for which you are trying to create the JCO. Run the transaction SMLG. It will show u the existing logon groups. carry out the following steps if the 'PUBLIC' group is not present in the list of logon groups.
Click on the create button. In the pop-up, type the logon as 'PUBLIC'. For the instance, select the F4 help and choose the existing instance number. Click on copy and click save. Try running the transaction /nsmlg and now it should show the logon group 'PUBLIC'.
When you create the JCO connection, it should now show the logon group 'PUBLIC'.
Regards,
Prathamesh.

Search help for Web Dynpro using the SAP-search help

Hi,
Im trying to create a generic search help for Web Dynpro using the SAP-search help. It should working so, that I construct a Web Dynpro-component, that gets the data of the search help from the SAP-system, interpreted it and creates the ui-elements and the needed context generic.
The mapping between the Input field of the customerview and the right search help is to be made with an xml-file, which contains the information: name of the view, the input field, the search-help-name and the name of the field that will be returned.
The xml-file is reading from a helper-class. That helper-class contains any information, witch need the search help-component as well as the customer-component.
The initialization takes place in the method wdDoModify of the customer. The call of the search help from the customer should be implement with an Action, witch is bound to a Button(create dynamic in the helper-class behind the input field).
In a second foot should be create a plugin for eclipse, witch insert the used files (search help component, helper class, ) in the project. In addition it should create the call in the customer generic.
It would be great if someone can give me a feedback!

Hi Mike,
The BlanketAgreement.exe is a reference to the executable that will be created when you compile the solution you created in Part II - Part III. I think there is a mistake in the tutorial because it asks you to name the project 'Blanket' which means that by default the executable will be called Blanket.exe and not BlanketAgreement.exe. The tutorial also misses the step asking you to compile the Blanket project before you go on to create an installer. You should compile your Blanket project in Release mode before creating an installer. By compiling the project you'll get a Blanket.exe file in the bin folder of your Blanket project which you then need to add to the installer per the instructions.
SAP do offer development courses in some areas and there is training material here on the SDN and on the SAP partner portal (and maybe the customer portal as well). Try searching this forum for 'training' or 'tutorial' and you should get a few links. There's also a development certification.
Personally I'd recommend you give yourself a little project to work on and just get stuck in
Kind Regards,
Owen

JCO Connection for web-dynpro tutorials (EP 6.0 SP9 downlaod from SDN)

Similar Messages

Maybe you are looking for