Alias SAP_LocalSystem

Hi @ all,
I have a webdynpro application an deployed it into a EP 6.
I've set up the SLD, the SSO and I have created a Jco connection. On testing the Jco connection in the WebDynpro "Content Administrator" it seems to work fine.
But if I execute the application in Portal I got some Error Messages. The first one is:
15:33:14:827 , /System/Server , 10/04/2005 , Failed to get system id of alias SAP_LocalSystem , Error , com.sap.portal.ivs.semantic.systemLandscape , sap.com/irj

Can anyone tell me what is wrong?
Regards,
Dennis

Hi Dennis,
Login to your portal with an administrator login, go to User Administration -> User Mapping. There search for the user whom you want to mapp to the 'SAP_LocalSystem' system. Edit the user, select 'SAP_LocalSystem' from the dropdown, provide a valid username & password. Save the changes. This will take acre of your user mapping.
Note that, to run the application, you have to login with the mapped user.
EDITED
Dennis, i'm extremely sorry, You needn't give a user mapping for the SAP_LocalSystem. This is because it is a default system being created to point to the same portal. So user mapping is not your problem.
Best Regards,
Nibu.
Message was edited by: Nibu Wilson

Similar Messages

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

UWL 404 error for 'LeaveRequestApproval'

Hi,
We are working on EP7 sp9 and ECC 6.0, Now the problem is when we are working with UWL in portal, when we click on worklist item(for leave request), we use to get ITS screen. At backend we changed it to 'Java Web Dynpro' USING SWFVISU transaction. In UWL Adminstration we cleared the cache and also re-registered the item types. But when we click on the work item it is throwing the following error.
Can anyone assist me, where we are mistaken?
Service cannot be reached
What has happened?
URL http://sapXXX.XXXXX.com:9904/webdynpro/dispatcher/sap.com/ess~lea/LeaveRequestApprover call was terminated because the corresponding service is not available.
Note
The termination occurred in system DV4 with error code 404 and for the reason Not found.
The selected virtual host was 0 .
What can I do?
Please select a valid URL.
If you do not yet have a user ID, contact your system administrator.
ErrorCode:ICF-NF-http-c:000-u:SAPSYS-l:E-i:klang_DV4_04-v:0-s:404-r:Notfound
HTTP 404 - Not found
Your SAP Internet Communication Framework Team
Thanks in advance.
Regards,
Raj

Hi Raj,
Looks like it is trying to open the WebDynpro application on the (ABAP R/3) backend system. This should be the system on which your ESS WebDynpro's have been deployed.
I guess this is the EP7 system on which your UWL is also running. In this case, go to UWL administration in the portal, and select the system/connector configuration of the ECC backend system. Choose "edit".
There is a property called "WebDynpro Launch System". Here you can enter the alias of the system definition in portal system landscape which refers to the WebDynpro application hosting system.
If this is indeed the EP7 system on which UWL is running, you can use the builtin system alias "SAP_LocalSystem". Otherwise create a WAS system definition referring to the WAS installation hosting the WebDynpro's and use that alias.
Regards,
Johan

Assertion: verticalPosition 0

