Using css with web dynpro

Hi
I have an application, where i have to use my own css files. regarding this i found one post (with the same heading as this post) in the forum where the method was specified and also it was mentioned that in the visual admin, in the property sheet of the application, the property for this has to be set true.
When we checked here, we are able to find the path and corresponding property sheet in SP9. But we are using SP14. In this version the specified path for the application and property sheet of that application couldn't be traced.
Is it possible that in SP14 version, the path might be somewhere else? If so,can anybody please provide with the updated path.
Thanks & regards,
Puneet

The source of Web Dynpro generated files aren't *.java files, but *.wdcontroller files
I'm not familiar with PMD, but you might need to add the extra file extension
(Being it Java source encapsulated in XML, you may run into a plethora of other issues, but you could give it a try)

Similar Messages

Using CSS for Web dynpro application in EP

Hi,
I have some CSS (Style sheets) which I need to apply to the portal, so that all the web dynpro applications can have the same look and feel.
I read something about Theme Editor in EP. Can I somehow use that to import the CSS contents into the EP theme?
Any pointer to using CSS for Web Dynpro applications will be appreciated.
Thanks.
Puneet

Hi,
Go thorugh the follwing Web Dynpro Java
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/business_packages/a1-8-4/nw04stack09themes.zip
To know how to use it and for the steps to be followed please follow the tutorial here
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/how to edit web dynpro themes.pdf
the last url gives you a step by step procedure with wizards..
Regards,
RK

How to use JDI with Web Dynpro

Can any one help me with detailed steps on how to put my Webdynpro development components into JDI?
We are already done with the development work. Now we have JDI installed and want to source safe the project in JDI.
So, my requirement is only to put them in JDI, to be able to check-in and check-out any future changes and use the JDI to deploy the applications into QA and production systems . No team development or anything.
For this case, which of the 3 tutorials ( Team oriented development, Development with track, Development with layers) given in help.sap.com will be ideal?
Please help.

Hi Aditya,
Step for creating Webdynpro:
1. Open Development Configuration Perspective in NWDS. In the Local DCs view, right-click on Local Development and choose Import
Configuration
2. Login remote with your username and password. It will create development infrastructure in Inactive DCs. There you can create the component like webdynpro, Java, J2EE, Enterprise Portal, etc.
3. Creating Webdynpro in the DTR perspective.
Step 1: Right click on Inactive DCs -> Create new DC.
1. By default vendor name is SAP. You can change vendor name according to your requirements.
2. create a new Web Dynpro DC with desired name.
Name should not exceed eight characters (Recommended)
create a new Web Dynpro DC with desired name.
3. Select the language
4. Select the domain
5. Select the component type
3. Copy the file structure from your existing local project to DC.. These will be under an activity..
Step 2:
1. Build and Deploy and test your new DC.If it works fine then in DC perspective..Right click on src folder->add subtree ->create activity.
See this thread discussing about how to migrate local project to JDI..
How to migrate local Web DynPro projects into the DTR?
Regards
Suresh KB

Using PMD with Web Dynpro

Hello,
We've been trying to integrate PMD (http://pmd.sourceforge.net/) with NetWeaver Developer Studio, but all we've been able to accomplish is it checking our own java classes. PMD completely ignores java classes generated by Web Dynpro. Is there a way to make it see those classes as well?

The source of Web Dynpro generated files aren't *.java files, but *.wdcontroller files
I'm not familiar with PMD, but you might need to add the extra file extension
(Being it Java source encapsulated in XML, you may run into a plethora of other issues, but you could give it a try)

Problems using Visual Composer with Web Dynpro runtime

I am currently trying to build a Visual Composer iView and we need to use the Web Dynpro runtime rather than Flash because it needs to work with a screen reader for users with sight problems. Which is a pity because Flash works fine. But when I use Web Dynpro runtime I'm getting the following problems:
a) When I define fields and pushbuttons in forms where Align Contents is set to Absolute, they do not appear at runtime in the positions in which I've placed them - all form elements are aligned vertically. The only other options are to align all fields vertically or align all fields horizontally. This lack of flexibility makes it rather difficult to create a good screen design; the only option seems to be to create a separate form for each set of differently aligned fields, which leads on to the next problem. .
b) When I define more than one form on a page, again at runtime the forms do not always appear in the positions in which I've placed them; the compiler seems to calculate how much space it needs to display the screen elements and then re-sizes and re-positions the forms accordingly, ignoring what I've told it to do.
c) Toolbar pushbuttons do not appear on forms (they do appear on tables). Irritating, but at least I can still create pushbuttons on the form itself.
There are other issues, but the main problems is that it appears that when I use VC with Web Dynpro I cannot trust the editor layout at all and the only way I can build something that looks decent is to fiddle about with field / form sizes and positions, checking every change on the output, until hopefully I get it looking ok. Having to do this will dramatically increase the time taken to develop VC applications. Has anyone else experienced these problems with VC and Web Dynpro? Has anyone managed to overcome them?

