Cannot show GP process title in universal worklist

Hi all,
    We're on EP 7.0 SP11,we've got a problem:
    in uwl,we cannot show GP process's title.
    I remember in former edition,it can be seen in "process" column.
    And following is my go.config.xml:("gp_system" is my GP system alias)
    <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE UWLConfiguration PUBLIC '-//SAP//UWL1.0//EN' 'uwl_configuration.dtd'
>
<UWLConfiguration version="2.0">
<ItemTypes>
    <ItemType name="uwl.task.gp" connector="GuidedProceduresConnector" defaultView="uwlTaskGPView" defaultAction="launchGP" executionMode="default">
      <Actions>
        <Action name="launchGP" groupAction="no" handler="SAPWebDynproLauncher" referenceBundle="launch_sap" returnToDetailViewAllowed="yes" launchInNewWindow="no" launchNewWindowName="GPWindow" launchNewWindowFeatures="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no">
          <Properties>
            <Property name="WebDynproApplication" value="RuntimeUWL"/>
            <Property name="WebDynproDeployableObject" value="sap.com/cafeugpuirt"/>
            <Property name="DynamicParameter" value="app.workItemID=${item.processID}"/>
            <Property name="System" value="SAP_LocalSystem"/>
          </Properties>
        </Action>
      </Actions>
    </ItemType>
    
    <ItemType name="uwl.task.gp.gp_system" connector="GuidedProceduresConnector" defaultView="uwlTaskGPView" defaultAction="launchGP" executionMode="default">
      <Actions>
        <Action name="launchGP" groupAction="no" handler="IViewLauncher" referenceBundle="launch_sap" returnToDetailViewAllowed="yes" launchInNewWindow="no" launchNewWindowName="GPWindow" launchNewWindowFeatures="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no">
          <Properties>
            <Property name="DynamicParameter" value="app.processId=${item.processID}&app.taskId=${item.activityID}&"/>
            <Property name="page" value="pcd:portal_content/com.sap.pct/platform_add_ons/com.sap.caf.eu.gp.folders.gp/com.sap.caf.eu.gp.roles.runtime/com.sap.caf.eu.gp.worksets.runtime/com.sap.caf.eu.gp.pages.procinstance"/>
            <Property name="System" value="SAP_LocalSystem"/>
          </Properties>
        </Action>
      </Actions>
    </ItemType>
   </ItemTypes>
<Views>
    <View name="uwlTaskGPView" selectionMode="SINGLESELECT" width="98%" supportedItemTypes="uwl.task.gp" columnOrder="subject, process, creatorId, createdDate, dueDate, status" sortby="dueDate:ascend, createdDate:descend" tableDesign="STANDARD" visibleRowCount="10" headerVisible="no" queryRange="undefined" tableNavigationFooterVisible="yes" tableNavigationType="CUSTOMNAV" actionRef="" refresh="300" dueDateSevere="86400000" dueDateWarning="259200000" emphasizedItems="new" displayOnlyDefinedAttributes="yes" dynamicCreationAllowed="yes" actionPosition="bottom">
      <Descriptions default="Guided Procedures">
        <ShortDescriptions>
          <Description Language="de" Description="Guided Procedures"/>
          <Description Language="en" Description="Guided Procedures"/>
        </ShortDescriptions>
      </Descriptions>
      <DisplayAttributes>
        <DisplayAttribute name="phase" type="string" width="" sortable="yes" format="default" hAlign="LEFT" vAlign="BASELINE" maxTextWidth="0" headerVisible="yes">
          <Descriptions default="Phase">
            <ShortDescriptions>
              <Description Language="de" Description="Phase"/>
              <Description Language="en" Description="Phase"/>
            </ShortDescriptions>
          </Descriptions>
        </DisplayAttribute>
        <DisplayAttribute name="process" type="string" width="" sortable="yes" format="default" hAlign="LEFT" vAlign="BASELINE" maxTextWidth="0" headerVisible="yes">
          <Descriptions default="Process">
            <ShortDescriptions>
              <Description Language="de" Description="Process"/>
              <Description Language="en" Description="Process"/>
            </ShortDescriptions>
          </Descriptions>
        </DisplayAttribute>
      </DisplayAttributes>
    </View>
</Views>
</UWLConfiguration>
Someone to help me?
Best regards
delma

Similar Messages

Cannot open GP process task in universal worklist.

Hi all,
    I cannot open GP process task in universal worklist.It says:"Could not retrieve process instance: contact your system administrator".But i can open the task in Runtime task.
