How Web Dynpro supports RSS (ATOM)?

Let's image to generate our feed (RSS/ATOM) via java classes or xslt; now how is it possibile to expose it to the end-user?
From the development point of view it is similar to expose other Web Dynpro UI and it would be nice to use the same "prospective" and project also for this kind of comunication method...

Valery, thanks for the replay.
I agree with you: "nothing of special about RSS/ATOM and
No problem also building the XML object".
Let me try again:
- user contacts the url of the WD application
- the system should response just with the RSS xml data and not with UI objects (tableView, textEdit, ...)
But the WD does not allow you "to send out raw XML" even "send out raw HTML".
It allows "only" to build nice UI via objects it knows.
When you say "construct contex value nodes" do you mean that you are able to replay with the raw XML data?
Are you really able to response to a browser as the following url https://forums.sdn.sap.com/rss/rssmessages.jsp?threadID=75910
does? (It is the feed of this post)
Sergio

Similar Messages

How web dynpro abap is used for snc

Hi folks,
I am new to web dynpro abap.Some one told we can upgrade snc from lower version to higher version but i dont have any knowledge on snc.For upgrading snc what we must have 2 know. How web dynpro abap is used for upgrading snc.Pls provide any links related to web dynpro abap with snc.
Thanks in advance

Hello Ravidanda,
I have found a link that provides some information on how Web Dynpro ABAP is used in SAP SNC in the SAP Help. Here you go:
http://help.sap.com/saphelp_snc70/helpdata/EN/46/7256ce7fde01dde10000000a1553f7/frameset.htm
I hope this will help you.

How web services support SAP transactions

Hi ,
How does webservices technology support SAP t-codes?
Regards
Raju

Yes and no. <a href="http://www.w3.org/Protocols/rfc2109/rfc2109.txt">rfc2109</a> . This means that cookies provide a kind of session and therefore state, which can be hold on server side.
SAP ABAP ERP holds session:
<a href="http://help.sap.com/saphelp_erp2005/helpdata/en/b7/d7baaf1481a349ab723e3acd7334b3/frameset.htm">Providing and Consuming Web Services</a>
"WSDLs - There are two kinds of WSDLs Standard and SAP WSDL. The standard WSDL is provided for those users who will use tools from other vendors to create clients. For SAP users, there is an extended SAP WSDL. This is an extended version of WSDL and can be parsed using SAP tools (SAP Proxy Generator), thus providing information about additional Web service requirements such as authentication, session, and so on."
for me is also the technical implementation - how is the webservice session managed on server and on client - not totally clear. If someone can help me to find exaxct technical details. Unfortenately I also always used it (esp. with Web Dynpro) without thinking about details.

How Web Services support transactions ?

Hello,
I have this questions:
- Web services support statefull?
- There is some specification about 2PhaseCommit for Web Services?
- How Web services handle transactions (commit, rollback)?
- How can I handle commit across multiple systems (using web services)?
There are standards that support this topics?
Best regards,
Luis Carlos

Yes and no. <a href="http://www.w3.org/Protocols/rfc2109/rfc2109.txt">rfc2109</a> . This means that cookies provide a kind of session and therefore state, which can be hold on server side.
SAP ABAP ERP holds session:
<a href="http://help.sap.com/saphelp_erp2005/helpdata/en/b7/d7baaf1481a349ab723e3acd7334b3/frameset.htm">Providing and Consuming Web Services</a>
"WSDLs - There are two kinds of WSDLs Standard and SAP WSDL. The standard WSDL is provided for those users who will use tools from other vendors to create clients. For SAP users, there is an extended SAP WSDL. This is an extended version of WSDL and can be parsed using SAP tools (SAP Proxy Generator), thus providing information about additional Web service requirements such as authentication, session, and so on."
for me is also the technical implementation - how is the webservice session managed on server and on client - not totally clear. If someone can help me to find exaxct technical details. Unfortenately I also always used it (esp. with Web Dynpro) without thinking about details.

