Integrating Web Dynpro and Portal

Hi people!
I'm starting the development of a simple web site in SAP Enterprise Portal. I created a simple web dynpro application to test the integration between web dynpro and SAP EP. I created a new folder and a new system in portal content. After I add a new page and a new iView (this iView open my webdynpro iview).
My Page open normally in SAP Portal Page Admin, now i would like to know how do for include the Portal Theme, Menu, Status Bar into to my page.
I investigated about wdPortalNavigation and wdPortalNavigationMode, but i don't understand very well how insert the Portal Navigation properties into my Page.
How do I insert this properties in my iView Code? or I should set this properties in Portal Admin?
Somebody have some e-books or tutorials to indicated?
Thanks in advance!!
Marcelo

Hi Marcelo,
First of all welcome to SDN....
For you Webdynpro pages to open with new THEME but not with default theme of portal you have to design new theme in portal and assign that theme to WebDynpro Components
for creation of THEMS please refer these Documents
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ccb6bcf4-0401-0010-e3bc-ec0ef03e13d1
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3ea0d790-0201-0010-80b8-b680496a3838
Please Reward Points if Helpfull...
Regards.
Vinit

Similar Messages

Abap web dynpro and portal events

First off, a little introduction: My name is Martin Kroppen, I am an Abap developer for SAP Netherlands, and I am currently involved in a project for hospitals to built a portal. For this, I have created 2 Abap web-dynpros, and then impemented the views as iviews in an EP. What I want to achieve is that the input view triggers the display view on a second page, and the data is shown for the values in the input view (all in the same browser window).
I am using the portal integration manager for this, with the method for relative navigation.
The navigation is working fine, only problem is that I don't know how to handle the business parameters that I send over.
My questions are:
1. is this the correct way for navigating between abap webdynpro iviews in the portal?
2. what is the correct way to read the business parameters into my context of the second Abap WD application?
I tried the solution that is described below, I could not get it to work correctly.
If you define BUSINESS_PARAMETERS as application parameters in your Web
Dynpro application and the parameter names start with ″APP″, they will
automatically be forwarded to the startup plugs of the Web Dynpro application
provided they are marked as startup parameters. In this case, keep in mind that
the iView/page used as the navigation target must be assigned to the user role.
If it is not, navigation cannot be triggered.
Hope someone can help me
Regards
Martin Kroppen

Hi,
please refer to this link for portal integration
Web Dynpro for ABAP Portal Integration [original link is broken]

How to integrate a Smart Form in Web Dynpro and how to view it on portal?

Hi,
I have created a Smart Form in ABAP. I need to use it in Web Dynpro. How can this be done?
I want to integrate this Smart Form in a Web Dynpro Application and then display this Smart Form on the Portal (when I deploy the Web Dynpro application).
Is it compulsory to first convert the Smart Form into PDF Format? Is there some other way ??
Thanks in Advance.
Regards,
Harshada

Hi,
Go through Re: Web Dynpro and Smart Forms.
Regards,
Satyajit.

Web dynpro documents regarding dynpro and Portal

Hi,
I am new in web dynpro so i need some documents regarding dynpro and portal. So please provide it and if possible send it my personal mail [email protected]
I am also looking for some examples applications .If any budy have links of it provide it.
Regards,
gurprit

Hi Gurprit,
I have sent Complete Webdynpro Examples to your mail.
And also please check the following links for more clear understanding
Programming UI and Navigation
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9214b1e5-0601-0010-fdb0-ec32d43b06e0
Webdynpro for Java
http://help.sap.com/saphelp_nw2004s/helpdata/en/15/0d4f21c17c8044af4868130e9fea07/frameset.htm
Webdynpro Samples
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webdynpro/web%20dynpro%20sample%20applications%20and%20tutorials.htm
Web Dynpro User Interface
https://www.sdn.sap.com/irj/sdn/developerareas/webdynpro?rid=/webcontent/uuid/ce44a14c-0a01-0010-af89-d7dbd944f176 [original link is broken]
PDf
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/com.sap.km.cm.docs/library/nw/netweaverdevelopersguide2004s/sap%20netweaver%20developer's%20Guide%202004s/UsingJava_00_PDFsList.ca
SAP Netweaver Application Server eLearning Catalog
https://www.sdn.sap.com/irj/sdn/elearn?rid=/webcontent/uuid/b1203f5e-0501-0010-bb88-915402c954f2 [original link is broken]
give rewards if useful.
regards
Anil