i configure the universal worklist by following this link:
http://help.sap.com/saphelp_nw04s/helpdata/en/43/ef06a7860c7061e10000000a1553f6/frameset.htm
I also create a simple GuidedProceduresConnector and doesn't change the xml file,but it doesn't work,either.
our portal is SP11.
Can anyone help me?
Thank you~!
Best regards
delma

Hello Delma,
Check out SAP note 1104652.    It discusses some changes for the uwl configuration file.   I just did this on a local installation of CE and used the following XML for my GP actions. I just uploaded a paper on this - it should be on SDN within a couple of days and I can get you the link.
The trick is that the name of your GP alias in UWL administration must be included in the XML. The note explains this and there is an example to download. Also, in my example the iView for the portal content to start the GP had to be changed - but that could be due to my local installation.
Check out this note and this XML and let me know if it helps.
Best regards
Ginger
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE UWLConfiguration PUBLIC '-//SAP//UWL1.0//EN' 'uwl_configuration.dtd'
>
<UWLConfiguration version="2.0">
<ItemTypes>
    
    <ItemType name="uwl.task.gp.GPSystem" connector="GuidedProceduresConnector" defaultView="uwlTaskGPView" defaultAction="launchGP" executionMode="default">
      <Actions>
        <Action name="launchGP" groupAction="no" handler="IViewLauncher" referenceBundle="launch_sap" returnToDetailViewAllowed="yes" launchInNewWindow="no"
launchNewWindowName="GPWindow" launchNewWindowFeatures="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no">
          <Properties>
            <Property name="page" value="pcd:portal_content/com.sap.pct/platform_add_ons/com.sap.caf.eu.gp.folders.gp/com.sap.caf.eu.gp.folders.pages/com.sap.caf.eu.gp.pages.procinstance2"/>
            <Property name="DynamicParameter" value="app.processId=${item.processID}&app.taskId=${item.activityID}&"/>
            <Property name="System" value="SAP_LocalSystem"/>
          </Properties>
        </Action>
      </Actions>
    </ItemType>
</ItemTypes>
<Views>
    <View name="uwlTaskGPView" selectionMode="SINGLESELECT" width="98%" supportedItemTypes="uwl.task.gp.GPSystem" columnOrder="subject, process, creatorId, createdDate, dueDate, status" sortby="dueDate:ascend, createdDate:descend" tableDesign="STANDARD" visibleRowCount="10" headerVisible="no" queryRange="undefined" tableNavigationFooterVisible="yes" tableNavigationType="CUSTOMNAV" actionRef="" refresh="300" dueDateSevere="86400000" dueDateWarning="259200000" emphasizedItems="new" displayOnlyDefinedAttributes="yes" dynamicCreationAllowed="yes" actionPosition="bottom">
      <Descriptions default="Guided Procedures">
        <ShortDescriptions>
          <Description Language="de" Description="Guided Procedures"/>
          <Description Language="en" Description="Guided Procedures"/>
        </ShortDescriptions>
      </Descriptions>
      <DisplayAttributes>
        <DisplayAttribute name="phase" type="string" width="" sortable="yes" format="default" hAlign="LEFT" vAlign="BASELINE" maxTextWidth="0" headerVisible="yes">
          <Descriptions default="Phase">
            <ShortDescriptions>
              <Description Language="de" Description="Phase"/>
              <Description Language="en" Description="Phase"/>
            </ShortDescriptions>
          </Descriptions>
        </DisplayAttribute>
        <DisplayAttribute name="process" type="string" width="" sortable="yes" format="default" hAlign="LEFT" vAlign="BASELINE" maxTextWidth="0" headerVisible="yes">
          <Descriptions default="Process">
            <ShortDescriptions>
              <Description Language="de" Description="Process"/>
              <Description Language="en" Description="Process"/>
            </ShortDescriptions>
          </Descriptions>
        </DisplayAttribute>
      </DisplayAttributes>
    </View>
</Views>
</UWLConfiguration>

Show Custom Attributes of GP Tasks in the Universal Worklist

