Random model exception in WD application

Hi,
I am using NWDS CE 7.1 Ehp1.
I have 3 web dynpro DCs in which I have imported a ARFC2 model for same RFC.
This application was working fine in all three landscapes dev, test and prod.
There was a change in table type parameter in this RFC which is working fine when tested from SAP.
I re-imported this model in 2 out of 3, WD DCs and transported in dev, test and prod.
Since then I am facing following issue: -
Application works fine sometimes and sometimes it gives following exception:-
java.lang.IllegalArgumentException: Target role name 'About_Me' not defined for model class 'com.vendor.javaportal.homepage.userdetails.userdetails.Z_Empprof_Getdetails_Output'
    at com.sap.tc.cm.base.model.BaseGenericModelClass.retrieveTargetRoleInfo(BaseGenericModelClass.java:104)
    at com.sap.tc.cm.base.model.BaseGenericModelClass.setRelatedModelObjectsInternal(BaseGenericModelClass.java:562)
    at com.sap.tc.cm.base.model.BaseGenericModelClass.setRelatedModelObjects(BaseGenericModelClass.java:537)
    at com.sap.tc.cm.arfc2.model.ARFC2GenericModelClass.setRelatedModelObjects(ARFC2GenericModelClass.java:490)
    at com.sap.tc.cm.arfc2.gci.ARFC2TypedModelClass.setRelatedModelObjects(ARFC2TypedModelClass.java:199)
    ... 76 more
I did some preliminary investigations: -
1.     I initially thought about a transport problem on one of the AS but prod server has only one single AS.
2.     The RFC has been tested in SAP R3 in all application servers and is working fine.
3.     JCO connections from WD to SAP are up and running fine.
Any idea what is going wrong here?
I also tried to reimport model for two erroneous DCs and created a activity each and transported to Prod.
but still same strange behavior!
Please help.
Regards,
Amey

Hi Pradeep,
Thanks for reply, but I have already re-imported the model and transported it.
Still I get this exception.
First time when I re imported the model after RFC change, it showed some deltas in re import.
I transported this activity to prod and I started getting this exception randomly.
Sometimes the application works fine but sometimes it runs into above mentioned exception.
So I re imported the model (this time it didnt show any deltas) and transported that activity to prod.
but still no success!

Similar Messages

CIF - Integration model name and APO application

Hi Experts,
In the CFM1 Transaction, there are 3 mandatory inputs are Model name, Logical system and APO application.
Logical systems are customized in CFC1 transaction. I couldn't trace the model name and application creation.
What is the transaction to customize/Create the new Model name and APO application.
Hope this is very simple question to you and expect your soon.
Thanks,
Saravanan V

Hi Somnath,
Thanks for ur reply.
First I saved the selection as variant. But it was not updated in the IM table.
Then I tried to generate the model and now I can see the details when I use the F4 help.
So, to create a integration model need to generate the variant once.
Thanks for the confirmation.
Thanks,
Saravanan V

Consuming AWS model in webdynpro java application

Hi,
We are using the following environment.
SAP Netweaver Portal 7.3
Netweaver Developer Studio 7.3.
We have imported a AWS webservice model in a webdynpro application. When we deploy the application in portal, we are receiving the following runtime error,
error in executing the model: Illegal model class renaming: Model classes with QNames '/definitions/types/xsd:schema[5]/xsd:element[15]/xsd:complexType' and '/definitions/types/xsd:schema[5]/xsd:element[15]/xsd:complexType#Choice1' were both renamed to the same name 'com.sap.demo.harmanmdmui.wd.models.addresswebservice.RunBatchJobRequest'
Addresswebservice is the webservice name and harmanmdmui is the application name.
Pleaae advise me with a probable solution.
Thanks,
Appachi

Hi
What does the log say?
Regards
Yuval

Exception in SAP Application Integrator occured: Unable to process templat

Hi,
We are trying to execute a BI report in portal through BEx web and we are getting the below error
[EXCEPTION]
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to process template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname><BWLauncherComponent[PORTAL_URL]>;jsessionid=<Request.JSessionID>?sap-ext-sid=<ESID[url_ENCODE]>&Language=<Request.Language>&theme=<LAF.Theme[url_ENCODE]>&sap-lafversions=<LAF.AllVersions[url_ENCODE]>&<Authentication>&<Report>&<BusinessParameters>', because 'Report' is an invalid terminal property of the Root context.
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(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)
I have tested the connection in the system and also checked the webas name and host details in the system. they look fine.
please help me with your inputs.
Thanks.
Kind Regards,
Priyanka.

