UWL - delta linked copy of iView

Hi Experts,
We have customized a delta link copy of the standard UWL iView and add this delta link copy to several role (delta linked too). We have NW 2004s (SPS15).
As I could see in NW 2005 HowTo guide from SAP that UWL personnlized iview should only be copy (and not delta link copy), which problem could occurs due to delta link copy?
Thanks in advance for your help,
Regards,
Oliver

Hi
http://help.sap.com/saphelp_nw04/helpdata/EN/f5/eb515d0e6a11d7b84900047582c9f7/content.htm
https://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=77988232
Regards
Shridhar Gowda

Similar Messages

MSS Appraisal Use Copy or Delta-linked copy of iView

We are using EP 7.01 on ECC 6 EHp4 and in the process of implementing MSS 1.41.
In order to use position to position in the appraisal process we need to make a Z copy of the application HAP_START_PAGE_POWL_UI_MSS. and then make an iView with the Z application.
We need to know which is best to use - a copy of the appraisal iview or a delta linked copy of the appraisal iview.
Thanks,
D. Maupin
University of Kentucky

These links are very useful and helpful.
The question is If we delta link a copy of the iView and change the Applicaiton property, will that show the Z copy of the application? and when SAP updates the original iView will that erase the changed property in the delta linked copy.
If we only make a copy then for every SP or EHp we will have to check the copy of the iview with the original iview.
Thanks,
D. Maupin
University of Kentucky

FPN Remote Delta Link - Bex Web - Iview Preview Error

We created a remote delta link in the Consumer Portal for Bex Web Iview from the Producer portal. The preview of the iview in the consumer portal fails with the following error:
Unexpected error - Unable to get IView: fpn:<Consumer Alias> /pcd:portal_content/com.sap.pct/platform_add_ons/com.sap.ip.bi/iViews/com.sap.ip.bi.bex:eV%2BqDnR62S5rnG4nJ%2F7uhw%3D%3D:1
In the default trace of the Producer we see the following:
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.sap.portal.fpn.exception.base.FPNFatalErrorException
 at com.sap.portal.fpn.runtime.FpnRuntimeService.doFpnLookup(FpnRuntimeService.java:171)
 at com.sap.portal.fpnprovider.fpn.GenericContext.lookup(GenericContext.java:48)
 at javax.naming.InitialContext.lookup(InitialContext.java:347)
 at com.sapportals.portal.prt.deployment.DeploymentManager.getPropertyContentProvider(DeploymentManager.java:1919)
 ... 40 more
Caused by: com.sap.portal.fpn.exception.base.unchecked.FpnCommunicationException: Cannot retrieve delta link remote state for remote path 'pcd:portal_content/com.sap.pct/platform_add_ons/com.sap.ip.bi/iViews/com.sap.ip.bi.bex' with user Id '<BIUSER>'
 at com.sap.portal.fpn.remote.AccessServiceImpl.retrieveDLRemoteState(AccessServiceImpl.java:158)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:331)
 at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:159)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
 ... 6 more
Caused by: com.sap.portal.fpn.exception.base.unchecked.FpnAuthenticationException: Could not find user from the user id '<BIUSER>'
 at com.sap.portal.fpn.protocol.marshal.ContentMarshallerService.marshalDLChain(ContentMarshallerService.java:294)
 at com.sap.portal.fpn.remote.AccessServiceImpl.retrieveDLRemoteState(AccessServiceImpl.java:156)
 ... 14 more
Caused by: com.sap.security.api.NoSuchUserException: USER_AUTH_FAILED: User account for logonid "<BIUSER>" not found!
 at com.sap.security.core.imp.UserFactory.getUserByLogonID(UserFactory.java:1317)
 at com.sap.security.core.imp.UserFactory.getUserByLogonID(UserFactory.java:1339)
 at com.sap.security.core.imp.UserFactory.getUserByLogonID(UserFactory.java:1354)
 at com.sap.portal.fpn.protocol.marshal.ContentMarshallerService.marshalDLChain(ContentMarshallerService.java:292)
 ... 15 more
Producer Portal - User data source is BI ABAP Backend
Consumer POrtal - User data source is LDAP
I have tested SSO both ways and it works:
Logged in to Consumer -> switched URL to producer --> switched back to consumer
Still looking at the default trace it looks like some how the end user is not recognized during the switch.
Any help/direction is much appreciated.
Thanks
Shabna

Dao,
Thanks for taking the time.
Versions:
Producer BI portal - NW 7.0 EHP1 SP6 (BI_JAVA SP8 Hotfix 12)
Consumer Portal - NW 7.0 EHP1 SP7 (BI_JAVA SP8 Hotfix 12)
BIUSER exists on both:
Producer - BIUSER is an ABAP user in the BI Backend
Consumer - BIUSER is the SAMAccount Name of AD account BISUER@<company.com>
SSO works both ways.
I checked the thread you mentioned. Though the error in the default trace is the same, I am using FQDNs everywhere and the correct P4 ports. I am able to telnet using the P4 ports between the two portals. The FP connection tests also work.
Thanks
Shabna