Hi all
I am suporting user that has received error message like this within berowsing some reports results. I am new in BI therefore any help will be realy appreciated
500 Internal Server Error
BEx Web Application
Failed to process request; contact your system administrator
Error Summary
Exception occured while processing the current request; this exception cannot be handled by the application or framework
If the information on this page does not help you locate and correct the cause of the problem, contact your system administrator
To facilitate analysis of the problem, keep a copy of this error page Hint: Most Web browsers allow you to select all content, and copy and paste it into an empty document (such as in an email or simple text file)
Root Cause
The initial exception that caused the request to fail was:
Assertion: verticalPosition < 0
java.lang.IllegalArgumentException: Assertion: verticalPosition < 0
at com.sap.ip.bi.webapplications.ui.advancedcontrols.universalgrid.impl.AcUniGridGeneric.setVerticalPosition(AcUniGridGeneric.java:227)
at com.sap.ip.bi.webapplications.ui.advancedcontrols.universalgrid.saptable.AcUniGridSapTable.notifyUiPaginationChange(AcUniGridSapTable.java:777)
at com.sap.ip.bi.webapplications.ui.advancedcontrols.paginator.impl.AcPaginator.doNavigateRowPageStartCommand(AcPaginator.java:627)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
Log ID 0017A4772430002D0000004B0000049900045DAF333F8EE8
Details: Full Exception Chain
System Environment
Server
BI Java Release: 7 - Patch level: 0000000013 - Description: BI Web Applications Java - Additional info: - Production mode: true
BI ABAP Release: 700 - Patch level: 0015 - Description: SAP NetWeaver BI 7.0 (SAP_LocalSystem) - Additional info: - Production mode: true
Java Virtual Machine IBM J9 VM - IBM Corporation - 2.3
Operating System Linux - amd64 - 2.6.5-7.283-smp
Context
ACCESSIBLE false
CACHE true
CONTENT_PADDING true
COUNTRY
DEBUG false
DEBUG_LEVEL 0
DEBUG_MESSAGES false
DEBUG_TEXTS false
DISPLAY_STACK_TRACE_IN_ERROR_PAGES true
LANGUAGE en
Master System Alias SAP_LocalSystem
NAVIGATION_NODE_LAUNCHER_URL pcd:portal_content/com.kone.kone/com.kone.Roles/com.kone.PR_Call_out_analyst/Call_out_Analyst/ZBIMNU_CORR_COAN/00000016/00000017
PROFILING false
Query String (Current Browser Request) BI_COMMAND=&BI_COMMAND-BI_ADVANCED=INFO_FIELD_ITEM_1_t_INFO_FIELD_ITEM_1&BI_COMMAND-BI_COMMAND_TYPE=PASSIVE_VALUE_TRANSFER&BI_COMMAND-PASSIVE_ID=INFO_FIELD_ITEM_1_t_INFO_FIELD_ITEM_1_tc&BI_COMMAND-PASSIVE_VALUE=true&BI_COMMAND-TARGET_ITEM_REF=INFO_FIELD_ITEM_1&BI_COMMAND_1=&BI_COMMAND_1-BI_ADVANCED=ANALYSIS_interactive_pivot_left_bottom&BI_COMMAND_1-BI_COMMAND_TYPE=PASSIVE_VALUE_TRANSFER&BI_COMMAND_1-PASSIVE_ID=ANALYSIS_interactive_pivot_left_bottom_paginator&BI_COMMAND_1-PASSIVE_VALUE=2&BI_COMMAND_1-TARGET_ITEM_REF=ANALYSIS&BI_COMMAND_2=&BI_COMMAND_2-BI_ADVANCED=QUERYVIEW_SELECTION_AcDDLBase&BI_COMMAND_2-BI_COMMAND_TYPE=PASSIVE_VALUE_TRANSFER&BI_COMMAND_2-PASSIVE_ID=QUERYVIEW_SELECTION_AcDDLBase_combobox&BI_COMMAND_2-PASSIVE_VALUE=ZG_COR_CLINICA_PRIOR_LIFT_01_default&BI_COMMAND_2-TARGET_ITEM_REF=QUERYVIEW_SELECTION&BI_COMMAND_3=&BI_COMMAND_3-BI_ADVANCED=DROPDOWN_DISPLAY_AcDDLBase&BI_COMMAND_3-BI_COMMAND_TYPE=PASSIVE_VALUE_TRANSFER&BI_COMMAND_3-PASSIVE_ID=DROPDOWN_DISPLAY_AcDDLBase_combobox&BI_COMMAND_3-PASSIVE_VALUE=Option_0&BI_COMMAND_3-TARGET_ITEM_REF=DROPDOWN_DISPLAY&BI_COMMAND_4=&BI_COMMAND_4-BI_ADVANCED=ANALYSIS_interactive_pivot_left_bottom&BI_COMMAND_4-BI_COMMAND_TYPE=NAVIGATE_ROW_PAGE_START&BI_COMMAND_4-TARGET_ITEM_REF=ANALYSIS&REQUEST_ID=7
Query String (Initial Browser Request) BUILDTREE=false&NAVIGATIONTARGET=navurl%3A%2F%2F92bb8192fffeaac665d3278118bec6e3&NAVPATHUPDATE=false&QUERY=ZG_COR_CLINICA_PRIOR_LIFT_01&RELATIVENAVBASE=&SAP-LAFVERSIONS=portal%3A7.0.13.0.1%3Bur%3A7.0.13.1.1&SAP-PP-CONSUMERBASEURL=http%3A%2F%2Fkwportal.kone.com%3A80&SAP-PP-PRODUCERID=BJ4_producer_LB&THEME=Kone
RTL false
Request URL http://bj4j2ee.kone.com:80
SAP_BW_IVIEW_ID pcd:portal_content/com.kone.kone/com.kone.Roles/com.kone.PR_Call_out_analyst/Call_out_Analyst/ZBIMNU_CORR_COAN/00000016/00000017
SAP_EXTERNAL_SID L3qPeYVSc3TG5fymiTefw--WFBMeufqxvZsoSKqv_ElA--
SERVER_URL_PREFIX http://bj4j2ee.kone.com
THEME_NAME Kone
TRACE false
TRAY_TYPE PLAIN
Template (Main Object) ELEM ZG_COR_CLINICA_PRIOR_LIFT_01
Template (Main) ZKONE_PATTERN
Template Parameters <parameterList>
<param name="BODY_ONLY" value="X"/>
<param name="CHECK_POPUP_BLOCKER" value="X"/>
<param name="DATA_MODE" value="NEW"/>
<param name="DOCUMENT_SAVE_LEVEL" value="0"/>
<param name="ERRORS_VISIBLE" value="X"/>
<param name="INFORMATION_VISIBLE" value="X"/>
<param name="ITEMS_STATELESS" value="false"/>
<param name="MELT_VARIABLES" value="X"/>
<param name="REPORT_REPORT_DISPLAY_TARGET" value="X"/>
<param name="RRI_OPEN_MODE" value="OPEN_IN_SEPARATE_WINDOW">
 <param name="OPEN_IN_SEPARATE_WINDOW" value=""/>
