Iview in innerpage not working

Iview in innerpage of desktop not working in production, same iview working fine in development server. Please provide help in the above regards.

What is "not working" please be more specific...
- What kind of iView do you use (WD4J, WD4A, URL, others? If others, which?) ?
- Are you getting any error?
- If yes, post all regarding error logs here from NWA tracelog, ST22, etc.
regards, Lukas

Similar Messages

Transactional iview for "session_manager" not working

Dear All,
we are creating transactional iview for t code "session_manager", the problem we are facing is that it is not going to session_manager screen, instead of that it is going to S000 Transaction.
I tried using webgui also, but here I m facing some strange problem, it is using webgui for one user and for rest it is using wingui for others and again going to S000 t code.
Can you please give me some recommendations?
Thanks,
Ganesh

Hi Ganesh,
Are the Tcodes "Service_manager", S000 user defined tcodes?
cheers
dev

URL iView content translation not working using Portal Content Traslation

Hi All,
I am using Portal Content Translation to translate text of URL iView from English to Spanish. I am unable to do so. I have followed the below mentioned link:
http://help.sap.com/saphelp_nw04/helpdata/en/74/641640b7b6dd5fe10000000a155106/frameset.htm
I have used Content Admin -> Portal Content Translation -> Translation Worlist Coordination to:
1) Generate worklist and add content
2) Generte translation data
3) Release for translation
After this, I am using Content Admin -> Portal Content Translation -> Worklist Translation for following:
1) Load worklist for translation
2) Translate worklist
I am facing difficulty in Translate Worklist. The step by step method followed by me are as below:
I am clicking on Content Admin -> Portal Content Translation -> Worklist Translation.
I am searching Translation Worklist and selecting my Worklist
After this I am selecting following
Source Language - English
Target Language - Spanish
Then I am clicking on 'Load for Translation' button. New screen appears. In this screen, Translatable Text table is shown:
It shows following
Number
Source Text <EN>
Target Text <ES>
Status
Object ID
In Status I can see 'Not Translated'. I click on Next for three times as there are three line Number (0, 1 & 2)
The Status does not change. It remains 'Not Translated'.
When I am using following combination
Source Language - Raw Texts
Target Language - Raw Texts.
I click on Next for three times as there are three line Number (0, 1 & 2). The status changes to Translated.
I do not know what is going wrong with my process while selecting Source Language - English & Target Language - Spanish .
I have another question. I have to translate content of entire URL iView. How I can change the whole content of URL iView.
In the source text I can NOT see the contents of URL iView.
Thanks
Stuart

Hi Prakash,
Did you check whether the translation has been done completely in PCD inspector? Some times you would have translated using Portal translation but it will not be written in the locale of the iView property. Then we have to set it manually in the PCD inspector.
Follow the procedure.
1. navigate to System Administration -> Support -> Portal Content Directory -> PCD Inspector
This will open the PCD inspector.
2. "Browse Into" the iview where you have developed it.
3. Click on the "All Props" for the iView which you need to translate.
This will open the Properties in new window
4. Check the property "com.sap.portal.pcm.title" what is maintained in Chinese? if it still displaying in English text against Chinese, Then you need to Edit the property for chinese and have to give the actual chinese word.
Note : I hope you would have selected "Raw Text" for Source language and "Chinese" as Target language. Pls confirm on this.
Thanks,
Mahendran B.

F4 help is not working in IAC Iview

Hi,
There is IAC iview for transaction PA61
F4 help is not working for the iview
it workes in backend SAP PA61
kindly give any hints what can we check
thanks in advance
b

Hi,
This might be due to the JRE version of the browser. We faced such issue and the update of JRE version in the browser helps to get the pop-up of F4 help. Check in the internet broswser Tools -> Internet Option -> Advanced. Check whether the JRE applet is checked or not. it has to be checked. if it is checked and even if you dont get the F4 help, upgrade the JRE version.
Thanks,
Mahendran B.

NW 7.3 + iView from remote source wizard + R3 Web Dynpro ABAP, not working

