Install NW 2004s SP9 - extremely limited callable objects in GP

I have installed the sneak preview for NW 2004s SP9 and find the selection of callable object types in the Guided Procedures design time to be extremely limited. The only callable object types are Service > Web Service, User Interface > Web Pages, Form > Web Dynpro Form, Form > Data Input Form, & Form > Data Display Form. The Time-Off Process example included in the doc uses the callable object type Web Dynpro Component (GP Interface), but this callable object type is not part of this installation.
Is there something else I need to install or activate or is this simply the content that is in this install?
Thanks,
Elizabeth

Maybe your problem is related to Re: exception during GP action creation. It appears that CAF is not correctly installed with the sneak preview.
Regards,
Christophe

Similar Messages

I am not able to create a callable object of my web Dynpro application

Hi,
I have my Portal server installed with NW2004S and with other components as follows.
·WAS 7.0 SP9
·EP7.0 SP9
·CAF 7.0 SP9
·VC 7.0 SP9
But now my webdynpro application is not reflecting in web Dynpro Component(GP Interface) during the design time, when I am trying to create a callable object.
So please can you suggest what is the problem and how I will get it corrected.
Regards,
Paresh.

Hi Aliaksei,
I had created a complete CAF application which was working fine. Then the server got crashed and i lost everything.So then i again installed the server and upgraded it to SP7.But than i was not able to see my web dynpro application while creating callable object. So i created another instance in the server at the base level(SP4) and i was able to create callable object.
There is no problem in the webdynpro application.I have added runtime library referece to my project : sap.com/cafeugp~api and also implemented the Interface IGPWebDynproCO in my component.
So i dont know where i am going wrong while i am upgrading the server.
Regards,
Paresh.

Callable object "input" is missing

Hi,
I am using some guides to learn to use block in Composite Application Framework.
I have a SAP Portal 2004s SP10.
I am using some guides I found on CAF Tutorial Center, in particular Designing a Block and Using Parallel Dynamic Block and Dynamic User Assignment.
Quite often in those guides it is asked to use a callable object called Input under the type Data Forms, but in my portal there is nothing with this name, the more similar is a callable object called Data input form, but it is no possible to insert input in it, so I cannot complete the tutorial.
Someone can help me, telling me if there is an alternative valid callable object, or if I have to install some other component?
Thank you
Giuseppe Pagnotta

Hi,
Most probably you're using an outdated documentation, as the Callable Object of type "Input" has been removed from recent releases.
Regarding the issue, you can most probably use Data Input Form or Web Dynpro Form instead of "Input" in this case.
OR
you can use Visual Composer to create the UI and use CO of type "Portal iView or Page" to integrate it into a Process.
You can find more information on Visual Composer here: https://www.sdn.sap.com/irj/sdn/visualcomposer
Hope this helps,
Ashutosh

Type in "Callable Object" gallery in CAF?

Hello,
I'm trying to follow the doc "Building the Job Application Process - SAP Composite Application Framework v1.1" to build a test process.
My environment is the NetWeaver Sneakpreview 2004s SPS4 on Windows 2003 Server.
sap.com/SAP-JEECOR 7.00 SP7 (1000.7.00.7.0.20060324070000) 20060703235737
sap.com/SAP-JEE 7.00 SP7 (1000.7.00.7.0.20060319012200) 20060703235756
I logged in ad Administrator, and verified that it also has the roles "GP Basic User" and "GP Business Expert".
After I clicked on "Create Callable Object", the next screen only shows 3 lines in the "Type" pane, which are 'Web Dynpro Form', 'Web Pages', and an expandable 'Data forms'.
I'm looking for "content package" and "Web dynpro component" types.
Am I missing something here? The install of the preview went without any errors (at least not on the installer console). I am able to create a Folder, create a new "content package", upload an HTML file into the package, and activate it.
Also, any references to such self guided study guides will be appreciated.
Ye

that was the easiest 10 points I ever received. thank you. so funny, sometimes you work your butts out and get no appreciation. in your case the question and answer was simple but I still get the maximum reward points. what a great return on investment.
Anyway, if your company is a SAP customer or partner, you should have or somebody in your organization should have the login id to service.sap.com. Otherwise go to SDN under the CAF Tutorial Center SAP Composite Application Framework - CAF Tutorial Center [original link is broken] where you should also get enough how-to guides. Enjoy you learning experience with GP!