</param>
<param name="START_STATELESS_INTERVAL" value="0"/>
<param name="STATELESS" value="false"/>
<param name="SYSTEM_MESSAGES_VISIBLE" value="X">
 <param name="SYSTEM_MESSAGES_DISPLAY_MODE" value="ALWAYS"/>
</param>
<param name="TEMPLATE_VERSION" value="1"/>
<param name="USE_CONTEXT_MENU_SNIPPETS" value="X"/>
<param name="USE_LAYERED_WINDOWS" value="X"/>
<param name="USE_PERSONALIZATION" value="X"/>
<param name="USE_SPECIFIC_VARIANT_CATALOG" value="X"/>
<param name="VARIABLE_SCREEN" value="X"/>
<param name="WARNINGS_VISIBLE" value="X"/>
<param name="WINDOW_MODE" value="modal"/>
</parameterList>
Time Wed Dec 10 12:02:47 CET 2008
USE_HTTPS_FOR_ADS false
USE_SAP_EXPORT_LIB false
User KCOIAR (USER.R3_DATASOURCE.KCOIAR)
Deployed SCAs
SCA Version SP Patch Compiled Deployed
ADSSAP 7.00 13 0 2007-08-12 01:18:54 CEST 2008-02-01 22:14:48 CET
BASETABLES 7.00 13 0 2007-08-12 01:36:38 CEST 2008-02-01 19:32:19 CET
BI-BASE-S 7.00 13 9 2008-04-25 07:00:46 CEST 2008-05-15 13:19:44 CEST
BI-IBC 7.00 13 0 2007-08-12 12:03:28 CEST 2008-02-03 11:20:37 CET
BI-REPPLAN 7.00 13 1 2008-01-04 12:21:05 CET 2008-03-06 11:20:39 CET
BI-WDALV 7.00 13 1 2007-11-05 11:28:29 CET 2008-03-06 11:20:52 CET
BIWEBAPP 7.00 13 9 2008-04-25 07:01:59 CEST 2008-05-15 12:14:34 CEST
BI_MMR 7.00 13 0 2007-08-12 01:37:49 CEST 2008-02-01 22:16:00 CET
BI_UDI 7.00 13 0 2007-08-11 19:04:00 CEST 2008-05-15 18:20:39 CEST
BP_BIADMIN 60.1 5 0 2006-01-18 13:49:00 CET 2008-03-06 17:28:36 CET
CAF 7.00 13 0 2007-08-09 09:23:15 CEST 2008-02-03 11:28:52 CET
CAF-KM 7.00 13 0 2007-08-09 07:54:22 CEST 2008-02-03 11:54:05 CET
CAF-UM 7.00 13 0 2007-08-09 09:23:24 CEST 2008-02-01 22:16:47 CET
CORE-TOOLS 7.00 13 0 2007-08-12 01:41:21 CEST 2008-02-01 19:32:32 CET
EP-PSERV 7.00 13 4 2008-02-05 10:49:39 CET 2008-03-06 11:21:04 CET
EP-WDC 7.00 13 0 2007-08-12 12:41:08 CEST 2008-02-03 11:43:28 CET
EPBC 7.00 13 0 2007-08-12 12:37:44 CEST 2008-02-01 22:19:37 CET
EPBC2 7.00 13 0 2007-08-12 12:38:06 CEST 2008-02-03 11:29:46 CET
JLOGVIEW 7.00 13 0 2007-08-12 00:16:00 CEST 2008-02-01 19:32:45 CET
JSPM 7.00 13 0 2007-08-12 00:17:00 CEST 2008-02-01 19:16:27 CET
KM-KW_JIKS 7.00 13 0 2007-08-12 01:45:19 CEST 2008-02-01 22:19:54 CET
KMC-BC 7.00 13 0 2007-08-12 12:41:47 CEST 2008-02-03 11:30:45 CET
KMC-CM 7.00 13 0 2007-08-12 12:43:04 CEST 2008-02-03 11:31:37 CET
KMC-COLL 7.00 13 0 2007-08-12 12:43:35 CEST 2008-02-03 11:33:32 CET
LM-PORTAL 7.00 13 0 2007-08-09 07:58:38 CEST 2008-02-03 11:33:38 CET
LM-TOOLS 7.00 13 0 2007-09-06 10:46:34 CEST 2008-02-03 11:40:26 CET
NET-PDK 7.00 13 0 2007-08-12 12:45:34 CEST 2008-02-03 11:08:38 CET
RTC 7.00 13 0 2007-08-12 12:48:07 CEST 2008-02-03 11:08:41 CET
RTC-STREAM 7.00 13 0 2007-08-12 12:48:07 CEST 2008-02-03 11:40:31 CET
SAP-EU 7.00 13 0 2007-08-09 08:01:01 CEST 2008-02-03 11:52:14 CET
SAP-JEE 7.00 13 0 2007-08-12 01:53:11 CEST 2008-02-01 19:33:23 CET
SAP-JEECOR 7.00 13 12 2008-04-14 12:47:29 CEST 2008-05-15 12:16:07 CEST
SAP_JTECHF 7.00 13 0 2007-08-12 01:56:44 CEST 2008-02-01 19:35:31 CET
SAP_JTECHS 7.00 13 0 2007-08-12 01:59:51 CEST 2008-02-03 11:42:33 CET
UMEADMIN 7.00 13 0 2007-08-09 09:39:47 CEST 2008-02-03 11:43:56 CET
UWLJWF 7.00 13 0 2007-08-12 12:52:23 CEST 2008-02-03 11:44:29 CET
VCBASE 7.00 13 0 2007-08-12 12:52:34 CEST 2008-02-03 11:54:35 CET
VCFLEX 7.00 13 0 2007-08-12 12:53:39 CEST 2008-02-03 11:54:08 CET
VCFRAMEWORK 7.00 13 0 2007-08-12 12:53:51 CEST 2008-02-03 11:54:14 CET
VCKITBI 7.00 13 0 2007-08-12 12:23:20 CEST 2008-02-03 11:54:38 CET
VCKITGP 7.00 13 0 2007-08-12 12:53:51 CEST 2008-02-03 11:54:41 CET
VCKITXX 7.00 13 0 2007-08-12 12:53:51 CEST 2008-02-03 11:54:44 CET
WDEXTENSIONS 7.00 13 0 2007-08-09 08:05:30 CEST 2008-02-03 11:55:52 CET
Full Exception Chain
Log ID 0017A4772430002D0000004B0000049900045DAF333F8EE8
com.sap.ip.bi.base.exception.BIBaseRuntimeException: Unknown Error at com.sap.ip.bi.webapplications.runtime.impl.Page._processRequest(Page.java:2872) at com.sap.ip.bi.webapplications.runtime.impl.Page.processRequest(Page.java:2632) at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.doProcessRequest(Controller.java:1007) at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller._processRequest(Controller.java:893) at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.processRequest(Controller.java:879) at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService._handleRequest(BIRuntimeService.java:505) at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:236) at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:22) at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209) at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114) at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328) at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136) at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189) at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215) at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645) at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328) at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136) at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189) at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753) 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(AccessController.java:246) 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:387) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266) 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(AccessController.java:219) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)Caused by: java.lang.IllegalArgumentException: Assertion: verticalPosition < 0 at com.sap.ip.bi.webapplications.ui.advancedcontrols.universalgrid.impl.AcUniGridGeneric.setVerticalPosition(AcUniGridGeneric.java:227) at com.sap.ip.bi.webapplications.ui.advancedcontrols.universalgrid.saptable.AcUniGridSapTable.notifyUiPaginationChange(AcUniGridSapTable.java:777) at com.sap.ip.bi.webapplications.ui.advancedcontrols.paginator.impl.AcPaginator.doNavigateRowPageStartCommand(AcPaginator.java:627) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at com.sap.ip.bi.util.MethodInvoker.callMethod(MethodInvoker.java:101) at com.sap.ip.bi.webapplications.runtime.command.CommandProcessorHelper.processCommand(CommandProcessorHelper.java:410) at com.sap.ip.bi.webapplications.runtime.command.CommandProcessorHelper.processCommand(CommandProcessorHelper.java:325) at com.sap.ip.bi.webapplications.ui.framework.base.impl.AdvancedControl.processCommand(AdvancedControl.java:214) at com.sap.ip.bi.webapplications.ui.framework.base.impl.Framework.dispatchAdvanced(Framework.java:206) at com.sap.ip.bi.webapplications.ui.items.UiItem.dispatchAdvanced(UiItem.java:470) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at com.sap.ip.bi.util.MethodInvoker.callMethod(MethodInvoker.java:101) at com.sap.ip.bi.webapplications.runtime.command.CommandProcessorHelper.processCommand(CommandProcessorHelper.java:439) at com.sap.ip.bi.webapplications.runtime.command.CommandProcessorHelper.processCommand(CommandProcessorHelper.java:325) at com.sap.ip.bi.webapplications.runtime.base.CommunicationProcessor.processCommand(CommunicationProcessor.java:174) at com.sap.ip.bi.webapplications.runtime.base.ItemRenderer.processCommand(ItemRenderer.java:53) at com.sap.ip.bi.webapplications.runtime.impl.Page.processItemCommand(Page.java:1479) at sun.reflect.GeneratedMethodAccessor34843.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:62) at java.lang.reflect.Method.invoke(Method.java:391) at com.sap.ip.bi.util.MethodInvoker.callMethod(MethodInvoker.java:101) at com.sap.ip.bi.webapplications.runtime.command.CommandProcessorHelper.processCommand(CommandProcessorHelper.java:439) at com.sap.ip.bi.webapplications.runtime.command.CommandProcessorHelper.processCommand(CommandProcessorHelper.java:325) at com.sap.ip.bi.webapplications.runtime.base.CommunicationProcessor.processCommand(CommunicationProcessor.java:174) at com.sap.ip.bi.webapplications.runtime.impl.Page.processCommandSuper(Page.java:1727) at com.sap.ip.bi.webapplications.runtime.impl.Page.processCommandInternal(Page.java:1706) at com.sap.ip.bi.webapplications.runtime.impl.Page.processCommandSequence(Page.java:2389) at com.sap.ip.bi.webapplications.runtime.impl.Page.doProcessRequest(Page.java:3747) at com.sap.ip.bi.webapplications.runtime.impl.Page._processRequest(Page.java:2792) ... 39 more

