Problem with iView Isolation

Hi All,
I am using two webdynpro iviews in a page .. i want the page to be displayed only after two iviews are loaded .. so i thought of using embedded property , but i came to know that both iviews will be refreshed if anyone of the ivews gets refreshed ... what exactly mean by refresh .. will the iview be loaded again .. if so is there any way to avoid this??
Regards,
R

Hi,
Read <a href="http://help.sap.com/saphelp_nw70/helpdata/en/37/21dd3f92c4f306e10000000a1550b0/frameset.htm">here</a> about Embedded Isolation Method and <a href="http://help.sap.com/saphelp_nw70/helpdata/en/b5/8d977463334342be192228d2824fe1/frameset.htm">here</a> about URL Isolation Method.
Roy

Similar Messages

Problem with IView Callable in GP

Hi Guys,
I encounter a similar problem to the one in thread Problem to execute a Callable Object in UWL iView doesn't work in my GP process at all. I always get the error message in GP Runtime when it comes to an iView callable: The portal page builder required to execute this callable object is not available.. If I open the corresponding task in UWL I get: "cannot get the process instance, please contact your system administrator.". The messages look familiar, but happen in a totally different situation.
I also get the modified config file, no help. So could any of you figure out what the problem is? Thanks.
Ge

try this uwl config file
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE UWLConfiguration PUBLIC '-//SAP//UWL1.0//EN' 'uwl_configuration.dtd' [
]>
<UWLConfiguration version="2.0">
<ItemTypes>
 <ItemType name="uwl.task.gp" connector="GuidedProceduresConnector" defaultView="uwlTaskGPView" defaultAction="launchGP" executionMode="default">
 <Actions>
 <Action name="launchGP" groupAction="no" handler="IViewLauncher" referenceBundle="launch_sap" returnToDetailViewAllowed="yes" launchInNewWindow="no" launchNewWindowName="GPWindow" launchNewWindowFeatures="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no">
 <Properties>
 <Property name="DynamicParameter" value="app.processId=${item.externalId}"/>
 <Property name="page" value="pcd:portal_content/com.sap.pct/platform_add_ons/com.sap.caf.eu.gp.folders.gp/com.sap.caf.eu.gp.roles.runtime/com.sap.caf.eu.gp.worksets.runtime/com.sap.caf.eu.gp.pages.procinstance"/>
 <Property name="app.processId" value="${item.externalId}"/>
 <Property name="System" value="SAP_LocalSystem"/>
 </Properties>
 </Action>
 </Actions>
 </ItemType>
</ItemTypes>
<Views>
 <View name="uwlTaskGPView" selectionMode="SINGLESELECT" width="98%" supportedItemTypes="uwl.task.gp" columnOrder="subject, process, creatorId, createdDate, dueDate, status" sortby="dueDate:ascend, createdDate:descend" tableDesign="STANDARD" visibleRowCount="10" headerVisible="no" queryRange="undefined" tableNavigationFooterVisible="yes" tableNavigationType="CUSTOMNAV" actionRef="" refresh="300" dueDateSevere="86400000" dueDateWarning="259200000" emphasizedItems="new" displayOnlyDefinedAttributes="yes" dynamicCreationAllowed="yes" actionPosition="bottom">
 <Descriptions default="Guided Procedures">
 <ShortDescriptions>
 <Description Language="de" Description="Guided Procedures"/>
 <Description Language="en" Description="Guided Procedures"/>
 </ShortDescriptions>
 </Descriptions>
 <DisplayAttributes>
 <DisplayAttribute name="phase" type="string" width="" sortable="yes" format="default" hAlign="LEFT" vAlign="BASELINE" maxTextWidth="0" headerVisible="yes">
 <Descriptions default="Phase">
 <ShortDescriptions>
 <Description Language="de" Description="Phase"/>
 <Description Language="en" Description="Phase"/>
 </ShortDescriptions>
 </Descriptions>
 </DisplayAttribute>
 <DisplayAttribute name="process" type="string" width="" sortable="yes" format="default" hAlign="LEFT" vAlign="BASELINE" maxTextWidth="0" headerVisible="yes">
 <Descriptions default="Process">
 <ShortDescriptions>
 <Description Language="de" Description="Process"/>
 <Description Language="en" Description="Process"/>
 </ShortDescriptions>
 </Descriptions>
 </DisplayAttribute>
 </DisplayAttributes>
 <Actions>
 <Action name="launchGP" groupAction="no" handler="IViewLauncher" referenceBundle="launch_sap" returnToDetailViewAllowed="yes" launchInNewWindow="no" launchNewWindowName="GPWindow" launchNewWindowFeatures="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no">
 <Properties>
 <Property name="DynamicParameter" value="app.processId=${item.externalId}"/>
 <Property name="page" value="pcd:portal_content/com.sap.pct/platform_add_ons/com.sap.caf.eu.gp.folders.gp/com.sap.caf.eu.gp.roles.runtime/com.sap.caf.eu.gp.worksets.runtime/com.sap.caf.eu.gp.pages.procinstance"/>
 <Property name="app.processId" value="${item.externalId}"/>
 <Property name="System" value="SAP_LocalSystem"/>
 </Properties>
 </Action>
 </Actions>
 </View>