Web Dynpro and Abobe Flex

Hi Folks,
I've seen a couple of responses to questions about the mixing of Web Dynpro and Adobe Flex technologies...
This thread mentions a "Flex Client" which is reportedly able to render existing Web Dynpro apps in Flex: WebDynPro ABAP in adobe flex client
This thread mentions a technology called "Web Dynpro Islands" which is apparently Flex components within Web Dynpro apps: Flex with WebDynPro
These concepts seem very different to me - the first being a run-time solution to Flex rendering and the second, design-time. In my opinion, the Flex Client sounds like a more flexible (excuse the pun) solution as it allows the designer to concentrate on application functionality and leaves the visual styling to the GUI. Following on from this thought, the Flex Client gives an added benefit in that, if the person executing the app wants to view it in the current WD style as opposed to Flex, they have this option by choosing a different rendering tool/user interface... and the underlying WD app remains untouched!
Does anyone have any thoughts on this?
On a potentially negative side of the Flex Client technology, is the this client yet another GUI tool that needs to be rolled-out and maintained on users' PCs or will it simply be a plugin that can be downloaded on-the-fly and used in a web browser (in a similar way to an ActiveX control)?
I hope this stimulates some interesting discussions...
Cheers
Glen

Thanks Thomas! I was hoping you'd be around to shed some light on this...
You're explanation of the use of Web Dynpro Islands was very useful - I was assuming that any UI elements created for Flex designer could also be created as a Web Dynpro component for the Web Dynpro designer (ABAP or Java) but you make a good point that they have different capabilities.
I think, my biggest concern was that the visual style of the WD Island/Flex component would be so different to the the rest of the WD app that it would stick out like a sore thumb but if you use the Flex Client to render it, as you suggested, then every UI element in the app should look and behave consistently... another assumption...
This makes me wonder whether we'll need to use the Flex Client for all our portal apps to keep the look-and-feel consistent throughout the portal. There's nothing worse to a user than having one UI element behave a certain way in one app and a totally different way in another - eg. compare the scrolling functionality of the WD table element to the Flex table element.
I'll look forward to hearing more about the Flex Client in the near future.
Cheer
Glen

JAVA, JAVA WEB dynpro and possibility of JAVA workflow

Hi all
Just a take here -- I'm just getting some feelers on the way WF SHOULD be going in future.
Since starting to use the JAVA WD system and netweaver developer studio it seems that having to encapsulate a lot of NEW Workflows as ABAP objects is going "Backwards". (Note I said NEW not EXISTING applications)
I understand that some compatability with existing systems needs to be maintained but if your user is doing all his applications from a Portal you really need the WF's to be triggered from the portal via say WEB SERVICES.
I find I'm actually using the older ERP / ECC 6.0 R/3 systems these days purely as DATA repositories and from a JAVA program can often retrieve the data via standard BAPI's and RFC calls in a JAVA or Portal application.
Isn't it about time that the workflow system as a whole was made much more JAVA and PORTAL friendly --since this is where more and more people are doing their developments from.
Since switching more or less full time over to JAVA WEB DYNPRO developments the whole development time is completed MUCH QUICKER and with many many less mistakes.
ABAP Web dynpro is also OK but it's still a little bit of a nightmare compared with JAVA when you need a lot of WEB SERVICES.
Some WF's obviously will need to remain ABAP based but newer custom WF's IMO should be WEB DYNPRO and WEB SERVICE based.
I can't think of too many large organisations who aren't making more and more use of Portals these days -- so C'mon SAP -- provide some proper Web hooks into WF's instead of us having to go through hoops and rings of writing LAST CENTURY's code to get stuff to work through a Portal.
Cheers
jimbo

