Changing a delta link

I have an iview, delta linked from a SAP Transaction iView template. Now the customer has decided that, for all their transaction iViews, they would like to use a different template. Is it possible to create a new template and switch the delta linked content behind the object?
Re-creating is not an option because we are talking of hundreds of objects.
Thank you
Sigi

Hi Sigi,
No, that won't be possible. The other template which should be used - is it based on the same component? If yes, why not changing the parameters on the template iView?
On the other hand, recreating the iViews as delta links from a different template iView (and deleting the existing delta links) shouldn't be that hard when doing it programatically (with respect to this, you are in the right forum ).
Hope ti helps
Detlev

Similar Messages

Role upload does not change the delta links

Hi,
We are using the Role upload functionality in the portal to upload BW roles by selecting the "Convert roles to worksets" and "Overwrite existing content" options.
The newly created workset (corresponding to the uploaded role) is then copied and pasted as a delta link in another folder.
We upload the BW role again whenever some changes are made to the original BW role (such as addition/deletion of reports).
However, these changes are not getting reflected in the delta link (although the delta link dependency still exists).
Does delta link work only for manual deletion/addition of portal content and the changes do not filter through using a role upload with overwrite?
It is definitely not working for us using the role upload functionality and It seems that overwriting content using role upload does not impact the associated delta links.
Any solution/workaround to this issue would be greatly appreciated.
Regards,
Vibhu

Hi Vibhu,
> Good to hear from you after such a long time
Yeah, I didn't had that much time the last months, but at the moment, I'm trying to be back a bit
> We investigated the problem further and found that it is only the deletions to a
> BW role in the backend that do not get reflected in the delta link.
>
> The additions work fine.
> It is defintely a bug.
So it's up to SAP to fix it - and you could mark the thread as closed?!
Best regards
Detlev

Remote Delta link setup problem with Bean / Access Service

Hello,
I am trying to setup Remote Delta Link (RDL) between two portals. (Both portals same version - EP 7.0 EHP1 SP 05 - are in the same domain)
I already have the Remote Role Assignment working without any issues.
The following have been done successfully:
1. Same user repository has been setup for both the portals
2. Setup trust between producer and consumer (SSO working fine)
3. Producer added and registered succesfully on consumer
4. Permissions setup on producer and consumer
4. pcd_service user with required UME actions setup
I am able to see all the remote content in the Consumer portal.
When I try to copy the remote content and paste it as local content, I am getting the following error:
Could not create remote delta link to object 'page id'. Could not connect to the remote portal. The remote portal may be down, there may be a network problem, or your connection settings to the remote portal may be configured incorrectly.
After increasing the log severity, I am able to see the following in Default Trace:
com.sap.portal.fpn.transport.Trying to lookup access service (P4-RMI) for connecting to producer 'ess_int' with information: com.sap.portal.fpn.remote.AccessServiceInformation@31c92207[connectionURL=hostname.mycompany.com:50004, shouldUseSSL=false, RemoteName=AccessService]
com.sap.portal.fpn.transport.Unable to lookup access service (P4-RMI) with information: com.sap.portal.fpn.remote.AccessServiceInformation@31c92207[connectionURL=hostname.mycompany.com:50004, shouldUseSSL=false, RemoteName=AccessService]
AbstractAdvancedOperation.handleDirOperationException
[EXCEPTION]
com.sap.portal.pcm.admin.exceptions.DirOperationFailedException: Could not retrieve the bean / access service to connect with producer
Could not retrieve the bean / access service to connect with producer
Like you can see above, there is some bean / access service which is not retrieved successfully. I am not sure if this is a permission problem on the consumer.
I have checked that the P4 ports are configured correctly (standard - not changed) and I am able to telnet from producer to consumer (and vice versa) on the P4 port.
I am stuck at this point and am not able to find any information on this.
I would really appreciate if some one can point me in the right direction.
Thank you for reading.
- Raj

Hi Raj,
Please check your config of the P4 port on the producer. Is it really 50004 (check SystemInfo of the producer)?
I do think there's a problem with the P4 communication since RDL requires P4 connection.
Do you have load balanced consumer-producer connection? Please refer to this blog for further details
Little known ways to create a load balanced Consumer Producer connection in a FPN scenario
Regards,
Dao

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

FPN Could not create remote delta link

Hi everybody,
I am trying to create a Remote Delta Link from producer content (EP Version 7.0 SP11) to consumer (EP Version 7.0 SP14).
I have achieved the following FPN settings/configuration:
SSO Connection in both direction
Connection test is done successfully
Producer registration done successfully
The user is existing in both portals (Producer and Consumer)
But unfortunately I am receiving the following RDL copy and paste error message:
*Could not create remote delta link
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.*
The producer is running.
There are no network problem
and the setting are correct.
Any replay is welcome.
Kind regards,
Rashid
Edited by: Rashid Salem on Aug 25, 2008 4:35 PM
Edited by: Rashid Salem on Aug 25, 2008 4:37 PM

