Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Launching UWL attachments fails on consumer portal

Hello,

we have discovered an issue, in case the UWL is used in a portal federation scenario. The following scenario fails, if the UWL is used on the consumer portal:

If an attachment from the UWL details dialog is opened on the consumer portal...

... a portal runtime exception is thrown/logged on the consumer.

The exception contains the following error message:

[EXCEPTION]

com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component

Application name : com.sap.portal.appintegrator.sap

Component : pcd:portal_content/every_user/general/uwl/com.sap.netweaver.bc.uwl.uwlSapLaunch

Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent

User : yyyy

[…]

Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unknown system alias.

System Alias:  'xxxx_SAPHR',

User:          'yyyy',

Reason:        System Alias is not defined or permission denied for this user

The exception mentions that no system alias is present. As from the concept of the federation, no system alias needs to be present on the consumer, however on the producer portal. As we try the same scenario on the producer portal, it is possible to launch the attachment object in the backend:

We did some more detailed analysis on the consumer portal and traced the generated request for the attachment link. In the following screenshot you can see the generated parameters when trying to launch the attachment from consumer portal:

So far we have identified that there might be an additional parameter called PrevNavTarget required in order to launch the attachment on consumer portal successful. To verify this, we enhanced the GET request with the missing parameter via the browser's address bar.

PrevNavTarget=gpn://gp:[Federation_Alias_of_Producer]/ROLES://portal_content/[…]

In this case, no exception is thrown and the attachment is opened successfully:

So far we are only able to add this GET parameter manually to the request via the browser's address bar. But how can we add this parameter into the launch URL of the attachment link in the UWL detail dialog?

Best regards

Mario

Tags:
Former Member
Former Member replied

Hello,


we were able to solve the issue. It took us a lot of time in order to investigate this with SAP, thus I would like to share with you the resolution.


We have solved it by overwriting the default configuration of the viewDetail action. The new XML configuration in UWL is derived from SAP default configuration viewDetail as defined in uwl.standard. The new configuration changes only the action attribute launchInNewWindow from yes to SHOW_HEADERLESS_PORTAL. The final action configuration looks like the following:


<Action name="viewDetailTvifWorkaround" groupAction="" handler="SAPWebDynproLauncher" referenceBundle="view_detail" returnToDetailViewAllowed="yes" launchInNewWindow="SHOW_HEADERLESS_PORTAL" launchNewWindowFeatures="width=700,height=600,resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no">

<Properties>

<Property name="excludeActions" value="${excludeActions}" />

<Property name="displayEmptyDisplayAttributes" value="${displayEmptyDisplayAttributes}" />

<Property name="isnewwindow" value="1" />

<Property name="sap_uwl_selecteditem" value="${item.internalId}" />

<Property name="display_order_priority" value="-2" />

<Property name="image" value="icon_detail.gif" />

<Property name="excludeDisplayAttributes" value="${excludeDisplayAttributes}" />

<Property name="WebDynproApplication" value="UWLDetail" />

<Property name="WebDynproDeployableObject" value="sap.com/tc~kmc~bc.uwl.ui~wd_ui" />

<Property name="System" value="SAP_LocalSystem" />

<Property name="excludePreviewSections" value="${excludePreviewSections}" />

</Properties>

</Action>

In order to use the new action viewDetailTvifWorkaround, it needs to be defined in property defaultAction of the ItemType configuration.


<ItemType name="…" ... defaultAction="viewDetailTvifWorkaround">

[…]

<Actions>

<Action reference="viewDetailTvifWorkaround" />

</Actions>

</ItemType>

Best regards

Mario

0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question