Hello,
I have created a GP Process and i can see and execute its task in the universal worklist.
But it only shows standart propertys like : Process,From, Sent, Due, Status.
I want to add Custom specific task propertys, but i couldn`t find the way. Reading javadoc documentation :
[https://help.sap.com/javadocs/NW04S/current/uw/com/sap/netweaver/bc/uwl/doc-files/uwldtd.html#ItemType|https://help.sap.com/javadocs/NW04S/current/uw/com/sap/netweaver/bc/uwl/doc-files/uwldtd.html#ItemType]
It says de we only can retrieve custom propertys from this connectors:
ABAP_BOR - for SAP Business Object Repository
WEBFLOW_CONTAINER - for Business Workflow container
UM - for Portal user attributes from user management
ALERT_CONTAINER - for alert container
GP_Connector is not in the list.... this means that it won`t be possible to show specific task attributes in the UWL if the tasks belong to a Guided Procedure Process?
Thanks in advance!
Marco.

Hello Chittya,
As I explained, my problem is not showing the GP tasks in the UWL ( in fact i have created a GP connector, and my GP tasks are correctly shown in my UWL ). The problem is that i can´t manage to show custom properties of this GP tasks in the universal worklist.
Regards.
Marco.

Universal Worklist is showing error

Hi SAP Guru's
I have configured workflow for the leave request, and registered system
under Universal Work list Administration.
Options under System Administration -> Universal Work list & Workflow
1) Universal Worklist Administration (working)
2) Universal Worklist (showing error)
3) Workflow (workflow)
When I am clicking Universal Worklist(Option 2), I am getting error
The specified root item cannot be retrieved from the configuration.
Correct the entry before trying again.
I have some questions regarding this error
1) Is Universal Worklist only will open after successful configuration of workflow , it is dependent on workflow
2)Is this is standard thing in EP 7.0
3)something wrong configuration for workflow
Please suggest

Have you done the system configuration for the landscape
defined system alias
ALso please read the Note 779075
Check the configuration of SAP_WebDynpro_XSS
The UWL system configuration page includes a Web Dynpro system field,
which can be used to configure the system alias of Web Dynpro
application.
Here is the help documentation:
http://help.sap.com/saphelp_nw70/helpdata/en/92
/a88931f2dd4631b9e8d530697d89c9/content.htm
in regards to this parameter.

Workitem in universal worklist not refreshed after processing the workitem

Hi,
We are using EP 7.0, we are having a problem in refreshing workitem in universal worklist. When a workitem in universal worklist is clicked a ABAP webdynpro application is opened in new window, this window has approve and reject button. Clicking on the approve or reject button completes the business process and workitem should be removed from the UWL. But in our case the workitem is still shown in the UWL and the user can again click on the same workitem and open.
Has anyone has encountered this problem? Could someone let me know how to resolve this issue.
Thanks & Regards,
H.K.Hayath Basha.

Hi,
Just check the status of the workitem whether its approved or rejected before opening the application. If its already approved
or rejected dont open the application.We also faced the similar problem and avoid opening the work item instead of refreshing
uwl.
Because by configuration it is possible to reduce till one minute and frequent refresh of uwl will result in poor performance.
You can give a try with writing code to refresh uwl once the workitem got approved or rejected.
http://help.sap.com/javadocs/NW04S/current/uw/com/sap/netweaver/bc/uwl/admin/IUWLAdmin.html
Try using clear cache.
Best Wishes
Idhaya R

How to call / execute BPM process out of portal (Universal Worklist)

Hi,
at the moment I try to get fimilar in working with bpm processes. In this regard, I try to execute a process outside the portal.
I always have to login at the portal, go to the Universal Worklist, refresh the list and execute the previously started process. But in future that would NOT be the prefered way for the user.
May anybody help me?
Thank you.

Hi Martin,
what do you mean exactly? Do you want to start the workflow without using the portal or do you want to start the different human activities outside the portal?
If you mean the first one, you can use a webservice to start the process (see Re: Starting a flow through a web service). As such you can start the process from pretty much everything with webaccess.
For the second one I dont have an answer... You can probably use a different application and check if there are any new tasks via webservice... but thats just a guess
cya,
Matthias

LeaveRequestApprover : "Page cannot be displayed" in universal worklist

Hi,
I really need some help on the leave request approver application.
When the approver clicks on a request in his universal worklist, the LeaveRequestApprover should be called. In our case, we have a "Page cannot be displayed" error message.
We have upgraded our system form ECC5 to ECC6.
Is there some configuration to do?
Thanks a lot for your help.
Karim

Hello Karim,
Can you check the whether the TASK of that workflow is properly configured in SWFVISU with your application name/component name.
Please check and confirm.
Regards
Nizamudeen SM

Universal Worklist showing cross-linked tasks