Hi Ivan,
have you got resolution for the said error? if yes, what was that, as i am getting same error after applying stack 13 for BW Java.
regards,
Amit

Integrating Portal and PPM

Dear Experts,
I'm trying to integrate PPM's web dynpro abap applications in Portal. My basis team has setup everything regarding SSO and it works OK.
When i define a WDA Iview, I set the following properties (as any standard WDA):
Namespace: sap
Application Name: inm_workcenter_app (this is the WDA that shows Project & Portfolio Management)
System: SAPPPM
Everything works perfect and the WDA is displayed in the iview.
That iview shows a list of the available projects, and when you click one of them, it opens a new window showing the project's detail.
The thing is, that when the new window tries to open, it shows an error that is logged in Portal's default trace as follows:
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template &\#39;<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>/;sap-ext-sid=<ESID[url_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[url_ENCODE]>&sap-wd-tstamp=<$TimeStamp>&<ProducerInfo>&sap-explanation=<User.Explanation[SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>&\#39;; the problem occured at position 310. *Cannot process expression <System.client> because Invalid System Attribute:*
*System: &\#39;SAP_LocalSystem&\#39;,*
Attribute: &\#39;client&\#39;.
I cannot figure out why it's fetching for the alias SAP_LocalSystem because i set up SAPPPM as System in mi iview.
Could anyone please help me?
Any ideas would be appreciated.
Thanks in advance,
Fede