This could be the problem . In your portal , copy the pcd path of a folder under which you would like to place this report and paste it in the bex analyser while publishing (pcd link) , see if this helps . A few more points .
1) You can also publish these queries as reports in portal using Bex Query designer - there will be an option to publish in portal . You will see it depending upon the version of designer. If you are able to see that option , selecting the pcd location would require you to have content admin role in portal .
2) Manually create iviews in portal (BI Reports) using the query string given to you by your BI folks . You can create either Bex 3.X or 7.0 depending upon the query string .
Regards
Mayank

Reg: Runtime exception occurred during application mapping

Dear SAP Gurus,
This is Amar Srinivas Eli working currently on SOAP to SOAP Scenario on PI 7.1 Server.
I Would like to inform you that I have done all steps regarding DESIGN and CONFIG and also regarding SERVICE REGISTRY part successfully.
While Testing the data in the WS Navigator by giving the input parameters I am getting an error that
*<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>*
*- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_HRS_LISTReferral_Response_MM_</SAP:P1>
<SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
<SAP:P3>on: Cannot create target element /ns1:PI_ListRefer</SAP:P3>
<SAP:P4>ral_Response_MT. Values missing in queue context.~</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_HRS_LISTReferral_Response_MM_; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns1:PI_ListReferral_Response_MT. Values missing in queue context.~</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
These are the steps I did while implementing..
1. Importing the XSD's successfully
2. Developed the design and config part and also checked nearly 3-4 times regarding both REQ and
    RESPONSE Mappings.
3. I already checked the link of WSDL once again...
4. Even I found REsponse Interface once again...
Still I am not getting where the error was ? Please guide me in detail in a right way in this issue.
Regards:
Amar Srinivas Eli
Edited by: Amar Srinivas Eli on Jan 13, 2009 7:53 AM

Hello,
I already checked all those queues and context fields////
Based on my Observation I found
1) As I am unable to view the SOAP BODY I increased the RUN TIME Trace Level to 3 and LOG_VAlue to 3
2) ANother most Important that I found later doing these settings are....
    I found Receiver Pay LOAD and I copied that entire pay load and pasted it in
    REceiver Message Mapping> Test Tab and Code->PASTED...and compared all those parameters
    in the TEST TAB and DEFINITION TAB in Tree View whether all the mandatory receiver mapped
    elements are coming I mean passing from source or not...
OBSERVATION::
I found that for nearly 3 fields there is a difference when I compared on Tree View in DEFINITION TAB and also parallely in the TEST TAB Tree View which I got by copied from MONI,,,,
see for example ::
CENTRE <----
> DISCHARGE DATE..
For going to CENTRE..here I found that in DEfiniition TAB...
Control Act Event-->Subject->document-->Component>Structured body> component> Section>Component>PatientCareProvisionEvent->EffectiveTime-->CENTRE
But immediately I have gone to TEST TAB and TREE VIEW and I found that respective field CENTRE is posting I mean passing any value or parameter to Discharged Date or not...
But I found that...
Control Act Event-->Subject->document-->Component>Structured body> component> Section>Component-->_PatientCareProvisionEvent_
This Implies that Effective Time and Centre are missing in the XML and I mean no values are passing to receiver right..
In PI XSD 's it is there but in I think after Compiling REQUEST MAPPING and while in returning to RESPONSE MAPPING I mean whenever the Response is posting to SOAP WEBSERVICE it is unable to found those target elements and I think due to this...
Am I Correct ?
If that is the case...Let me know where the issue is whether in the data present in the WEBSERVICE created on target side or in PI Side..any issue...
Regards:
Amar Srinivas Eli
Edited by: Amar Srinivas Eli on Jan 13, 2009 10:00 AM

Runtime exception occurred during application mapping

Hi All,
Please find the error message which we are getting:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_CRM_COD_ProductCategoryHierarchy_R~</SAP:P1>
<SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
<SAP:P3>on: Cannot create target element /ns0:ProductCateg</SAP:P3>
<SAP:P4>oryHierarchyMassReplicationRequest/ProductCategor~</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_CRM_COD_ProductCategoryHierarchy_R~; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns0:ProductCategoryHierarchyMassReplicationRequest/ProductCategor~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please give your expert Advice on the same.
Regards
RK

Dear Rableen,
As Muniyappan and peter told about the mandatory field value is missing for the target element
"/ns0:ProductCategoryHierarchyMassReplicationRequest/ProductCategor", I am able to see other fields are also not getting input data.
as below
"Cannot create target element /ns0:ProductCateg"
Request you to test with the payload in message mapping and activate the message mapping first and then edit your operation mapping and call the same message mapping in your operation mapping and activate all your objects.
Thank you!
Regards
Hanumantha Rao

Runtime exception occurred during application mapping in SAP PI

