Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 9069

Re: FPN between two NW 7.31 SP16 PO Systems

$
0
0

Dear Venkat,

 

 

Basically there are few options – in FPN you have the Remote Delta Link (RDL) for remote content that is not iView nor a role, and Remote Role Assignment (RRA) to assign remote roles.

In case you want to consume remote iViews, then you can use the iView from Remote Source, without the overhead of FPN.

 

Regarding using remote content differently –

It is done by creating iView from remote source from the Portal Content of the Content Administration.

There are 4 options in the wizard, and one of them is creating iView from remote portal.

The remote portal is configured by creating just a system landscape object, with the host and portal of the producer.

Please refer to the relevant documentation that explains it:

http://help.sap.com/saphelp_nw74/helpdata/en/4b/8d080d231e2b5fe10000000a42189c/frameset.htm

 

The relevant part is "iView based on a remote portal component".

This option requires to create a system landscape object, with the WAS parameters (like host & port) of the remote portal.

As written in the documentation:

 

·        It is necessary to create a portal system object on the local portal that points to the application (remote) portal. No specific system type is recommended but the system must have Web Application Server (Web AS) properties, such as an SAP system with load balancing or an SAP system using a dedicated application server.

The following system properties must be configured:

o   Web AS host and port

o   Web AS protocol

o   System alias

 

A wiki page that explains how to extract those parameters:

http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=316769602

 

There is also a troubleshooting guide for this wizard:

http://scn.sap.com/community/enterprise-portal/blog/2014/01/02/creating-iviews-from-remote-sources-troubleshooting-guide

 

Again, using the above approach is relevant when consuming remote iViews.

It is recommended many times because of the overhead of using FPN (performance, configuration, TCO, etc.).

Examples for overhead: the maintenance of connections, the need to synchronize when remote content changes, etc.

 

More information can be found here: http://scn.sap.com/docs/DOC-7179

 

Please refer also to SAP note 1398273 - Federated Portal Network (FPN) - Specific Component Note.

In includes all the relevant information about the different usage types, and their prerequisites and limitations.

 

Thanks & regards,

Michal Zilcha-Lang


Viewing all articles
Browse latest Browse all 9069

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>