Hi,
I think this forum is my last resort.
I'm running NetWeaver 7.3 Enterprise Portal and also have an existing ECC6 on backend.
Our ABAP Programmer has built some WD4A application on ECC, I'd like to made them available
on EP as ABAP WebDynpro iView.
From the document, I know the way to create ABAP WD iView is different since 7.3. I have to use "iView from remote source" to do it.
On EP side, I have made an system alias (test ok) for ECC, assigned permission, provide mapping id/pwd, and test.
On ABAP side, all webdynpro app are activated (T-code sicf, /sap/bc/webdynpro, /sap/public/bc/webdynpro...). I can even test WAS by bringing up browser and access some sample ABAP webdynpro .
However, I cannot success on "iView from remote source" wizard and it always show me "Nothing found. Check your search Criteria.". Eventhough I use "*" as search criteria.
Anyone has the similar situation ? I even doubt that it is a placeholder of a feature , not working for now. Anyone made it work on NW 7.3 ?
More detail:
My System Alias for ECC:
 Application Host: myr3.mydomain.com
 SAP Client: 600
 SAP System ID: DEV
 SAP System Number: 00
 Server Port: <leave it blank>
 System Type: SAP_R3
 Logon Method: UIDPW
 User Mapping Type: admin,user
 ICM Host: myr3.mydomain.com:8000
 ICM Protocol: http
 ICM URL prefix: <leave it blank>
 SAP Netweaver AS Description: <leave it blank>
All other fileds are leave it as default value
I also assign a group to have "read" and "user" permission to this system
Also assign Alias to the system.
I also create a user belong to the group, assign his system mapping an ECC user ID & PWD to it.
I tested the System alias, it is working (both WEB AS test, and R3 test)
Then I try to create an iView on EP, under a PCD folder , new->iview->iview from remote source. A wizard show up. Then I can select the ECC alias just created, and provide * as application search criteria, and then select "WEB DYNPRO ABAP" as the application type. Then "GO"
as I mentioned, it always show "Nothing Found. Check your search crieteria"
But I'm sure the web dynpro applications are activated on R3.
OK, that's it, please help this one. Thanks
IF YOU DID MAKE IT WORK ON YOUR NW 7.3, PLEASE DROP A LINE HERE SO I KNOW IT IS MY OWN PROBLEM !!!
Edited by: Wilson KU on Nov 14, 2011 10:42 AM
Edited by: Wilson KU on Nov 14, 2011 10:46 AM

Thanks for the reply,
[About Backend]
I feel confident about the backend R3 system because I can use the WAS URL to access the sample WD4A application, for example, I can bring up the wd4a application ui in my browser. It is purely browser and R3 stuff, no EP involved.
http://soeprdev.mydomain.com:8000/sap/bc/webdynpro/bobf/demo_sales_order?sap-client=600&sap-language=ZF
I also already activate all nodes and sub-nodes (in SICF Services) under /sap/bc/webdynpro as well as /sap/public/bc/webdynpro. (and some other nodes to make icon and include work)
[About the system object in EP]
I have done all kind of test on the system object (alias):
1. In EP System Administration -> Landscape Configuration, I select the system object, click "Test Connection", It shows me a Check mark, and the detail message is SOE_DEV_600 connection
2. Edit the System object, then click on "Connection Tests" page, I see two lines there, check both and click test, here is the result:
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 if the system can be retrieved
3. Check if the system object has a valid system alias
4. Check if an SAP system is defined in the system object
5. Validate the following parameters: Web AS protocol; Web AS hostname
6. Checks if the host name of the server can be resolved.
7. Pings the Web AS Ping service (works only if the service is activated on the Web AS, and only on ABAP Web AS)
8. Check HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. System retrieved successfully
3. Retrieval of the default alias was successful
4. The system object represents an SAP system
5. The following parameters are valid: ICM Protocol (http) ICM Host Name (soeprdev.mydomain.com:8000)
6. The host name (soeprdev.mydomain.com) was resolved successfully
7. The Web AS ping service http://soeprdev.mydomain.com:8000/sap/bc/ping was pinged successfully
8. An HTTP/S connection to http://soeprdev.mydomain.com:8000 was obtained successfully.
Connection Test for Connectors:
: Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the back-end application using the connector defined in this system object
Results
Default alias retrieved successfully
Connection successful