Hi Sascha,
no, there was no changes on the P4 Ports.
The producer and consumer P4 Ports are configured as default ports. Producer P4 Port: 50004 and Consumer P4 Port: 51004.
And if the P4 ports have been changed there is a possibility to enter the P4 Ports values in both Producer and consumer portals:
System Administration > System Configuration > Service Configuration >Applications > ProducerInformationService > Alias To Ports
I tried also this way/possibility without any success ;-(
Any idea how to solve the issue?
Kind regards,
Rashid
Edited by: Rashid Salem on Aug 25, 2008 5:00 PM

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...

Validating that delta links are used

Hi there
In our current project, we have a number of workbenches which have to be delivered as part of the Enterprise Portal solution. Each workbench comprises a number of roles that are merged in various manners to create the navigation.
The iviews that are assigned to the roles are only created once, and are supposed to be assigned to the roles using delta links.
However, I have found in the last few days that some iviews have not been linked with delta-link as changing the source files hasn't necessarily changed the iview in the role.
Is there a relatively painless way of checking that the iviews are inserted as delta-links and not copies?
I have thought about going through each role and checking either with the Delta Link Tracer or just re-assigning the iview as delta-link, but that could be a lengthy process, and I am looking for something a bit easier than that.
Any ideas?
Cheers,
Andrew

Hi Andrew,
If you are on NW04 SP13 or higher, there is an easy way out. Use the support platform to check your broken delta links.
Check these
Support Platform II: Reports for Portal Administrators
and
https://www.sdn.sap.com/irj/sdn/developerareas/?rid=/webcontent/uuid/a232f867-0c01-0010-fd88-f82e0e264bb5
Akhilesh

Reverting delta links?

Hi All,
I made a delta link of an standard SAP PCD object(X) into my local workspace (Y) and then edited only one property of that delta linked object (Y). so now i could see a sybmol "#" beside that delta linked object(Y). which means that there is some change from the original one (X).Now I want to revert this to the properties of original. I changed that property back to the orignal. but still i see "#" beside my PCD object.
Is there soem tool available such as delta link comparator..which compares two delta link objects and show the differences between them..i.e. properties changed from the original
Thank you

I think what you want is to reset the Property
If you want to do so, you have to "expand" the Property (small black triangle at the left of a Property on the Properties Panel) and then click on the Reset button. This will return the Property to the source value (and remove the "#" symbol)
You can also do the same for the entire object with the "Reset Node" button
As far as I know, there is no option to do it 'massively' in the Multiple Property Replacement functionality.
Let me know if you find it !

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.

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

Delta-links not updated

Hi
We have created some delta-links between uploaded roles, but the delta-links are not updated when changes are made to the source object.
How are delta-links updated? Is it a service running in intervals? If yes, how can I access the service to see if it is running, restart it or change the interval?
Any help is appreciated
Kind regards
Morten Ellgaard

We are on SPS13, and I think something has changed. The documentation only refers to remote delta-links, but we do not use federated portal. I am pretty shure that I have seen a delta-link update service in a previous version, but now it is gone / I can't find it.

Remote Delta Link vs Direct Link - Federated Portal

Hi, We couldn't get our Remote Delta Links to work on our Enterprise Portal so we just built a direct link to our IViews. This link goes through the Enterprise Portal and to the IView on the BI Portal. (Points to the Producer on the Consumer) This works great. My only question is if I can build a direct link to my IViews what is the benefit of Remote Delta Links that became available as of SPS10? Just a shorter link?
Thanks!

Yes it is a 'shorter' link doing it direct, however it is more flexible to use a remote delta link (when making changes). You also get the benefit of user personalisations being attached to the view on the consumer portal (rather than the producer). Its slightly cleaner when it comes from transporting or cloning a whole PCD as well. Thats is my basic understanding anyway

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

Delta Linked object: reset attribute to inherit from parent

Hi all,
I inherited an ESS system where the SAP content had changes made to it. The SAP supplied Employee Self-Service Role had some of the worksets set to Invisible in Navigation Areas. I would like to clear the indicator that says that attribute is defined locally and have it back to inherit from parent. Then I can make the Invisible change in the delta linked role in our custom content folder.
Is this possible without a program?
Thanks
--Amy Smith
--Haworth

Hi Gopal,
That would seem to make sense to me too. I have one question about that that you may be able to help with.
The role I am working with is a delta linked role that points back to the ESS role. I can remove a workset from my delta linked role. Later we will want to put that workset back in the role.
I can link it in pointing to the ESS workset, but the delta link trace will look different and anything done in the ESS role to that workset will not be reflected in my custom role. So is there a way to tell my delta linked role to undelete the workset so it is still linked back to the ESS role.
Does this make any sense?
--Amy Smith
--Haworth

Changing a delta link

Similar Messages

Maybe you are looking for