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

Similar Messages

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

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

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

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?

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

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

Transporting Remote Delta Links--Primary versus Producer Alias

I am having difficultly transporting iViews that are Remote Delta Links. In the target consumer portal, the delta links iviews import as broken. According to the SAP documentation, an indentical "producer alias" must be created in the source and target consumer portals.
Currently, I have created the producers in the consumer with specific instance names. Specifically, in my consumer DEV portal, the producer is created as "BWDEV". In my consumer QC portal, the producer is created as "BWQC". As a result, SAP created a "primary alias" of "BWDEV" and "BWQC" in DEV and QC, respectively.
My question is this:
Are the "producer alias" and the "primary alias" two names for the same object? A "primary alias" is automatically created when the producer is created, and it matches the name of the producer entered. In order to transport this content, do I need to create my producers with generic (non-instance) names such as "BW"?
Thanks,
Kevin

Hi Kevin.
Are the "producer alias" and the "primary alias" two names for the same object?
Generally speaking, it is true. You can create additional aliases, but only when instructed to do so in the documentation or by an SAP support person (additional aliases are currently intended for internal SAP usage). Thus for a customer "producer alias" means "primary alias".
A "primary alias" is automatically created when the producer is created, and it matches the name of the producer entered.
It matches the producer ID if the alias is not already used by another system in your portal (refer to [help.sap.com|http://help.sap.com/saphelp_nw70/helpdata/en/43/2280c70d21400ee10000000a11466f/frameset.htm])
In order to transport this content, do I need to create my producers with generic (non-instance) names such as "BW"?
Yes, for sure.
Best regards,
Aliaksandr Zhukau

Not able to create Remote Delta Link from Producer content to Consumer.

Hi everybody,
I am trying to create a Remote Delta Link from producer content (EP Version 7.0 SP15) to consumer (EP Version 7.0 SP15).
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.
Regards,
Nagaraju

Hi Nagaraju,
did you solve this problem? I get the same error message and no hints in the log/trace files in both portals.
Kind regards
Gerd

Federation: Remote role assignment vs Remote delta link

does anyone know whats the difference on what percentage of load falls on the Consumer portal and what percentage of load on producer between federation via remote role assignment and via remote delta link
which way is better?

Hi,
Basically the load differences between RRA and RDL on the consumer and producer is not a good way to look at it. Technically all the load to run the content and render it is done on the producer portal and the producer portal just has to display the content in either case.
As to which one is better, it depends on what you want to do. RRA only works with roles. If you have roles already created on you producer portal and you just want to use them as is on the consumer portal then RRA is the way to go. But if you only want to use iViews or pages from the producer then you have use RDL. (or remote application integration)
You can of course use both if you want. You don't have to use only one so use the ne that meets you need the best.
Hope this helps,
John

Problem with file access in other computer in jsp

I have problem with file accessing in other computer in jsp.
The follow code
File folder=new File("Z:"+File.separator+"sharefolder");//Z is a net share driver
File[] files=folder.listFiles();
System.out.println("test");
System.out.println("length="+files.length);
will throw exception at the second print.
but it works well in main funtion.
Is anybody know what is the problem.
JSP works on windows2003 server,tomcat 5.0.28 JDK1.4 net share folder on windows2000 server

no error code for this.But when I start tomcat I get the follow error.
java.lang.IllegalArgumentException: Document base Z:\ does not exist or is not a readable directory
     at org.apache.naming.resources.FileDirContext.setDocBase(FileDirContext.java:138)
     at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:3910)
     at org.apache.catalina.core.StandardContext.start(StandardContext.java:4138)
     at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:823)
     at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807)
     at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595)
     at org.apache.catalina.core.StandardHostDeployer.addChild(StandardHostDeployer.java:903)
     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:585)
     at org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java:216)
     at org.apache.commons.digester.SetNextRule.end(SetNextRule.java:256)
     at org.apache.commons.digester.Rule.end(Rule.java:276)
     at org.apache.commons.digester.Digester.endElement(Digester.java:1058)
     at org.apache.catalina.util.CatalinaDigester.endElement(CatalinaDigester.java:76)
     at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
     at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source)
     at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
     at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
     at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
     at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
     at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
     at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
     at org.apache.commons.digester.Digester.parse(Digester.java:1567)
     at org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:488)
     at org.apache.catalina.core.StandardHost.install(StandardHost.java:863)
     at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:483)
     at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:427)
     at org.apache.catalina.startup.HostConfig.start(HostConfig.java:983)
     at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:349)
     at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
     at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1091)
     at org.apache.catalina.core.StandardHost.start(StandardHost.java:789)
     at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083)
     at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478)
     at org.apache.catalina.core.StandardService.start(StandardService.java:480)
     at org.apache.catalina.core.StandardServer.start(StandardServer.java:2313)
     at org.apache.catalina.startup.Catalina.start(Catalina.java:556)
     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:585)
     at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287)
     at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425)
Jun 5, 2006 6:55:41 PM org.apache.catalina.core.StandardContext start
SEVERE: Error in resourceStart()
Jun 5, 2006 6:55:41 PM org.apache.catalina.core.StandardContext start
SEVERE: Error getConfigured
Jun 5, 2006 6:55:41 PM org.apache.catalina.core.StandardContext start
SEVERE: Context startup failed due to previous errors
Jun 5, 2006 6:55:41 PM org.apache.catalina.core.StandardContext start
SEVERE: Exception during cleanup after start failed
LifecycleException: Container StandardContext[msgstore] has not been started
     at org.apache.catalina.core.StandardContext.stop(StandardContext.java:4466)
     at org.apache.catalina.core.StandardContext.start(StandardContext.java:4371)
     at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:823)
     at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807)
     at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595)
     at org.apache.catalina.core.StandardHostDeployer.addChild(StandardHostDeployer.java:903)
     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:585)
     at org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java:216)
     at org.apache.commons.digester.SetNextRule.end(SetNextRule.java:256)
     at org.apache.commons.digester.Rule.end(Rule.java:276)
     at org.apache.commons.digester.Digester.endElement(Digester.java:1058)
     at org.apache.catalina.util.CatalinaDigester.endElement(CatalinaDigester.java:76)
     at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
     at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source)
     at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
     at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
     at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
     at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
     at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
     at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
     at org.apache.commons.digester.Digester.parse(Digester.java:1567)
     at org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:488)
     at org.apache.catalina.core.StandardHost.install(StandardHost.java:863)
     at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:483)
     at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:427)
     at org.apache.catalina.startup.HostConfig.start(HostConfig.java:983)
     at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:349)
     at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
     at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1091)
     at org.apache.catalina.core.StandardHost.start(StandardHost.java:789)
     at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083)
     at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478)
     at org.apache.catalina.core.StandardService.start(StandardService.java:480)
     at org.apache.catalina.core.StandardServer.start(StandardServer.java:2313)
     at org.apache.catalina.startup.Catalina.start(Catalina.java:556)
     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:585)
     at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287)

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

BI reports not getting opened using remote delta link in local pcd.

Hi All,
I have connected BI to portal and the BI reports are working fine in BI but when i copy the reports in the local pcd using remote delta links it is showing the error "500 internal server error" and no esid found.
Thanks & Regards
Mary.

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

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

Remote Delta link setup problem with Bean / Access Service

Similar Messages

Maybe you are looking for