Universal Worklist Configuration Problem

Hi,
We are running on EP60 SP2 and we have installed the Workflow component "universal worklist". I see the Universal worklist tab, and when i click it i see
"Unable to perform the request. Please try again. If the problem persists, please inform your system administrator."
I understand that this is the configuration of Portal runtime component
"com.sap.portal.runtime.config.component.ConfigUI"
When i open this iview i see only one configuration
-->Folders
>Portal Application Configuration
I don't see the Universal Worklist configuration under Folders as per the document.Which is used to configure the UWL component with SAP systems.
Can somebody tell what is the problem?
Thank you
arun
Message was edited by: Arun Prasad

Hi Arun,
did you upgrade to patch 27 (EP&KM) before? If yes, did you upgrade to Hotfix 1?
If the first answer is yes and the second is no, then this is the reason.
See note 792995 - Major problems fixed with this Patch 27 Hotfix 1: [...] Config : After upgrading to Portal SP2 Patch 27 the configuration iView did not work.
Hope it helps
Detlev

Similar Messages

Problem in Universal worklist configuration

Hi,
I wnt to register sap system.
i have
Navigated to System Administration  System Configuration  Universal Worklist and Workflow  Universal Worklist - Administration.
Click new button and provided the following details:
System alias : sapr3
Connector type: webflow connector
then i save and clicked on Register button. Then i get the following error message :
Status
Errors:
System SAPR3: Tue Apr 21 17:05:04 GMT+05:30 2009
(Connector) :com.sap.netweaver.bc.uwl.connect.ConnectorException:Tue Apr 21 17:05:04 GMT+05:30 2009
(Connector) :com.sap.mw.jco.JCO$Exception:User RAJU has no RFC authorization for function group SWN_UWL_URL_GEN.
Item type retrieval and registration requires a connection to the systems and may take a couple of minutes
For each system, they are generated as the configuration named 'uwl.webflow.<system_alias>' or 'uwl.alert.<system_alias>'.
After configuration changes in the backend system, you must re-register the system.
can i know what is the pbm.
Raju

Hi,
i have used j2ee_admin login to register.
it has registered successfully.
But when i login with my user id, it is giving me following error.
Exception type:com.sap.netweaver.bc.uwl.connect.ConnectorException Message:Tue Apr 21 17:39:39 GMT+05:30 2009
(Connector) :com.sap.mw.jco.JCO$Exception:User RAJU has no RFC authorization for function group SWN_UWL_WL.
can i know what is the prob.
Regards,
Raju

Universal Worklist Refresh Problem

Hi All,
I got a Problem with the Workitem not showing up in the universal worklist. The workitem appears in the backend but its not created in UWL. However it is created when configuration object is delted and uploaded again. But it is not refreshed automatically.
Any help on this will be greatly appreciated.
Thanks ,
Rakesh.

Hi Rakesh.
Go to System Administration --> System Configuration --> Universal Worklist & Workflow --> Universal Worklist - Administration
1) Select you System Alias and click in Re-Register.
2) Click in link Cache Administration Page, Select your system and click in Clear Cache.
Good Luck
Eduardo

Exception in Universal Worklist configuration

Hi,
I'm getting the following error while connecting from the Portal UWL to a R/3 system.
Exception type:com.sap.netweaver.bc.uwl.connect.ConnectorException
Message:Thu Apr 20 17:23:14 GMT+08:00 2006 :
JCO.Client not connected in repository call
Portal is SP14 and the R/3 system is NW 640 SP12.
Any help is greatly appreciated, stuck on this for a while now.
Thanks,
Manik

I am facing similar error while trying to register a R/3 system with Portal.
(Connector) :com.sap.netweaver.bc.uwl.connect.ConnectorException:Mon Jun 05 10:23:29 EDT 2006
(Connector) :com.sap.mw.jco.JCO$Exception:User is locked. Please notify the person responsible
The R/3 system has been configured for UID/PWD and tested successfully. Connection test is successful. But when I tried to register the same system through
System Administration -> System Configuration -> Universal Worklist & Workflow -> Universal Worklist Administration, I am getting the above error.
I am trying to configure the R/3 system using 'WebFlowConnector' type.
Can anyone please guide me how to configure a R/3 more detail.
Thanks in advance.

Universal Worklist Configuration

Hey guys
Please can someone tell me where I can find a universal wordlist config guide for EP7.0?
Many thanks in advance
Jo-lize

