topic Re: UWL refresh issue in Application Development and Automation Discussions

UWL refresh issue

Former Member — Wed, 19 Nov 2014 13:00:09 GMT

Hi Experts,

We have a UWL implemented in our SAP EP 7.31 portal.

It fetches work items from a back end system which is connected by a RFC destination.

It is seen that users have to hit the refresh button in UWL more than once to get the actual list.

When I checked the logs, found the following connectivity error to back end system:

com.sap.portal.connectivity.destinations.PortalDestinationsServiceException: Could not get connection for alias PXXCLNTXXX. Contact your system administrator.

at com.sap.portal.connectivity.destinations.portal.PortalSystemLandscapeSource.getConnectionWithOverridingProps(PortalSystemLandscapeSource.java:123)

at com.sap.portal.connectivity.destinations.impl.DestinationServiceImpl.getConnection(DestinationServiceImpl.java:261)

at com.sap.portal.connectivity.destinations.DestinationsService.getConnection(DestinationsService.java:122)

at com.sap.netweaver.bc.uwl.utils.r3.Transaction.begin(Transaction.java:112)

at com.sap.netweaver.bc.uwl.utils.r3.Transaction.createInput(Transaction.java:216)

at com.sap.netweaver.bc.uwl.core.connect.webflow.R3SubstitutionManager.getAllSubstitutions(R3SubstitutionManager.java:120)

at com.sap.netweaver.bc.uwl.core.SubstitutionCheckThread$1.run(SubstitutionCheckThread.java:51)

at com.sap.netweaver.bc.uwl.core.SubstitutionCheckThread$1.run(SubstitutionCheckThread.java:40)

at java.security.AccessController.doPrivileged(Native Method)

at javax.security.auth.Subject.doAs(Subject.java:337)

at com.sap.netweaver.bc.uwl.core.SubstitutionCheckThread.run(SubstitutionCheckThread.java:40)

at com.sap.netweaver.bc.uwl.core.ThreadManager$PoolWorker.run(ThreadManager.java:209)

Caused by: com.sapportals.connector.connection.ConnectionFailedException: Connection Failed: A nested exception occurred. Could not initialize physical connection.

at com.sapportals.connectors.SAPCFConnector.SAPConnectorException.getNewConnectionFailedLocalizedException(SAPConnectorException.java:182)

at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnectionFactory.createManagedConnection(SAPCFConnectorManagedConnectionFactory.java:155)

at com.sap.engine.services.connector.jca.ConnectionHashSet.match(ConnectionHashSet.java:401)

at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:295)

at com.sap.engine.services.connector.jca.ShareableConnectionManager.allocateConnection(ShareableConnectionManager.java:54)

But when I pinged the destination, it shows successful connection established.

Is there any option that I could try.

Regards, Biswajit.

Re: UWL refresh issue

troy_cronin2 — Wed, 19 Nov 2014 13:52:58 GMT

Dear Biswajit

I hope you are well and many thanks for using the SAP Discussion Forums .

Now in relation to the scenario that you have described you mentioned the following:

You have the UWL implemented in your SAP EP 7.31 portal.
It fetches work items from a back end system which is connected by a RFC destination.
It is seen that users have to hit the refresh button in UWL more than once to get the actual list.

Now regarding the exception you are recieving we can clearly see the following:

connectivity.destinations.PortalDestinationsServiceException: Could not get connection for alias PXXCLNTXXX. Contact your system administrator.

Based on this exception there are several avenues of analysis that we can follow:

In scenarios like this when we see such a message what may be causing it is a misconfiguration/misalignment with regards to the UWL and destination setups.

Kindly view and implement the following note:

SAP Note 1133821 - UWL Destination Service Configuration

In addition to the possibility of a misconfiguratin we can also consider checking the system alias and the connector setups themselves.Kindly implement the note number outlined above and also view the two documentation links provided below as they provide a detailed overview on the correct settings and configurations.

- Check that after applying Note 1133821 the destination names and the UWL connector names exactly match, even considering case-sensitiveness. If your portal system alias (=UWL connector name) is for example XYZCLNT100, then the rfc destination name should be exactly XYZCLNT100$WebFlowConnector. Please correct the rfc destination accordingly. (If Required)

1: If you make changes kindly restart the Portal Cluster

2: Clear the UWL Cache/Restart the UWL service

Now retest, are you still encountering the issue?

Kindly update me as per your findings.

I greatly appreciate your time and patience and I look forward to recieving your reply.

Kind Regards

Troy Cronin - Enterprise Portal Support Engineer

Re: UWL refresh issue

Former Member — Wed, 19 Nov 2014 14:00:05 GMT

Hi Troy,

Actually the refresh issue happens with a few users only. It works fine for others.

The log trace is fetched for one of those users.

If you still insist that RFC configuration is incorrect, I would look into your suggestion and let you know.

Regards, Biswajit.

Re: UWL refresh issue

Former Member — Wed, 19 Nov 2014 14:07:25 GMT

Hi Biswajit,

You can look up below the link ;

(UWL)Completed tasks disappear only after a refresh of UWL cache - Technology Troubleshooting Guide - SCN Wiki

Regards

Özgün

Re: UWL refresh issue

troy_cronin2 — Wed, 19 Nov 2014 14:09:45 GMT

Dear Biswajit.

Many thanks for the response and update.

Regarding the observation of the traces I recommend and suggest reviewing the RFC configurations as based upon the exception there is a discrepancy. I've come across issues like this many times before.

Regarding the refresh from a general perspective let us remember the baseline through which it functions and how the smallest discrepancy can obstruct this core functionality.

Firstly upon the initial loading of the UWL it takes a total of 5 minutes for all tasks to be loaded in.

The behaviour is completely normal. The UWL works using two Pull operations. Firstly tasks are pulled
from the backend into the UWL cache. They are pulled a second time from the cache into the UWL User Interface. Due to thisarchitecture there is an inherent delay in the automatic refreshes
of the UWL. There is no way, in the current architecture that the UWL can refresh instantaneously.

This is upon inital load as the cache must be built first upon logon so there will always be a delay. Real time refresh in the latest versions, is only when you complete a task.

Kindly let me know how you get on.

Cheers

Troy Cronin - Enterprise Portal Support Engineer

Re: UWL refresh issue

Former Member — Wed, 19 Nov 2014 14:20:29 GMT

Hi Troy,

Thanks for the detailed explanation, really good info.

Now if I input "Delta Pull Channel Refresh Period (in Seconds):" as 60 (at present it is blank), will the first time load be vulnerable or will it have no effect; considering the default 5 minutes time that you mentioned.

Regards, Biswajit.

Re: UWL refresh issue

Former Member — Sat, 22 Nov 2014 06:20:27 GMT

Hi Biswajit,

Please try this setting :

In the portal, navigate to System Administration System Configuration Universal Worklist and Workflow Universal Worklist Administration .
Select the New button to configure the connector. Enter the system alias you are using. You can also select an already registered WebflowConnector and choose the Edit button.
From the Connector Type dropdown list, choose WebFlowConnector.
Fill in the configuration details for the connector.
Select the Refresh completed items checkbox.
To define the time period for UWL task list update, enter a number (in seconds) in the Refresh Period for Completed Items (in Seconds) field.

for this setting, you need to give some authorizations to end users :

Authorization object : S_RFC_ADM

Authorization Field ACTVT must have value "01: Create.

Regards,

Sarita