Hyperlink not working in KM Iview

Hi All,
I have created a html file in KM which has hyperlinks to other html in the same folder.
When i click the preview of html in km folder the hyper link works fine.
But when i create an KM document ivew and attach the html link there, the hyperlink in the attached html does not work ?
Please can anyone guide me on this.... any properties of ivew i need to set ?
why is it that the hyperlink works in km preview and not when embeded in an Iview.
Regards,
Sanjyoti.
Edited by: sanjyoti lengare on Apr 1, 2010 10:32 AM

Hi Sanjyothi,
Follow the below steps:
1) To create Internal Link, first we need to upload some documents into the KM repository.
2) Uploading Documents: Go to Content Management -> Explorer, on Detailed Navigation area.
Click on Folder on the Object Based Navigational Area, New -> Upload.
3) Upload some documents in the same folder which we have created i.e. Test, the file can be a text file, pdf or any other word document. Incase you have problem uploading the file then please go through this wiki link.
https://wiki.sdn.sap.com/wiki/x/kdc
4) For your understanding the documents which you have uploaded are saved in database in the form of BLOB or CLOB.
5) Now again click on Folder on the Object Based Navigational Area, New -> Link
6) Select the document for which you want to create a Link.
7) Now create an iview, through which we can view the document.
8) Go to Content Administration -> Portal Content
9) To avoid confusion it is recommended to create a Folder in which you can create the iView.
10) Select the Folder you have created.
11) Right Click on the Folder choose New -> iView.
12) In the displayed iView wizard, choose iView template (This is the SourceType in the RoadMap)
13) Click next, in the template selection wizard choose KM Document iView and click next
14) In the general properties provide iView name, id, and description and click Next button
15) In the next step click Open Object for Editing and click ok button
16) In the properties view, edit the path so that the iView which we are creating points to the document which we have uploaded.
For Example if there is a document which is uploaded in Documents folder. Give the path of the document. E.g.: /documents/< folder name>/<file_name>
17) Save the changes and preview the iView which displays the file contents.
Regards,
Ponneswari.
Edited by: Ponneswari Adapa on Apr 5, 2010 9:15 AM

Portal buttons not working for transaction type iviews

Our buttons on our portal transaction programs quit working. We are currently on ecc6,ehp5, portal 7.02. The buttons still work on our test and production systems, so it's not a browser issue. The buttons work on the newer webdynpro programs in our dev portal. Please get back with me if you have any ideas on how to fix this button problem. Thanks, Mike

Hi Ajay,
Double posting
[ITS services not working for Transaction iview with gui for html -;
Thanks
Siva

Standard Leave iView of ESS does not work... What to do?

Hi Experts,
We are implementing ESS / MSS. Most of the iViews of ESS are working fine. However, iView of Leave Request is not working.
1) Is it possible that during the portal installation due to some error, some of the components needed for Leave Request has not got installed properly.
2) If yes, can we take the dump / par / WD file of other SAP EP system and import it in my portal.
3) If no, what is the remedy for the solution.
Please suggest. I am getting following message while running application in web dynpro content administration :
An object with ID portal_content/com.sap.pct/srvconfig/com.sap.pct.erp.srvconfig.ess.employee_self_service/com.sap.pct.erp.srvconfig.lea/com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.LeaveRequest does not exist.
Regards,
Gary

Hi Pinki,
Case 1:
From content admin --> portal content > Content Provided by SAp>End User Content > Employee Self-service> Iviews--> working time I am getting following error message:
iView : The initial exception that caused the request to fail, was:
   com.sapportals.portal.prt.runtime.PortalRuntimeException: Failed in WD JNDI lookup. javax.naming.NameNotFoundException: No child found in WebDynproContext with name base
    at com.sap.portal.pcm.iview.admin.AdminBaseiView.createAttrSetLayersList(AdminBaseiView.java:357)
    at com.sap.portal.pcm.iview.admin.AdminBaseiView.getAttrSetLayersList(AdminBaseiView.java:205)
    at com.sap.portal.pcm.iview.admin.AdminBaseiView.getCustomImplementation(AdminBaseiView.java:148)
    at com.sap.portal.pcm.admin.PcmAdminBase.getImplementation(PcmAdminBase.java:530)
    at com.sapportals.portal.ivs.iviews.IviewServiceObjectFactory.getObjectInstance(IviewServiceObjectFactory.java:442)
    ... 40 more