Thanks, but neither of these describes the problems I've been having. And they are misleading since they say that you can use VC with Web Dynpro only with Web Services ie not directly with BAPIs / RFCs, but using it with BAPIs / RFCs is one of the few things that works well in our system.
The most recent problem I've found is that if you make a form or table read-only it will stay read-only in Flash but the fields are editable in Web Dynpro. The individual field disable option does work for Web Dynpro, but it turns the fields from black to a vey pale and almost invisible grey (this doesn't happen in Flash). And you can't seem to change this.
It does seem to be a bit pathetic that input fields can't be made read only. I've tried expression boxes, which are read-only anyway, but they appear in as pale a grey as the disabled input fields. And although plain text fields can be added to tables, they are pretty useless since they can only hold a single value and so all the lines will contain the same value.
I guess I should resign myself to the fact that I am never going to be able to produce a decent screen using VC and Web Dynprp.

MDM with Web Dynpros

Hello,
I am new to MDM, Can anybody please let me know how could I use MDM with Web Dynpro's? I have read the article "MDM connectivity to java application" that could be the way to use if the sda are available!
Regards,
Dharmi

Dharmi,
This is excellent, in fact we are also working on a similar scenario. We already have developed some web dynpros which call the API's exposed by MDM and display the data. (Very soon we will write a blog on the same). However the problem is these web dynpro's become very specific with the respository you are dealing with. If that is all you want they that should be fine.
However, if you want to come iViews just like SAP then we mihgt have to think out of the box.
Have you seen the example of Applied.com? the back for these sites is SAP MDM. However these are the J2EE applications which are accessing the API's of MDM and also with other applications for placing the order.
The ideal solution that I can think of is to publish a catalog using MDM API's, give additional functionality of shooping cart, once everything is done, place the order which will create a sales order (SAP R/3 or any other ERP) via SAP XI (SAP EP communicating with SAP R/3 via XI.
Regards,
Ravi

Oracle as Back-end with Web Dynpro

hello
i wish to know how to use oracle with web dynpro as database store
initially we have been using R/3 system as our store with
backend of r/3 as oracle
but now we directly want to communicate with oracle

Hi Mitesh,
Initially I had tried few ways to connect directly from WD to Oracle, but nothing worked for me. Finally I could achieve it only through ejbs & even today I stick to that. I tried out many things for connecting directly including accessing the JDBC connector service of the server, but don't know why nothing worked for me.
Anyway, I'll send you the step by step process to create the ejb & use it in your WebDynpro application to connect to the database (you might find it a bit long, but I believe I have included every step). If someone knows a better way to connect pls let us know, cos it is tiresome to write ejbs each time we need to connect.
1) Open the J2EE perspective
2) Create an EJB Module project
3) Right click on ejbModule, create a new EJB (select your EJB type)
4) While creating the ejb itself, you can add business methods by clicking Next in the UI. Another option is after creating the ejb, write the method in the bean, then select the method from ejb-jar.xml -> <bean name> ->method. Right click and select propogate to local & remote.
5) Double click on ejb-j2ee-engine.xml. select your bean and specify a Jndi name for eg: MyJndi.
6) Right click on the EJB project and add classes12.zip file (provided by Oracle) to its build path. (under libraries tab). Also check the same file under Order & Export.
7) Create an Enterprise Application project.
8) Right click on the EJB module project and select add to EAR project, then select the created EAR project.
9) Right click on the EJB project, select Build EJB Archive
10) Right click on the EAR project, select Build Application Archive
11) Open the WebDynpro perspective, open a new project, right click on the project ->properties. Do the following configurations :-
 Java Build path - select the EJB project from projects , check the selected project under Order & Export
 Project references select the EAR project
 WebDynpro references select sharing references tab, click add & make an entry as : <vendor>/<EAR project name without .ear extension>
You can find the vendor name under application-j2ee-engine.xml file of the EAR project. By default it is sap.com. So if my EAR projects name is ABC, my entry would look like sap.com/ABC
12) Now the configurations are over and the EJB can be invoked by writing the client code inside the webdynpro component. Like:
InitialContext context = new InitialContext();
 Object obj = context.lookup("MyJndi");