Hi
This are the steps need to be followed.please do give full points
The Universal Worklist (UWL) gives users unified and centralized way to access their work and the relevant information in the Enterprise Portal. It collects tasks and notifications from multiple provider systems SAP Business Workflow, Collaboration Task, Alert Framework and Knowledge Management Recent Notifications - in one list for one-stop access.
Administration and configuration for the Universal Worklist (UWL) is described.
General Prerequisites
1.     As an administrator, you have full administration rights for the Portal and the required business workflow rights in back end system (reference roles such as SAP_BC_BMT_WFM_UWL_ADMIN and SAP_BC_UWL_ADMIN_USER). Refer to SAP note 941589.
Summary
Symptom
UWL administrative and/or end users are not allowed to perform or look up business workflow functions or data in the backend system.
Reason and Prerequisites
Corresponding adminsitrative and end users in the backend systems are created from scratch and have zero initial authorization.
These roles are provided as an option to enable UWL administrative and end user authorization to readily utitlize the APIs of the SAP Business Workflow and relevant basis components remotely.
(Note: Usually these roles are not needed as backend user is already assigned with roles that have sufficient authorization.)
Also refer to BWF note 938717 for the corresponding roles required by business workflow.
SAP_BC_UWL_ADMIN_USER
For UWL administrative user who mainly deals with business workflow system registration.
SAP_BC_UWL_END_USER
For UWL end user to carry out all business workflow actions currently supported in UWL.
Solution
The roles can only be imported with a support package
Header Data
Release Status:     Released for Customer
Released on:     25.04.2006 04:57:52
Priority:     Recommendations/additional info
Category:     Advance development
Primary Component:     EP-BC-UWL Universal Worklist
Releases
SoftwareComponent     Release     FromRelease     ToRelease     AndsubsequentSAP_BASIS     60     640     640      SAP_BASIS     70     700     700
Highest Implemented Support Package
SupportPackages     Release     PackageNameSAP_BASIS     640     SAPKB64017SAP_BASIS     640     SAPKB64019SAP_BASIS     700     SAPKB70008SAP_BASIS
Summary
Symptom
This note delivers two roles (PFCG) with the authorizations required to display and edit Business Workflow work items in the universal worklist.
SAP_BC_BMT_WFM_UWL_ADMIN
This role has the workflow authorizations required to perform the configuration for the Business Workflow connection in the universal worklist. These are authorizations for Business Workflow interfaces on the back-end system. The role does not have any authorizations for the portal or other interfaces used by the universal worklist.
SAP_BC_BMT_WFM_UWL_END_USER
This role has all workflow authorizations required by end users to be able to edit Business Workflow work items with the universal worklist. The role does not have any authorizations for the portal or other interfaces used by the universal worklist.
You can either use the two roles directly or as templates for your own roles.
Note 941589 contains more information about roles with authorizations for the universal worklist.
Other terms
Universal worklist
Solution
The roles can only be imported with the relevant Support Package.
Header Data
Release Status:     Released for Customer
Released on:     20.04.2006 07:43:26
Priority:     Recommendations/additional info
Category:     Advance development
Primary Component:     BC-BMT-WFM Business Workflow
Secondary Components:     EP-BC-UWL Universal Worklist
Releases
SoftwareComponent     Release     FromRelease     ToRelease     AndsubsequentSAP_BASIS     60     640     640      SAP_BASIS     70     700     700
Highest Implemented Support Package
SupportPackages     Release     PackageNameSAP_BASIS     640     SAPKB64017SAP_BASIS     700     SAPKB70008
Related Notes
941589 - UWL: administrative and end user roles
Attributes
1.     Make sure that each user is known to all connected SAP systems as per role requirement (make sure that there is one-to-one mapping between the portal user and the backend user)
If an iView is based on a system object defined in your system landscape, you must assign user permission for the relevant user, group, or role to the system object, as well. User permissions assigned to a system permits the iView to retrieve data from the respective back end application through the system object at runtime.
2.      Each connected SAP system for back end system (below release 7.0, WP-PI plug-in 6.0) has the connection to its respective SAP Internet Transaction Server (ITS)
Authorizations needed for working with Business Workflow
Normally, when the corresponding back end system user already has the correct authorization to work on the Business Workflow directly, no additional setup is required when working in UWL. However, manual configuration to assign RFC access authorization to the following function groups may be needed (Note: this is not common):
1.     ●      Function group and transaction SWK1 (for back end systems using WP-PI plug-in)
2.     ●      Function group SWN_UWL_WL (for back end system on release 6.40 and above, without the need of WP-PI plug-in)
3.     ●      Function group SWRC, SSCV (for all cases)
4.     ●      Authorization rights for SDTX
User Mapping:
1.      Navigate to User Administration ®identity Managementà User Mapping.
       2.      There are three scenarios:
