Skip to Content
avatar image
Former Member

Migration of Producer Content

Hi all, I was wandering if anyone could help on this one, I have done a bit
of digging around but can’t seem to find anything, we currently run a Federated
Portal Landscape for BI and Portal, also on our portal we run SRM. We are decommissioning
our SRM system very soon, so will be left with two portals just for our BW
content. This I feel in terms of overhead and maintenance etc is going to be
over kill, so I was wandering if there was any way without having to re-create
it all, to migrate all of our federated content from the producer portal, to
the consumer portal as local content not federated, we could then go through
the process of turning the federated network off.

Is this possible?? Has anyone done anything like this before?? Any pit falls
or things to watch out for that someone may help me able to help with

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Jan 28, 2015 at 08:06 AM

    Dear Dave,

    Considering whether to use FPN is the correct approach.

    It should be used only in certain scenarios due to the overhead in managing remote content, and performance implications.

    FPN influences on the infrastructure of the whole portal, and that is why it should be used only on special business cases where it is really needed.

    More details can be found under:

    Content Sharing with SAP NetWeaver Portal

    Regarding your question, of course maintaining one portal is easier than two, and without the overhead of the FPN, but you didn't specify the versions of the two portals.

    Are they on the same version? What is the content that is being used on the producer portal? Are those business packages? Or just Application Integration iViews?

    For business packages, many times there are new packages for the new versions, that replace the old ones, so it might be that exporting and importing the content will not be supported.

    If those are just AI (Application Integration) iViews, then you can just define the system landscape object on the consumer, and connect directly to the backend system (BW).

    (make your consumer a BI portal)

    Another option is to consume the iViews from the producer via the "consuming content from remote resource" – it will create special AI iViews that know to consume remote iViews from remote portals, without the overhead of the FPN.

    It is explained in the document I referred to.

    Thanks & regards,

    Michal

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Michal Zilcha-Lang

      That is brilliant thankyou very much, I didn't realise the transport would work from producer to consumer like that, but that is exactly what I was after. Thank you very much you have saved me weeks having to re-create content.