BI Application Callable Object

Hi,
I am new to Guided Procedures.
I tried to use BI Application Callable Object under Services Type and i created a BI System in Portal to use in the callable object.when i use it in the callable object it is showing error cannot connect to system .
Can you help me how to create a system in Portal and help me with a scenario how to use BI Application Callable Object.
Regards,
Bala Baskaran.S

Hi KC,
When you start your process from GP Runtime, does the actual action/callable object open in a new window?
Have a look at this SAP Note:
[Error when executing a GP task - Page builder|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_gp/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d393831353137%7d]
Although the error message you are getting is different, but if your callable object opens in a new window, then the problem (in most probability) is the same as mentioned in the SAP Note.
Also, try testing the Web Dynpro callable object in standalone mode. For more information on this, see:
[Testing Callable Objects|http://help.sap.com/saphelp_nw04s/helpdata/en/4c/588041a17e060de10000000a1550b0/frameset.htm]
Bye
Ankur

Similar Messages

Web Dynpro application callable object error: Page Builder Not available

Hi, SDN Fellow.
I created a callable object of Web Dynpro application. The callable object is atatched to an Action, and Action --> Block, and Block --> Process.
I initiate the process in GP Runtime, when it comes to the Action screen the Web Dynpro application atatched to, I got the following error:
The page builder required to display this application UI inside the portal environment is not available.
As aa comparison, another callable object that atatched to a Web Dynpro component (that implement GP interface) is working fine.
Please advise.
Thanks in advance,
KC

Hi KC,
When you start your process from GP Runtime, does the actual action/callable object open in a new window?
Have a look at this SAP Note:
[Error when executing a GP task - Page builder|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_gp/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d393831353137%7d]
Although the error message you are getting is different, but if your callable object opens in a new window, then the problem (in most probability) is the same as mentioned in the SAP Note.
Also, try testing the Web Dynpro callable object in standalone mode. For more information on this, see:
[Testing Callable Objects|http://help.sap.com/saphelp_nw04s/helpdata/en/4c/588041a17e060de10000000a1550b0/frameset.htm]
Bye
Ankur

How to create a WD4VC callable object in GP

Hi Guru's;
I want to use a WD4VC callable object in GP , can any one tell how to configure . I tryed the link given below
http://help.sap.com/saphelp_nw70/helpdata/EN/44/5d5634cae308f9e10000000a422035/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40bfb641-9575-2a10-4794-e5f23ff06b4f
but its not working. i am using verson 7.0 SP 13
My task is to pass parameter form VC to GP.
Please help me in that task
Regards
Vivekananthan.s

Hi,
you can look at this (from help.sap.com) (not sure if it works for 7.0):
You can expose composite views created in Visual Composer as callable objects in the Guided Procedures design time, and then attach the callable object to an action in a Guided Procedures process flow. In Guided Procedures, these Visual Composer applications are called Web Dynpro for Visual Composer (WD4VC) Application callable objects. More information: Exposing WD4VC Applications as Callable Objects.
Following are some general guidelines for modeling composite views for use as WD4VC application callable objects in a Guided Procedures process flow:
Each WD4VC application callable object that passes data to and from Guided Procedures should contain at least a Start Point and an End Point, or a Data Bridge and an End Point depending on the use case:
¡        Use a Start Point and End Point when the dataset is flat and there is no semantic relationship between the fields. For example, if the dataset includes a customer ID field and a purchase order ID field
○       Use a Data Bridge in any of the following situations:
■       The dataset is clustered.
■       The dataset is flat, but there is a semantic relationship between the fields. For example, if the dataset includes an address consisting of 10 fields (such as street, zip code, country, and so on).
■       The structure of the dataset is based on a Web service, RFC, or similar.
More information: Transferring Data Using a Data Bridge
·        Add an end point to each WD4VC application callable object to terminate the application.
·        A WD4VC application callable object that does not pass any data to Guided Procedures does not need a Start Point or a Data Bridge, it only needs an End Point.
·        In a WD4VC application callable object that uses a Data Bridge to communicate with Guided Procedures, and the component terminates with result states, you should model the mapping lines to the Data Bridge with the same events that are used to trigger the End Point connectors.
·        In a WD4VC application callable object that uses a Data Bridge to communicate with Guided Procedures, a Start Point can be used to initialize the application (and not to pass data to Guided Procedures).
best regards,
v s
Edited by: v s on Jul 3, 2008 2:26 PM
Edited by: v s on Jul 3, 2008 2:26 PM

Callable object for WD java

Hi Experts,
I am new to GP, and i need your help to design my GP.I am a web dynpro developer . I want very basic process to be implemented through GP as follows
1) Employee gets a UI screen for filling some requisition form (in WD java) which wud hit R3
2) Employee's supervisor can Approve / Reject requisition . (UI in WD JAVA)
3) Employee should get a summary of whole process (Again UI in WD JAVA).
When i am creating calling object for above process and under UI category there are two different type of callable object for wd java
1 ) Web dynpro component (GP interface)
2) Web dynpro application
when i am creating ( Web dynpro application ) callable object , its giving me error , maybe some config problem .
can anyone just guide me how to implement above process or give me some material through GP (WD java UI) and whats diff between two kinds of callable object.Thanks in advance.
Regards,
Abhay