Case 2:
From Content Admin> Webdynpro> Deployed content (int he left side panel) >sap.com> sap.com/ess~lea I am getting following error message:
An object with ID portal_content/com.sap.pct/srvconfig/com.sap.pct.erp.srvconfig.ess.employee_self_service/com.sap.pct.erp.srvconfig.lea/com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.LeaveRequest does not exist.:
com.sap.xss.config.FPMInconsistentObjectException: An object with ID portal_content/com.sap.pct/srvconfig/com.sap.pct.erp.srvconfig.ess.employee_self_service/com.sap.pct.erp.srvconfig.lea/com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.LeaveRequest does not exist.
Thanks
Gary
     at com.sap.xss.config.pcd.PcdObjectBroker.retrieveObjectInternal(PcdObjectBroker.java:90)
     at com.sap.xss.config.pcd.PcdObjectBroker.retrieveObject(PcdObjectBroker.java:47)
     at com.sap.xss.config.domain.PersistentObjectManager.retrieveObjectInternal(PersistentObjectManager.java:106)
     at com.sap.xss.config.domain.PersistentObjectManager.retrieveObject(PersistentObjectManager.java:80)
     at com.sap.xss.config.FPMRepository.retrieveObjectInternal(FPMRepository.java:83)
     at com.sap.xss.config.FPMRepository.retrieveObject(FPMRepository.java:66)
     at com.sap.pcuigp.xssutils.ccpcd.FcXssPcd.initializeConfiguration(FcXssPcd.java:816)
     at com.sap.pcuigp.xssutils.ccpcd.FcXssPcd.loadConfiguration(FcXssPcd.java:250)
     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcd.loadConfiguration(InternalFcXssPcd.java:178)
     at com.sap.pcuigp.xssutils.ccpcd.FcXssPcdInterface.loadConfiguration(FcXssPcdInterface.java:138)
     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcdInterface.loadConfiguration(InternalFcXssPcdInterface.java:148)
     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcdInterface$External.loadConfiguration(InternalFcXssPcdInterface.java:240)
     at com.sap.pcuigp.xssutils.ccpcd.CcXssPcd.loadConfiguration(CcXssPcd.java:282)
     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalCcXssPcd.loadConfiguration(InternalCcXssPcd.java:184)
     at com.sap.pcuigp.xssutils.ccpcd.CcXssPcdInterface.loadConfiguration(CcXssPcdInterface.java:115)
     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalCcXssPcdInterface.loadConfiguration(InternalCcXssPcdInterface.java:124)
     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalCcXssPcdInterface$External.loadConfiguration(InternalCcXssPcdInterface.java:184)
     at com.sap.xss.essservices.cc.ccesspcd.CcEssPcd.loadConfiguration(CcEssPcd.java:268)
     at com.sap.xss.essservices.cc.ccesspcd.wdp.InternalCcEssPcd.loadConfiguration(InternalCcEssPcd.java:169)
     at com.sap.xss.essservices.cc.ccesspcd.CcEssPcdInterface.loadConfiguration(CcEssPcdInterface.java:115)
     at com.sap.xss.essservices.cc.ccesspcd.wdp.InternalCcEssPcdInterface.loadConfiguration(InternalCcEssPcdInterface.java:124)
     at com.sap.xss.essservices.cc.ccesspcd.wdp.InternalCcEssPcdInterface$External.loadConfiguration(InternalCcEssPcdInterface.java:202)
     at com.sap.pcuigp.xssutils.ccxss.CcXss.loadConfiguration(CcXss.java:209)
     at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXss.loadConfiguration(InternalCcXss.java:153)
     at com.sap.pcuigp.xssutils.ccxss.CcXssInterface.loadConfiguration(CcXssInterface.java:112)
     at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface.loadConfiguration(InternalCcXssInterface.java:124)
     at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface$External.loadConfiguration(InternalCcXssInterface.java:184)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:187)
     at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:756)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     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)