This is a really strange problem.
I have a Guided Procedure process that is being heavily utilized in our company. Occasionally, tasks in a user's work list will become 'cross-linked': the description will say one thing, but opening the task will open another similar task. And vise-versa.
For example, say I have processes assigned to a Manager:
- Task for Employee 'A' (example process id 6a1234)
- Task for Employee 'B' (example process id 6a4567)
When 'Task for Employee A' is opened, the task for Employee 'B' is started. And, when 'Task for Employee B' is opened, the task for Employee 'A' is started. Very strange!
I've checked the underlying process data via /nwa, and the process instances are defined correctly: all data assigned to the process is correct. But, where this really get's weird is when you look at the URL's processed when the task from the Universal Worklist is opened.
If you look at the process ID's embedded in the URL's, they're wrong! Using the information above, the URL for the task for Employee 'A' contains the process ID for the task for Employee 'B'. This explains why the wrong back-end document is opened, since the GP run-time is passing the wrong context.
The process id's defined in the actual GP tasks look correct, so this appears to be a presentation issue.
I have not had the employee try to open the task via the GP Workbench, as this roles not assigned to users in general.
Suggestions?
We're on NW 7.0 sp17.

Hi Ken,
Yep, cheers for that. Now, I did find some information from older messages for you, and it appears that sometimes, this works as designed based on how you have defined your roles for GP.
Do you have a group used as a default for the requestor role?
If you want only one user(the initiator) to be a requestor than you
should change the Requestor role to be of type "Initiator". If this is the case
all the users in the group are used as processors and all of them
would have a task in then in the UWL. This is normal behaviour of the GP.
Here is some additional documentation....
http://help.sap.com/saphelp_nw70/helpdata/EN/96/b48c42ee585551e10000000a
1550b0/content.htm
http://help.sap.com/saphelp_nw70/helpdata/EN/43/8acc8f3b682673e10000000a
1553f7/content.htm
Am I understanding you correctly? I also may need to check with a GP colleague on this for clarification...
Beth Maben
EP - Senior Support Consultant
AGS Primary Support, Business Suite & Technology
Please see the UWL Wiki @
https://www.sdn.sap.com/irj/scn/wiki?path=/display/bpx/uwl+faq ***

Processing EIC follow up via the Universal Worklist (UWL)

Hi
We are implemented EIC (Employee Interationc Centre) ERP and have an issue whereby the follow up appears in both the agent inbox within EIC and the Universal Worklist. The workflow for follow up is WS61000086. How do we get the follow up to work from the UWL as well as the EIC agent inbox? At the moment if the user clicks on the work item in the UWL a blank window is opened 'Display Object' close window.
Many thanks
Julie

Hi,
You are most likely missing a proper configuration for the task in UWL. The UWL configurations are done in Portal in system admin -> system config -> UWL (->Manage item types). This will require some XML "coding" experience, since you would need to do a proper XML configuration for the task. Now I don't know that what should happen when the user clicks the task in UWL, since I don't know this workflow or this area. Is there some web application existing for this task, are you just supposed to open the SAP GUI for the task? In both cases it might also be possible to do the needed configuration in transaction SWFVISU. Basically you need to enter your task ID there and then configure what is the "visualization" for the task. After the SWFVISU has been done correctly, you need to re-register the workflow system (in system admin -> system config -> UWL), and this would create the XML configuration automatically.
Regards,
Karri

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

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

Java Web DynPro and Universal Worklist Interaction

HI ESS/MSS Gurus,
Good day!
I am a workflow consultant who is working on an ESS/MSS project. I have already completed and tested (successfully) all of the workflows needed in the backend using the PTARQ and PTCOR applications. We are also successful in showing the work items in the universal worklist.
Now the question is, whenever we click on the work item, we encounter an error in the portal. Now, I need to determine the following:
1. How are we going to integrate the ESS/MSS portal with the execution of the work item in the universal worklist?
2. Do we need to develop custom Java web dynpro applications for the approval process of the leaves, or is there a standard offering from the ESS/MSS packages?
Your inputs are very much welcome.
Regards,

Hi Gurus,
Here is what we have done so far:
1. Implemented the details as indicated in note 779075 and changed the parameters defined in SWFVISU
2. Upon re-registering and clearing the cache from the UWL, we tested if the task will call the standard application for leave request approval. It returns the error Internal error. :
Item is null for action acknowledge, and for item type uwl
It seems that the xmls files are not being generated or read successfully. although when we check uwl.webflow.SAP_ECC_HumanResources, there is an updated xml file for the task
Questions are:
1. What checks do we need to execute between the back end, UWL and portal?
2. Whenever changes in SWFVISU are made, what items do we need to check to ensure that the changes are reflected in the UWL? I have read that SWFVISU helps the user do away with the tedious xml creation. How can we verify that the changes are implemented/updated in the xmls generated?
3. Any other items we need to look into?
Regards,

