Hi All,
We have two portals and on different versions.(one is 7.0 and the other is 7.3)
We have our applications deployed on 7.3 portal.
Users will be given access to 7.0 portal from which they has to get connected to 7.3 and access the applications.
As of now we have users only in 7.0 portal.
Has any one configured FPN between two portals on different versions.
I am planning to go with Content federation: A network comprising two or more portal installations – one functions as the logon portal for all users and the remaining portal installations function as content providers. This allows you to separate application execution and rendering from the main portal server.
Could you please help me with ur experience which would be the best approach to achieve this scenario.
I am confused which portal feature will be the best to achieve my scenario from the below.
list of the portal features used to implement a federated portal network:
Single user persistence | All portals in the federation connect to a global user repository. |
Assign users and groups to remote roles | - User administrators on a consumer portal can search for and assign users to roles on a remote portal (producer).
- The role is executed on the remote producer portal at runtime.
- The remote roles are defined, configured, and maintained solely on a producer portal, thereby minimizing content maintenance by the consumer.
|
Create content as remote delta links | - Content administrators on a consumer portal can browse the Portal Catalog of a producer portal, and then create remote delta links to iViews, pages, worksets, and roles residing on the producer portal.
- The remote delta link content can be reused and customized locally on the consumer portal, while maintaining the ability to keep unmodified content synchronized with their source objects on the remote producer portal.
|
WSRP-based application sharing | - Content administrators on an SAP NetWeaver consumer portal can integrate WSRP portlets from remote non-SAP portals into SAP NetWeaver Portal.
- SAP NetWeaver developers can create WSRP compliant iViews that can be consumed in non-SAP consumer portals.
|
| Dedicated caching | A portal-based caching service for the federated portal scenario can be used to reduce network traffic by storing semantic objects on the consumer portal for reuse. |
Consistent user experience | - End users can personalize remote iViews the same way they personalize local iViews, for example, configuring iView properties.
- End users can personalize remote pages in a manner similar to the way they personalize local pages, for example, removing iViews from a page and changing the page layout. In some cases, limitations apply.
- Users on the consumer portal can personalize themes and languages.
- The portal look-and-feel can be consistent for all integrated content.
|
Regards,
Eswari