Hi Abhay,
You can design your process by this way:
1) Employee gets a UI screen for filling some requisition form (in WD java) which wud hit R3
If you need to update R3 at this time, you can create a custom WD Java calling a RFC. To do that, you may use WD with GP API (https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50d74ada-0c01-0010-07a8-8c118d408e59 ) or you may call your RFC directly by External Service Callable Object (https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7c313ada-0c01-0010-dfba-9ac88b353a47). It depends of how you will design your process.
IE:
Custom WD Screen that will have input fields and will update R3 -> use GP API
Standard input screen -> use Data Input Form and to update R3 use External Service CO
2) Employee's supervisor can Approve / Reject requisition . (UI in WD JAVA)
You can use Visual Approval standard Callable Object to do that. If you need to update R3 according with approval results, you can insert the External Service CO as next step according with result. To accomplish that you must set Result States.
3) Employee should get a summary of whole process (Again UI in WD JAVA).
Data Display Form standard Callable Object give you exactly what you want.
Scenario 1: WD Custom UI that update R3 -> Visual Approval CO -> Data Display Form
Scenario 2: Data Input Form -> Visual Approval CO -> External Service CO -> Data Display Form
Reward points if itu2019s helpful.

Is Callable Object Defination in GP Changable?

Hi All,
Once the callable object has been create, can the type of it be changable?
I'd like to change a "Simple Input Form" callable object to a Webdynpro application callable object, is it possible?
Thanks,
YiNing

Hi,
You need to create the new CO separately.
Thanks,
Dipankar

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.

GP, callable object Web Dynpro Application (bespoke) not appearing in list

Hey y'all
We're developing our first GP, and we would like to call an existing bespoke Web Dynpro. When creating the callable object, we're selecting type Web Dynpro Application, but our Web Dynpro screen is not appearing in the drop down list on the next page. We think that this is because the application has been deployed to a different server (i.e. it has not been deployed onto the portal server).
So the question is, has anyone faced this problem before, and is there a solution?
Kind regards
Jon

Hi John,
Please have a look at this Exception on creating GP Action
This will solve your issue definitively. Do not take care of a given SDA, just redeploy everything and make sure that everything is overwritten by selecting the right option.
Best regards,
David

WebDynpro Application as callable object in GP?

Hello,
I have created a WebDynpro application in NetWeaver Studio.I have to create a callable object of this application in GP.
This application is available in GP.I create a callable object of it, with an action, block process for this single object.(Since i cant test this callable object).
Once i generate url and acess it, it generates an error in browser saying:
"The page builder required to display this application UI inside the portal environment is not available".
Kindly help me solve this issue.
Thanks,
Sharath