○     Portal user ID is different than the back end SAP user ID and back end SAP user IDs are different in all back end SAP systems connected to the portal (UIDPW)
1.      Maintain the user mapping for each portal user corresponding to all the respective back end systems
2.      Portal user ID is different than the back end SAP user ID and backend SAP user ids are the same in all back end SAP systems connected to the portal (logon ticket)
Maintain the user mapping for each portal user to the reference system
3.     Portal user ID is the same as the back end SAP user and back end SAP user IDs are the same in all back end SAP systems connected to the portal (logon ticket)
1.       No user mapping is necessary
User Permissions
According to the prerequisites, if an iView is based on a system object defined in your system landscape, you must assign user permission for the relevant user, group, or role to the system object, as well.
User permissions assigned to a system permits the iView to retrieve data from the respective back end application through the system object at runtime.
     Procedure
       1.      Navigate to System Administration ® System Configuration ® Portal Content. Open the folder where the existing systems were created.
       2.      From the available system list, click with the secondary mouse button on the system name and choose Open ® Permissions.
       3.      Assign permissions. Make sure that under the Administrator column you assign Read permissions for the assigned role (for example for role eu_role). Also mark the check box End User.
       4.      Choose Save.
     Registering the Provider Systems
Each UWL iView can retrieve work items from multiple Business Workflow back end systems. Register each back-end connection to be used with the following procedure:
On the port...
       1.      On the portal, choose System Administration ® System Configuration ® Universal Worklist and Workflow ® Universal Worklist Administration.
The Universal Worklist Systems list appears. Here you can define connectors and systems as item providers for the Universal Worklist.
       2.      To add a new entry, choose New. To edit existing information, select (highlight) the row and choose Edit.
       3.      To save the current system registration, choose Ok.
       4.      Multiple system connections are defined by repeating the above steps 1 to 3.