Hi,
Since it's a WDA application can you try running the app from Backend system SE80 and see if it works?
I assume when running the application from Portal it uses Object Based Navigation(OBN) to navigate and open the details in new window.
Within the application there will be code to call the page, make sure you are using the same System Alias within the application and also see the OBN is setup properly.
Can you also verify if the Standard Application from the Business Package works fine.
How to create a direct URL for xRPM Item
How to create a direct URL for xRPM Item
Cheers-
Pramod

Importance of UWL in Guided Procedures.?

Hi,
I need to know the importance of UWL (Universal Worklist) in our Guided Procedures,
One thing that I can visualize is that, All the actions pending for a user can be seen here.
But that we can see in respective workcenter also.Then why do we need UWL seperately?
Also what if I want to terminate some task inbetween,
Is there any option for removing tasks from the list?because all the tasks, with the status as pending or running remains there until they are completed.
Please share....
Thanks
Deepak

Hi,
You have to create new system for GP.
Go to System admin - System config - UWL
click on New button
Fill in the details as below:
System Alias: * SAP_LocalSystem
Connector Type: GuidedProceduresConnector
Rest of the fields are optional
In the UWL - Configuration page, at the bottom, click on the link "Click to Configure Item Types and Customize Views Using a Wizard" , I think u can take it from there..
Add the UWL iview (pcd:portal_content/com.sap.pct/every_user/general/iViews/com.sap.netweaver.bc.uwl.iviews/com.sap.netweaver.bc.uwl.uwl_iview)to ur role.
You can see all ur GP tasks in UWL.
Good luck
Som

