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 !

Similar Messages

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

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

Content Transport with Remote Delta Links

Hi Folks,
we using Federated Portal mechanism for building ESS scenarios (producer) in an SAP Intranet Portal (consumer).
The Federation integration works fine (with known ......), we are using remote delta links. Now we try to transport from the development consumer portal (connected to the development producer portal) the content with normal transport packages to the consumer test portal (connected with the producer test portal). But the remote delta links from the consumer development portal are not transported to the consumer test portal !
We can´t use the same producer Alias like describe in http://help.sap.com/saphelp_nw04s/helpdata/de/43/2280c70d21400ee10000000a11466f/content.htm
why the producer portal connected to the consumer test portal is the producer test portal! This have different alias names, because these are different portals !
Is there any possibility to use the transport for remote delta links via using different producer portals ?
THX
mario

Hi Lakshmi,
Have you updated your consumer and producer with the latest patches from SMP?
Please switch on the traces of the following components to DEBUG severity in the visual admin, re-run the scenario and look for an error in the default trace of the server and dispatcher (consumer and producer).
Dispatcher -> Services -> Log configurator -> Locations (Tab) and then navigate to :com -> sap -> engine -> services -> rmi_p4
and
Server -> Services -> Log configurator -> Locations(Tab) and then navigate to :com -> sap -> portal -> fpn -> persistancy , com -> sap -> portal -> fpn -> transport
Regards,
Oren

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

Error when using Broken Delta Links Detector

I am trying to run the Broken Delta Links detector from the support platform. I get the following error:
Tue Nov 07 12:03:01 CET 2006 : java.lang.NullPointerException
     at com.sapportals.utilities.analyzer.plugin.helpers.ContextHelper.getContext(ContextHelper.java:60)
     at com.sapportals.supportplatform.plugins.portal.content.report.BrokenDeltaLinksDetector.analyze(BrokenDeltaLinksDetector.java:142)
     at com.sapportals.utilities.analyzer.PluginManager.analyze(PluginManager.java:281)
     at com.sapportals.utilities.analyzer.PluginManager.run(PluginManager.java:995)
     at java.lang.Thread.run(Thread.java:534)
Portal Version
Value *****
7.0.8.0.0
J2EE version
Value *****
7.00   PatchLevel SP 08
It seems like a required component is missing. Can anyone offer any advice?
Thanks
Andy

Hi Andy,
No, there is no component missing but it's just a "simple" bug. You have two possibilities: Upgrade to SP9 and check if the bug has gone with that, or (or "and" if the bug hasn't gone with SP9, either) open an OSS message.
Hope it helps
Detlev

PCD search for delta links

Hi all,
I'm trying to look for delta link pcd objects in my portal.
I have code that works for iviews, pages, roles & worksets, for example:
NamingEnumeration ne = dirCtx.search("","(com.sap.portal.pcd.gl.ObjectClass=com.sapportals.portal.iview)",
pcdSearchControls);
The following example shows how to read ONE delta link properties::
http://help.sap.com/saphelp_nw04/helpdata/en/44/703fd42043053ce10000000a1553f6/content.htm
I want to run this code for all delta links in the portal.
How to look for ALL delta links by code?
I'm using 7.00.17.
Regards,
Omri

Hi
use our coding to fetch iViews/pages/...
got through them and check wether one is a delta link or not:
If the object is not a delta link or inherited via a delta link, getDlModificationState() returns null.
regards
Johannes

Anyone know how Delta Links are stored in a Clustered environment?

We have a situation where we have a clustered EP6 production environment with 4 servers in the load balancer.
However, we've found that on just one of the servers the Delta Link between one of our roles and its only workset is missing.
Wanted to know if anyone could explain how these delta links are stored and/or what happens during transport import in a clustered environment (e.g. are components deployed only to the central database or deployed to each server in the cluster)?
Thanks for any help/advice on this you can provide.

Hi Steve,
The delta links are stored in the PCD which is common for all nodes in the cluster (there is only one database).
When importing portal content to a cluster it is stored in two locations: one in on the central instance and the other one is locally on the specific node to which it was imported.
All other nodes are informed that there is a new content but will only upload it locally on demand (only when a user is calling this content).
Please award points if you find this answer helpful.
Regards,
Amit.

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

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?

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

FPN and Remote Delta Link

Hello,
We are implementing FPN. We have a consumer portal in NW 7.0 SP15 and a BI-Java producer portal in NW 7.0 SP17.
I would like to know whether it is necessary to have both consumer and producer portal to have the same SP stack in order to use Remote Delta Link scenario ?
Thank you in advance.
The-Hung Nguyen

Hi,
it's not necessary that the producer and consumer have the same SPS. That's one of the advantages of an FPN. Your portals can have different release cycles and SLA's.
Sure, it's good to have both on the same SPS, but it's not necessary. Some functionality won't work, depending on the SPS of the Consumer / Producer, like RAI for BI if the SPS for the BI system simply doesn't know what RAI is (Remote Application Integration).
br,
Tobias

Reverting delta links?

Similar Messages

Maybe you are looking for