</Views>
</UWLConfiguration>

Problem with iview URL

Hi,
When copied and view the url in a new window the following problem is coming.
can any one help, to generate url for my iview.
Current url: "http://ps5207:50300/irj/servlet/prt/portal/prtroot/pcd!3aportal_content!2fsriram2!2ftestiview?sap-config-mode=true"
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
Access denied (Object(s): portal_content/sriram2/testiview).
Exception id: 10:51_14/08/07_0096_38481850
See the details for the exception ID in the log file "

hi Ram,
your URL contains the port and other info which we get for the iViews being displayed in portal.
URL iviews are for simple URLs....copying the iview address as such and putting this under the URL iView will not work I guess.
better try the quick links for this.
just search for quick links in the forum..you will get enough answers on how to do this.
Cheers........

Problem with small text in iview header

hi,
i got a little problem with iView header.
I've set 2 pages containing the same iViews. The 2 pages have layout (1 column full width -- standard) and the 2 pages have the same properties, themes.
The problem is that in the first page the header text is very small and in the second one the header text display correctly.
Have anyone had this problem and how did you solve it ?
Thanks in advance.

Hi,
I don't have a straight answer but:
1. Have you tried creating a copy of the page which is working correctly?
2. Why do you need two pages with the same content? Personally, I can't see any reason for maintaining two identical objects.
Roy

Problem with JavaScript in URL iView

Hi,
I am facing a problem with javascript when i am trying to access my application through URL iView. In the javascript window.top is used to access the frames in the window. But the EP is not recognizing it as valid. what exctly the problem and please suggest me a solution.
Ashok.

Hi,,
thanks for the quick reply. But what i asked was different. I will put it in different way. I have deployed a application in Web Application Server and trying to access it through URL iView. My application is pure J2EE application with html,jsp and JS files. In javascript we used window.top property of the java script which is working fine MS IE. The problem is window.top is a IE specific property which is not having any equallent open standerd so EP is throwing a java script error. As I know the only possible solution for this problem is inherating IE rendaring capabilities to iView(i.e iFrame). is there any way to do that?
Ashok.

Caching problem for iViews with URL parameters

Hi,
We have a big problem with iView caching.
Our objective is to use SAP Netweaver Portal 2004s & External Facing portal for a public Internet Portal
For performances reasons we need to activate iviews caching on the principal iviews. But the problem is that a page called with different parameters generates exactly the same html result
example --> The display of a news item:
/irj/portal/anonymous/index.htm?rid=/news_123.xml
gives the same cached result as
/irj/portal/anonymous/index.htm?rid=/news_456.xml
The caching level is "shared" because all users are anonymous !
The iview caching seems to be occuring on component (iView) level and not on URL level
Can someone help ?
At the moment we have performances of 10 seconds for a page, and with caching it's becoming less than 1 second, so we really need the caching !!!
Thanks
Laurent