Andre,
Thanks a lot for your how to guide.. it's really good!.. I've followed all your steps and I've created my WD DC. Everything works fine, the build is correctly made, but when I deploy the application the following error is getting throw:
Deployment aborted
URL to deploy : file:/C:/DOCUME1/MARIAM1/LOCALS1/Temp/temp62306bcp.compa001de.ear
Result
=> deployment aborted : file:/C:/DOCUME1/MARIAM1/LOCALS1/Temp/temp62306bcp.compa001de.ear
Aborted: development component 'pa001de'/'bcp.com'/'local'/'20070606173629'/'0':Caught exception during application deployment from SAP J2EE Engine's deploy service:java.rmi.RemoteException: Cannot deploy application bcp.com/pa001de.. Reason: Clusterwide exception: Failed to deploy application bcp.com/pa001de. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application bcp.com/pa001de. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine? (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted
I think that the referenced components are not at the J2EE, but how can I check this or what do you think can be happening??
Regards and thanks a lot to all!
María Margarita Monteverde

Callable Object for Webdynpro Application

Hello,
I have a Webdynpro for Java Application where I am importing a model from R/3 and displaying certain records......and want to include it in GP Framework....so which is the Callable Object I should use.....i tried using Webdynpro application type but it gives me the error at runtime while execution as :
Application error occurred during request processing.
Details: com.sap.tc.webdynpro.services.sal.core.DispatcherException: Failed to start deployable object sap.com/home~<webdynpro component name>
Any help would be highly appreciated.
Regards,
Anil

Hi Anil,
I am also facing a similar problem . Can you please guide how to solve it.
Thanks and Regards,
Anurag

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

Web Dynpro as Callable object in GP using PDF Forms

Hi All,
I somehow want to integrate a user filling out a pdf form within a Guided Procedure. So far I have created a local web dynpro DC and I want to make it a Web Dynpro Callable Object (GP Interface). The problem is, I want the user to be able to see the PDF form when filling out the form. For example, if they had a role in the portal where they can invoke the Web Dynpro application with the pdf form, then when they click submit on the pdf they invoke the guided procedure...is this possible? This is so, I can use the web dynpro to do some data validation and call some bapis to get info, then submit this all to the GP. Is this achievable? I know how to do most things, I just want to know things like when is the "execute" and "getDescription" methods called? I want my execute( com.sap.caf.eu.gp.co.api.IGPExecutionContext executionContext ) method to call a bapi also. Is that possible? How do I automate a GP process when I click submit on the pdf form?
Thanks in advanced
TM

Hi,
You can integrate a PDF control in a Web Dynpro view. Refer the following links for that:
<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/dc/f1783fe3263042e10000000a114084/frameset.htm">Example of the Use of an Interactive PDF Form (SAP Library - Web Dynpro for Java)</a>
<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/60/6fc10c6748479392101e09c9e8d33a/frameset.htm">Interactive Forms in Web Dynpro for Java</a>
Also you can create Web Dynpro Java callable object in GP by implementing the IGPWebDynproCO interface. Refer the following links for that:
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50d74ada-0c01-0010-07a8-8c118d408e59">Implementing a Web Dynpro Callable Object which Implements the GP Interface</a>
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e3f07a7a-0601-0010-ebbd-b9cfb445b814">Implementing a Web Dynpro Callable Object</a>
<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/fd/afb4429027da11e10000000a155106/frameset.htm">Implementing a Web Dynpro Component</a>
<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/de/8976417f2d5558e10000000a1550b0/frameset.htm">Implementing and Exposing a Web Dynpro as a Callable Object</a>
You can start a GP process using the public API:
<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/43/fcdf77fc6510b3e10000000a11466f/frameset.htm">Starting and Terminating Processes Using the GP API (SAP Library - Creating Composite Applications)</a><a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5f27e290-0201-0010-ff82-c21557572da1">Creating Interactive Forms in Web Dynpro for Java</a>
Also you can start a GP process using Web Service:
<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/44/44c59fd7c72e84e10000000a155369/frameset.htm">Starting a Process Using Web Services (SAP Library - Creating Composite Applications)</a>
<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/93/27dc108cfc407fbf6c726151840001/frameset.htm">Starting and Terminating Processes Within a Composite</a>
Refering the above links you'll get a fairly good idea how to integrate Adobe forms in WDP and how to start GP process programitically. My suggestion for your requirement would be if always you need to start the process after the user submits the Adobe form, then consider having the Adobe form as the first step for the process. In that case you don't need to start the process programitically. Whenever the user starts filling up the Adobe form the GP process will start. You can refer <a href="/people/dipankar.saha3/blog/2007/03/02/how-to-present-your-gp-processes-to-the-end-user">this blog</a> on how to start a GP process as an iview link in portal.
Otherwise if based on certain conditions you need to start the process then you can either use the Java API or the web service to start the process from Web Dynpro. You should have the Adobe form embedded in Web Dynpro and on submit event you can check the conditions and start the process if required.
Thanks,
Dipankar