MyEJBHome home = MyEJBHome)PortableRemoteObject.narrow(obj,MyEJBHome.class);
 MyEJB mybean = home.create();
 int a = 0;
 a= mybean.add(10,15);
 wdContext.currentContextElement().setSum(a);
where MyEJB is my EJB name and MyJndi is my JNDI name
To connect to Oracle , you can write the usual Java code (given below) as a business methos of the ejb (similar to add() method in the example). And access it like mybean.<businessMethodName>().
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
Connection conn = DriverManager.getConnection("jdbc:oracle:thin:@Oracle_server_ip:Oracle port:SID of the Database","user_name","password");
Statement stmt = conn.createStatement();
ResultSet rs = stmt.executeQuery("your query");
Hope this helps & pls do let us know if you have any further queries,
Best Regards,
Nibu.

Problem in submit button on adobe form integrated with web dynpro

Hello,
I'm facing prob in triggering web dynpro event onSubmit for Interactive form.
I've created a submit button from web dynpro activex pallete on adobe form (integrated with web dynpro) to send the form as email.
Then in the web dynpro view where this form is embedded i have created an action against onSubmit event and called a method within this.
However, on clicking Submit button this event is not getting triggered.
Please let me know what is lacking in this process?
Thanks.

Hi,
I am also facing the same problem. i have developed a simple scenario under which user have to input his/her details and on submit button it will be updated to database.
I have tried the above solution but after adopting this solution all the editable fields become non-editable.
so the above solution is not working for me could you help me out.
I think ... try this....
When you create the Adobe Form from WebDynpro, you need to follow one step in SFP Transaction or inSE80 transaction. Open the Adobe Form in any one the transaction and now in SAP menu bar "Utilities" in that you will find the "INSERT THE WEBDYNPRO SCRIPT" just click on that one. Then you will see a new Script Object is being created with the name "ContainerFoundation_JS" under the "Variables" in the Heirarchy of the Object Pallete of the Adobe Form.
This step is mandatory to use the SUBMIT Button of the "WebDynpro Native", to trigger the OnSubmit event of the WebDynpro.
Thanks
Edited by: shailendra2sap on Mar 6, 2009 12:24 PM

Using EJBs in Web Dynpro