Learning Solution: Instructor / Tutor iView(s) not working in Portal

Hi all . . .
We just installed the Instructor/Tutor package in our sandbox portal. I gave the role to myself so that I could see the Instruction and Tutoring tab. Yet, when I click on Work Overview to see the Instructor's Work Center iView, it throws a Portal Runtime Error. I have already reviewed the following:
Link: Instructot iview is not working in portal
This gave me some ideas, but no real help.
I have also reviewed
Link: http://help.sap.com/erp2005_ehp_03/helpdata/EN/44/5f713e28cf4688e10000000a11466f/content.htm
and ensured that I created the entry for the system required (connection tests ran successfully - with the exception of the ITS connection test - citing that port number not found in host name - but it's like this in Production so apparently it's not needed ) . . . and I assigned the SAP_ERP_TrainingManagement alias name to the system.
Here is the respective result in the defaultTrace file. Any ideas?
#1.5 #00145EC81CCC0046000001250016503800045BAA531ED439#1226687003939#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#44785#915##n/a##2f73d450b27911dd8ba700145ec81ccc#SAPEngine_Application_Thread[impl:3]_12##0#0#Error#1#/System/Server#Java###Exception ID:01:23_14/11/08_0002_8013050
[EXCEPTION]
{0}#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/com.sap.pct/specialist/com.sap.pct.erp.instructor.bp_folder/com.sap.pct.erp.instructor.roles/com.sap.pct.erp.instructor.instructor/com.sap.pct.erp.instructor.instructor/overview/com.sap.pct.erp.instructor.work_overview/com.sap.pct.erp.instructor.work_overview/com.sap.pct.erp.instructor.instructor_worklist
Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
User : 44785
 at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:973)
 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: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: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template '<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]>&<ProducerInfo>&sap-explanation=<User.Explanation[SAP_BOOL]>&<StylesheetIntegration[IF_false PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 310. Cannot process expression <System.client> because Invalid System Attribute:
System: &#39;SAP_LocalSystem&#39;,
Attribute: &#39;client&#39;.
 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 #00145EC81CCC0046000001270016503800045BAA531F1371#1226687003955#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#44785#915##n/a##2f73d450b27911dd8ba700145ec81ccc#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Java###01:23_14/11/08_0002_8013050
[EXCEPTION]
{0}#1#com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template '<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]>&<ProducerInfo>&sap-explanation=<User.Explanation[SAP_BOOL]>&<StylesheetIntegration[IF_false PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 310. Cannot process expression <System.client> because Invalid System Attribute:
System: &#39;SAP_LocalSystem&#39;,
Attribute: &#39;client&#39;.
 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)
 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)

Hi Anagha,
I am integrating the ABAP Webdynpro into GP Process callable object. When I click on the task I am getting the following error.
Please help
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.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;.
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)

IView not working when added to workset

Hi all,
I have come across a very strange scenario.
I have deployed a PAR file created in NWDS & created an iView out of it. When I preview the iView, it works fine. But when I add the iView to the workset and assign a role to the workset & try viewing the iview, it doesn't work!! There's no error msg displayed. The log file lists a NameNotFoundException.The iView contains inputfields & buttons. there's a Fileupload UI element in the iView. That alone works. None of d other button click events work. What could be the reason? Can someone help me?
Any help in this regard will be rewarded.
Regards,
M.Subathra

Hi Subathra,
When you are able to see the iView from preview and not from the iView link, then there is sure to be a error in the creation process. Do the following:
1. Run the application from the Content Administration->Web Dynpro->Deployed contents.
2. From the browser address, copy the workspace and application name.
3. Edit the iView properties and replace the workspace and application name, with the copied ones.
Ensure there is no blank space prefix/suffix to workspace or application name.
Regards,
Srinivasan T

Bookmark not working in BW query report iview in EP?

Dear all
When i was clicking on "bookmark" button in SAP BW Query iview ..nothing is displaying.
do i need to give any properties of that iview. or do i need to do any configs in BW level.
Pl suggest me
rgds
pradeep

