Using an other web dynpro application into an actual application

Hello,
I have a web dynpro application into a developer component previously developed. I want to import it an another web dynpro application.
The goal is to click a button, display the window of the other application and then once it is finished, go back to the first application (with some context parameters)
Is it possible ?
Thanks
Quentin

Hi,
Solved same issue in this thread Re: Data transfer between two different Web Dynpro components
PradeeP

Similar Messages

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

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

Using Web Dynpro WDUrlGenerator from within J2EE Application deployed on NW

I have two applications deployed on a NetWeaver Application Server 2004s.
1. A Web Dynpro application.
2. A J2EE Application
What I want to do is to be able to build a url to the Web Dynpro application from within the J2EE application. Obviously the problem is using Web Dynpro classes within the J2EE application.
So I edited the Java Build Path of the J2EE application to include the werbdynproservices.jar file and exception.jar files by extending ECLIPSE_HOME variable in the libraries section. I also checked them in Order and Export. I verified the built .war file and it does contain the two .jar files.
This was sufficient to get my project build and deployed, however the servlet in my J2EE application shows NoClassDefFoundException when I run it. My guess is there's more I need to do to get the WDUrlGenerator to run in my J2EE class.
Is this possible or is there a better way? I am trying to avoid the client having to modify a web.xml for each depployment.
Thanks in Advance.

This looks like what I want, but I am unable to test it.
I found the application-j2ee-engine.xml file under the <project-root>/gen_wdp folder. I then attempted to open it with the SAP EARDD editor. It opens with the Source tab selected. If I try to click the General tab I get an error saying:
"The source page has errors. Other pages cannot be used until these erros are corrected."
I see nothing wrong with the XML document. It's source is here:
<?xml version="1.0" encoding="UTF-8"?>
<application-j2ee-engine>
 <provider-name>local</provider-name>
 <modules-additional>
 <module>
 <entry-name>EVENTS_WorkflowNotification.wda</entry-name>
 <container-type>webdynpro</container-type>
 </module>
</modules-additional>
</application-j2ee-engine>
When I deploy the application, everything works fine. I was going to edit the XML document by hand, but of course there is no DTD listed so I don't know what's supposed to go in there without the Editor doing it for me.
Getting closer. Thanks so much.

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

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

Adding a field in Web dynpro java in Travel Request application

Hi All,
How to add a field in Web dynpro java in Travel Request application or can we copy the Web dynpro java application to Web dynpro ABAP and add a field. Experts, Can you please suggest me step by step in resolving the problem.
Thanks & Regards,
Kumar

Hi Kumar,
First, in order to customise the ESS webdynpro Java iViews you need to be aware that, you are about to change the SAP standard iviews. In order to avoid this you can make a copy of the SAP standard one's and then try to customise the copied one's.
Now, you should have NetWeaver Development Infrastructure(NWDI) installed. Once it is installed you should also install the Netweaver Developer Studio (NWDS) on your computer.
Once you have these two installed, you should deploy the ESS Business Package onto the NWDI by creating tracks. There is a cookbook available on SAP Service Marketplace for configuring NWDI for ESS.
Once you have all the above mentioned tools, have a look at the following blog which clearly explains about the procedure of customising ESS iviews.
/people/vinoth.murugaiyan/blog/2007/08/24/essmss-customization-150-make-it-simple
Also check the following Wiki, this might be useful!
https://www.sdn.sap.com/irj/scn/wiki?path=/display/erphcm/employee%252bself%252bservice
I hope this helps. Let me know if you have any issues.
Dont forgett to contribute points if this is useful! All the Best.
Regards,
PG

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

Converting Web Dynpro project into a Web Dynpro DC

Hi
I have a Web Dynpro project created.
Now I want to convert it into a Web Dynpro DC (Development Component).
Could anyone tell me if there is a standard procedure to do this?
Right now, I am following the below procedure:
Copy all the folders under root folder->src-> packages of Web Dynpro project into root folder->src-> packages of Web Dynpro DC.
Rebuild the DC.
But in this procedure I am getting errors (in view code) as the required interfaces (example, IPrivate<<component-name>>.java) are not getting generated when I re-build the DC.
Could anyone help me with this issue?