How many roles delta link a particular iview

Dear experts,
sir, i a creating a iview and i assign this iview to many roles by using delta link.
My problem is that is it possible to find that how many roles with their names we delta link that iview.
please help.............

Hi Mousam,
If you want to know the roles that are connected with a particular iview, open the iview object and then select delta link tracer from the display dropdown > select show delta link dependants radio button and you'll see all the dependant objects.
Regards,
Sen

Delta links

I followed SAP's recommendation to make copies of the original ESS Portal objects (iViews, Pages, Worksets) so that customer modifications do not happen on the original SAP objects. I have therefore created delta-link copies for all the original SAP objects. However, the "delta-link copy" pages I created use original SAP iViews, not my "delta-link copy" iViews. So customer modifications to the copied iviews will have no effect. One option I have is to re-attach the delta-link-copy iviews to delta-link-copy pages, but in the future SAP may change the relationship page-iView and then my system won't work (or won't take advantage of the SAP enhancement). Any other ideas?

I think re-attaching the delta linked iViews is the only option. When SAP privdes any update we need to do this excersize again.

Problem with Delta Links

I have :
- a standard Workset with pages that are delta-linked to standard pages (nothing extraordinary so far...)
- a delta-link copy of that Workset
Consequently, the pages in my Workset are linked to pages in the standard Workset (themselves delta-linked to the "stand-alone" pages). Here is the link chain :
Pages <- Pages (Workset) <- Pages (specific Workset)
I deleted certain pages in the specific Workset.
Question :
1) How can I put those pages back in the specific Workset as if they hadn't been deleted ?
(if I copy the standalone standard pages with Delta-Link, I will lose 1 level in the Delta-Link hierarchy, am I wrong ?!
Indeed, I have this actual link chain :
Pages <- Pages (specific Workset)
instead of
Pages <- Pages (Workset) <- Pages (specific Workset)
2) Is it possible to change the ID of pages inside my own Workset for I have annoying suffixes (like '_2') that I think disturb the Navigation (I am implementing xRPM 2.0) ?
Thanks for your answers.

Hi Rajeev,
1) As illustrated, the only way I found to replace the deleted Pages in my Workset was to copy them from the standard Pages.
 However, doing so, you can see in the Delta-Link tracer that this implies a direct Link from the Pages in my Workset to the standard pages.
==> this means that if the Pages in the standard Workset are modified, modifications will NOT be reported in my pages.
 Only modifications on the standard Pages will be reported...
For instance :
a or A : Pages (stand-alone)
b : Pages (standard Workset)
c or C : Pages (specific Workset)
By copying the Workset, we create this Delta-Link chain :
a1 <- b1 <- c1
an <- bn <- cn
But, by copying directly from standard Pages, we've got this :
A1 <- C1
An <- Cn
As a consequence, changes on the standard pages are OK in both cases.
ai' <- bi' <- ci'
Ai' <- Ci'
We have : ci = Ci
But changes on the pages inside the standard Workset is troublesome :
ai <- bi' <- ci'
Ai <- Ci
We get : ci' <> Ci
The whole point is : is it possible to copy the pages inside the standard Workset ?
Hope it is clearer now...

Why editing iview id break the delta link in the portal page?