Hi,
Have you checked the new BPM tool that SAP is offering? I think that it is definately a big step into to the drection that you are describing. I haven't really checked all its features and the technology that is is based on, so I am not the biggest expert of this matter.
Check for example this article to get an overview: http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b06c49b2-ac63-2c10-3d8d-d17b817ba4ca?quicklink=nw-bpm&overridelayout=true
Of course it will be a long road before this new tool will (if it will ever) replace the old ABAP based workflow engine.
I wouldn't totally agree with all the points that you presented (ABAP WD being a nighmare, etc.). Actually I think that the direction (at least in some parts) is the opposite. For example SAP seem to have replaced their "old" travel management applications (Java WD) with new ABAP WD applications, so I see that they believe more in ABAP than Java (of course there might be some financial & other reasons behind this also.). In my opinion WDA has so many advantages compared to WDJ, that I would consider carefully the options when choosing the technology (the possible better(?) compatibilitly with web services might be one of the reasons).
Regards,
Karri

Web dynpro and database

I need to get to the sap db from my web dynpro, and I need to be able to save/retrieve/modify data.
Any idea how to approach it??
I've looked into creating ejbs but have been unsuccessful at finding an ejb document on how to create them and then use them in web dynpro.
If not, what other ways are to go about saving/retrieving data??
Thanks

Hey!
Try this out, it should work.. I would sugest that you use this code snipet on DAO's and put them in a java library project, and make reference to it from the web dynpro project properties so you don't have business logic on your WD Application, although it will also work in the WebDynpro if you copy/paste and customize this code
import java.sql.Connection;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;
import java.util.Properties;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.sql.DataSource;
     Connection conn = null;
     try {
          InitialContext dbInitContext = new InitialContext();
          Properties sysProperties = System.getProperties();
          String sysname = sysProperties.getProperty("SAPSYSTEMNAME");
          String dbName = "jdbc/" + "SAP" + sysname + "DB";
          DataSource dataSource = (DataSource) dbInitContext.lookup(dbName);
          conn = dataSource.getConnection();
          Statement stmtQ = conn.createStatement();
          ResultSet rs = stmtQ.executeQuery( "SELECT... ");
          while (rs.next()) {
               //iterate query
     } catch (NamingException e) {
          //handle exception
     } finally {
          try {
               conn.close();
          } catch (SQLException e) {
//handle exception
Cheers,
JV
Edited by: Jesus Valencia on Aug 6, 2009 11:00 AM

Web Dynpro and CAF (BOs, Application Services, returning Complex Types)

Hi All,
I am trying to develop an application using Web Dynpro and CAF for days now and did not get it running.. I need some help here.
What I am trying to do / have done is the following:
- Design a Business Object (BO) in CAF
- Implement an Application Service that has a method called getAllBOs that calls the findAll method of the BO
- call this method using AWS model or EJB model in Web Dnypro, show the result in a table.
My getAllBOs returns a set of BOs (Data Type is the Complex Type of my BO in CAF). I was able to design the Application Service so that it returns a collection of BOs (using a Wrapper Comple Type), but I was never able to call the generated Web Service successfully in Web Dynpro. The WebService worked fine when testing it in wsnavigator...
However, i never got it running.. is there anybody out there who is able to explain what to do to import a AWS model or an EJB model in Werb Dynpro and particularily how to implement the stuff so that it returns a set of BOs successfully...
Thanks in advance.. Useful help is highly appreciated
Please note: THIS IS ABOUT Netweaver CE 7.1 - do not post stuff about 7.0!

Hi,
You have to return a single object from caf layer to webdynpro layer.
Since you are returning a list of BOs, create a wrapper in caf which contains the list of your BOs.
Your application service should return this wrapper.
Creating Wrapper:
1. Create a complex data type.
2. Include your BO as one of the properties in it. and set the cardinality to 0..n.
In Application service invoke your findAll() of BO and use the returned list to populate the wrapper's BO list.
Return this wrapper.
Hope it helps.
Regards,
Fazal

Problem with integrating Web Dynpro into anonymous Portal

The problem is that we can't run the Web Dynpro application in combination with an anonymous portal.
We get the following error:
Runtime error portaal
Fout opgetreden bij verwerking opdracht voor :
iView : pcd:portal_content/com.spe.spe_intranet/content/sites/nullAtSPE2/Connecting/nullAtSPE/AtSPE/Random4
Naam component : com.sap.portal.appintegrator.sap.WebDynpro
Exception in SAP Application Integrator occured: ApplicationIntegratorException.
Exception id: 02:31_29/10/07_0168_426375450
See the details for the exception ID in the log file
Detail description of the situation:
At one of our companies we are using a Portal in combination with a Web Dynpro application. The portal is for internal use only so therefore we are using a language specific anonymous user (/irj/portal/anonymous?guest_user=Guest_intra_NL). The Web Dynpro application needs no authentication either. The Web Dynpro applications runs inside an appintegrator iView somewhere on the frontpage. If we set the authentication schema on 'default' instead of 'anonymous' we have to authenticate (inside the iView only). If we authenticate then the Web Dynpro application works fine. So only in combination with a anonymous user the application is not working.
We performed all these settings:
Anonymous user access to Web Dynpro
This is a small part of the trace file:
Component : pcd:portal_content/com.spe.spe_intranet/content/sites/nullAtSPE2/Connecting/nullAtSPE/AtSPE/Random4
Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
User : Guest_intra_NL
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: ApplicationIntegratorException
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:123)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
... 29 more
#1.5 #00144F790FF0005D00000D8500000D5500043D60120F2656#1193382735975#com.sap.portal.sapapplication#sap.com/irj#com.sap.portal.sapapplication#Guest#0####c817f770839211dc850f00144f790ff0#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/System/Server#Java###Content pass of Application Integrator failed.
Component Name: 'com.sap.portal.appintegrator.sap.WebDynpro',
Context Name (iView): 'pcd:portal_content/com.spe.spe_intranet/content/sites/nullAtSPE2/Connecting/nullAtSPE/AtSPE/Random4',
Top Layer: 'WebDynpro/TopLayer',
Producer ID (FPN): 'null',
System Alias: 'SAP_LocalSystem',
[EXCEPTION]
#1#com.sapportals.portal.appintegrator.ApplicationIntegratorException: ApplicationIntegratorException
 at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:96)
 at com.sapportals.portal.appintegrator.accessor.system.SAP_LocalSystemAccessor.getAuthenticationData(SAP_LocalSystemAccessor.java:83)
 at com.sapportals.portal.appintegrator.layer.authenticationmethod.AbstractAuthenticationMethod.getUserCredentials(AbstractAuthenticationMethod.java:54)
 at com.sapportals.portal.appintegrator.layer.authenticationmethod.SAPLogonTicket.computeAuthentication(SAPLogonTicket.java:31)
 at com.sapportals.portal.appintegrator.layer.SingleSignOnLayer.processLayer(SingleSignOnLayer.java:45)
 at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:159)
 at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:68)
 at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:54)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:396)
 at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
 at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)
 at com.sapportals.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:799)
 at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:652)
 at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.security.api.umap.NoLogonDataAvailableException: No logon ticket available.
 at com.sap.security.core.umap.imp.UserMappingDataImp.getAuthenticationTicket(UserMappingDataImp.java:1772)
 at com.sap.security.core.umap.imp.UserMappingDataImp.enrich(UserMappingDataImp.java:351)
 at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:91)
 ... 33 more
