Transporting Content 

The standard transport services provided by the portal support content that is shared across portals which are part of a federated portal network. This topic provides information you need to consider when transporting content within a federated portal network.

For general information about transporting portal content, see Transport of Portal Objects.

Remote Role Assignment

In a single-portal environment, the standard transport of roles does not include user assignments. For this reason, when you transport roles that contain remotely assigned users from one producer portal to another producer portal, none of the remote user assignments are carried to the target producer portal.

Therefore, if you transport roles containing remotely assigned users from one producer portal to another, the user administrator on the consumer portal must then manually reassign its users to the same remote roles residing on the new producer portal.

Remote Delta Links

If you are using remote delta links, the standard transport services allow you to move your content from one producer-consumer portal landscape to another, while keeping remote delta links intact on the target producer-consumer portals following the transport.

This is useful for example when using the standard import and export services in the portal to move your content from a development environment to a test environment, and then ultimately to a production environment.  

To achieve this, do the following (see also following figure):

 

Note that steps 1-3 can be done in any order. Step 4 must be done last.

...

       1.      On the consumer portal in the new landscape create a producer object. Ensure the following:

○       The producer object has an identical producer alias to the primary one used by the consumer portal in the original landscape.

When you create a producer portal, the consumer portal automatically generates an alias for the producer from the producer ID you enter in the Producer Wizard. For more information, see Adding NetWeaver Producers and Viewing a Producer Alias.

○       During the registration process, use the identical consumer name as the one defined for the consumer portal in the original landscape.

       2.      Transport (import/export) the content from the source producer portal to the target producer portal in the new landscape.

       3.      Export the content from the source consumer portal.

       4.      Import the content exported from the source consumer portal to the target consumer portal in the new landscape.