Table describing the parameters
Parameter     Description and Use
Connector     This is the identifier with which the connector is registered. It indicates the type of items retrieved through the connection. For example: WebFlowConnector.For connector types WebFlowConnector or Alert Connector item types have to be registered with the UWL service after defining a new system connection.
Configuration Groups     Leave this blank, when working with the default UWL iView. You can add a number of configuration groups separated by commas but only one configuration group per iView. first installed, one UWL iView is defined. The System Configuration Group property for that iView is empty (blank). This means that no System Configuration Group is named, but in effect there is only a single group. The default behavior for the blank setting is this: when any user logs onto the UWL iView, UWL tries to log that user onto all registered back end systems. There is a limitation with the blank setting. When a large number of systems are accessed during log on, the overall portal load is increased. Also, the user receives error messages from those back end systems that have no user account for the particular UWL user. For large system landscapes do the following:...       1.      Partition back end systems into groups. This is accomplished by creating additional UWL iView instances, each of which refers to a specific group of backend systems. The group is defined, using the System Configuration Group iView property.       2.      Then use the value of the System Configuration Group property when registering back end systems by placing it in parameter Configuration Group, when you register the SAP system.
System alias     The name of the alias for the back end system, as defined in the system landscape. The length cannot exceed 25 characters.If Web Dynpro applications are configured on a SAP NetWeaver Application Server which is different from the SAP NetWeaver Application Server of the system alias, then specify that system alias as a Web Dynpro system
Web Dynpro Launch System     Enter the Web Dynpro system name if the SAP NetWeaver Application Server for the system is not the same as that running the Web Dynpro.Leave empty otherwise
User Roles     Restricts who can get work items via the user role. For example, you can assign a portal role here, such as buyer. Only users with the role buyer will see items from the provider system in UWL.You can have multiple user roles separated by semi-colon. By specifying user roles for the portal users, it can be restricted as to who gets the work items in UWL. For example, you can assign a portal role to a user, such as buyer. Only users with the role buyer will see items from a system, for example, B7QCLNT000 in UWL.
Pull Channel Delta Refresh Period (in Seconds)     Delta Pull mechanism of UWL enables new items to be fetched from the back end SAP systems every minute by default every 60 seconds, and every 30 seconds for alerts. However, this can be configured. The user does not need to use the refresh function to update the inbox. Once items are retrieved, timestamps are updated for the users whose items are successfully retrieved. These retrieved items are updated in the UWL cache. Setup necessary from Business Workflow to enable Delta Pull MechanismSome configuration settings are required if you use the UWL and the Extended Notifications for SAP Business Workflow. Define the following two batch jobs:...●      Background job (for example UWL_DELTA_PULL_1), consisting of a single step of ABAP report RSWNUWLSEL in FULL mode, using a report variant.Run the job once a day.1.     ●      A background job (for example UWL_DELTA_PULL_2), consisting of a single step of ABAP report RSWNUWLSEL in DELTA mode (default mode is delta, so report variant is optional).Run the job every one to three minutes (depending on the performance of the back end SAP system).Setup necessary from UWL to enable Delta Pull Mechanism The UWL service user in portal, with user id uwl_service, has to be granted access to the corresponding back end systems. This is a predefined service user provided by UWL. When the back end system is configured in the UWL administration page, an automated process is triggered to create a corresponding UWL service user in the back end system.Check role assignments and profiles status of this automated generated UWL service user and perform user comparison if necessary.●      If SAPLogon ticket is used (without using user mapping), you first create the system entry. A message about uwl_service user appears. Then in the back-end system give the uwl_service user an initial password. Now edit the system entry.●      If user mapping is used, you can first configure the back end system in the UWL administration page. Then access the respective back end system to initialize the password for the user uwl_service. Then, do user mapping in the portal as usual for service user uwl_service.In case uwl_service fails to be created in the back end and does not exist, you can manually create a back end user with the id uwl_service and assign the role SAP_BC_UWL_SERVICE and the rights as other end users.ORMap uwl_service to an existing back end user. Make sure that there is no multiple user mapping (there must not be two portal users mapped to the same back end user). This back end user must have the role SAP_BC_UWL_SERVICE.
Snapshot Refresh Period (in minutes)     All items at the current time are fetched from the backend (for example from the SAP Business Workflow). The cache is synchronized thereafter. New / modified / deleted / updated items are fetched every session (every log on) if you leave the field value empty or enter a negative number.To specify a particular time frame for which the refresh occurs, enter the number of minutes
The above registration procedure is usually sufficient to use a UWL iView. Item type retrieval and registration requires a connection to the systems and may take a couple of minutes.
For each system, they are generated as the configuration named uwl.webflow..
In Manager Self-Service (MSS), the Universal Worklist groups together in Workset: Work
Overview the various workflow tasks and alerts that are relevant for a manager.
The standard MSS delivery includes the configuration file com.sap.pct.erp.mss.001.xml for the universal worklist.
1. In the portal, choose System Administration →System Configuration →Universal
Worklist and Workflow →Universal Worklist →UWL Systems Configuration.
2. Create the following system connections:
If you have already registered a suitable connector to the system connected to
the system alias, the existing connector is sufficient and you do not have to
register an additional one.
○ System alias: SAP_ECC_Financials
Connection types:
■ WebFlowConnector
■ AlertConnector
○ System alias: SAP_ECC_HumanResources
Connection type WebFlowConnector
○ System alias: SAP_SRM
Connection type WebFlowConnector
Leave the Web Dynpro Launch System field blank for all system connections.
With regards
subrato kundu

Universal Worklist Configuration error

