Show TOC

Running the UWL in the Producer PortalLocate this document in the navigation structure

Use

If the UWL runs in the producer portals you have two ways to provide the UWL in the consumer portal.

  • Using remote role assignment mode

  • Using remote delta link mode

Procedure

Depending on how you make the UWL available in the consumer portal, you have to execute several steps and consider some restrictions.

Remote Role Assignment

The UWL runs in the producer portals and is available to the consumer portal via remote role assignment . Local roles are configured in and owned by each producer portal. The roles are then assigned to users in the consumer portal using remote role assignment .

More information: 'Remote Role Assignment' Mode

The following figure shows the connection between the consumer portal and the producer portal and also the back-end systems, for example customer relationship management (CRM):

Restrictions

  • A central UWL is not possible.

    In the consumer portal you see two different UWL screens: Start of the navigation path home  Next navigation step work/UWL1 End of the navigation path and Start of the navigation path home Next navigation step work/UWL2 End of the navigation path. Collaboration tasks created in the UWL under Start of the navigation path home Next navigation step work/UWL1 End of the navigation path are visible in work/UWL 1 only. Collaboration tasks created in the UWL under Start of the navigation path home Next navigation step work/UWL2 End of the navigation path are visible in work/UWL 2 only.

  • Collaboration between producers is not possible. Collaboration tasks are stored in different producers depending on where they are created.

    There is no remote connectivity. We recommend running only one UWL in the federation. That means the UWL runs in only one of the producer portals.

  • It is not necessary to deal with configurations, firewalls, or item launching.

Remote Delta Link

The UWL runs in the producer portals and is available to the consumer portal via remote delta links .

More information: 'Remote Delta Link' Mode

Using this content usage mode, a content administrator for a consumer portal can create delta links to content objects (iViews, pages, worksets, and roles) residing in a remote producer portal.

  1. For all iViews and portal pages that have to be launched, create remote delta links from all producers to the consumer.

    This enables automatic remote launching of these iViews and portal pages.

  2. For the UWL, create iViews (AppIntegrator iView wrappers) from all producers to the consumer.

    This enables automatic remote launching of the SAP applications. The system in the System property is looked up in the producers.

    More information about the Application Integrator: Working with the Application Integrator

  3. If the UWL launcher's iViews are linked by remote delta link to a location other than from the default location ( portal_content/every_user/general/uwl/ ), then copy the iView wrapper for the Web Dynpro launcher for Java to the same location in the producer.

  4. If producers run different versions of the same application, the iViews or portal pages to be launched can have the same IDs in several producers. In this case, you must create the remote delta link of the conflicting iViews or portal pages manually.

    Since item types are configured to launch iViews or portal pages, the iViews and portal pages are configured against an iView ID or a portal page ID. This requires a manual change in the configuration XML file.

    More information: Running UWL in the Consumer Portal → 2. Copying iViews and Portal Pages by Remote Delta Link

  5. If more than one producer is running the UWL, you create the remote delta links of the launcher iViews at different locations in the consumer. You have to do this manually.

    Configure the UWL whose launcher iViews are linked to a location other than the original location, to look for this new location.

The following figure shows the connection between the consumer portal and the producer portal and also the back-end systems, for example customer relationship management (CRM):

Restrictions

  • A central UWL is not possible.

    In the consumer portal is one remote iView. That means there is one UWL for each producer UWL.

  • Collaboration between producers is not possible. Collaboration tasks are stored in different producers depending on where they are created.

    There is no remote connectivity. We recommend running only one UWL in the federation. That means the UWL runs in only one of the producer portals.

  • Conflicting iViews and portal pages.