Problem in creating a callable object of type Business Logic

Hi SDN,
I am trying to create a callable object of type Business Logic in CE.
When I give all information and click Next, I get this error message.
Error while loading configuration dialog: Failed to create delegate for component com.sap.caf.eu.gp.ui.co.CExpConfig. (Hint: Is the corresponding DC deployed correctly? Does the DC contain the component?)
Can anybody help me out with this problem.
Regards,
Sumangala

Hi.
I'm having the same problem as Senthil in NW2004s SP15 with my application service and methods not showing up in the Callable Object wizard for Composite Application Services after I choose the Endpoint. The only application name that shows up in the wizard is caf.tc, and the only service names that show up for it are LDDataAccessor, Metadata, and PropPermissionService.
My IDE is on one machine and the application server I deploy to is located on a different machine. My endpoint to the remote application server looks to be correctly configured. The Composite Application Service seems to be deployed properly as I'm able to see it and test that it works in the Web Services Navigator <http://remotehost:50000/wsnavigator/>
My deployed application service is a remote enabled service and is also web services enabled as well.
I'm not sure if this is relevant, but I noticed that the generated Java code does not create any remote EJB interfaces (only home and local interfaces were generated).
Something else I noticed is that when I proceed to the External Service Configuration -> Business Entities screen <http://remotehost:50000/webdynpro/dispatcher/sap.com/cafUIconfiguration>, I only see three business entities displayed, and the following error message is displayed: "Corrupt metadata has been detected. This may prevent some objects from being displayed. Check the server log for more details." I was unable to find anything in the instance log files. Is the error message indicative of the problem?
I am developing locally without a NetWeaver Development Infrastructure (NWDI) in place.
I'm wondering if the credentials specified in the endpoint require any special roles or privileges.
Senthil, do any of these additional descriptions apply to you as well?
Edited by: Ric Leeds on Jun 20, 2008 4:37 PM

ABAP Webdynpro as callable object to connect MDM Server

Hi All
if we want create MDM workflows in portal thru GP then we need to create the callable object initially which will integrate the MDM system thru MDM Apis
suppose if we choose the option of taking the ABAP webdynpro as callable object then what is the development efforts/Steps to involve for creating the callable objects.
i hope that we can use the ABAP wendynpro thru MDM ABAP APIs where we can integrate MDM data in ABAP webdynpro application.
can you please list out what is the Aims from enduser level and development level.
Please more details on this??
Regards
Suresh babu

Hi All
if we want create MDM workflows in portal thru GP then we need to create the callable object initially which will integrate the MDM system thru MDM Apis
suppose if we choose the option of taking the ABAP webdynpro as callable object then what is the development efforts/Steps to involve for creating the callable objects.
i hope that we can use the ABAP wendynpro thru MDM ABAP APIs where we can integrate MDM data in ABAP webdynpro application.
can you please list out what is the Aims from enduser level and development level.
Please more details on this??
Regards
Suresh babu