Hi Aditya,
I have used two way for this and both worked fine for me.
1. While creating DC project at the end there eill be a check box, which when you tick will show your local dynpro project and you can then import that.
2. Create DC project after that copy the component of your local dynpro project and paste it on the option where you can create the component of DC project.
After pasting click next - next so that everything remain in sync.
After that check if you have any compilation error, check them if they are because of some jar files.. you have to add the library files by using the option -> DC Metadata ->DC Definition ->Used DC.
If you got no compliation error, then just rename the component ( again click next) and then deploy.
otherwise you may get deployment error.
Hope this helps,
Thanks,
Namrta

Calling one Web-Dynpro program into Another

Hi All,
I'm currently working on a Web-Dynpro program in which I am display 3 tabs(Using TabStrip) and in each tab I have a ViewContainer.
I want to be able to execute other Web-Dynpro programs within the Viewcontainers of the Tabs.
If the End-User goes from tab to tab, I want to pass a select number of parameters between tabs.
Is this possible to do and if so, how can I set this up?
Thanking you in advance.

Hello Lisa,
I'm not sure what you really want...
If you want to share data between several views of one webdynpro component, you should use the [context|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/444941db42f423e10000000a155106/frameset.htm] of your [component controller|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/e2/434941db42f423e10000000a155106/frameset.htm].
If you mean by "execute other Web-Dynpro programs within the Viewcontainers" to embed another webdynpro component you should have a look at [Cross-Component Programming|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/a7/1d8b412bb5b35fe10000000a1550b0/frameset.htm].
Regards,
Alej

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

Embed a Flash Application into a Flex Application

Hello everybody,
I'd like to know if there is a way to embed a Flash
Application into a Flex Application. My goal is to wrap Flash apps
in Flex Modules, and I don't know how to do it.
I know it is possible to embed swf by using @Embed and an
mx:Image tag, or to use flash content by creating a flash swc
component. However these two solutions don't allow to call the
methods of the Flash app.
On the other hand, it is possible to load a swf file via the
Loader Class, and then call the methods via loader.content. But
with this solution I can't embed the swf in my flex application and
I have to load it at runtime.
Any ideas ?

Look into SWFLoader.
Be aware though, you can not directly access AS2/FP8/Flash8
swf's from within an AS2/FP9 app. Local connection is used in this
case.
There are dataType and timing issues with SWFLoader. Here is
a complete example:
http://www.cflex.net/showfiledetails.cfm?ChannelID=1&Object=File&objectID=690
Tracy

Can I convert a Lookout application into a labview application?

We here are seriously thinkig to migrate to Labview. There is a complex application done with Lookout 6.0 that we want to convert to a labview application. Having the proper Labview, is there a way of compiling it, open and save, or convert the Lookout application into a Laview application?
Excuse my ignorance in this matter.
Best regrads.
Rudy
Solved!
Go to Solution.

Rudy,
First of all I hope you first question regarding lookout is solved. If so then mark my answer as solution.
For the next time, if you have other questions, which are not related to the one you started the thread of, then open a new thread!
And no, National Instruments don't has drivers for Non-NI Products, so LabVIEW has no driver for your motion card. Anyhow National Instruments has it's own Motion Hardware and Software (ni.com/motion).
And for LabVIEW and Linux just go to ni.com/linux, and you will find supported hardware/software and the linux derivates it works on.
Christian
Message Edited by Christian_M on 11-20-2009 01:28 AM

How to convert an existing db application into a clustered application

Hi,
I want to know how can i convert my application into a clustered application.
my current application there are 5 modules and thses modules have 5-10 tables in common.Since these modules work simultaeously the processing time gets increased drastically.Is it possible that to have seperate instances of these tables and every module works independently and oracle take care of the consistency.
I want to know if RAC could be the solution?

user8731258 wrote:
Hi,
I want to know how can i convert my application into a clustered application.
my current application there are 5 modules and thses modules have 5-10 tables in common.Since these modules work simultaeously the processing time gets increased drastically.Is it possible that to have seperate instances of these tables and every module works independently and oracle take care of the consistency.
I want to know if RAC could be the solution?Sounds like an application design issue. I think you'd be best served tracing the applications and see where the overhead is being introduced when they do their process concurrently.
Throwing RAC at a poorly developed application would do nothing except amplify the poor design (it'll make things worse).
Cheers,

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 an other web dynpro application into an actual application

Similar Messages

Maybe you are looking for