Hello
I hope you get your answer since, nevertheless it could help other.
Have you tried to put the cache level to "session" instead of "user" or "shared" at the iview level?
Regards
Benoit

Isolating problems with MPEG2 VBR "best"

There have long been discussions here around problems with the quality of MPEG2 compression with Compressor v2.x, usually difficult to quantify or "solved" with "It doesn't work, use something else" such as a different product, Compressor v1 or a Quicktime MPEG2 export component. Maybe I'm an optimist, but I have to believe that someone who owns the code behind the Compressor product really does care to improve the quality of the compression, and is just waiting for a decent test case to figure-out what everyone is complaining about.
That in mind, I would like to propose that the most visible problems I've seen can be isolated to something to do with what is done when switching from "VBR" compression to "VBR best" compression, either in 1-pass or 2-pass mode. I would be curious if others who have had similar quality complaints could also check if they are using "VBR best" compression, such as the various default presets for "DVD: MPEG2 best quality..." which use "2-pass VBR best". In short, it seems as though one can get rid of the most serious artifacting problems by taking a "best quality" preset and changing the quality from "2-pass VBR best" to simply "2-pass VBR" (and similarly for 1-pass).
My own example: I've taken a short clip (less than 30 seconds) from the start of a recent home movie and published it along with some results on my iDisk's Public folder (Finder > Go > iDisk...): member name "dickermn" [sic], with no password. There you will find the folder CompressorTest, containing...
-> 2006winter - a self-contained QT movie with the DV source material.
-> dualG4 - a folder with the results of Compressor's MPEG2 compression with various settings, as run on a dual-1GHz G4 system.
-> coreDuo - a folder with the results of the same settings as above, but with Compressor run from a coreDuo mini.
-> *.png - two pairs of window-capture shots showing the same frames as compressed with "VBR" and "VBR best" settings.
Background: after having various odd and intermittent problems with MPEG2 compression results, I've used the recent upgrades to start with a clean slate: on the G4 system I ran Software Update, then removed all the components of DVD Studio Pro 4, Compressor and Qmaster, along with all preferences, application support files, frameworks, receipts, etc, as recommended in these web pages to remove these programs, then did a full install of my unversal upgrade to Final Cut Studio, and re-ran Software Update. This got me up to the current ProApps updates and Compressor v2.3.
Using only Compressor's default presets, selecting "DVD: Best Quality 150 minutes - 4:3" (2-pass VBR best, 3.7Mbps average rate), gives results with very visible artifacting. Using this same preset but changing the quality to "2-pass VBR" appears to clear up the most visible problems. Similarly, selecting "DVD: Fastest Encode 150 minutes - 4:3" (1-pass VBR) gives good results, but changing the preset's quality to "1-pass VBR best") produces visible artifacting.
For the purposes of testing, I also installed just Compressor on my coreDuo mini - a clean install - then ran Software Update to bring this to Compressor v2.3. Running the same tests as above on the Intel-based machine produced similar artifacting problems when selecting "best quality", but in different places in the media than on the G4. Using the same quality settings as above, but moving the average bitrate down to 3.0Mbps has similar behavior, but the artifacts are just more pronounced, and using a default preset with higher bitrate (5Mbps average, not included here) the artifacts are still quite visible, but less pronounced. From the 3Mbps results on the G4, the still frames captured show good examples of the problems at hand, though the artifacts are much more visible with the video in motion. These are the examples described below.
The clip shows some still titles against a still, horizontal-blurred background. At the end of the titles, the blurred background "un-blurs" and the motion starts: a horizontal pan, a wipe transition, and a downward pan. The subject is all falling snow, trees, our back deck, my son and me. The footage was taken with a consumer-grade Sony handheld camcorder.
The problems first noticable in the video appear as a blockiness to the images, particularly notable against the floor of snow where the image shifts visibly to different intensities of gray/white as the camera moves. More severe are blocks which don't move correctly with the camera, at first visible as a jerkiness to the opening background as it un-blurs, but more pronounced in the trees and decking during the downward pan at the end.
At about 14s is a good still of the blocking artifacts, seen here in the 1-pass VBR still frame. Note the large blocks in the snow in the "best" encoding, which are small enough to be lost in the noise for the "not-best" encoding. These shimmer between the different shades of gray as the camera moves.
At the last half of the clip, as the camera pans down, parts of the trees appear to jump independently of their branches. This is very clearly visible around the straight-lines of the railing in the lower part of the frame as the clip ends. The still is from about 23s into the clip, and you can see a block of the railing in the lower right which has clearly jumped-above the rest of the railing. Interestingly enough, this is the correct placement for those pixels in the next frame (as the camera continues to pan downward). In each of these "jumpy" cases, it would appear as though blocks of pixels show-up one frame early, and their surrounding blocks catch-up in the next frame (while these hold still). Again, when using the same settings without "best" quality, the jumping does not occur.
Note that with each pair of still (png) images you can group-select the pair and double-click to open them both in Preview, which allows you to toggle back-and-forth easily between the "best" and "not-best" versions. Comparing the two, you can easily spot several blocks in the frame which shift relative to their surroundings.
While I am aware that MPEG2 at low bitrates is a complicated thing (though I will leave open for debate how low 3-4Mbps is in today's world), and consumer-grade video has lots of noise which the encoder has to dance-around, I do believe it is fair to assume that the "best" settings should give visibly better results than their faster "non-best" counterparts, all else being equal - at the very least, the results should not be visibly worse. It is worth noting that the "best" VBR settings do appear (subjectively) to give better contrast or color-depth, so clearly something right is going-on - I just have to believe that there is something going awry in the whole process which creates artifacts negating the other benefits, but which, with any luck, could easily be fixed.
Please post with your comments, experiences or similar issues... or exactly what is the proper way to get this information to someone who could fix it?
dual 1GHz G4 + coreDuo mini Mac OS X (10.4.8) Compressor v2.3 / Final Cut Studio (univseral)

Well, I've found one more piece to this puzzle: hardware graphics accelerators.
In short, I tried this same test running Compressor on my G4 PowerBook (with Radion Mobility 9700) and got better results. The terrible blockiness and pixelation problems seem - dare I say it - gone from the MPEG2 video. In this regard, the video compressed as both the default "2-pass VBR best" and the same preset adjusted to use "1-pass VBR best" both looked cleaner than any of the VBR "not best" encodings produced on this machine, or either of the others.
Unfortunately, we're not completely out of the woods: the problems evidenced later in the clip - blocks which appear displaced in space/time for one frame - are still there, though they have moved to different locations in the frame.
This gets me to thinking: my PowerBook is just barely past current muster in terms of hardware-accelerated graphics (enough to run Motion, for example), whereas my other two machines are not (NVidia GForce4Ti & mini's Intel graphics). So this starts to get to the root of "If these presets don't work, why does Apple label them best - or distribute them at all?" I'm going to hazard a guess that there are various pieces to the codecs which can take either a software-only path or a hardware-accelerated path, and the bugs seen here exist only in the software (non-accelerated) path. Anyone testing on the latest top-notch hardware with a fancy-shmancy graphics card wouldn't go down that path and see any problems. And the problems are subtle enough that they'd even slip by the occasional testing of the slower path.
So now I'm out to find a more-current-than-my-PB graphics card to run the test, to see if I can get rid of the other problem. Updating to Compressor v2.3 got rid of most of the problems, and if buying new hardware is all it takes to fix MPEG2 compression, I might just spring for it - and hey, I'd get to run Motion, too.
So anyone out there with a whiz-bang graphics card care to run these tests and compare/contrast with what I've got here? I might know someone with a new MacBookPro, which I hear has a pretty current graphics chip in it...

Problems with MDM 5.5 SP05 Portal Content - ResultSet iView

Hello Experts,
We are having problems with standard iViews from MDM 5.5, more specific with ResultSet iView. We created an iView using English as default browsers language but our client wanted it in Portuguese, so in the MDM Repository both languages were defined and used in MDM Data Manager, when passed to the Portal iView an error occur, but only in a ResultSet iView from the MDM Portal Content, the others iViews (itemDetails, PicklistSearch, etc...) are shown in Portuguese, and we cannot figure out why it works fine in English and not in Portuguese. We left the default language defined by clients browser. Below Im sending the LOG, which by the way, doesn't help much, but I put it also here. Any ideas of what should I do ?
LOG ERROR:
java.lang.IllegalArgumentException: unknown format type at
We are using Portal 7.0 SPS11 and MDM 5.5 SP05 - Portal Content in a Win2003/Oracle server each.

Alex,
sorry to disturb you with this issue, can you explain me basic steps in order to setup standard MDM iviews from the portal?
I mean, I have already installed all standard mdm business content, and also have configured system and aliases in the portal to connect to my mdm repositories. Those system/aliases are working propperly.
But, when I try to preview standard MDM iviews/pages I got several JAVA errors in trace logs.
Specific iviews are: Item Details, Show products, etc..any iview execution fails.
So, am I missing something?, do i have to create a specific user in portal?, assign specifi roles or groups???.
Platform is: nw2004s SR2, SP11, MDM content 5.5
Thank you in advance.

Problem with DiscussionGroups iView

Hello Yogi/Robert,
I have a problem with my discussion groups iview.
I am using the discussion groups iView, and layout set is DiscussionGroupsContributor. The iView is using the /discussiongroup folder to store the discussions created.
Here's the problem: all the discussions created are stored in the same folder, and every new room created is able to view the same discussions.
I want to be able to restrict discussions to different rooms, so that members of one room cannot view/read the discussions from another room.
Please,how can I get this done...it is very urgent!!!
Thanks in advance.
Collins

Hi Collins,
have a look on how the room template "SAP_Standard_Template_2 (Read only)" is configured and configure your template in the same way.
You need two Room Extensions, one for the DiscussionPermission and the second for Discussion Persistency. In the second a preconfigured room extension CM store is used (here cmDocuments with the label "Documents"). The output parameter "discussion_path" is mapped on the Path parameter of the RoomDiscussion iView on the RoomDiscussion Page.
So the sentence "For data for discussion groups inside rooms, the system determines the path to the storage folder automatically." is only correct if you work with room extensions as mentioned above.
If you need more information on CM Room Extensions have a look at this link: http://help.sap.com/saphelp_nw04s/helpdata/en/f2/3c9041eedda009e10000000a155106/content.htm
Hope this helps,
Robert

Problems with the postal code in address iview ESS.

I would greatly appreciate if someone answer this threat. I am having this big problem with the address iview. It is not possible to change the postal code in the address iview.

Can you explain the issue? Means for which country this issue is coming. We faced similar issue. There is some bug in ESS/MSS package itself. You send me details of issue at [email protected] I will reply you back with OSS message answered by SAP if that is a bug.

Problems with the "my tasks" iView

Hello,
we use the EP 6 SP 09.
I have problems with the "my tasks" iView (com.sap.netweaver.bc.uwl.ui.uwl). The first problem is, that the user get no e-mail if anybody give him a task (Options: Notification = Notify on Updates, Completion ...). The next problem I have is, if a user (without admin rights) click on the button "Personalize" he get an empty window. But a user with admin rights get the window with the "Personalize" view.
Can anybody help me? Where are the possibility to customizing?
kind regards
Jochen Kormannshaus

hi,
The personalization tray is only visible if the iView tray is visible.So make sure that iView tray is visible.
Also u can look into followinw links.
https://weblogs.sdn.sap.com/weblogs/topic/22
Think outside the box - enhance processes with Universal Worklist Action Handlers!
Regards mujjammil

Page Layout Problems with embedded iViews

Hi all,
We are having problems with the position of the iviews in the layout page using embedded iviews. Sometime load in one order and other times in another one. I need that the iviews load in the same order always.
Any idea, please?
Thanks for all.

Hi José,
if in fact this is the case, then I would expect that the single iViews are called via different threads. If this is the case, then I would implement within the iView to wait for some result provided by the iView, which should be loaded first (for example, by putting some certain value into the http session object).
For deeper discussions on this topic see and
Hope it helps
Detlev
PS: Please consider rewarding points for helpful answers on SDN. Thanks in advance!

Problem with Tools Area iView Creation - Help Needed.

Hi Guys,
I am having a small problem with the Tool Area Par, I downloaded the Par and have edited it and then redeployed it on the Portal, however when I am creating an iView I am getting the Following error:
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/every_user/general/defaultDesktop/frameworkPages/frameworkpage/com.sap.portal.toolAreaiView
Component Name : null
Page could not create the iView.
See the details for the exception ID in the log file
Can anyone suggest me what could be wrong and why I am not able to see the Iview and why I get this exception.
Thanks,
John.

Log File:
[code]
Component : com.sap.portal.navigation.toolarea.default
     at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
     at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
     at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
     at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
     at com.sapportals.portal.prt.connection.PortalRequest.getRootContext(PortalRequest.java:435)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:607)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
     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:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     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.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.navigation.ToolAreaiView of Portal Component com.sap.portal.navigation.toolarea.default because: Could not find implementation class
     at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:242)
     at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
     at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
     at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
     at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
     ... 26 more