Two action in Universal Worklist

Hi Experts,
Whenever I test any of the process by initiating it and then I check that action in the universal worklist then it show two action means if I have generated Action1 from the process1. then in the Universal Worklist I found the list as
Action1
Action1
So, do you how to remove this duplicacy of the action in the Universal Worklist..
Thanks in Advance
Regards,
Kuldeep Verma

hi kuldeep,
please check the GP conector using the following path, system administraiton->system configuration->universal worklist and workflow->universal work list administration
inside that there will be universal worklist system.
please check the connector to the GP, there should be only one active connector to the GP.
If there is 2 active connector to the GP then it will give the error as you got.
With regards
Shanto Aloor

Portal runtime error - for Universal Worklist

Hi All,
We have upgraded SAP Portal from 7.0 to 7.3 Ehp1, after upgrade we faced some issues and have resolved those.
Right now some tabs in the portal is working fine whereas Universal Worklist and some tabs are throwing runtime error, where it shows "No logon ticket available" in trace file.
I have checked login module components in nwa and it shows as
EvaluateTicketLoginModule SUFFICIENT
BasicPasswordLoginModule REQUISITE
CreateTicketLoginModule OPTIONAL
Please find the below trace details. Kindly suggest your views.
Thanks in advance !!!!!
05:24:13:181#0-800#Error#com.sap.portal.prt.runtime#
#EP-PIN-PRT#tc~epbc~prtc~api#C000A7EEAF6101B000000002000043B0#14599450000000004#sap.com/com.sap.portal.runtime.system.hooks#com.sap.portal.prt.runtime#C933075#83##9C25C9AEA5FB11E38FEB000000DEC51A#be36c9ada5fb11e39ffa000000dec51a#be36c9ada5fb11e39ffa000000dec51a#0#Thread[HTTP Worker [@1426801953],5,Dedicated_Application_Thread]#Plain##
[EXCEPTION]
com.sapportals.portal.appintegrator.ApplicationIntegratorException: com.sap.security.api.umap.NoLogonDataAvailableException: No logon ticket available.
at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:99)
at com.sapportals.portal.appintegrator.accessor.system.SAP_LocalSystemAccessor.getAuthenticationData(SAP_LocalSystemAccessor.java:106)
at com.sapportals.portal.appintegrator.layer.authenticationmethod.AbstractAuthenticationMethod.getUserCredentials(AbstractAuthenticationMethod.java:53)
at com.sapportals.portal.appintegrator.layer.authenticationmethod.SAPLogonTicket.computeAuthentication(SAPLogonTicket.java:30)
at com.sapportals.portal.appintegrator.layer.SingleSignOnLayer.processLayer(SingleSignOnLayer.java:45)
at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:175)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:111)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:70)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:398)
at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher$1.service(RequestDispatcherFactory.java:168)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:292)
at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher.handleEvent(RequestDispatcherFactory.java:158)
at com.sap.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:242)
at com.sap.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:342)
at com.sap.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:732)
at com.sap.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:473)
at com.sapportals.portal.prt.connection.ServletConnection._handleRequest(ServletConnection.java:224)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:101)
at com.sap.portal.prt.dispatcher.DispatcherServlet.service(DispatcherServlet.java:132)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)
at com.sap.portal.http.EnrichNavRequestFilter.doFilter(EnrichNavRequestFilter.java:49)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at com.sap.portal.prt.dispatcher.CustomHeaderFilter.doFilter(CustomHeaderFilter.java:58)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at com.sap.portal.http.EnrichNavRequestFilter.doFilter(EnrichNavRequestFilter.java:49)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:441)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: com.sap.security.api.umap.NoLogonDataAvailableException: No logon ticket available.
at com.sap.security.core.umap.imp.authndata.LogonTicketAuthnData.<init>(LogonTicketAuthnData.java:57)
at com.sap.security.core.umap.imp.authndata.AuthnDataFactory.getAuthnData(AuthnDataFactory.java:76)
at com.sap.security.core.umap.imp.UserMappingDataImp.enrich(UserMappingDataImp.java:257)
at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:94)
... 64 more

Hi,
Did you implement SSO in the 7.31?
BR,
Saar

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

Cannot show GP process title in universal worklist

Similar Messages

Maybe you are looking for