Exposing Web Services as Callable Objects

Hello!
I have SAP NetWeaver 04s SP7. How can I expose Web Services as Callable Objects?
According to "Exposing Web Services as Callable Objects" (http://help.sap.com/saphelp_nw2004s/helpdata/en/44/4758351fcb1193e10000000a155369/frameset.htm), I should start with choosing type of CO "Service -> Web Service".
Actually, I haven't this entry in CO type list!
According to integrate Web Services with GP, this type appeared in SP8. What are the alternatives in SP7?
"Background execution" and "External service" seem to be the best candidates...
What is the best solution?
Thanx in advance!

Hello, Jan!
I have SAP NWDS 7.0.07, and I cannot find there an option to create a CAF project. I can create Web service, EJB, Web DynPro, and something else - but not a CAF project. In documentation I did not find the connection points between NWDS and External Services, except some plug-ins.
Maybe I've misunderstood you, sorry - I'm a newbie in SAP
Actually, I've made a simple EJB, created a Web service from it, and deployed the WS to portal. Maybe, EJB instead of Web service can be somehow used in CAF?
I've tried to create a CO of type Composite Application Service, but there was necessary to configure endpoint aliases. I've read the manual "Configuring Endpoint Aliases", but didn't succeed to make one for EJB remote call... I've defined the name, URL (http://<host_of_portal>:<portal_port>), user and pwd - but I've got an exception when tried to use the created alias:
com.sap.caf.core.gp.servicelocator.exception.MetaModelBrowserException: Exception while trying to get InitialContext. at com.sap.caf.core.gp.servicelocator.CAFMetaModelBrowser.getAllApplications(CAFMetaModelBrowser.java:77) at com.sap.caf.core.gp.ui.backgroundco.admin.VSelect.browseCAFCore(VSelect.java:305) at com.sap.caf.core.gp.ui.backgroundco.admin.VSelect.onActionSelectEptAlias(VSelect.java:750) at com.sap.caf.core.gp.ui.backgroundco.admin.wdp.InternalVSelect.wdInvokeEventHandler(InternalVSelect.java:287) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at
Maybe, the easiest way is to upgrade the versions of SAP and NWDS?
Are there some manuals that could provide me some help about:
1) creating CAS from the deployed Web service (from its creation in NWDS till its use in CAF, step-by-step)
2) binding Web Dynpro apps and Web services, using CAF and GP.
Or maybe I should attend SAP courses?
I have SAP NetWeaver 04s SP7 and NWDS ver. 7.0.07.
Sorry for the messy post, I did my best
Message was edited by:
Kirill Shepitko

Adobe WebDynpro Callable Object

Hi all
I created Adobe WebDynpro application whihc worked well.
After creating callable object with WebDynpro (GP instance), and when i click complete button which is linked with complete method, following error occoured.
Actually adobe form web dynpro works well independently.
What do you think about that?
java.lang.NullPointerException
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.prepareSoapMessage(PDFObject.java:517)
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:351)
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.inputPDF(PDFObject.java:3643)
     at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentInputPDFHandler.handle(PDFDocumentInputPDFHandler.java:145)
     at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentProcessor.process(PDFDocumentProcessor.java:52)
     at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentAccessibleContext.execute(PDFDocumentAccessibleContext.java:149)
     at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.AdobeFormHelper.updateDataContainer(AdobeFormHelper.java:161)
     at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.beforeTransportData(InteractiveForm.java:465)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.beforeTransportData(ClientApplication.java:1130)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:141)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:297)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:726)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:662)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:228)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
     at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:808)
     at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:80)
     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1289)
     at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:324)
     at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:830)

Hi Aliaksandr,
I have the same issue and we desire the same. Also the button is placed outside the form....
Have you found out what could be a possible solution?
I couldn't find any note on this occurence.....
Thanks in advance!

BI Application Callable Object

Similar Messages

Maybe you are looking for