Portal Page Builder Error in Portal Callable Object

We have created a callable object in GP of type Portal Page or IView
When we try execute the action from UWL, the following error it shows,
The portal page builder required to execute this callable object is not available.
The same concept we tried in 2004s, its working fine.
Any idea about this error in ce. Highly urgent..

Not yet answered

Problem to execute a Callable Object (SAP R/3 transaction) in UWL

Hi,
I have developed a callable object which calls a SAP R/3 transaction. It runs perfectly in design time , when I run it in UWL I am getting the Error "An error occurred while displaying the callable object, which uses the page builder. Check that the page builder is installed, and the transaction iView is available .
Please let me know your thoughts and suggestions.
Regards
Wesley Solomon

Hi Wesley
According to me, it is because of some missing package that this problem is encountered coz even i have faced this problem w.r.t the UWL and then i imported the required packages and it worked.
Regards
Navneet

Info Callable Object of type SAP R/3?

Hi Friends,
I have designed a Business Process using CAF GP, in which, in one of the actions I have inserted an Info Callable Object of type SAP Transaction, though the callable object is working fine with the process,
I can see callable object in a limited area only,
 I am not able to maximize it, neither I can any scroll bars to scroll up and down,
so that I can see full R/3 window within the GP window,
Can anybody help me doing that?
Thanks
Deepak

Thanks David,
I got the solution
I have rewarded for the same,
Thanks once again,
Best Regards,
Deepak

Can't add GP Component Interfaces to WebDynpro Callable Object

Hi, I've just installed the IDE for Composition Environment 7.1 SP3 and I'm following the tutorial to create a WebDynpro Callable Object for a Guided Procedures that I'm working for a demo. It seems that there is something wrong with my NWDS, 'cause once I add the the required DCs dependencies to my project for caf/eu/gp/api and caf/eu/gp/api/wd and mark them for Design time, I cant add the to any new component as implemented component interfaces 'cause the list for adding them is empty. I really don't understand why this is happening, 'cause that's the way the tutorial explains it to work. I've already try to reinstall the NWDS, without success. Has any of you face the same problem?
Thanks for you answer.

Hi,
You should not create Design Time dependency. It is not required.
Ensure only that you have created a Build Time dependency on the public of "caf/eu/gp/api and caf/eu/gp/api/wd".
After creation of dependency ensure that you have build WD DC.
Check if it works now ?
Regards,
Ashwani Kr Sharma

ABAP Table Type in RFC Callable Object in GP

Hi Experts,
I have created a RFC in ABAP that has as one of its export parameters a table type. I am trying to call this RFC in my GP process. So I created the external service callable object as required. However, when I look at the output parameters for the callable object, the table type is not shown as a list (the is list column is not checked for this parameter).
Do you know if ABAP table types is supported/recognized by GP as a list? or is this a limitation?
Any help is welcomed!
Thanks in advance.
Robert

Hi Aneel,
You can try the following:
e.g.
for j = 1 to ActiveCell.SpecialCells(11).Column
oParam4.Rows.Add
if j=1 then oParam4.Value(j, "NAME") = ActiveSheet.Cells(1,j).Value
if j=2 then oParam4.Value(j, "TYPE") = ActiveSheet.Cells(1,j).Value
if j=3 then oParam4.Value(j, "NUMB") = ActiveSheet.Cells(1,j).Value
next j
Regards,
ScriptMan

NWDS setup for exposing web dynpro as callable object

Hi
I need help in understanding how to set-up my NWDS 7.0 environment, so as to implement and expose a web dynpro as callable object in Guided Procedure. I tried following some of the weblogs in the SDN but I get stuck at the step where depencencies to DC's caf/eu/gp/api/wd & caf/eu/gp/api etc. is to be done.
It appears that NWDS 7.0 does not come with GP DC's.
My NWDS version is 7.0.09 & in have NW 2004s.
Thanks
Vijendra

Hi
I need help in understanding how to set-up my NWDS 7.0 environment, so as to implement and expose a web dynpro as callable object in Guided Procedure. I tried following some of the weblogs in the SDN but I get stuck at the step where depencencies to DC's caf/eu/gp/api/wd & caf/eu/gp/api etc. is to be done.
It appears that NWDS 7.0 does not come with GP DC's.
My NWDS version is 7.0.09 & in have NW 2004s.
Thanks
Vijendra

