Exception due to UWL trying to access all the systems in the landscape.

Question

Hello everyone!
We have a problem with UWL in all our environments.
When a user is trying to see his tasks, an error appears at the top of the screen at the end of the update: u201CAn error occurred while trying to connect to the provideru201D.
This happens because the UWL is trying to establish a connection with all the backend systems in the landscape including the ones that the end user has no username in.
Because of that, the SSO fails to this backend system & we get this error.
My question is: how do I limit UWL to access only the relevant systems?
Thanks,
Yoav Zilberman

Answer 1

Hi Yoav ,
Its very easy to solve your problem.
First i would like to explain the your scenario .. so you can get the correct idea of what you need to
do for your problem.
Suppose there are
2 user called UA and UB
2 Roles RA and RB
2 Back-end System SA and SB
Let SA is accessing R3 system and SB is accessing SRM System.
User UA is having SA access and User UB is having SB system access.
Role RA is having  iviews for SA and Role RB is having iviews for SB Syetem
Role RA assigned to user UA and Role RB is assigned to user UB
So in your case when user UA is seeing his UWL he will be getting error for SB system and
UB will be getting erorr for SA system.
I hope you are getting same error ... explained above ..........???????
Now Solution
Now to solve the issue you need to edit the  Registered Universal Worklist Systems .
Go to the Universal Worklist - Administration from System Administration->System Configuration
Now select your desired registered System Alias and click edit button
now you will see below mentioned attributes
System Alias: * 
Connector Type: *  
Web Dynpro Launch System: 
User Roles: 
System Configuration Groups: 
Delta Pull Channel Refresh Period (in Seconds): 
Delta Pull Channel Snapshot Refresh Period (in Minutes):
In above mentioned Attributes ... go to User Roles: and for SA Alias in User Roles type RA
and for SB Alias in User Roles type RB.
That's all.... your problem solved .. just clear the cache and test.
How It works
From Above case SA Alias will run only for users/groups those who are having RA role same as
SB Alias will run only for those who are having RB role.
So in your case when user UA will log-in only SA will get activated not SB so user will not see any errors
for SB System.
Regards,
Piyush