What is required to use OVS in Web Dynpro?

OVS in Webdynpro

Hi,
OVS is used to give an advanced value help, whereby you can give filter criteria before the values are displayed. You have to implement a custom controller for it to work. More details are available here, have a look at the pdf document,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webdynpro/tutorial%20on%20advanced%20value%20help%20and%20object%20value%20selector%20-%209.htm
cheers,
LM

Similar Messages

Requirements for using pdf in web dynpro

Hi,all
What are the basic system requirements to be able
to use PDF forms in Web Dynproapplications?
Regards
Michael

Hi Michael,
1. Adobe document services should be configured on your J2EE Engine.
2. Adobe Reader 7.0.1 should be installed on your m/c.
3. SAP NetWeaver Developer Studio (Support Package Stack 11) including Adobe LiveCycle Designer (forms design tool) should be installed on your m/c.
4. Active Component Framework (ACF) of the Interactive Forms integration should be installed on your m/c.
Hope this helps.
Plz reward points.
Regards
Nikhil

HT4108 What is required to use the video composite out on the iPhone 4. Left and right audio works ok

What is required to use the video composite out on the iPhone 4 The left and right audio works ok

Please not that the iPhone uses mono channel for internal speakers, the other path that you see is not the speaker per say. It is the phone microphone. Try using headphones, you will hear both channels. If the problem still persists when using headphones, check your sound balancing in the settings. Go to setting-general-accessibility scroll down and check the slide under mono audio. It should be put at the centre for you to hear both channels ON YOUR HEADPHONES

What tool do we use for BW web report ?

Hi all:
What tool do we use for BW web report ? Could you please give some development steps
for an example ?
Thank you very much!!

Hi,
You can use the Report Designer for creating reports and displaying them on the web.
You can refer to the below links for more information -
http://help.sap.com/saphelp_nw70/helpdata/EN/c8/2d1442505d5033e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/EN/43/8a95791b1f22a8e10000000a1553f6/frameset.htm
Hope this helps!
Regards,
Saurabh

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

How to use Cookies in Web DynPro?

Hello,
Is there a way to use Cookies in Web DynPro like a regular Servlet uses in it's response Object?
If yes, I could use a code example...
Roy

Hi Roy,
1. This will create a Request Objec containing all the client's request just like in a regular Servlet or does it have special considerations I should worry about?
A: If you have portal and webdynpro components, both have to use the same runtime. If you are using only webdynpro components then you can use the "Task" class. But it is a non-standard API.
Task.getCurrentTask().getWebContextAdapter().getHttpServletRequest()
2. Where do you recommend putting this statement? I assume at the wdDoInit() method right?
A: Don't put this statement in the doInit(), if you are handling some event within the component and refreshes the view, your doInit() will not get executed.
3. Is there a Response object I can create as well?
A:
HttpServletResponse response =((com.sap.tc.webdynpro.services.sal.adapter.core.IWebContextAdapter) WDWebContextAdapter.getWebContextAdapter()).getHttpServletResponse()
Regards,
Santhosh.C

What SAP component support Flash Island in Web Dynpro for ABAP?

Hi Experts,
What SAP component support Flash Island in Web Dynpro for ABAP? I don't find flash island control to place it in the view.
Thanks,
Duy

FlashIsland is a native UI element like table or image - not a reusable component like ALV. What release level is your system? FlashIsland is only available on NetWeaver 7.0 Enhancement Package 1 and higher.
Also the FlashIsland UI element must be a root UI element. Therefore it has be created in its own view. Right mouse click on the ROOTUIELMENT in the UI element hierarchy and choose Swap UI Element Definition.
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/47/b907cd77eb2d66e10000000a42189c/frameset.htm

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

Error using tabs in Web Dynpro application

Hi all,
I am working on a web Dynpro application where I want to use "tabs" to display different vendor details, basically I need two tabs one for header data, one for address data. What I did is I created a group and there created the element for the user to enter the vendor number and also created a button and binded it with the BAPI, now I created a tab using tabstrip and then inserting the tab and adding the element to the tab (in my case i m using the table type), once I finish this and try to do the syntax chek i am getting this error: "ACC: Element "TAB" does not have a header"
Can you please help me with this?
Thanks,
Rajat

Looks like i was missing some step... I deleted everything and then re created and this time it works.

Using RepositoryFrameworkWS in web dynpro Java 7.1 CE

Hi All,
I am new to KM, and i have a requirement to create a document in KM of 7.0 from a web dynpro java application developed in NWDS 7.1 CE. I know i can use RepositoryFrameworkWS web service to achive this. But I need some help to start with it.
So it would be of great help, if i am provided with some Documents, Code snippets or links regarding this.
Thanks & Regards,
Vishweshwara P.K.M.

Hi Mukhuti,
I had tried setting ParentCollectionRid as "\documents" and when I execute the application i get the exception stating "Exception on execution of web service with WSDL URL 'http://<URL>' with operation 'createDocument' in interface 'RepositoryFrameworkWSVi_Document'".
Also is it mandatory to set UserId and password to create new document, if yes is it an admin Id.
Thanks & Regards,
Vishweshwara P.K.M.

Using ICacheService in Web Dynpro DC