Our experience has been that the bookmark button does not work in the EP. If you select bookmark from the context menu it should work fine
Stan

BugsEye iView does not work in EP6.0 sp10

Hello,
We are using SRM and we also want to use BugsEey but the iView does not work. When i ask a preview i get the following error message.
Could not find portal application PDKSystem
Is there anybody who can help me to solve this
Thanks
Kurt

Hi Kurt,
did you change the URL in the BugsEye iView?
To do that, open the mySAP SRM: Content Management folder, right click the BugsEye ECM iView and choose Edit -> Object. In the Property Category drop down menue select Show all. Search for the Content Link property.
The default is something like http://<server>:<port>/DemoCat/servlet/BugsEyeSAP?cmd=login&...
Change this link to your URL (in my case it was something like http://reg/servlet/BugsExeSAP?cmd=login&...) If you don't know which link to use, call your SRM admin to give you the exact URL; after that you should control your link by calling it directly in the browser. If it works, change the URL in your iView.
Hope that helps,
Frank

Business Planning is not working in Portal BI iviews

it give me error of JCO . SLD is fine, and JCO is configured but it still does not work. help me please

Hi,
Please refer to this link : http://help.sap.com/saphelp_nw04s/helpdata/en/fa/c1194276e0de2ce10000000a1550b0/frameset.htm. This documentation provides all the information you need to configure and run business planning on Portal.
Just refer to the section Tasks -> Business Planning Scenario Variant. It refers to the JCo Connections and other configurations you would need to maintain.
Hope this helps.
Cheers,
Sunil
PS: Reward points for helpful answers.

Qiuck link is not working for pages/iViews

Hello,
I have set the quick link property of a page that is assigned to the role and named it myQuickLink but when I browse to:
http://<server>:50000/irj/portal/myQuickLink after the logon page I am not being directed to that page.
The user I am trying with has this role assigned and has access to that page.
Anything I'm missing here?
Roy

Hi.
Please, check the following tread Quick Link not working.
Hope it helps.
Best regards,
Aliaksandr

SSO to R3 not working after system copy

Hi Experts,
Recently our QA R3 client XXX was deleted and the whole system was rebuild using system copy of client ZZZ of R3 production. Now we had to reconfigure the SSO between portal and QA R3 with the new client.
But it is not working. It was found that the QA R3's own self signed certificate shows CN=ERP (same as R3 Prod) and not ERU as it should have been. We changed the CN value to ERP,in Visual Admin (Services ->key storage , Ticket ). Still the result is same.
How to re-generate the self signed certificate in R3 with CN=ERU ?
or a workaround for this problem.
Regards
Jimmy

HI Jayendra
Recreate the saplogonticketkeypair following the procedure outlined here
http://help.sap.com/saphelp_nw70/helpdata/en/75/c80b424c6cc717e10000000a155106/content.htm
Then you can export the SAPLogonticketkeypair-cert (public key certificate) of the Java AS and import it into the target ABAP system
Important: the following two steps must be done in the ABAP client that will receive the logon tickets i.e the ABAP client that the component/application on the Java AS is configured to connect to e.g the client specified in the portal iview properties or the client specified in a Web Dynpro JCo Destination
(1) Import the public-key certificate of the Java AS into the ABAP systems certificate list using transaction STRUSTSSO2
(2) Add the certificate to access control list
When adding the certificate to the ACL the SID should be set to the SID of the ticket issuing Java AS and the client should be set to the client that the Java AS is writing to the logon tickets i.e the value of login.ticket_client in the Java AS
Remember, in an Add-In installation, where the system IDs are the same, you must change the default client for the J2EE Engine (000) to a client that does not exist on the SAP Web AS ABAP system e.g change login.ticket_client to 999
See: http://help.sap.com/saphelp_nw70/helpdata/en/cb/ac3d41a5a9ef23e10000000a155106/content.htm
The reason for this change is that the system ID and client combination must be unique when tickets are to be accepted by an SAP Web AS ABAP system
By the way it is better to start a new thread with your question rather than bumping a thread that was already set to 'answered'

Iview in innerpage not working

Similar Messages

Maybe you are looking for