#1.5 #00144F790FF0005D00000D8700000D5500043D60120F3B56#1193382735981#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Guest#0####c817f770839211dc850f00144f790ff0#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/System/Server#Java###Exception ID:09:12_26/10/07_0701_426375450
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/com.spe.spe_intranet/content/sites/nullAtSPE2/Connecting/nullAtSPE/AtSPE/Random4
Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
User : Guest_intra_NL
 at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
 at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
 at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
 at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
 at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: ApplicationIntegratorException
 at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:123)
 at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
 ... 29 more
Hopefully someone has any clues. Thanks in advance. Of course will I reward points for the solution.
Grtz, JM

Hi Kelly,
the point here is native SharePoint integration. If your company does not have a SharePoint strategy then I absolutely agree with you. There are plenty of ways on how you can integrate WebDynpros, iViews, and other "SAP views" in SharePoint.
The "problem" with these integrations is always that it is not a native / low-level integration. It is just an iFrame within SharePoint that contains data coming from another system. This means that this data is isolated from any other functionality that is available in SharePoint.
Of course this can be enough for some usecases (maybe for all of yours ), but there are lots of companies who do want to leverage all of SharePoints (collaborative) functionalities. In this case Duet Enterprise does offer a way to integrate SAP objects into SharePoint on a "low-level". All objects that are integrated into SharePoint are then available as "real" SharePoint objects. You can work with them like with any other SharePoint object. You can even offline them using standard SharePoint functionalities. You can bring them to Outlook without any major development, ...
All this because we not only include an isolated iFrame in SharePoint, but really integrate the data.
Like I said: there are certainly usecases where this is not required and a simple iFrame is all that you need. However, we have seen in several projects now that there is also a requirement / need for a "deeper" integration.
Regards,
Holger.