Hi Team,
Please help me regarding this issue is very urgent:
Runtime Error in configuration part:
Here i test the XML message in Receiver Determintion:
Below i am getting error:
Runtime exception occurred during application mapping com/sap/xi/tf/_MaterialStockUpdate_Multi_AllPlant~; com.sap.aii.utilxi.misc.api.BaseRuntimeException:The processing instruction target matching "[xX][mM][lL]" is not allowed
SXMB_MONI:
I am getting below error:
Runtime exception occurred during application mapping

Hi,
Actually my problem is what i am getting,I am trying to test the data in runtime workbench and configuration part copied from inbound payload XML structure .
I already sent the screenshots of above errors,
Configuartion:
Runtime workbench:
This the error i am getting below in "Runtime Workbench"
Error While Sending Message: Additional error text from response: com.sap.engine.interfaces.messaging.api.exception.ConfigException: ConfigException in XI protocol handler. Failed to determine a receiver agreement for the given message. Root cause: com.sap.aii.af.service.cpa.CPAObjectNotFoundException: Couldn't retrieve outbound binding for the given P/S/A values: FP=;TP=;FS=MHEPL_Sandbox_100;TS=;AN=MaterialStockUpdate_Multi_AllPlants_N;ANS=http://www.manipalhospitals.com/his/mm; in the current context [Unknown].

Runtime exception occurred during application mapping "EXCEPTION_DURING_EX"

Hi Gurus,
I am getting following error in MONI:
SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_MDM_CMS_Backfeed_Group_</SAP:P1>
<SAP:P2>com.sap.aii.mappingtool.tf7.MessageMappingExceptio</SAP:P2>
<SAP:P3>n: Runtime exception when processing target-field</SAP:P3>
<SAP:P4>mapping /ns0:BackfeedGroup/group/MasterId; root m~</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_MDM_CMS_Backfeed_Group_; com.sap.aii.mappingtool.tf7.MessageMappingException: Runtime exception when processing target-fieldmapping /ns0:BackfeedGroup/group/MasterId; root m~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have tried to refresh the mapping cache and restart the message but stil this message persists.
For me it seems an issue with a wrong mapping or some wrong value in the inbound scenario.
Please suggest if any one of you had come across this error before.
With Reg,
Vikash

Hi Vikash
Whenever you have a problem in your mapping you will get this kind of error in monitoring
According to your log the problem is in parameter /ns0:BackfeedGroup/group/MasterId
First of all check your mapping. If it is fine than check the value of this parameter from your payload.
Also try to copy your xml and test the mapping in IR. Check wether you are getting same error there .
If same error comes than try to manipulate the value of that field and try the same test again
Regards,
Shradha

With weblogic workshop 9.2 I see Java Model Exception

Hello,
With workshop 9.2 I see error window displayed when importing projects form my zip file.
com.bea.wlw.controls.core.publish.AssemblyException: Java Model Exception: Java Model Status [EJBproject does not exist]
at com.bea.wlw.controls.core.publish.ClassPathBuilder.buildClassPathImpl(ClassPathBuilder.java:45)
at com.bea.wlw.controls.core.publish.ClassPathBuilder.buildClassPathImpl(ClassPathBuilder.java:34)
at com.bea.wlw.controls.core.publish.ClassPathBuilder.buildClassPath(ClassPathBuilder.java:18)
at com.bea.wlw.controls.core.validation.ControlValidator.build(ControlValidator.java:69)
Why this is happening ?
Liang Zhong

Hello Liang,
I've seen a similar issue occur in Workshop 9.2 when I import a set of projects which have interdependencies. In my case the error window is displayed and then disappears as soon as the build is able to find the class.
If this is the same behavior you are seeing in Workshop 9.2 then you can safely ignore the window
This issue has been fixed in the newer Workshop build.
cheers
Raj

SAP NetWeaver: SAP's Model-Driven Business Process Application?

Hi All:
I am a graduate student currently doing a research on 'Model-Driven Business Process Application'. I came across some literature about SAP NetWeaver during my research. SAP NetWeaver has generated a lot of interest in me and I would like to know more detailed information about it:
How is SAP adopting BPM principles to manage Work-flows? Can we consider any of the current NetWeaver applications as model-driven?
It would be great to know the answers to some of these questions. I would sincerely appreciate if anyone of you could please help me with this. Also, thank you very much for your time and efforts. I would be happy to assign reward points to any informative responses.
Regards,
Alok

Refer to this link
http://help.sap.com/saphelp_nw70/helpdata/EN/6e/fb9442047b0831e10000000a1550b0/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5045b3cc-acbe-2910-2bab-8d930cb31a33
Regards, IA

Java Model Exception