Callable objects using ABAP API

hi,
Is it possible to develop Callable objects for MDM using ABAP APIs?
Regards
Nisha

Hi Nisha,
As far as I know, itu2019s not possible. You can use just RFC/BAPI as external services CO or ABAP Web Dynpro (this CO is limited regarding output parameters).
MDM offers two APIS for Java development:
1) MDM4J API, which is an old API and will be discontinued from MDM 7.1
2) MDM Java API that is recommended
With this API you can create Java Libraries or/and Web Services to re use into your CO.
Best Regards,
Pedro Nunes

Can Dynamic xml templates be used in interactive form callable objects?

Hi,
We are trying to implement Offline adobe forms using guided procedures (Impersonalized forms).
We have no problem while creating the callable object using the normal xdp template. But whenever we try to use Acrobat 7/8 dynamic xml template, the following error occurs and the template is not picked.
"Could not retrieve template fields: Wrong document format or adapter mismatch from adapter"
Cant we use dynamic xml templates for adobe forms in GP? If we can, how to resolve this? Please let me know.
Version:
Netweaver SAP 2004s Sp15
Adove Live Cycle desginer 7.0

Closed

Error with Dynamic XML template in interactive form callable objects :GP

Hi,
We are trying to implement Offline adobe forms using guided procedures (Impersonalized forms).
We have no problem while creating the callable object using the normal xdp template. But whenever we try to use Acrobat 7/8 dynamic xml template, the following error occurs and the template is not picked.
"Could not retrieve template fields: Wrong document format or adapter mismatch from adapter"
Cant we use dynamic xml templates for adobe forms in GP? If we can, how to resolve this? Please let me know.
Version:
Netweaver SAP 2004s Sp15
Adove Live Cycle desginer 7.0
Edited by: Subramanya Srinivas Mullapudi on Oct 25, 2008 1:31 AM

Hi Srivinas,
take a look on that [docu dynamic forms|http://help.sap.com/saphelp_nw70/helpdata/en/44/bca11fc60b7006e10000000a155369/content.htm] and let me know if this is solving your problem.
In addition also consider [integrating offline and form-based activities|http://help.sap.com/saphelp_nw70/helpdata/en/44/d44bea51103ee1e10000000a114a6b/content.htm] and the mentioned sublinks.
Best regards
Berndt

Rapid Installer 2004s SPS07 Any limitations?

Hi,
We have used the Rapid Installer 2004s (SPS07) to install the portal. Are there any limitations by using this installation? (like the number of users?)
Thanks in advance,
Antony.

Hi Marcelo Behr,
Thanks so much for the reply.
You have mentioned that JVM parameters need to be changed based on our configuration.
We have used the rapid installer to install Netweaver 2004s and will be using a few iviews on the home tab as well going live with a few iviews on Employee Self Services (ESS).
We will be going live with 2000+ users.
Current Config ->
2CPU & 4GB memory server for portal
2CPU 4GB server for ITS production.
Your input will be greatly appreciated.
Antony.

Error while creating a callable object - User Interface

Hello,
When i'm trying to create a callable object - User Interface in the guided procedure design time. i'm getting an error. An internal server error. This is happening while i'm trying to create a guided procedure with webdynpro's.
Is there any body who allready had somthing like this.
Greetings
Kurt

Hi Raja Akella,
I allready had the roles and my portal version is upgraded until SP8 and all the possible patches.
I get an internal server error when i want to create a callable object. specially when i want to create a webdynpro ( ABAP / JAVA).
In the visual administrator i get the following errors.
Error 1
Exception occured during processing of a Web Dynpro application: "com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.".
[EXCEPTION]
com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.
 at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:640)
 at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponentInternal(IWDApplicationInfo.java:286)
 at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponent(IWDApplicationInfo.java:270)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.addWdappsElement(COConfigWDApp.java:646)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readWebDynproApps(COConfigWDApp.java:631)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readApplications(COConfigWDApp.java:308)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalCOConfigWDApp.readApplications(InternalCOConfigWDApp.java:190)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.initCreate(VSelect.java:306)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.onPlugFromDispatch(VSelect.java:174)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalVSelect.wdInvokeEventHandler(InternalVSelect.java:168)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:826)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
 at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:330)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 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.tc.webdynpro.repository.RepositoryRuntimeException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)
 at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:178)
 at com.sap.tc.webdynpro.repository.persistence.xml.XMLPersistence.doReadVMO(XMLPersistence.java:126)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.readVMO(RepositoryPersistence.java:356)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.doFindRepositoryObject(RepositoryPersistence.java:598)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.findRepositoryObject(RepositoryPersistence.java:170)
 at com.sap.tc.webdynpro.repository.model.Repository.findRepositoryObjectInternal(Repository.java:590)
 at com.sap.tc.webdynpro.repository.model.RepositoryObjectRelation$XMLGuidWrapper.getModelObject(RepositoryObjectRelation.java:462)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.getCurrentLayerObject(RepositoryPersistence.java:702)
 at com.sap.tc.webdynpro.repository.model.Repository.getCurrentLayerObject(Repository.java:1483)
 at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.doMergeInheritedTarget(NonSharedRelationToOne.java:85)
 at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.mergeInheritedTargets(NonSharedRelationToOne.java:49)
 at com.sap.tc.webdynpro.repository.model.RelationToOne.getTarget(RelationToOne.java:93)
 at com.sap.tc.webdynpro.repository.model.AbstractRepositoryModelClass.getRelatedModelObject(AbstractRepositoryModelClass.java:234)
 at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:636)
 ... 39 more
Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)(:main:, row=1, col=491) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
 at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:148)
 at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:166)
 ... 52 more
Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
 at com.sap.engine.lib.xml.parser.XMLParser.scanAttList(XMLParser.java:1566)
 at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1687)
 at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2792)
 at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:227)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:141)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:156)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:259)
 at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:278)
 at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:340)
 at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
 ... 53 more