Does Web Dynpro support adding Enhancement Points/Sections

Hi,
Can someone answer whether the ABAP Web Dynpro framework is supposed to support add enhancement points/sections to code within a component method?
Cheers
Michael Arter

hi,
check out this link :
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/47/c21ba177be3376e10000000a421937/frameset.htm
also check out the foll post:
Pre-Exits and Post-Exits for WDA
hope this will surely help you!!!
Thanks & regards,
Punit Raval.
Edited by: punit raval on Jul 9, 2009 10:53 AM

Web Dynpro access Application Services directly?

We're looking at implementing some processes using Guide Procedures, and I have a question about design 'style'.
I'm creating a data layer using Entity Services. The entity services will be utilized by the Application Services to create a business layer. How to do this is clear, and straightforward.
However, where I have a question is how the automatically generated Web Dynpro application (or any other Web Dynpro application, for that matter) can interact with Application Services. I've seen sample applications where the Web Dynpro application interacts with application services via mapping from the Web Dynpro interface layer through the GP Runtime - from my perspective, this looks like a good way to deal with a small amount of data being passed between the steps in the GP.
The primary Web Dynpro application will let the user interact with the data, massaging it until it's in a form where the next person needs to deal with it. I was thinking of having the Web Dynpro application interact with the Application Services layer directly to move data from the database to the web dynpro application, and back again. The only thing that would be passed between the steps in the GP would be the guid of the primary data structure. I would also expose a method of the Application Service as a CO which would take the guid and return the entire business object, so viewing screens could be constructed - as well, PDF's could be generated, and so on.
Is this considered bad form in a GP, specifically accessing Application Services directly, instead of through a step in the GP? I understand that what I want to do ties the Web Dynpro application directly to the Application Services layer, but my thinking is that the CO that encompasses the Web Dynpro should be 'atomic', in that all operations related to that specific step should be contained in a single CO. In other words, the action of creating the business object, fiddling with it, an then submitting it upstream should be contained in one CO.
Comments, suggestions?

Hi,
      In the Composite Application Framework scenario, you first create the Business Entities. These act as data holder. To fill the data within these entities the Application services are created. These application services are later exposed as a webservice and deployed.
               These webservices can contain different methods along with the CRUD operations depending on the Process Flow and Design implemented. We can import the webservices as a model in the WebDynPro Component. The UI elements of the Views can be binded to the Model. So when we execute the model methods the data gets entered into the Business objects.
               This WebDynPro component should be a callable object ( It requires some Dependencies to be added to the WebDynPro Component ). So that you can have Input/Output parameters and ResultStates. These parameters are useful if you have to pass some parameters from one view to other within the same component. So this WebDynPro Callable object includes the Application service calls and also the passing of data through the GP Input/Output Structures.
               These callable objects are then included within the Process.
This is how I think a Composite Application must be designed.

Help in Web dynpro research

Hello everyone, i m doing my masters research on Web Dynpro and i need some opinions of Web dynpro users..
Is it possible for u guys to answer some really simple questions and help me..
following are the questions.
1.Do you think Web Dynpro facilitates only in GUI development or it comprises other benefits as well?
2. How does Web dynpro helps a programmer?
3. To what extent does it help the programmer?? are there any possible alternatives??does a programmer requre anything more from web dynpro??
4. How the Web Dynpro is beneficial over traditional technology?
5. What shorcomings in encomapasses?
6.What are the other comparable technologies?
7. Are any improvemnts required in web dynpro in future???
Lot of questions here..answer them for me if you can..it will be a great help..
Cheers,
Dakshata Gulkhobare