Integrating Web Dynpro ABAP application in portal

Dear experts,
I created a Web Dynpro ABAP application. I need to Integrate it in portal and have to capture portal login id to my application.
Kindly guide me how to integrate WDA in portal and how to capture Portal Logon id in my application.
Thanks,
Kind Regards,
Ram

Hello ,
It is asking for SAP system user id and password becasue there is no SSO established between portal and the web dynpro system.
Now, either you can establish SSO between portal and the backend system by SAP Logon TIcket or user mapping.
SSO stands for single sign on.
SSO using SAP Logon Tickets :-
by using this technique you will be able to login into the backend by using SAP logon ticket
issued by the portal system. For this you need to import the .der certificate form the system administration ->system config -->
key ticket store. there download verify.der and upload it in the trusted system list in the backend in the trasaction strust_import.
here is link for this method.
http://wiki.sdn.sap.com/wiki/display/EP/LogonTickets,CertificatesandBackend+Certificates.
SSO using user mapping. :-
For this method you need to map the user in the portal to one user in the backend system.
You can do so by going to user administration in the portal there find the user id with which the user will login.
then go to the user mapping for system access tab there select the system from the dropdown and give user id and password
for the same system save it.
Now when you will login it wont ask for the user id and password.
And after this you can get the portal user id also in your web dynpro application.
Thanks
Sarbjeet Singh

Integrating Web Dynpro to ep6 sp12

I have created the simple Web Dynpro example program from the How to Guide -- Use Portal Eventing. However, I am having trouble integrating the Web Dynpro Application with the portal. I am using the How to guide -- Integrate a Web Dynpro Application into SAP Enterprise Portal 6.0 SP2 as a reference. Since the document refers to SP2 some of the screenshots does not match. Is there a more current documentation out there?
Thanks,
Jin Bae

Hi Jin
I am not sure about the latest document on integration with portal, But the procedure is same for integrating webdynpro components into portals.
For Integrating webdynpro components into portal
1. Click on Content Management/Portal content.
2. Right click on the required folder and choose iview
3. Select SAP webdynpro iview
4. choose iview name
5. Choose the system name
6. Give the namespace(if this is a DC then vendor name\project name, if it is a local webdynpro component then it is local\applcaiton name) and the application name
7. Preview the component
Let me know if you require furthur clarifications on this
Kishore
7.

Adobe Interactive Forms without Web Dynpro and ACF???

Hi All, we would like to build an interactive forms solution based on the Adobe software integrated into WAS. However, the customer requires a true thin client application with no additional installation on the client. Integrating Adobe Interactive Forms into Web DynPro however requires the Active Component Framework (ACF) to be installed since these forms are integrated into the page within an ActiveX container.
So the question is whether there is a way to use Adobe Interactive forms including the Adobe Documents Service within WAS but without(!) using Web Dynpro?(the full blown Adobe LifCycle Forms solution is not an option). Any suggestions on this are highly appreciated!
Tanks!
Frodo

Hello everyone,
I would like to add a couple of points from the SAP Product Management perspective.
Adobe has a number of stand-alone products that are the foundation for what SAP can now offer thanks to our partnership. This is exactly why we decided on a partnership that provides us with established technology, which is now integrated.
It is true that Web Dynpro is the main SAP way of integrating the interactive functions of the solution. We made this decision consciously, because the development and run-time environments provide very useful features that reduce the need for manual coding, such as the possibility of passing the data back to the backend using the Web Dynpro context. The automatism we offer here needs to be implemented from scratch with any other solution, including the Adobe stand-alone one.
While it is true that the ACF constitutes a certain limitation for the reasons you mention, Adobe will remedy this in 2005. The Reader/Web Dynpro integration will be available later this year for multiple platforms (OS, browsers) and will not require ACF anymore.
If you do not want to use a full-blown Web Dynpro application for your concrete scenario, consider developing an application that provides nothing but the interactive PDF form to the end user, to be filled in using the stand-alone Reader. The submit of the form data (with or without the PDF itself) could then happen via HTTP or e-mail.
Kind regards,
Markus Meisl
SAP NetWeaver Product Management