error 2
Processing HTTP request to servlet [dispatcher] finished with error. The error is: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.
 at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:640)
 at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponentInternal(IWDApplicationInfo.java:286)
 at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponent(IWDApplicationInfo.java:270)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.addWdappsElement(COConfigWDApp.java:646)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readWebDynproApps(COConfigWDApp.java:631)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readApplications(COConfigWDApp.java:308)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalCOConfigWDApp.readApplications(InternalCOConfigWDApp.java:190)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.initCreate(VSelect.java:306)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.onPlugFromDispatch(VSelect.java:174)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalVSelect.wdInvokeEventHandler(InternalVSelect.java:168)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:826)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
 at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:330)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 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.tc.webdynpro.repository.RepositoryRuntimeException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)
 at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:178)
 at com.sap.tc.webdynpro.repository.persistence.xml.XMLPersistence.doReadVMO(XMLPersistence.java:126)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.readVMO(RepositoryPersistence.java:356)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.doFindRepositoryObject(RepositoryPersistence.java:598)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.findRepositoryObject(RepositoryPersistence.java:170)
 at com.sap.tc.webdynpro.repository.model.Repository.findRepositoryObjectInternal(Repository.java:590)
 at com.sap.tc.webdynpro.repository.model.RepositoryObjectRelation$XMLGuidWrapper.getModelObject(RepositoryObjectRelation.java:462)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.getCurrentLayerObject(RepositoryPersistence.java:702)
 at com.sap.tc.webdynpro.repository.model.Repository.getCurrentLayerObject(Repository.java:1483)
 at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.doMergeInheritedTarget(NonSharedRelationToOne.java:85)
 at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.mergeInheritedTargets(NonSharedRelationToOne.java:49)
 at com.sap.tc.webdynpro.repository.model.RelationToOne.getTarget(RelationToOne.java:93)
 at com.sap.tc.webdynpro.repository.model.AbstractRepositoryModelClass.getRelatedModelObject(AbstractRepositoryModelClass.java:234)
 at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:636)
 ... 39 more
Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)(:main:, row=1, col=491) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
 at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:148)
 at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:166)
 ... 52 more
Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
 at com.sap.engine.lib.xml.parser.XMLParser.scanAttList(XMLParser.java:1566)
 at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1687)
 at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2792)
 at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:227)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:141)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:156)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:259)
 at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:278)
 at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:340)
 at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
 ... 53 more
error 3
Processing HTTP request to servlet [dispatcher] finished with error.
The error is: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.
Exception id: [00505691431B006F0000003E00000FE800041B45B87F7617]
thanks in advance
Kurt

Install NW 2004s SP9 - extremely limited callable objects in GP

Similar Messages

Maybe you are looking for