Problem creating Bi Iview

Hi All,
We have two Bi 7.0 Systems in our landscape , We want to create BW Iviews for both the systems in Portal . But the problem is BW Iview when selected as BI 7.0 is always taking the master system as its system .. so now all my BI iviews can only point to one system .. Is there any way to create BI iviews to two different systems.
Regards,
Tarun.

Have u tried these
Create Two system objects for two BI systems and give two different Syatem alias for them
Now create a BI Iviews for both BI Reports
Now goto to iview -- open -- property category -- system -- change the system alias SAP_LOCALSYSTEM to ur BI sytem alias u have created
Regards
Krishna.

Errors with UWL iViews

Hi All,
We're on EP 7, sp13. ever since we first installed ep7, we've been seeing errors on all the UWL iViews including the UWL administration iView (under System admin). Upon clicking the iView, i see "Portal Runtime error" and this is true for all users including admin users, i tried previewing the iViews from content admin but still got the same error msg.i retrieved the following from the logs via nwa:
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,
i also referred to the below thread on the same issue:
UWL Administration error
but im really not sure what is the impact of deleting the .bak par file etc as mentioned in the thread above..
Can somebody pls advise on how to troubleshoot this and configure the uwl iViews/service? Thanks!!
cheers
Prachi

This has been resolved - the reference system was set incorreclty in system admin -->ume
~Prachi

Problem with integrating Web Dynpro into anonymous Portal

The problem is that we can't run the Web Dynpro application in combination with an anonymous portal.
We get the following error:
Runtime error portaal
Fout opgetreden bij verwerking opdracht voor :
iView : pcd:portal_content/com.spe.spe_intranet/content/sites/nullAtSPE2/Connecting/nullAtSPE/AtSPE/Random4
Naam component : com.sap.portal.appintegrator.sap.WebDynpro
Exception in SAP Application Integrator occured: ApplicationIntegratorException.
Exception id: 02:31_29/10/07_0168_426375450
See the details for the exception ID in the log file
Detail description of the situation:
At one of our companies we are using a Portal in combination with a Web Dynpro application. The portal is for internal use only so therefore we are using a language specific anonymous user (/irj/portal/anonymous?guest_user=Guest_intra_NL). The Web Dynpro application needs no authentication either. The Web Dynpro applications runs inside an appintegrator iView somewhere on the frontpage. If we set the authentication schema on 'default' instead of 'anonymous' we have to authenticate (inside the iView only). If we authenticate then the Web Dynpro application works fine. So only in combination with a anonymous user the application is not working.
We performed all these settings:
Anonymous user access to Web Dynpro
This is a small part of the trace file:
Component : pcd:portal_content/com.spe.spe_intranet/content/sites/nullAtSPE2/Connecting/nullAtSPE/AtSPE/Random4
Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
User : Guest_intra_NL
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
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:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: ApplicationIntegratorException
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:123)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
... 29 more
#1.5 #00144F790FF0005D00000D8500000D5500043D60120F2656#1193382735975#com.sap.portal.sapapplication#sap.com/irj#com.sap.portal.sapapplication#Guest#0####c817f770839211dc850f00144f790ff0#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/System/Server#Java###Content pass of Application Integrator failed.
Component Name: 'com.sap.portal.appintegrator.sap.WebDynpro',
Context Name (iView): 'pcd:portal_content/com.spe.spe_intranet/content/sites/nullAtSPE2/Connecting/nullAtSPE/AtSPE/Random4',
Top Layer: 'WebDynpro/TopLayer',
Producer ID (FPN): 'null',
System Alias: 'SAP_LocalSystem',
[EXCEPTION]
#1#com.sapportals.portal.appintegrator.ApplicationIntegratorException: ApplicationIntegratorException
 at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:96)
 at com.sapportals.portal.appintegrator.accessor.system.SAP_LocalSystemAccessor.getAuthenticationData(SAP_LocalSystemAccessor.java:83)
 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:522)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
 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:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
 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:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.security.api.umap.NoLogonDataAvailableException: No logon ticket available.
 at com.sap.security.core.umap.imp.UserMappingDataImp.getAuthenticationTicket(UserMappingDataImp.java:1772)
 at com.sap.security.core.umap.imp.UserMappingDataImp.enrich(UserMappingDataImp.java:351)
 at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:91)
 ... 33 more