I have recently started to develop Web applications using the Web Dynpro framework. Coming from a pure J2EE world, I must admit that Web Dynpro has a few innovative features that I find interesting for user interface development. The use of component & view contexts, for example, is not unlike the ActionForms that one may find in a Struts application, but pushed a bit further. No complaints here.
What I do have some problems with is the whole CommandBean paradigm that is put forth by SAP (refer to the document <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webdynpro/using%20ejbs%20in%20web%20dynpro%20applications.pdf">Using EJBs in Web Dynpro</a>).
I do understand the usefulness of defining a model that will be used to generate and eventually bind to Context data structures. That's fine. What I do object to is the use of a so-called CommandBean to play that role. Again, coming from a J2EE world, I am familiar with the BusinessDelegate pattern - which would typically be used by a client application to invoke business logic on the server side. I would propose that a better, cleaner way of integrating EJBs with the Web Dynpro framework would be to use a BusinessDelegate for invoking business logic, and importing a separate and distinct ModelBean (instead of a CommandBean) to be used for defining and binding to Context data.
I have built one Web Dynpro application thus far. Instead of using a CommandBean, I created a ModelBean that extends my business object DTO (Data Transfer Object) (which is quite appropriate for that role, given that it implements all the get & set methods that are required for the business data that I need to model). My Web Dynpro application also makes use of an independant BusinessDelegate that is packaged with my EJB DC - this is a standard best practice on J2EE projects. I have been asked by the people working with me to modify this architecture to bring it more in line with the SAP way of doing things. I am open-minded and willing to learn and accept new ways of thinking and doing things. However, I fail to understand the usefulness of merging structure and behaviour by resorting to CommandBeans:
- It violates the MVC paradigm by having one object (the CommandBean) serve as both model AND controller as far as the Web Dynpro application is concerned. The CommandBean is obviously a model - since it is literally imported as such into the Web Dynpro application. It is ALSO a controller from the Web Dynpro's application perspective, since all calls to the back-end go thru the CommandBean via one or more of its execute_xxx methods. In contrast, the use of a business delegate by the Web Dynpro application clearly separates the model (the CommandBean... or rather, a more suitably named ModelBean) from the controller (BusinessDelegate).
- Doesn't carry its own weight. In other words, I haven't yet been provided with any valid justification for going thru the extra effort of coding the CommandBean's execute methods. It's been proposed to me that it somehow serves as an abstraction layer between the Web Dynpro application and the business logic. I would argue that it is the BusinessDelegate's role to abstract away the back-end logic from clients. If one does have a BusinessDelegate available, I would argue there's no need to code execute methods in a separate CommandBean. To prove my point, I would simply point out that all of the CommandBean examples that I have seen so far, either in How-To documents, or in production code, all follow the same pattern....
CommandBean.execute_doSomething() calls BusinessDelegate.doSomething()
Not a heck of an "abstraction" layer... I would in fact argue that it is worse than useless. If some major change occurs in the business logic that requires changing the doSomething() operation, we expect of course to modify the BusinessDelegate. The Web Dynpro client will also presumably need to be modified - that's to be expected, and unavoidable. But then, we'll also need to go about and change the CommandBean's execute_doSomething() method - again, extra work for no apparent benefit. Adding and removing business methods has the same implication. All this for an layer that simply adds the prefix execute_ in front of all business method calls... Is this "abstraction layer" worth the cost of creating and maintaining it ??
- Unnecessarily complicates error handling. I have been told that for technical reasons, it is recommended that all exceptions thrown by the CommandBean be of type WDException or WDRuntimException. But what if the client application needs to react differently to different failure scenarios ? When I create a business object, I might wish to provide the user with an error messages if connection is lost to the backend, and with a different error message if an object already exists in the database with the same attributes. In order to do that, I will have to catch the WDException, extract the cause, and continue processing from there... possible, yes, but clearly less standard and more labor intensive than the classical try/catch mechanism.
To say nothing about the fact that SAP's own API documentation clearly states that applications using Web Dynpro can reference and catch WDExceptions, but THEY MUST NOT THROW OR EXTEND IT !
- Produces unnecessary DCs. Page 6 of the aforementioned document presents an architectural view of a Web Dynpro project that uses a CommandBean. Why an extra DC for the CommandBean ?? I created my ModelBean class right inside the Web Dynpro project (in the Package view). That, to me, is where this class should reside, because it is created for no other reason that to be used by this particular Web Dynpro application. What is the benefit of placing it in its own independant DC ?
- Not a typical application of the Command pattern. The well-documented command pattern (Design Patterns - Gang of Four) has been devised mainly to enable encapsulation of request as objects, thereby making it possible to:
- specify, queue and execute requests at different times
- decouple execution of a command from its invoker
- support undo operations
- support logging changes so that they can be reapplied in case of system crash making it possible to assemble commands into composite commands (macros), thereby structuring a system around high-level operations built on primitive operations.
None of this applies to the way the SAP CommandBeans are being used. Not that much of an issue to people new to J2EE and/or OO development... but quite confusing for those already familiar with the classic Command pattern.
At this point, I fail to understand the advantage of merging structure (model) and behaviour (execute methods) through the use of a unique CommandBean object. Am I missing something ?

Thanks for your reply and your suggestion. I have posted in the Web Dynpro Java forum... and suggest those wishing to participate in this thread to refer to the Web Dynpro Java forum.
As for your answer, I'm afraid it doesn't satisfy me.
Reuse is hardly an issue, since the CommandBean is specifically tailor-made for the Web Dynpro application that needs to use it. I could hardly imagine building another application that would just happen to have the exact same needs as far as data structure and processing is concerned...
As for the right Eclipse environment... the CommandBean is not an EJB artifact - it is an EJB client. The aforementioned tutorial in fact suggests creating it in the Java perspective.
But thanks anyway for your time and suggestion

Using EJBs in Web Dynpro Applications

I have recently started to develop Web applications using the Web Dynpro framework. Coming from a pure J2EE world, I must admit that Web Dynpro has a few innovative features that I find interesting for user interface development. The use of component & view contexts, for example, is not unlike the ActionForms that one may find in a Struts application, but pushed a bit further. No complaints here.
What I do have some problems with is the whole CommandBean paradigm that is put forth by SAP (refer to the document <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webdynpro/using%20ejbs%20in%20web%20dynpro%20applications.pdf">Using EJBs in Web Dynpro Applications</a>).
I do understand the usefulness of defining a model that will be used to generate and eventually bind to Context data structures. That's fine. What I do object to is the use of a so-called CommandBean to play that role. Again, coming from a J2EE world, I am familiar with the BusinessDelegate pattern - which would typically be used by a client application to invoke business logic on the server side. I would propose that a better, cleaner way of integrating EJBs with the Web Dynpro framework would be to use a BusinessDelegate for invoking business logic, and importing a separate and distinct ModelBean (instead of a CommandBean) to be used for defining and binding to Context data.
I have built one Web Dynpro application thus far. Instead of using a CommandBean, I created a ModelBean that extends my business object DTO (Data Transfer Object) (which is quite appropriate for that role, given that it implements all the get & set methods that are required for the business data that I need to model). My Web Dynpro application also makes use of an independant BusinessDelegate that is packaged with my EJB DC - this is a standard best practice on J2EE projects. I have been asked by the people working with me to modify this architecture to bring it more in line with the SAP way of doing things. I am open-minded and willing to learn and accept new ways of thinking and doing things. However, I fail to understand the usefulness of merging structure and behaviour by resorting to CommandBeans:
- It violates the MVC paradigm by having one object (the CommandBean) serve as both model AND controller as far as the Web Dynpro application is concerned. The CommandBean is obviously a model - since it is literally imported as such into the Web Dynpro application. It is ALSO a controller from the Web Dynpro's application perspective, since all calls to the back-end go thru the CommandBean via one or more of its execute_xxx methods. In contrast, the use of a business delegate by the Web Dynpro application clearly separates the model (the CommandBean... or rather, a more suitably named ModelBean) from the controller (BusinessDelegate).
- Doesn't carry its own weight. In other words, I haven't yet been provided with any valid justification for going thru the extra effort of coding the CommandBean's execute methods. It's been proposed to me that it somehow serves as an abstraction layer between the Web Dynpro application and the business logic. I would argue that it is the BusinessDelegate's role to abstract away the back-end logic from clients. If one does have a BusinessDelegate available, I would argue there's no need to code execute methods in a separate CommandBean. To prove my point, I would simply point out that all of the CommandBean examples that I have seen so far, either in How-To documents, or in production code, all follow the same pattern....
CommandBean.execute_doSomething() calls BusinessDelegate.doSomething()
Not a heck of an "abstraction" layer... I would in fact argue that it is worse than useless. If some major change occurs in the business logic that requires changing the doSomething() operation, we expect of course to modify the BusinessDelegate. The Web Dynpro client will also presumably need to be modified - that's to be expected, and unavoidable. But then, we'll also need to go about and change the CommandBean's execute_doSomething() method - again, extra work for no apparent benefit. Adding and removing business methods has the same implication. All this for an layer that simply adds the prefix execute_ in front of all business method calls... Is this "abstraction layer" worth the cost of creating and maintaining it ??
- Unnecessarily complicates error handling. I have been told that for technical reasons, it is recommended that all exceptions thrown by the CommandBean be of type WDException or WDRuntimException. But what if the client application needs to react differently to different failure scenarios ? When I create a business object, I might wish to provide the user with an error messages if connection is lost to the backend, and with a different error message if an object already exists in the database with the same attributes. In order to do that, I will have to catch the WDException, extract the cause, and continue processing from there... possible, yes, but clearly less standard and more labor intensive than the classical try/catch mechanism.
To say nothing about the fact that SAP's own API documentation clearly states that applications using Web Dynpro can reference and catch WDExceptions, but THEY MUST NOT THROW OR EXTEND IT !
- Produces unnecessary DCs. Page 6 of the aforementioned document presents an architectural view of a Web Dynpro project that uses a CommandBean. Why an extra DC for the CommandBean ?? I created my ModelBean class right inside the Web Dynpro project (in the Package view). That, to me, is where this class should reside, because it is created for no other reason that to be used by this particular Web Dynpro application. What is the benefit of placing it in its own independant DC ?
- Not a typical application of the Command pattern. The well-documented command pattern (Design Patterns - Gang of Four) has been devised mainly to enable encapsulation of request as objects, thereby making it possible to:
- specify, queue and execute requests at different times
- decouple execution of a command from its invoker
- support undo operations
- support logging changes so that they can be reapplied in case of system crash making it possible to assemble commands into composite commands (macros), thereby structuring a system around high-level operations built on primitive operations.
None of this applies to the way the SAP CommandBeans are being used. Not that much of an issue to people new to J2EE and/or OO development... but quite confusing for those already familiar with the classic Command pattern.
At this point, I fail to understand the advantage of merging structure (model) and behaviour (execute methods) through the use of a unique CommandBean object. Am I missing something ?

Hi Romeo,
You would be disappointed, this reply ain't anywhere nearby to what you are talking about...
I wanted to mail you, but you have not mentioned your email in your profile.
I am really impressed by your flair for writing. It would be far better had you written a blog on this topic. Believe me, it would really be better. There is a much wider audience waiting out there to read your views rather than on the forums. This is what I believe. To top it, you would be rewarded for writing something like this from SDN. On the blogs too, people can comment and all, difference being there you would be rewarded by SDN, here people who reply to you would be rewarded by you. Doesn't make much a difference.
Anyways the ball is still in your court
As far as I am concerned, it has still not been much time since I have started working on Web Dynpro. So can't really comment on the issue...
Bye
Ankur

Search Help on Adobe Interactive Form with Web Dynpro ABAP

Hi All,
I have created Adobe Interactive Form with ZCI type and XML based interface type using Webdynpro ABAP.
I placed a text field USER_NAME on the form ( data element is linked to search help USER_COMP ).
Added Native WD UI element 'Value Help' to form to search for users and changed script
*var fieldName = "INSERT_NAME_HERE*"; to var fieldName = "USER_NAME";
The problem is that when I click on the value help button, nothing happens.
Is any more additional steps required ?
Thanks
Karu

Hello
Check this
F4 Value Help on Adobe Interactive Form with Web Dynpro ABAP
Thanks
Anirudh

Business Graphics with Web Dynpro?

Hello @ all,
I have got a question about displaying dashboards and other charts on mobile devices using SAP Technology.
1) Does someone know, when it will become possible to display BusinessGraphics in Mobile Devices like BlackBerry, Pocket PC a.s.o buildt with Web Dynpro?
2) Which Technology can I use instead of Web Dynpro? Does it make sense to use HTMLB or should we use non SAP Products like "JFree Chart" for J2EE applications specially buildt for Mobile Devices?
Thank you for any hints!
Mehmet