Hi,
We are working on EP6 SP23.
KMC 23 has been installed.
ECC5 Basis 640 SP21 is our R3 system.
While trying to access System Administration -> Syatem Configuration -
>Universal Worklist Administrator throws runtime error with header
com.sap.portal.pcm.Title.
The trace file logs
#1.5 #000F20F6601900FD0000000200001364000468B183E677EA#1241011538258#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#Administrator#960##n/a##3903dae034c111dec646000f20f66019#Thread[PRT-Async
0,5,PRT-Async]##0#0#Error##Java###06:55_29/04/09_1120750
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException:
Error in init method
Component : com.sap.netweaver.bc.uwl.ui.UWLConfigurationAdmin
at
com.sapportals.portal.prt.component.PortalComponentContext.init
(PortalComponentContext.java:251)
at
com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
at
com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
at
com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
at com.sapportals.portal.pb.PageBuilder.createIviewProfile
(PageBuilder.java:418)
at com.sapportals.portal.pb.PageBuilder.createiView
(PageBuilder.java:372)
at com.sapportals.portal.pb.PageBuilder.createAndAddiViews
(PageBuilder.java:234)
at com.sapportals.portal.pb.PageBuilder.doOnNodeReady
(PageBuilder.java:576)
at
com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent
(AbstractPortalComponent.java:388)
at com.sapportals.portal.pb.PageBuilder.handleEvent
(PageBuilder.java:725)
at
com.sapportals.portal.prt.component.CachablePortalComponent.handleEvent
(CachablePortalComponent.java:706)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent
(ComponentNode.java:252)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode
(PortalNode.java:369)
at com.sapportals.portal.prt.pom.AbstractNode.addChildNode
(AbstractNode.java:340)
at com.sapportals.portal.navigation.workAreaiView.doOnNodeReady
(workAreaiView.java:309)
at
com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent
(AbstractPortalComponent.java:388)
at com.sapportals.portal.navigation.workAreaiView.handleEvent
(workAreaiView.java:362)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent
(ComponentNode.java:252)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode
(PortalNode.java:369)
at com.sapportals.portal.prt.pom.AbstractNode.addChildNode
(AbstractNode.java:340)
at
com.sapportals.portal.pb.PageBuilder.createAndAddEmbeddediView
(PageBuilder.java:178)
at com.sapportals.portal.pb.PageBuilder.createiView
(PageBuilder.java:391)
at com.sapportals.portal.pb.PageBuilder.createAndAddiViews
(PageBuilder.java:234)
at com.sapportals.portal.pb.PageBuilder.doOnNodeReady
(PageBuilder.java:576)
at
com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent
(AbstractPortalComponent.java:388)
at com.sapportals.portal.pb.PageBuilder.handleEvent
(PageBuilder.java:725)
at
com.sapportals.portal.prt.component.CachablePortalComponent.handleEvent
(CachablePortalComponent.java:706)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent
(ComponentNode.java:252)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode
(PortalNode.java:369)
at com.sapportals.portal.prt.pom.AbstractNode.addChildNode
(AbstractNode.java:340)
at
com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle
(PortalRequestManager.java:642)
at
com.sapportals.portal.prt.connection.ServletConnection.handleRequest
(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run
(Dispatcher.java:547)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service
(Dispatcher.java:407)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet
(HttpHandlerImpl.java:401)
at
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet
(RequestAnalizer.java:386)
at
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet
(RequestAnalizer.java:364)
at
com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at
com.sap.engine.services.httpserver.server.RequestAnalizer.handle
(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle
(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request
(Processor.java:175)
at
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run
(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run
(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute
(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run
(SingleThread.java:172)
Caused by:
com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class
com.sap.netweaver.bc.uwl.ui.admin.ConfigurationAdmin of Portal
Component com.sap.netweaver.bc.uwl.ui.UWLConfigurationAdmin because:
Could not instantiate implementation class
at
com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:269)
at
com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
at
com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
at
com.sapportals.portal.prt.component.PortalComponentContext.getComponent
(PortalComponentContext.java:103)
at
com.sapportals.portal.prt.component.PortalComponentContext.init
(PortalComponentContext.java:242)
... 51 more
Caused by:
com.sapportals.portal.prt.core.broker.PortalApplicationNotFoundException: Could not find portal application
com.sap.portal.runtime.application.rfcengine
at
com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare
(PortalApplicationItem.java:413)
at
com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare
(PortalApplicationItem.java:385)
at
com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare
(PortalApplicationItem.java:385)
at
com.sapportals.portal.prt.core.broker.PortalApplicationItem._refresh
(PortalApplicationItem.java:505)
at
com.sapportals.portal.prt.core.broker.PortalApplicationItem.getCoreLoader(PortalApplicationItem.java:1334)
at
com.sapportals.portal.prt.core.broker.PortalComponentItem.getClassLoader(PortalComponentItem.java:569)
at
com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getClassLoader(PortalComponentItemFacade.java:102)
at
com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
... 55 more
Please suggest is their any patch/support package need to be installed.
Thanks,
Sekhar

Thank you Sonali and Amit.
But I am getting the error in the standard SAP iview, that is when trying to open the System Administration -> Syatem Configuration - >Universal Worklist Administrator page.
From the log is seems that some application is missing
Caused by: com.sapportals.portal.prt.core.broker.PortalApplicationNotFoundException: Could not find portal application com.sap.portal.runtime.application.rfcengine at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare (PortalApplicationItem.java:413) at com.sapportals.portal.prt.core.broker........
So did I misout some pakages to be deployed or the error exists in the corresponding release itself?
Thanks,
Sekhar

Standard Portal activity report configuration and Universal worklist config

Hi,
I need help for follwong topics:
Standard Portal activity report configuration and Universal worklist configuration.
Thanks & Regards
Sushama Pandey

Hi
Check this
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/904ca240-63bc-2a10-1c98-de81b6a045bf

User roles property, when system alias is configured in universal worklist

Hi,
I am configuring system alias in Universal Worklist Configuration. I have keyed in system alias and connector type and saved the system alias and its working fine.
Apart from system alias and connector type, there are other properties like "User Roles, Delta Pull Channel Refresh Period(in seconds) and Delta Pull Channel Snapshot Refresh Period(in minutes). Can you any let me know what is the use of these properties.
I heard that "Delta Pull Channel Refresh Period(in seconds)" is the time period to refresh the UWL is it correct.
Thanks & Regards,
H.K.Hayath Basha.

Try searching the http://help.sap.com SAP NetWeaver pages for delta pull!

Custom ItemTypes in Universal Worklist

Hi Comunity,
I have created two views in the Universal Worklist configuration that work just fine. Now I want to have certain items to only show up in one of those views. Therefore I have set the supported itemtypes parameter to the itemtype I want to show up in this view. Unfortunatelly the item type is none of the standard types. I have added one level of hirarchy by adding staff to the standard uwl.task.webflow item type. I have also tried to add an item type uw.task.webflow.staff into the file but this does not work either, there is no item showing up in my UWL.
Please have a look at the xml, I have inserted some snippets.
Any hint is welcome.
Regards Nicolas
Edited by: Nicolas Löwe on Oct 8, 2009 11:59 AM

Hi I found the solution myself.
I have done the configuration correctly. But the new Item Types do only appear when there are no other items in the cache.
Cheers Nicolas

Substitution in universal worklist

Hi,
We have an issue in substitution in universal worklist.The problem is
that we will able to create substitution rule in UWL after which when
we refresh the button it is disappeared from the screen. I have
enclosed the screen shot for your reference
Please Suggest
Regards,
Prasath

HI,
HRUS_D2 has not maintained anything . what should i do
Regards,
Prasath

Configuration problem Universal Worklist (UWL)

Hi,
I'm trying to do the configure the Universal Worklist using the
<a href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/fa21a890-0201-0010-708b-d0cfc117e7cd">How to Configure the Universal Worklist.pdf</a>.
Problem is that I can't find the 'Registration for Item Types of Universal Worklist Webflow' in System Administration -> System Configuration -> Universal Worklist.
Does anyone know where it went or how I can make it visible again.
Thanks in Advance,
Jeschael

Hi Jeschael,
I have the similar kind of issue with my UWL.
Could you please help in Configuring UWL.
I will be grateful if you can share any docs or any sought of assistance will be appreciated.
Screenshot for your reference:
Thanks in advance.
Srikanth Naidu. Akula

Configuring universal worklist for SAP workflows

Hi All,
How to Configure Universal Worklist for SAP Workflows....could you please tell me the configuration steps in Portal and please tell me required Transaction codes to configure in SAP R/3 side for configuration of UWL....
This is urgent.....
Really i appreciate.
Thanks and Regards,
Abhi.

Hi Abhiram,
u cn refer to these links.......its of very use to u.......
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a3461636-0301-0010-3787-978f5ac8bd45
http://help.sap.com/saphelp_nw2004s/helpdata/en/57/c223be82104792a15c2df11377b9ed/frameset.htm
How configure UWL in Portal 7.0
configuring the Universal Worklist
Problem configuring UWL
Regards
Bhargava
points are welcome

Universal Worklist Problem

Hi gurus!.
Im having a strange problem. I defined connector as WebFlowconnector and system under Universal Worklist, inside the System configuration menu.
The next step according to the documentation is to go to Universal Worklist Administration and click on the "Register Item Types for all Systems" (The connector is listed)
I get this error:
<b>uwlExceptionID: 1124307103781 :uwlExceptionID: 1124307103781 JCO Function template URL_SERVER_TYPE_DATA_GET:R3 not found in system</b>
Please note that R3 is the name of my system which is tested OK by the way.
Do you have any ideas? Thanks!!

Hi all,
Whe I goto "Register Item Types for all Systems" , in the iview I get an error "Unable to perform the request. Try again. If the problem persists, inform your system administrator."
Pls help.
Thanks,
Vivek

Configuring Guided Procedures with the Universal Worklist

hi experts,
Pls give me the steps to Configure Guided Procedures with the Universal Worklist....
I have the help file with me but it doesn't work ... and my configuration is NWDS 7.0 sp9.
pls help me
with regards,
sriram

Hi,
You can configure your system so that the tasks generated in Guided Procedures (GP) workflows, both on local and remote systems, are displayed in the Universal Worklist (UWL) together with the tasks pertaining to other SAP NetWeaver Portal work areas.
You perform the configuration steps on the consumer side:
       1.      Create a portal system, specifying the host name, HTTP port of the GP tasks provider and, if available, the WSDL of the relevant service.
       2.      Register the system as the item provider for UWL and configure it for remote access.
You establish the connection between GP and the UWL by assigning a system alias.
       3.      In UWL, browse all pending GP tasks assigned to your user.
You can only view tasks assigned to your user, that is, the logon ID of the user on both systems must match.
Prerequisites:-
a) You have been assigned the System Admin portal role to be able to create portal systems and aliases. For more information, see Administration Roles.
b) You have been assigned the Standard User role to be able to access UWL in the portal. For more information, see Default Portal Content for Standard Users.
c) You know the host name of the system from which you want to retrieve GP tasks
Step by Step Procedure guide can be found out at
[Step by Step Procedure for COnfiguring GP with UWL|http://help.sap.com/saphelp_nw04s/helpdata/en/43/ef06a7860c7061e10000000a1553f6/frameset.htm]
Hope this helps,
Regards,
Shailesh Nagar

Runtime error in Universal Worklist in portal

Hi!
An error occurs when I open the page Universal Worklist -
Administration under System Administration > System Configuration >
Universal Worklist & Workflow. The error message is:
Portal runtime error.
An exception occurred while processing your request. Send the exception
ID to your portal administrator.
Exception ID: 09:44_02/10/08_0004_221082950
Refer to the log file for details about this exception.
This error is also displayed when opening the page Portal Eventing,
Portal Navigation under System Administration > Support > Web Dynpro
Test Tools > Application Integrator Tests.
The portal UME is configured with ADS as data source and we are using
the dataSourceConfiguration_ads_readonly_db_with_krb5.xml configuration
file. Single Sign-On using SAP logon tickets with user mapping to
reference system is also implemented.
Users have different users IDs in the SAP System than in the portal,
and scenario 2 from SAP Help "Single Sign-On to SAP Systems"
(http://help.sap.com/saphelp_nw04/helpdata/en/4d/dd9b9ce80311d5995500508b6b8b11/frameset.htm) is implemented
"Scenario 2: Single Sign-On using SAP logon tickets with user mapping."
The problem occurred after changing the UME with ADS and implemented
Single Sign-on.
Error messages from log:
Date : 10/03/2008
Time : 10:08:56:057
Message : Content pass of Application Integrator failed.
Component Name:       com.sap.portal.appintegrator.sap.WebDynpro,
Context Name (iView): pcd:portal_content/every_user/general/uwl/com.sap.netweaver.bc.uwl.uwlSapWebDynproLaunch,
Top Layer:            WebDynpro/TopLayer,
Producer ID (FPN):    null,
System Alias:         SAP_LocalSystem,
[EXCEPTION]
com.sapportals.portal.appintegrator.ApplicationIntegratorException: ApplicationIntegratorException
     at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:104)
     at com.sapportals.portal.appintegrator.accessor.system.SAP_LocalSystemAccessor.getAuthenticationData(SAP_LocalSystemAccessor.java:91)
     at com.sapportals.portal.appintegrator.layer.authenticationmethod.AbstractAuthenticationMethod.getUserCredentials(AbstractAuthenticationMethod.java:54)
     at com.sapportals.portal.appintegrator.layer.authenticationmethod.SAPLogonTicket.computeAuthentication(SAPLogonTicket.java:31)
     at com.sapportals.portal.appintegrator.layer.SingleSignOnLayer.processLayer(SingleSignOnLayer.java:45)
     at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:159)
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:68)
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:54)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:396)
     at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
     at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)
     at com.sapportals.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:799)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:652)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.security.api.umap.NoLogonDataAvailableException: (No text available)
     at com.sap.security.core.umap.imp.UserMappingDataImp.enrich(UserMappingDataImp.java:329)
     at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:99)
     ... 33 more