For some reason, everytime I edit the iview id, the delta link in the page will be broken.
After I changed the iview id, the iview id that I added as delta link in portal page remain same, and seems like become a separate copy , rather than the original delta link.
This frustracted me as I have to remove the old iview , and add the new edited iview into the page again.
Why is this happen? (I am very sure I didn't accidentally add the iview as copy, instead of delta link)
By the way, I am in NW04s SP9.
Thanks for help.
Kent

Hi Kent,
> (I am very sure I didn't accidentally
> add the iview as copy, instead of delta link)
The wording "I am very sure" points to the fact that you didn't really check and re-try it?!
I just checked it on NW04 / SPS18 (which corresponds to SP09 on NW2004s) - and it works like a charme. The delta-link on the test page points to the new ID (as the ID-Change-Wizard announces it).
As I have no 2004s installation at hand, I would suggest really to re-check if you are really talking of a delta-link. If it really doesn't work on SP09 while it works on SP18 in parallel, you would have to open an OSS message. Anyhow, this really should behave analogously...
Hope it helps
Detlev

Basic Question on Copy and Delta link which one to use when?

Hi
Its basic question
My understanding about copy and Delta link is
Copy doesnot ahve direct relationship with source object (but it acts as a sibling) any changes done to spurce object does not affect target object.
Where as Delta link will have a parent child relation ship between source object bacially its a copy of source and inherits id properties. in case if i change source object does this affect target object, we can delete, add content to delta link target object.
let's say if i want to use standard quickpoll iView do i need to use copy or delta link similarly for other iviews, worksets, roles which one will be better.
Regards,
Murali

Murali,
Yes, your understanding is right.
Case 1 : Copy
A- Object
B- Copy of A
Both of them are independent.Any changes in A are not dependent on B and vice versa.
Case 2 : Delta Link
A - Object
B - Copy of A (via Delta link)
Any changes to A are reflected in B, as A is a parent and B a child.
But B would be an independent entity.Any changes to B would not effect A.
When you use either of them, depends on your need. When you are working with standard iviews or roles or workset, you can do a copy of the original, because in most cases we would not make changes to the standard roles or worksets or iviews. There by eliminating the process of making a delta copy.
But, if you are dealing with the roles that you have created and want to make a copy of it, you can use a delta link, because, even if you want to add more iviews and worksets to that role, they would get reflected when you make a delta copy.
Hope that helps.
Consider rewarding points for handy posts!
Cheers,
Sandeep Tudumu
Edited by: Sandeep Tudumu on May 6, 2008 2:10 AM

Federated Portal - ESS/MSS remote content copy / remote delta link mode

Hello,
We have established an Federated Portal Network between two Enterprise Portal systems.
The Consumer System is an Netweaver Enterprise Portal, the Producer also an Enterprise Portal installation + XSS.
We use remote role assignment and remote delta link functionality between this two systems.
We have an request to enable BI JAVA Iviews on the consumer and as transitive content sharing is not provided, we would like to copy the ESS/MSS roles as remote content copy/remote delta links from the producer XSS system to the consumer system.
When we try to copy the ESS or MSS roles the copy process end with the following error message :
"Due to an unexpected error the action will be canceled"
The remote content copy/remote delta link usage mode is working correct on other roles
Is this a restiction that ESS/MSS roles can not be used in remote delta link mode ?
Is there an workaround for such usage type ?
Thank you
Best Regards
Martin Vartik

Hello,
We have established an Federated Portal Network between two Enterprise Portal systems.
The Consumer System is an Netweaver Enterprise Portal, the Producer also an Enterprise Portal installation + XSS.
We use remote role assignment and remote delta link functionality between this two systems.
We have an request to enable BI JAVA Iviews on the consumer and as transitive content sharing is not provided, we would like to copy the ESS/MSS roles as remote content copy/remote delta links from the producer XSS system to the consumer system.
When we try to copy the ESS or MSS roles the copy process end with the following error message :
"Due to an unexpected error the action will be canceled"
The remote content copy/remote delta link usage mode is working correct on other roles
Is this a restiction that ESS/MSS roles can not be used in remote delta link mode ?
Is there an workaround for such usage type ?
Thank you
Best Regards
Martin Vartik

How to find the Delta Linked iView's Origin ?

Hello all,
How r u ?
We found some new Delta Linked iViews in the Workset, but these iViews are not available in the Portal Content under the mentioned Folder. How do we find the origin of that iView ?
Best Regards....
Sankar Kumar
+91 98403 47141

Hi Maran,
Please follow these,
Content Admin -> Open your Workset.
Now your workset will display names of the iView that assiged to that workset.
If the iview is copied without delta link means that will mentioned as (changed) near by the iView Name.
 Example: Content Admin -> Open your Workset Object
 <MyWorkSet>
> MyiView1
> MyiView2(changed) [This means this iView copied w.o Deltalink)
> MyiView3
Here MyiView1,MyiView3 are deltalinked iViews.
Regards,
Ramganesan K

Federated Portal Network FPN: exception Remote Delta Links rdl

Consumer Portal version: 7.01 SP2
Producer Portal version: 7.00 SP15
I always receive an exception when i try to preview a remote delta link.
I think I've setted up correctly the trust relationship between my portals. Because when I log on to my consumer portal and I open the producer portal in the same browser I don't need to give my user credentials. This is a simple test to see if the the trust relationship is working...
In the portal content studio I'm able to see my portal producers and their content. There is also no problem to copy for eg. an url iView from my producer to the portel content of my consumer portal as local content. when I try to preview my iView I receive a runtime error!
Anyone who'd like to share some ideas? Known issues?
Thanks

I've posted my solution in this thread:
Re: Federated Portal Network FPN: exception Remote Delta Links rdl
My problem is already solved!
Thanks anyway,
Gert

Problem- Create Remote Delta link in Federated Portal Network environment

Dear Experts,
I am working in a Fedeated protal network environment where the producer is BI 7.0 Portal and the EP portal is the consumer.
FPN was already configured at client side and some reports were already integrated .
Now i am working to integrate some other BI reports and need to work on PCD ( creating iviews/pages/worksets/roles )..for integrating the BI reports.
I followed to create th remote delta link for content of producer in the consumer portal as following .
1.In consumer portal i navigated to the Portal catalog of NetWeaver Content Producers
2 .Browse the Portal Catalog of the remote producer and then, choose Copy.
3.Right-click a folder in conusmer local Portal Catalog (in the Portal Content root folder) and then choose Paste as Local Content.
While perfoming third step i am getting following error
"*Could not create remote delta link to object'pcd:portalcontent/com.analog.analog/hcm_bi_reports/iviews/basic_reports/com.analog.cost_center_report'Could not connect to producer portal. Please check that the producer portal is running, there are no network problems, and your consumer settings for the producer are configured properly_* "
Producer potal is already in running mode and producer content is get dispalying in consumer portal under NetWeaver Content Producers.
Could any body help me what might be the problem.
i would appriciate if you replied for the same.
Thanks and Regards
Ratnakar

Hi,
Could you try to set the log level ALL for com.sap.portal.fpn and its subtree (From log configurator service in Visual Administration)?
Then see the log messages in the default.trc logs and possibly post them to this threads.
Regards
Dagfinn

FPN SP12: Remote Delta Linking does not work

We have two portals, both running NW70 SP12. The Producer portal is a BI portal, the consumer is a plain EP. SSO has been implemented, and the consumer has been registered on the producer. Remote Role Assignment works, and content from remote roles is visible on the consumer. The producer portal object is called BI_Portal, and the consumer portal object is called EP_Portal.
While RRA is working, Remote Delta Linking is not.
I can browse the producer PCD from the consumer and copy the selected iView to the consumer PCD. I can then take the copied iView and place it in a role. Once I grant the consumer role to a user, the item then shows up in the navigation structure. However, when clicking on the iView, I get the following error in the Producer log file:
com.sapportals.portal.prt.runtime.PortalRuntimeException: Unexpected error - Unable to get IView: fpn:EP_Portal/pcd:portal_content/ca.company.fld_comp/ca.company.fld_projects/ca.company.fld_fed_con/ca.company.rl_loc_fed_con/fld_my_work/fld_loc_fed_con/ca.company.iv_sd_org:Uql7CRb%2FAHAgS69lwbBcoA%3D%3D:1:
Now, this error appears on the producer portal - why is the path fpn:EP_Portal in there? I think what's happening is that the wrong fpn object is being placed in the iView object, so when the request hits the producer portal, the portal runtime can't find the object since the object fpn:EP_Portal doesn't exist.Or, perhaps I don't understand what the fpn: locator is supposed to mean.
If you use the PCD Inspector, the iView attribute FpnLocator is what contains the fpn:EP_Portal/ string. I've tried modifying it to point at the local portal, but that doesn't work either.
Anyone else at this service pack level get RDL working?

I'm a bit confused:
EP_Portal is the name I entered for the consumer portal when I registered with the producer. So, when I go the producer portal, EP_Portal is listed as one of the consumers. Therefore, EP_Portal is the name of the consumer, as seen on the producer.
And, where do I specify the P4 port? There is not property for the consumer PCD entry - the only port number I can specify is the external network port, which is in this case 52000 (for the BI Portal).
The only other port number I can set is in the URL of the Consumer. The web dispatcher is running on the consumer, so the url does not specify a port number.
Are you saying that this URL should point at the P4 port on the consumer?

Delta links on applying patches/upgrade.

Hi,
I have a basic question. What happens on applying patch/upgrade to the delta linked copies, when the source objects have been updated/upgraded with new SAP changes.
Will the delta linked object properties get over written by new upgraded (or SAP patches) source objects.
I have made delta links of the SAP delivered WPC IView container objects and using them in the custom pages. Lets say on applying a patch or upgrade, the orginal source objects are changed. Will those changes undo my changes on target delta linked objects.

Hi,
Copying to your namespace is possible but by that you loose all the advantages in the delta-link.
What exactly are you copying Roles, iView, Pages everything?
Adding additional delta link layer between the roles and SAP content is a wise step but copying everything will only dupplicate content and will not allow you upgrade safty with SAP features.
Regards, Elisha
PCD Team Leader
SAP

Federated Portal Remove Delta Links

I have two portals running Netweaver 04S running SP10. I have them up as a federated portal. I cannot however copy items as remote delta links in the Portal Content Catalog. I can do a regular copy but not the delta link. What am I missing? I am at SP 10. Thanks

Lee,
Do you mean that you used "Copy" from the producer portal's PCD and "Paste as Local Content" on the consumer portal's PCD? That's what I do, but I'm receiving a "string out of bounds: 7" error on all URL iViews copied this way. The iView previews just fine on the producer, but gives this error when previewed on the consumer.

UWL - delta linked copy of iView

Similar Messages

Maybe you are looking for