Web Dynpro is the SAP programming model used to develop professional Web UIs for business applications. It consists of a runtime environment and a graphical development environment with special Web-Dynpro tools that are integrated in the SAP NetWeaver Developer Studio.
The Web Dynpro tools support application development during the implementation and design phases. When a Web Dynpro application is developed, a platform-independent metamodel is created from which Java classed are generated.
Since Web Dynpro features a clear separation between layout data and business data, you can develop Web Dynpro applications with the same programming model both for mobile devices and conventional PCs.
WebDynpro Provides Application Developers the following advantages:
1.Web Dynpro supports a structured design process
2. Strict separation of layout data and business data through use of the Model View Controller concept
3. Different implementation languages are supported
4.The use of declarative and graphical tools significantly reduces the implementation effort
5.Reuse and better maintainability by using components
6.Syntax check at design time
7. Automatic data transport using data binding is also possible.
8.Automatic input check.
9.Flicker-free screen construction.
10. Ensuring platform-independence with the meta model approach
11. Minimizing the implementation effort through declarative programming
12. Supporting a structured design process by applying the model view controller paradigm
13. Providing reuse and better maintainability by using components
14. Providing graphical support with tools in the Web Dynpro perspective
15. 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.
Please check these threads
Why Webdynpro
Why WebDynpro ?
Why webdynpro and not BSP or JSP?
Webdynpro vs. Struts
Web Dynpro vs. Struts - a few questions
Kind of applications smade thru Webdynpro
What kind of applications are being developed with Web Dynpro?
Advantages of webdynpro
Re: Why WebDynpro ?
Hope it helps.
Regards.
Rajat

508 / Accessibility for Web Dynpro

Hi,
Does web dynpro support accessibility / 508 ?
As I have read and heard on teh techEd the web dynpro stack9 will support this, so I can set the property sap-accessibility=x resp. accessibilityDescription="testtext".
Also in the thread "Keyboard access to UI Element"
Posted on: Jul 29, 2004 10:27 PM, by user: Armin Reichert
Accessibility has been addressed and will be supported in the production release.
So I have download the WAS 6.40 as a 90 days test licence. But in the NW Dev. Studio there is no such a attribute for the GUI elements. Do I have to upgrade? But how?
Regards Ralph

Hi Armin,
thanks for the quick reply.
What I mean is, that in the presentation PRTL205 of the TechEd2004, on page 30 there is a screenshot from the NW Dev. Studio where you can see a property 'accessibilityDescription' for a GUI Element. Is property is not in the current NW Dev.Studio which you can download from SDN.
You know, if there is a 'newer' IDE than the one you can download?
Regards
Ralph

Web Dynpro version

Hi All,
OSS Note 991449 talks about Web Dynpro support packages. How can I see the version of our Web Dynpro?
thanks,
kbas.

Hi,
Go to http://<serverName>:<Port>/sap/monitoring/SystemInfo and log in as an administrator. Click on the link All Components under Software Components to view version information for all deployed components.
Bye,
Sameer

Creating mobile web dynpro application which customized theme

Hi guys,
I have created a mobile web dynpro application and a theme with Theme Editor. Then I have appended this theme with the sap-cssurl parameter to my application.
my_application? sap-cssurl=http://host:port/webdynpro/resources/sap.com/tcwddispwda/global/SSR/themes/MyTheme
It works well in my first testing on my laptop.
In order to test it on my mobile device I have also appended sap-wd-client parameter to my application. Now my URL looks like
my_application? sap-cssurl=http://host:port/webdynpro/resources/sap.com/tcwddispwda/global/SSR/themes/MyTheme&sap-wd-client=PieClient
It doesnt work. My application layout looks as if I dont use the theme. Did somebody have the same problem and can help me by finding a solution.
Thanks for your answers.
Marita

Hi Marita,
Mobile Web Dynpro supports several handheld mobile devices. I guess yours is a Pocket PC. Except the newest Pocket PC 2003, all the other versions don't have CSS support. Therefore the current Pocket PC client "PieClient" of Web Dynpro lacks the ability for customized themes. On the other hand, themes are supported for more advanced devices, such as Nokia Communicator 9500/9300.
Regards,
Wei