Severity : Error
Category : /System/Server
Location : com.sap.portal.sapapplication
Application : sap.com/irj
Thread : SAPEngine_Application_Thread[impl:3]_18
Datasource : 1223021485930:N:\usr\sap\DPN\JC32\j2ee\cluster\server0\log\defaultTrace.trc
Message ID : 00145ED7E6460061000007830000B6B800045854D84A3E79
Source Name : com.sap.portal.sapapplication
Argument Objs : com.sapportals.portal.appintegrator.ApplicationIntegratorException: ApplicationIntegratorException
     at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:104)
     at com.sapportals.portal.appintegrator.accessor.system.SAP_LocalSystemAccessor.getAuthenticationData(SAP_LocalSystemAccessor.java:91)
     at com.sapportals.portal.appintegrator.layer.authenticationmethod.AbstractAuthenticationMethod.getUserCredentials(AbstractAuthenticationMethod.java:54)
     at com.sapportals.portal.appintegrator.layer.authenticationmethod.SAPLogonTicket.computeAuthentication(SAPLogonTicket.java:31)
     at com.sapportals.portal.appintegrator.layer.SingleSignOnLayer.processLayer(SingleSignOnLayer.java:45)
     at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:159)
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:68)
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:54)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:396)
     at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
     at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)
     at com.sapportals.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:799)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:652)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.security.api.umap.NoLogonDataAvailableException: (No text available)
     at com.sap.security.core.umap.imp.UserMappingDataImp.enrich(UserMappingDataImp.java:329)
     at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:99)
     ... 33 more