Using EJBs in Web Dynpro and others model tecnology patterns

I'm having difficults in order to implement the business logic in Java.
I did a simple application and I put all business rules inside de controller in the web dynpro. Everything is ok to users, but I know that this isn't indicate.
I tried to encapsulate de business rules and dao in a session bea, but I'm not sucessfull. I'd like to receive advices/tutorial about model, I found some treads in the forum, but almost all links in the sdn are browke. I was thinking in using hibernate and spring, but I don't know with it's a good choive to sap world.

Hi,
try these tutorials:
(ejb) https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/1f5f3366-0401-0010-d6b0-e85a49e93a5c
(hibernate) https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/14f55178-0801-0010-0bac-974ed17e51d3
Regards
Ladislav
PS. Consider rewarding helpful answers

WEB DYNPRO AND WEB SERVICE MODEL: ejb remove doesn't work

Hi guru,
this is my scenario:
J2EE-7.00 SP14-> PORTAL ->7 sp14 ->WEB DYNPRO FOR JAVA ->Web Service Model -> WS Custom with MDM API JAVA
The my WS is a Stateless Session Bean and i have this code:
     public void ejbCreate() throws CreateException {
          loc.setMinimumSeverity(Severity.INFO);
          loc.addLog(new ConsoleLog());
          this.plug = (MdmPlug) new MdmPlug(true);
          try {
               this.loadProperties();
               this.plug.connect(
                    hostname,
                    repository,
                    language,
                    username,
                    password);
               loc.fatalT(msgLog+"[ ejbCreate ] START....");
          } catch (Exception e) {
               if (e.getMessage()!=null)this.error=e.getMessage();
               loc.fatalT(msgLog, this.error);
public void ejbRemove() {
          try {
               loc.fatalT(msgLog+"[ ejbRemove ] STOP....");
               this.plug.close();
               loc.fatalT(msgLog+"[ ejbRemove ] ...OK");
          } catch (ControlException e) {
               loc.fatalT(msgLog+"[ ejbRemove ] ...K O !!!!");
The my problem is:
When open the IE and open my WD the new EJB's instance is created (I see my log +"[ ejbCreate ] START....in LOG VIEWER).
But, when I do log-off or I close IE, I don't see "[ ejbRemove ] STOP...." in LOG.
Result:
I open the MDM connection but not close it.
Where is the problem?
In Web Dynpro?
In Web services?
I have to create another WS's type?

Hi Max,
You can't run an EJBControl from a simple java class using either @Control or programmatic instantiation.
The EJBControl implementation relies on Resource Context events so it "needs" a container context to run.
You can use the ControlTestCase to unit test an EJB via EJB Control. You will need to configure the JNDIContextEnv annotation to bind to the server where the EJB is deployed. Note that this only works with EJBs that have a remote interface and a global JNDI name.
The test case would look something like this (I've seen this example run as long as the JUnit classpath includes weblogic.jar)
public class SimpleClient extends ControlTestCase {
public void setUp() throws Exception { super.setUp(); }
public void tearDown() throws Exception { super.tearDown(); }
@Control
@EchoEjbControl.JNDIContextEnv(
contextFactory="weblogic.jndi.WLInitialContextFactory",
providerURL="t3://localhost:7001",
principal="weblogic",
credentials="weblogic"
public EchoEjbControl echoEjb;
public void testXXX() {} // ... test methods that reference echoEjb
Thanks
Vimala

Web Dynpro And JDO JavaBean Model

Hello all,
I have read so many threads about the use of a JDO model within Web Dynpro components, but non of them gave me a real idea of which is the best practice to follow when communicating the business layer which is part of my JDO project with the component controller and view controllers...
There are other threads about communicating a model based on EJBs with WD components based on the command pattern, i see this cases are very likely but im not sure this is the best way to reach my goal...
Please, any help or comments would be just great...
Regards.

Hallo Jonathan,
please have a look at our Web Dynpro tutorial on how to apply the Java Bean Model Importer. It also contains some information on the intermediate command bean layer. We actually work on an extended version of this tutorial comprising a more complex business object model (with model class relations).
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/webdynpro/tutorial on using ejbs in web dynpro - 20.html
Regards, Bertram

Integrating Web Dynpro and Portal

Similar Messages

Maybe you are looking for