HTML Template for Web Dynpro (ABAP)

Hi Guys,
I am developing a webpage in webdynpro abap.
my requirement is to use a existing HTML(same as existing applications) template for this.
how do i do that ?
regards
Siddharth

You don't. That isn't how Web Dynpro works. The architecture is such that it abstracts the HTML/JavaScript rendering of the output. You place a UI element on the screen and only a metadata reprsentation of the screen is created at design time. At runtime different rendering engines can be applied to produce the final output. This allows SAP to add new rendering engines and to improve the rendering engines over time without having to adjust the applicaitons itself. This makes Web Dynpro sutiable for producing Business Transactions, but not general web pages. It also gives us the flexibility to render Web Dynpro in HTML/JavaScript, a desktop client (.Net 3.0 and WPF), and a RIA client (Adobe Flex).
You can alter the theme of the WDA application when running in HTML rendering. The theme gets automatically inherited from the NetWeaver Portal - or you can apply a stanalone theme when running without the portal. Theming allows for some basic changes of color scheme and branding elements - but is not the same as applying a complete HTML template.

Web Dynpro JAVA VS. Web Dynpro ABAP

Hi,
I'm interested in advantages and disadvantages of WD JAVA & WD ABAP. Could anybody give me some "detailed" information about it?
We need any information you can give us.
regards,
Sharam

Hi,
Web Dynpro for ABAP:
Web Dynpro for ABAP or 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).
The use of declarative and graphical tools significantly reduces the implementation effort
1) Web Dynpro supports a structured design process
2) Strict separation between layout and business data
3) Reuse and better maintainability by using components
4) Automatic operation of the Web Dynpro application using the keyboard
5) User interface accessibility is supported
6) Full integration in the reliable ABAP development environment
for more see:
http://help.sap.com/saphelp_nw2004s/helpdata/en/77/3545415ea6f523e10000000a155106/frameset.htm
Web Dynpro for 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:
1) Ensuring platform-independence with the meta model approach
2) Minimizing the implementation effort through declarative programming
3) Supporting a structured design process by applying the model view controller paradigm
4) Providing reuse and better maintainability by using components
5) Providing graphical support with tools in the Web Dynpro perspective
6) 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.
for more see:
http://help.sap.com/saphelp_nw2004s/helpdata/en/15/0d4f21c17c8044af4868130e9fea07/content.htm
The concept of Web Dynpro ABAP is identical with Web Dynpro Java and offers more or less the same functions
hope it helps
regards

BSP vs Web Dynpro ABAP

Hello,
we are looking for a listing that states the functional and technical differences between Web Dynpro ABAP an BSP.
Is there anybody who has come along such a list ?
Tx a lot in advance!
Best regards,
Ana

Annette,
check this
The SAP Web Application Server (WAS) provides a page-based programming model with server-side scripting as well as server page technology for developing, designing and implementing Web applications:
Business Server Pages (BSP). Server-side scripting enables direct access to all elements in the application server (such as function modules, database tables, ABAP Objects, and so on.).
We can create HTML pages or Business Server Pages (BSPs) with server-side scripting in ABAP or JavaScript.
The HTMLB and XHTMLB HTML Business libraries are available as BSP Extensions for a uniform layout and its associated usability advantages.
And In the Web Application Server, the presentation layer is separate from the business logic. This makes it possible to implement front-end technology.
Why BSP NOT WebDynpro
                          BSP
              ABAP WEBDYNPRO