I have a DC which uses another DC.
The Used DC has a Model in it.
When I sync and create Project for the main DC (ie Using DC), it gives an Exception (Java Model Exception).
Also it says that .classpath file is read-only.
I had some nodes in the using DC structure boubded with the Model(which is in Used DC).
But now becoz of this Exception, all structure bounded nodes(in using DC) are in error.
I had the Model in "Used Models" of the main DC but that also does not seem to appear now.
Please suggest a solution
The exact exection is org.eclipse.jdt.core.JavaModelException: File /GGD_NPIDEV_Dsnsnpiadminconfig~pg.com/.classpath is read-only.
Regards
Mrinalini
Edited by: Mrinalini_Sharma on Mar 8, 2010 12:47 PM

Hi Saravanam,
One more information about my scenario.
In the open activities view, I can see that the name of development configuration is followed by number 1 and 2 in brackets like
VBD_FPIDEV_D(1)(2). The actual name of the devlopment configuration is VBD_FPIDEV_D. Why are numbers 1 and 2 following the name. It appears in the same way in Activation view and in Transport view too.

Cannot create target element(Runtime exception occurred during application

Hi ,
this is IDOC TO HTTP Scenario. in error description it is shoein g below error.
Runtime exception occurred during application
Cannot create target element (inbound)
please advice
thank you.

Copy the payload from sxmb_moni and test it in the mapping tool using debug mode. I suspect some mandatory elements in target structure requires value but it is missing during mapping. Sometime sender data structure due to values are not getting at runtime does not create target structure element. Check all the individual fields in the mapping tool.

Exception in SAP Application Integrator occured

Hi,
I am facing a problem while opening transaction iviews in portal.In the default trace file below is the logs:
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component :pcd path of the component
Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Exception occured in layer CommonTopLayer
Please suggest.Its urgent.
Regards,
Rajani

Hi,
Thanks for the reply.
Please find the default trace log:
=============================================
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd path of component
Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
User : name of user as in portal
     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(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: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: 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]>&<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)
     ... 29 more
=============================================
Regards,
Rajani

Exception in SAP Application Integrator occured: ApplicationIntegratorExcep

Hello All
I have encountered a quite peculiar problem.
In My Portal( WAS SP 14), whenever i go to
System admin-> system config->uwl-> Universal Worklist Administration
It shows me Portal exception.
[EXCEPTION]
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: ApplicationIntegratorException .
Also when i check inside Content provided by SAP-> Admin content->system administrator->iviews->Universal worklist iview,( ALL UWL Iviews), throw Portal exception...
I tried uploading the com.sap.portal.appintegrator.sap.par from another WAS 7.0, SP14
but still it shows me same error in worklist iviews.
Also i trannsported the iviews via .epa files to My Portal, But no Success.
Help...
What to do????
Thanks...

EXCEPTION]
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.doPreview(AbstractPortalComponent.java:240)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:168)
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(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)

Exception in SAP Application Integrator occured while proccesing HCM F&P

Hi
I am getting following error, while Start Process.It's part of the HR Administrator; HCM forms & Proccess.
Open Process
Portal Runtime Error
An exception occurred while processing your request
Exception id: 05:05_11/03/10_0004_9166150
See the details for the exception ID in the log file.
Detail :
#1.5 #0050568F649300690000001E0000024800047FEF69B04AFB#1266566154115#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#CAP.GEMINI1#8121##torepdev_SPD_9166150#CAP.GEMINI1#983566c01d2b11dfb5c60050568f6493#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#/System/Server#Java###Exception ID:02:55_19/02/10_0001_9166150
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.roles/com.sap.pct.erp.mss.manager_self_service/com.sap.pct.erp.mss.manager/overview/com.sap.pct.erp.mss.work_overview/com.sap.pct.erp.mss.work_overview_page/com.sap.pct.erp.common.key_figure_monitor
Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
User : CAP.GEMINI1
     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(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sapportals.portal.prt.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]>&<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)
     ... 29 more
#1.5 #0050568F64930069000000200000024800047FEF69B3E251#1266566154349#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#CAP.GEMINI1#8121##torepdev_SPD_9166150#CAP.GEMINI1#983566c01d2b11dfb5c60050568f6493#SAPEngine_Application_Thread[impl:3]_4##0#0#Error##Java###02:55_19/02/10_0001_9166150
[EXCEPTION]
#1#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]>&<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)
     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(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)
Please help.
Points Gauranteed.

Hi,
I am also facing same kind of error , can you suggest where can I check HCM F&P under webdynpro in portal side.
can you suggest which one is best way for to resolve my querry.
Full Message Text
04:43_12/04/11_0006_116801251
[EXCEPTION]
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]>&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]>'; 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:125)
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: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(AccessController.java:219)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Thanks
Renu

Random model exception in WD application

Similar Messages

Maybe you are looking for