Hi Memhet!
You can use Business Graphics with Web Dynpro with version NWDS 2.0(we are in was 6.40)and could be displayed on mobile devices.We use Symbol devices.I am not sure abt Blackberry.Is that your question? OR Are you looking for some alternate solution to WebDynpro.Is that because you have some limitations in running your WD applications in mobile devices?Just trying to understand......
Thx
Gisk
Message was edited by: Sivakumar Ganesan(Gisk)
Message was edited by: Sivakumar Ganesan(Gisk)
Message was edited by: Sivakumar Ganesan(Gisk)

Search Help with Web Dynpro call on another system

Hi all,
I have to create a search help with web dynpro on a field but the database is on another system... How can I do?
Many Thanks in advance...

I would use a search help exit. Nothing WDA specific here, as this has been possible long before WDA came around. With a search help exit you define the search help like normal, but instead of database table or view being the source of selection, you have a function module. Within the coding of this function module you can call an RFC to read data from another system or call a web service if you need to bridge over to something that isn't ABAP based.
You can read more about Search Help Exits here:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/cf/21ee52446011d189700000e8322d00/frameset.htm

Search Help with Web Dynpro

Hi all,
I have to create a search help with web dynpro on a field but the database is on another system... How can I do?
Many Thanks in advance...

I would use a search help exit. Nothing WDA specific here, as this has been possible long before WDA came around. With a search help exit you define the search help like normal, but instead of database table or view being the source of selection, you have a function module. Within the coding of this function module you can call an RFC to read data from another system or call a web service if you need to bridge over to something that isn't ABAP based.
You can read more about Search Help Exits here:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/cf/21ee52446011d189700000e8322d00/frameset.htm

Tutorials to implement Flash Islands with Web Dynpro Java

Hi,
We have downloaded the CE 7.1 EhP1 trial version.
Any pointers to tutorials to implement Flash Islands with Web Dynpro Java would be helpful.
Thanks,
Chitrali

Hi,
I read a document which says Adobe Flex Builder is not been included part of shipment of NW. So not lots of documents available. Yet with WDA, some tutorials and blogs are available. Similar application can be developed using WDJ. Please check these.
WDJ:
The specified item was not found.
WDA:
http://www.adobe.com/devnet/sap/
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10989ef6-968c-2b10-50a9-eb34a5267163
https://www.sdn.sap.com/irj/scn/wiki?path=/display/emtech/sapRichIslandsforAdobe+Flash
Regards,
Harini S

Using css with web dynpro

Similar Messages

Maybe you are looking for