Caused by: java.lang.ClassNotFoundException: com.sapportals.portal.navigation.ToolAreaiView
Found in negative cache
Loader Info -
ClassLoader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@2086d]
Parent loader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@695f94]
References:
   not registered!
Resources:
   C:
usr
sap
J2E
JC00
j2ee
cluster
server0
apps
sap.com
irj
servlet_jsp
irj
root
WEB-INF
portal
portalapps
com.sap.portal.navigation.toolarea
private
classes
     at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:360)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:219)
     at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
     ... 30 more
[/code]

Problem with SAP Transaction iView after Patch 34 install

Hi All,
We're running EP6SP2 on AIX/Oracle and have currently upgraded from PL5 to PL34.
The problem we are now having is as follows:
We have an SAP Transaction iView that is using the 'Auto' method for the 'Technique to start SAPGUI for Windows' and the 'WinGui' as the 'SAP GUI Type'.
Now when we click on the iView we are getting the IE popup that asks us if we want to Save, Open, or Cancel the file open for tx.ssd
Prior to the patch upgrade we did not have this issue.
Any help would be appreciated.
Thanks,
Robin.

Hi Praveen,
Thanks for the quick response.
I have seen those notes already and unfortunately they don't solve this specific problem. These will solve the problem for the SSD method (.sap file) of starting the SAPGUI for Windows but not for the SSF method (.ssf file).
The main issue is that before the install of the Patch we did not get the popup, everything worked fine. It doesn't make sense why we would have to change our IE settings now to get it to work properly. It should work the same as before the patch.
Plus, I don't want to have to do an SMS push to all the PC's here to fix a problem with a Patch upgrade.
I have tried to add the .ssd and .sap types to the Mime section for the http service in the Admin tool but this hasn't fixed the problem either.
Also, I found that in Patch 31 SAP has made a change to the way the SAP GUI for windows starts. After some searching I found that in the file WinGuiRenderLayer.properties under
the 'com.sap.appintegrator.sap/property/Transaction/' folder I see that it has some entries in it that look like they relate to the above mentioned fix for Patch 31. The lines in particular are:
- # postfix for roundtrip URL - should help IE to detect the mime-type
- SSF_URL_Postfix = /tx.sap
- SSD_URL_Postfix = /tx.ssd
These lines were not in this file prior to implementing the patch and I believe that this may be causing the problem.
Any other suggestions would be appreciated.
Thanks,
Robin

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.

Problem with iView Isolation

Similar Messages

Maybe you are looking for