Arguments : com.sapportals.portal.appintegrator.ApplicationIntegratorException: ApplicationIntegratorException
     at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:104)
     at com.sapportals.portal.appintegrator.accessor.system.SAP_LocalSystemAccessor.getAuthenticationData(SAP_LocalSystemAccessor.java:91)
     at com.sapportals.portal.appintegrator.layer.authenticationmethod.AbstractAuthenticationMethod.getUserCredentials(AbstractAuthenticationMethod.java:54)
     at com.sapportals.portal.appintegrator.layer.authenticationmethod.SAPLogonTicket.computeAuthentication(SAPLogonTicket.java:31)
     at com.sapportals.portal.appintegrator.layer.SingleSignOnLayer.processLayer(SingleSignOnLayer.java:45)
     at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:159)
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:68)
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:54)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:396)
     at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
     at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)
     at com.sapportals.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:799)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:652)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.security.api.umap.NoLogonDataAvailableException: (No text available)
     at com.sap.security.core.umap.imp.UserMappingDataImp.enrich(UserMappingDataImp.java:329)
     at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:99)
     ... 33 more
Dsr Component : n/a
Dsr Transaction : f52708e0912011ddb1e200145ed7e646
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 1
Relatives : /System/Server
Resource Bundlename :
Session : 32121
Source : com.sap.portal.sapapplication
ThreadObject : SAPEngine_Application_Thread[impl:3]_18
Transaction :
User : Asle.Gaarder
Date : 10/03/2008
Time : 10:08:56:026
Message : Cannot provide backend user ID and password for user "Asle Gaarder" (unique ID: "USER.CORP_LDAP.asle.gaarder") for system "SAP_ECC_REFERENCE" because these credentials could not be found in the user mapping data.
Severity : Info
Category :
Location : com.sap.security.core.umap.imp.UserMappingDataImp.enrich(Properties)
Application : sap.com/irj
Thread : SAPEngine_Application_Thread[impl:3]_18
Datasource : 1223021485930:N:\usr\sap\DPN\JC32\j2ee\cluster\server0\log\defaultTrace.trc
Message ID : 00145ED7E6460061000007820000B6B800045854D849CB92
Source Name : com.sap.security.core.umap.imp.UserMappingDataImp
Argument Objs : "Asle Gaarder" (unique ID: "USER.CORP_LDAP.asle.gaarder"),"SAP_ECC_REFERENCE",
Arguments : "Asle Gaarder" (unique ID: "USER.CORP_LDAP.asle.gaarder"),"SAP_ECC_REFERENCE",
Dsr Component : n/a
Dsr Transaction : f52708e0912011ddb1e200145ed7e646
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 1
Relatives :
Resource Bundlename :
Session : 32121
Source : com.sap.security.core.umap.imp.UserMappingDataImp
ThreadObject : SAPEngine_Application_Thread[impl:3]_18
Transaction :
User : Asle.Gaarder

Hi,
Check the logon type for systems SAP_LocalSystem and SAP_ECC_REFERENCE which must be set to SAPLOGONTICKET not UIDPWD.
It basically fails since the password doesn't exist for the mapping, as it is only dependent on trust.
There was a change in a recent SP which added an extra check in this area.
Dagfinn

Universal Worklist Configuration Problem

Similar Messages

Maybe you are looking for