#1.5 #00144F790FF0005D00000D8700000D5500043D60120F3B56#1193382735981#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Guest#0####c817f770839211dc850f00144f790ff0#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/System/Server#Java###Exception ID:09:12_26/10/07_0701_426375450
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/com.spe.spe_intranet/content/sites/nullAtSPE2/Connecting/nullAtSPE/AtSPE/Random4
Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
User : Guest_intra_NL
 at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
 at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
 at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
 at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
 at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
 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:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
 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:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: ApplicationIntegratorException
 at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:123)
 at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
 ... 29 more
Hopefully someone has any clues. Thanks in advance. Of course will I reward points for the solution.
Grtz, JM

Hi Kelly,
the point here is native SharePoint integration. If your company does not have a SharePoint strategy then I absolutely agree with you. There are plenty of ways on how you can integrate WebDynpros, iViews, and other "SAP views" in SharePoint.
The "problem" with these integrations is always that it is not a native / low-level integration. It is just an iFrame within SharePoint that contains data coming from another system. This means that this data is isolated from any other functionality that is available in SharePoint.
Of course this can be enough for some usecases (maybe for all of yours ), but there are lots of companies who do want to leverage all of SharePoints (collaborative) functionalities. In this case Duet Enterprise does offer a way to integrate SAP objects into SharePoint on a "low-level". All objects that are integrated into SharePoint are then available as "real" SharePoint objects. You can work with them like with any other SharePoint object. You can even offline them using standard SharePoint functionalities. You can bring them to Outlook without any major development, ...
All this because we not only include an isolated iFrame in SharePoint, but really integrate the data.
Like I said: there are certainly usecases where this is not required and a simple iFrame is all that you need. However, we have seen in several projects now that there is also a requirement / need for a "deeper" integration.
Regards,
Holger.

BPM - "UWL connector"

Hi,
Appreciate your kind clarification on system alias SAP_LocalSystem in BPEMUWLConnector. Is it a default system alias? If so how transport will affect once I transport from dev to quality. Because after transport UWL status in failed.
So please let me know how to test the connection & what system the alias pointing to. and refer std. documents.
Thanks in advance,
cheers.
dev

Hi Radhesh,
If you need to get some BPM skills then try the BPM space itself or better yet the Process Orchestration space has the most recent materials by checking out the materials in http://scn.sap.com/community/process-orchestration
Apart from that the BPM forum can help you, but it's always best to post one question at a time.
Perhaps you could be clearer about what you are looking for?
Is it an approach to the process?
Is it how to call the backend system?
Is it how to work with the user interfaces?
Think about it carefully and then start a new discussion for each issue.
Rgds,
Jocelyn

If statement in select statement alias

I have the following select statement. It has the alias Survivors, Deaths and "All Cases". Is it posible to use :P_LANGUAGE variable to say that -- IF :P_LANGUAGE = FRENCH THEN alias are Survivants for survivors, Décès for Deaths, Tous_les_cas for All Cases. Please advise
SELECT ALL T_NTR_MULTIBAR.CAT, T_NTR_MULTIBAR.NUM_CASES_LEFTBAR AS Survivors,
T_NTR_MULTIBAR.NUM_CASES_MIDDLEBAR AS Deaths, T_NTR_MULTIBAR.NUM_CASES_RIGHTBAR AS "All Cases"
FROM T_NTR_MULTIBAR
WHERE INSTANCE_NUM = :P_INSTANCENUM
order by ORDERS

You may not be able to add this condition inside the SQL Statement. But you can add this condition outside the statement, if you're using PL/SQL...
IF :p_language = french THEN
SELECT ALL t_ntr_multibar.cat,
t_ntr_multibar.num_cases_leftbar AS survivors,
t_ntr_multibar.num_cases_middlebar AS deaths,
t_ntr_multibar.num_cases_rightbar AS "All Cases"
ELSE
END IF;

Unable open Project details or a project from PWA Project server 2010 with Alias name