Currently PMUSA/JMC customers are using Fire fox (Mozilla), Internet Explorer and Netscape navigator web browsers to access WEBUYPM application.
BSP supports these web browsers.
Restricted (Some of the features will not be supported by WebDynpro)
Existing WEBUYPM application is written in HTML, Business HTML and JavaScript language.
BSP supports these languages. And it allows even to mix ABAP, HTML and JavaScript thus has more flexibility to convert WEBUYPM application into BSP.
Web Dynpro does not support HTML/JavaScript.
Existing WEBUYPM displays the trade communications (Information tab) based on JavaScript and custom configuration file
BSP supports JavaScript, we can display the trade communications in BSP too.
Web Dynpro does not support Java Script.
Existing WEBUYPM application has different colors schemes, Logos and graphical elements for PMUSA/JMC companies.
BSP support s multiple color schemes/logo. These color schemes can be set dynamically based on company code selection at runtime.
Separate Themes has to be developed for each User Interface elements.
Development effort needs to be involved to even display a logo.
BSP supports client side (user) validations. As most of these validations can be done at client side, the no. of hits on the server can be reduced and thus giving better response for the user inputs.
In this way, performance can be increased.
Web dynpro does not support any client side validations, every time the request must be sent to server to validate the useru2019s input. This increases the traffic and reduces the performance
WEBUYPM application has logos, images.
BSP supports Client side caching, and thus loads these element from client side very quickly.
Web dynpro supports very little use of caching on the client side, and hence quite a significant delay in starting on some customeru2019s browsers.
BSP has no restriction on user interface possibilities, Ex. Grid, drop down boxes, Font colors, size etc.
Significantly more restrictive in user interface possibilities.
Ex. Only those fonts, which are provided by SAP, can be used.
Appearance can be changed dynamically using same web pages, to support different colors for different companies.
We can have same (or better) look and feel if we convert the application into BSP.
As there is no HTML coding involved in web dynpro the same look and feel as we have it today can't be achieved by using web dynpro.
BSP is built for developing any type of web application (including mobile applications. It can be accessed from desktop, laptop, and any kind of smart devices like PDA.
Web dynpro applications can not be accessed from PDA s (Not possible)
Why WebDynpro NOT BSP
             ABAP WEBDYNPRO
                           BSP
Personalization can be given to the end user if they do not want see any of the user-interface elements.
We can not hide any of the user-interface elements (Ex buttons ex) during the runtime.
Note - Current WEBUYPM application does not support any of these options.
Currently we are setting/retrieving the runtime context values in a session.
Web dynpro supports State full applications.
No additional development would be required.
BSP also supports to set runtime values and to retrieve the runtime context values, but minor development would be required to achieve this functionality.
Currently users can see view source for WEBUYPM HTML pages.
Using Web dynpro this can be restricted thus providing more security to the application.
HTML view source can be available to the users, Users can see the HTML client side code (not server side coding) as it does today.
By using Adobe Flash Island, powerful web pages (RIA) can be created.
But, Flash Island comes with Net weaver.
BSP does not support Flash Island. But, BSP supports Java Script.
JavaScript is essential for the new trend of rich internet applications (RIA), it is used by all the new applications, Ajax, Widgets, Flash, and even Microsoft is supporting JavaScript for the new generation of RIA
Web dynpro has wizard tools to generate the code to create/configure the User Interface elements.
Development effort would be required to create UI elements.
We dynpro has uniformity as we use standard colors provided by SAP
Uniformity can be achieved by using style sheets (minor development would be required).
Thanks
Bala Duvvuri

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

ABAP Web Dynpro v/s BSP

Hi All
Can you pls tell the difference between ABAP Web Dynpro v/s BSP.
Regards
DM

Hi madan....
Web Dynpro for ABAP
Features
Web Dynpro ABAP 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, the data that is required remains intact so that you can re-access the data in 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
BSP
BSP applications are standalone Web applications with presentation, workflow and application logics that are self-contained in terms of function.
In many ways, BSPs are similar to the server page technologies (xSP)from other software manufacturers, such as Active Server Pages (ASP)from Microsoft and Java Server Pages (JSP) from Sun Microsystems.
This technology has become relatively widespread in the field of Web development thanks to its various advantages.
regards,
get back for more help
vijay
Message was edited by: Vijayasarathy Raghunathan

How Web Dynpro supports RSS (ATOM)?

Similar Messages

Maybe you are looking for