Dear,
My Web Dynpro DC application allows users to upload several files. Since I don't want to keep all these files continuously in memory, during the complete user session, I want to temporarily save them to disk. Therefore I'm trying to use the ICacheService interface, <a href="https://media.sdn.sap.com/javadocs/NW04/SPS15/km/com/sapportals/wcm/service/cache/package-frame.html">com.sapportals.wcm.service.cache.ICacheService</a>, part of the Knowledge Management and Collaboration (KMC) API.
To be able to compile (the code below), I created a separate DC of type "External Library" that contains these 3 jar files: bc.sf.framework_api.jar, bc.sf.service.cache_api.jar and bc.util.public_api.jar. These 3 jar files where obtained from these 3 par files: com.sap.netweaver.bc.sf.par.bak, com.sap.netweaver.bc.sf.service.par.bak and com.sap.netweaver.bc.util.par.bak. It took a little bit of searching to find the required jar files, but anyway, everything compiles fine... The External Library only has a public part of type API.
As you may have guessed, my problem is to get this working at runtime... I can't deploy the External Library DC (using a public part of type assembly) together with my Web Dynpro, because that causes class loader issues. After all, these jar files are already deployed on the server. But if I don't define any runtime dependency or reference, I get a java.lang.ClassNotFoundException.
The question is: how to define the runtime reference(s)?
Should I define a Web Dynpro Sharing Reference like "PORTAL:sap.com/com.sap.km.bs.sf.service"? Then how can I obtain a reference to CacheServiceFactory?
FYI, we're using SAP NetWeaver 2004 SPS 15.
FYI, the relevant code I (think I) need looks like
ICache cache = CacheServiceFactory.getInstance().getCache("CACHE_ID");
Any help is greatly appreciated!
Kind regards,
/Sigiswald

Hi Sasi,
Thanks for your reply!
I don't think your suggestion of creating a public part of type assembly will work. Eventually, this will deploy the jar files on the server, which is not required since they're already deployed and it won't work either because of the same reason (class loader collissions).
But this is how I actually solved it, to my great surprise it's working perfect. All I had to do was create this sharing reference: "PORTAL:sap.com/com.sap.km.application".
Note that the referenced par file, com.sap.km.application.par.bak, does not include the CacheServiceFactory class. Neither was it necessary to obtain a reference via WDPortalUtils.getServiceReference.
Anyway, I'm glad it's working
Kind regards,
/Sigiswald

Using DTR in Web Dynpro

Hi All,
I'm interesting in using the DTR component of the JDI (without CBS & CMS) for version management.
scenario:
A number of developers are working on a WD project (the project is local and not DC).
I want the developers to checkin and checkout like in VSS.
I tried to use VSS: it works fine with "regular" java projects but not so good with WD projects.
I've setup the DTR server.
in NWDS I went to Web Dynpro prespective -> Navigator view -> context menu [DTR] -> Share Project
I went to the DTR prespective and saw that the project files are marked with a blue house icon (local files).
A few questions:
Checkin:
1) I've read some threads and I'm not sure which WD files I need to check
2) How do I checkin? I tried to open a new activity then right click it and choose 'Check In' but not all the files were checked in.
Checkout
1) How to create a new project in the client from DTR?
2) how to update a project in the client from DTR?
Thanks,
Omri

Hi Omri,
Step for creating Webdynpro in DTR:
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
Step 2. Now it will ask for create new activity name(give name relevant to project name so that you can identify afterwards easily).
Develop your components.
Step 3:
1. Build and Deploy and test your new DC.If it works fine then in DC perspective..right click on activity name ->checkin activity.
Mandatory:
In Webdynpro project src folder should be checked in.
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

Using Webservice in Web Dynpro

Hello,
I have a webservice which takes two parameter account number and pincode and returns true/false to indicate account exists or not. I have deployed the webservice and tested it using EP wsnavigator utility.
After that I created a web dynpro application, created an adaptive webservice model, its corresponding custom controller and views using apply template option. Also configure the webservice call in visual administrator.
But when I run the application all the fields displayed are disabled, I couldn't understand what I have done wrong?
I appreciate if someone can guide me to resolve this issue?
Regards,
Jawed Ali

I think I have done that see the code below:
[code]
public void wdDoInit()
 //@@begin wdDoInit()
 //$$begin Service Controller(1593472463)
 BankServiceModel2 model = new BankServiceModel2();
 wdContext.nodeRequest_CheckBankAccount().bind(new Request_CheckBankAccount(model));
 //$$end
 //@@end
//@@begin javadoc:executeRequest_CheckBankAccount()
/** Declared method. */
//@@end
public void executeRequest_CheckBankAccount( )
 //@@begin executeRequest_CheckBankAccount()
 //$$begin Service Controller(2056258565)
 IWDMessageManager manager = wdComponentAPI.getMessageManager();
 try
 wdContext.currentRequest_CheckBankAccountElement().modelObject().execute();
 wdContext.nodeResponse().invalidate();
 wdContext.nodeCheckBankAccountResponse().invalidate();
 catch(Exception e)
 manager.reportException(e.getMessage(), false);
 //$$end
 //@@end
[/code]
additionally when I clicked the button, I got following exception:
Exception on execution of web service with WSDL URL 'http://pep:50000/BankService/Config1?wsdl' with operation 'checkBankAccount' in interface 'BankServiceVI_Document'
Following is the xml file displayed on the browser when I browsed URL: http://pep:50000/BankService/Config1?wsdl
[code]

−
 <wsdl:definitions name="BankServiceWSD" targetNamespace="urn:BankServiceWSD">
<wsdl:import location="http://pep:50000/BankService/Config1/bindings?wsdl&style=document" namespace="urn:BankServiceWSD/Config1/document"/>
−
 <wsdl:service name="BankService">
−
 <wsdl:port name="Config1Port_Document" binding="bns0:Config1Binding">
<soap:address location="http://pep:50000/BankService/Config1?style=document"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
[/code]

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

What is required to use OVS in Web Dynpro?

Similar Messages

Maybe you are looking for