Hi,
I am unable to open the Projects from Project center with the Alias name with the server name i am able to open the projects, version is project server 2010,
My system is ABC.DC.IN alias name i have given is DEF.AD.COM
With the system name i can able access PWA and all are working fine.
As i have observed with alias name i can able to login to pwa and all the server setting approval center all are working fine but only in the project center i am not able to open the projects (http://DEF.AD.COM/pwa/ProjectDrillDown.aspx .xxxx)
its is coming in the below of the ie.
But with Alias name these are the issues i am facing,
1.when longing with alias name its asking two times for user name and password
2.when i click on a project from project center its taking some time and asking for user name and password after i enter user name and password "PAGE cannot displayed" error i am getting.
can any one Help me.
vijay kommireddi

Hi Eric,
Thanks for your Reply.
As you said i have added in Manged Path as (Testpwa/projects.aspx as <Wildcard inclusion>) But still problem is there it is asking user
name password again if click on any project in project center and and showing page cannot be displayed error.
This is url its is showing in the below of the IE ( http://def.ad.com/testpwa/projectdrilldown.aspx?ProjUid=e28c6d43-85b6-478d-9542-2961cc81a69e)
I have observed one more thing if click on Project
details then only this issue is coming project schedule and project information
is also opening with Alias name.
My farm version is 14.0.7015.1000
Vijay Kommireddi

How to change the Existing alias with new alias name...MAXL SCRIPT

HI Experts
I need to change alias name of the existing member with new alias name.
please send me maxl code to change the alias name .
My thought is
1) Old alias should be replaced with new alias name .
2)There is one account that should be rolled out to another parent..these parents are already exsist
3) I need a MAXL Script to change the new alias name .
please suggest ASAP.
Thanks
USER

John
I heard that we can replace existing alias name with new alias thru MAXL
i.e replace alias name XXXX member with YYYY ;
please correct me if iam wrong ,might be Maxl command is wrong but this is the idea.
Thanks
USER

HT4436 How can I transfer my odl family pack email to new iCloud id? Or add a new email account (not an alias) to my main icloud id?

I had a family pack but now I am not able to reach my son's email account. How can I find and transfer it? Or how can I open a new email account for my son through my icloud id. Actually it seems as if there is an oprating email account under his name but e-we cannot receive any emails or cannot reach the account settings...

Each sub-account of a MobileMe Family Pack should have been individually migrated to iCloud before August 1st last. Assuming that you didn't do this, you should be able to reactivate the address (though not retrieve its previous contents) by signing in with it in System Preferences>iCloud and enabling Mail - your son should do this on his own Mac or his own user account if he is using your Mac. It's not clear whether he will be able to reactivate the @me.com version or only get an @icloud.com version. (It would be useful to know, when he tries it.)
If he did migrate the account to iCloud then signing in in the same way should retrieve the contents and the @me.com address should work.
Alternatively he can just create a new Apple ID (for which he will need a new non-Apple email address) if he doesn't already have one, and sign in with that, enabling Mail and choosing a new @icloud.com address.
You should note that in none of these cases does his account have anything to do with yours (there is no need for a Family Pack equivalent in iCloud as it's free at basic level).
You could add an email alias to your account, but it's not a good idea as it will mix his emails up with yours and he won't be able to detach it later.

Problem in creation of system alias for bw system

Hi,
I want to create system alias for the bw system
system admin->sys Config->system landscape->portal content->my own folder
for this folder i created the system object
after creation of system object, from property category i select the connector and give the details.
after that i select the user management and give
authentication ticket - select
Logon method- UIDPW
User Management type- admin,user
i saved till now
in the display object i select the system alias
then that screen displays
In the system alias screen, i clicked on add button for adding alias then we r getting this message.
User Mapping Status: (Not ready for user mapping configuration)
Please give the solution for solving this problem
Regards,
Sid.
Edited by: sid m on Mar 11, 2008 12:15 PM

Hi Krishna,
I checked the connection settings.
WAS settings in system object is giving this mistake
before user mapping it works fine.
after giving usermapping i ma getting this exception.
SAP Web AS Connection
Test Details:
The test consists of the following steps:
1. Check the validity of the system ID in the system object
2. Check whether the system can be retrieved
3. Check whether a SAP system is defined in the system object
4. Validate the following parameters: WAS protocol; WAS host name
5. Check HTTP/S connectivity to the defined backend application
Results
1. The system ID is valid
2. Retrieval of the system was successful
3. The system object represents an SAP system
4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (172.19.18.75)
5. HTTP/S connection failed
for testing the connector i am getting this exception
Test Connection with Connector
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the backend application using the connector defined in this system object
Results
Retrieval of default alias successful
Connection failed. Make sure user mapping is set correctly and all connection properties are correct.
Regards,
Sid.

Alias SAP_LocalSystem

Similar Messages

Maybe you are looking for