Error: BLS is exposed as Web Service

Hi All,
I have one small BLS which will get two integers as input params and yield their Sum as output param with Integer Data type. This BLS itself is working fine. Now while generating WSDL file on this BLS, I have use the URL like following
http://<server>/XMII/WSDLGen/<trasnactionpathname>/<transactionname> which is running fine in browser session itself
But when Iu2019m trying to test the same WSDL in WSNavigator from Netweaver, this is giving error as follow
The markup in the document following the root element must be well-formed
And while checking the log in NW this is saying as follows
An error occurred while loading WSDL: http://<Host>:<Port>/XMII/WSDLGen/Default/<Package>/<BLS>
[EXCEPTION]
com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: GenericServiceFactory initialization problem. [Problem with WSDL file parsing. See nested message.]
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:667)
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:130)
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:119)
at com.sap.esi.esp.wsnavigator.ManualTestView.createServiceByWSDL(ManualTestView.java:414)
at com.sap.esi.esp.wsnavigator.ManualTestView.onEventWSDLSelected(ManualTestView.java:1531)
at com.sap.esi.esp.wsnavigator.wdp.InternalManualTestView.wdInvokeEventHandler(InternalManualTestView.java:526)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:131)
at com.sap.tc.webdynpro.progmodel.components.Component.fireEvent(Component.java:488)
at com.sap.esi.esp.wsquery.ui.wsquerycomp.wdp.InternalWSQueryComp.wdFireEventWSDLSelected(InternalWSQueryComp.java:571)
at com.sap.esi.esp.wsquery.ui.wsquerycomp.WSQueryComp.searchByWSDL(WSQueryComp.java:826)
at com.sap.esi.esp.wsquery.ui.wsquerycomp.WSQueryComp.getSelectedService(WSQueryComp.java:459)
at com.sap.esi.esp.wsquery.ui.wsquerycomp.wdp.InternalWSQueryComp.wdInvokeMethod(InternalWSQueryComp.java:455)
at com.sap.tc.webdynpro.progmodel.generation.ExternalControllerPI$ExternalInterfaceInvocationHandler.invoke(ExternalControllerPI.java:339)
at $Proxy1834.getSelectedService(Unknown Source)
at com.sap.esi.esp.wsnavigator.ManualTestView.onActionStepChanged(ManualTestView.java:1314)
at com.sap.esi.esp.wsnavigator.ManualTestView.onActionNext(ManualTestView.java:1277)
at com.sap.esi.esp.wsnavigator.wdp.InternalManualTestView.wdInvokeEventHandler(InternalManualTestView.java:486)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:131)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:72)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:156)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:91)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:512)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:52)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1549)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1363)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDoProcessing(AbstractExecutionContextDispatcher.java:154)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppProcessing.doService(DispatchHandlerForAppProcessing.java:35)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToApplicationDoProcessing(ExecutionContextDispatcher.java:114)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:80)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:618)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:649)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:570)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:309)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:743)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:258)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:259)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:202)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToDispatcherContext(ExecutionContextDispatcher.java:146)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:92)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:104)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:61)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:486)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:243)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Problem with WSDL file parsing. See nested message.
at com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.loadWSDLapi(ProxyGeneratorNew.java:638)
at com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.generateAll(ProxyGeneratorNew.java:400)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.loadProxy(DGenericServiceImpl.java:231)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.<init>(DGenericServiceImpl.java:69)
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:617)
... 87 more
Caused by: com.sap.engine.services.webservices.espbase.wsdl.exceptions.WSDLException: The markup in the document following the root element must be well-formed.
at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.loadDOMDocument(WSDLLoader.java:145)
at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.load(WSDLLoader.java:90)
at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.load(WSDLLoader.java:79)
at com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.loadWSDLapi(ProxyGeneratorNew.java:632)
... 91 more
Caused by: org.xml.sax.SAXParseException: The markup in the document following the root element must be well-formed.
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.loadDOMDocument(WSDLLoader.java:131)
... 94 more
So is there anything Iu2019m missing or is there anything to be configured at NW server side? Please help
Our MII version : 12.1.5
Regards
Chandan
Edited by: Chandan Jash on Jun 8, 2011 6:47 PM

Hi Jeremy,
Thanks for your help. I am able to test it from WSnavigator but at the time of execution within XacuteRequest: two field are coming always.
XacuteRequest: 1) LoginName 2) LoginPassword:
Eithere I need to put the value there or I need to put the value within a popup when I click on next button.
But if I consume the Web Service from other place like as SAP ECC and trying to execute it then again I need to put the value for XacuteRequest: 1) LoginName 2) LoginPassword: as hardcode.
Is there any solution that I can avoid these two fields.
Thanks
Chandan

Similar Messages

XML Serialization Error- While testing BAPI turned Web service

I have a requirement to create sales order in SAP R/3 from an e-commerce site. I went through many forums suggesting "exposing FMs into Web Service". I wrapped BAPI_SALESORDER_CREATEFROMDAT2 and BAPI_TRANSACTION_COMMIT into one FM and exposed as Web Service. I did a successful test-sequence.
When I tested the web service without giving values I got a response asking for "Sold-to Party or Ship-To Party". While testing the Web service with some values, I got the below error -
XML Serialization Error. Object content does not correspond to Schema restrictions of type [urn:sap-com:document:sap:rfc:functions][numeric4].
The e-commerce team tried to hit the Web service and got the below error-
IWAB0383E Error validating parameters
Note: Our servers does not have any ENHPacks. Only ECC 6.0.
Please suggest what might have gone wrong and how to resolve this.
Thanks!

Hi Gourav Khare,
I have created WSDL file through function module in SAP-ECC 5.0v.
I have followed below steps:
Crated FM (SE37)
Crated Web-service (SE37)
Generated WSDL file using (WSADMIN)
And consumed WSDF file in SOAP UI (SOAP UI 4.5.2 Trailer version)
Problem is: while consuming WSDL file in SOAP UI I getting ‘Serialisation failed’
For your reference I have furnished xml string below.
SOAP UI Input:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:sap-com:document:sap:rfc:functions">
<soapenv:Header/>
<soapenv:Body>
<urn:YSDF_INV_PRINT_FINAL_RFC_WS_N>

<PWR_INVOICE>
<INVOICE_SHIPPED_LINE>

<item>
<POSITION1></POSITION1>
<SALES_PART></SALES_PART>
                  <PART_DESC></PART_DESC>
<PRICE></PRICE>
<QUANTITY></QUANTITY>
<CUSTOMER_TAX_NO></CUSTOMER_TAX_NO>
<PROD_NONINVENTORY></PROD_NONINVENTORY>
<PROD_TAXABLE></PROD_TAXABLE>
<TAX_LEVEL></TAX_LEVEL>
</item>
</INVOICE_SHIPPED_LINE>
<INVOICE_NO></INVOICE_NO>
<ORDER_NO></ORDER_NO>
<DATE_PRINTED></DATE_PRINTED>
<DIV_CD></DIV_CD>
            <LAST_COST_INVOICE></LAST_COST_INVOICE>
<DELETE_ZERO_COST></DELETE_ZERO_COST>
<DELETE_NON_SHIPPED></DELETE_NON_SHIPPED>
<GLOBALREF></GLOBALREF>
<ORIGIN></ORIGIN>
<ORIGINID></ORIGINID>
</PWR_INVOICE>
</urn:YSDF_INV_PRINT_FINAL_RFC_WS_N>
</soapenv:Body>
</soapenv:Envelope>
SOAP UI Output:
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
<soap-env:Body>
<soap-env:Fault>
<faultcode>soap-env:Client</faultcode>
<faultstring xml:lang="en">Serialisation failed</faultstring>
<detail>
<n0:SimpleTransformationFault xmlns:n0="http://www.sap.com/transformation-templates">
<MainName>/1BCDWB/WSS0130716111624448000</MainName>
<ProgName>/1BCDWB/WSS0130716111624448000</ProgName>
<Line>8</Line>
<Valid>X</Valid>
<ReferenceFault>
<DescriptionText>Error accessing the ref. node 'INVOICE_ID'</DescriptionText>
<RefName>INVOICE_ID</RefName>
</ReferenceFault>
<Caller>
                  <Class>CL_SRG_RFC_PROXY_CONTEXT</Class>
<Method>IF_SXML_PART~DECODE</Method>
<Positions>1</Positions>
</Caller>
</n0:SimpleTransformationFault>
</detail>
</soap-env:Fault>
</soap-env:Body>
</soap-env:Envelope>
And one more things are
I don't know the exact reason, but now the WSDL is working fine. No Idea, will it be consistent.
No changes in import and export parameters of RFC and no change in code, even if the logic is changed it should not affect the output on SOAP UI but in my case it does.
Wonder why all this happens, I cannot explain the exact reason technically because my RFC works fine every time, only issue is with SOAP UI.
From SAP point of view FM is working fine, and input parameter of FM is optional, validations are done by the programming logic and it will capture the message and its details with respect to input data.
I am not sure SOAP will work consistently and we are using ECC 5.0 most of the t-code not there like "SOAMANAGER" and all.
Kindly help me on this
Thanks & Regards,
   Akshath.L.T

Steps to expose a web service without using SR

Hello,
How can I expose a web service without using the service registry? Is there some documentation for this process?
Thanks,
Matt

Thanks for the response. Although, I do not have an * in the Sender Agreement.
Here is the situation:
When I attempt to reach the URL for my Web Service but using NWA instead of the Service Call I get into NWA.
https://xxxxx.steelcasedev.com/nwa
Result: Success
When I use SOAPSonar to run this URL I get the CPA error:
https://xxxxx.steelcasedev.com//XISOAPAdapter/MessageServlet?senderParty=&senderService=WSProcurement_Async_Sender&receiverParty=&receiverService=Steelcase_Dev&interface=WSProcure_Out&interfaceNamespace=urn:steelcasedev.com:wsprocure:xsuppliers
Result: Error
<context>XIAdapter</context>
          <code>ADAPTER.JAVA_EXCEPTION</code>
          <text><![CDATA[
com.sap.aii.af.service.cpa.CPAException: com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Couldn't retrieve inbound binding for the given P/S/A values: FP=;TP=;FS=WSProcurement_Async_Sender;TS=Steelcase_SAPR3_D01;AN=WSProcurement_Out;ANS=urn:steelcase.com:wsprocurement:xml2suppliers;
     at com.sap.aii.af.service.cpa.impl.lookup.CommonLookup.checkForError(CommonLookup.java:53)
     at com.sap.aii.af.service.cpa.InboundRuntimeLookup.getBinding(InboundRuntimeLookup.java:411)
     at com.sap.aii.af.service.cpa.impl.lookup.AbstractLookupManager.getBinding(AbstractLookupManager.java:714)
     at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:430)
The sender adapter is active in ID but in RTWB it is "Started but Inactive". I have found that this status could be related to the fact that I have not had a successful transaction for that channel yet.
My NW Admin says he found this error:
Marked transaction for rollback for message 0015605e-09d7-1ddf-94f7-d5031c019713(INBOUND). Reason: Channel has been configured as inactive and cannot accept messages
I am quite confused.
Thanks,
Matt

How to expose a web service to the outside world?

Hello,
i have created a Web service from a Session bean and successfully published it on one of my UDDI registries using the Admin tool.
At this point, what do I need to do further in order to expose this Web service not just in our LAN but to the outside world?
Roy

Offcourse it should be published at UDDI.
Four play key roles in Web services: Universal Description, Discovery and Integration (UDDI), Web Services Description Language (WSDL), Web Services Inspection Language (WSIL), SOAP, and Web Services Interoperability (WS-I).
The UDDI specification defines open, platform-independent standards that enable businesses to share information in a global business registry, discover services on the registry, and define how they interact over the Internet.
See this link too:
http://help.eclipse.org/help32/index.jsp?topic=/org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cwsdlud.html
Regards, Suresh KB

How to retrieve error message(s) after failed web service call

Hi!
I tried to create an item using the web service ego_item_pub.process_item and it worked ok (version 12.1.1). Sending the same request again, I got an error which should be ok since the item id already exists. The thing is, that I only get an "E" as return status:
<X_RETURN_STATUS>E</X_RETURN_STATUS>
<X_MSG_COUNT>1</X_MSG_COUNT>
As described in the integration repository, there should be a parameter called msg_data which should contain the message if there is exactly 1 message, but I cannot find it.
So, I tried to get the message using fnd_message.get, but the response of my web service call is:
AuthorizationFailure : User not authorized to execute service. (I use sysadmin/sysadmin as ws security user).
I use the following grant details:
All Users Direct GLOBAL Revoke Action Enabled
SYSADMIN SYSADMIN Direct USER
What else can I do or how can I retrieve error messages for a failed web service call?
Thanks a lot,
Konrad

Hi Konrad,
As we've found out, search the Integration Repository for internal name ERROR_HANDLER and use that. Letting the general public know the answer for this one!
Regards,
Gareth
http://garethroberts.blogspot.com

Are all RFCs and BAPIs automatically exposed as web services?

Hello,
Our product helps business users exchange data with SAP. We use standard RFCs and BAPIs to communicate with SAP. This is a .NET application although my question is not specific to .NET.
It seems SAP obsolete their .NET connector in near future. The emphasis is on web services. This is a great move. We can simply drop using the .NET connector and start using the web services. However, I have a few doubts:
1. RFCs and BAPIs are automatically exposed for remoting. When the customer installs our application, it just works out of the box. Customers do not have to make any configuration changes to SAP to expose RFCs and BAPIs.
In the new world, are all RFCs and BAPIs automatically exposed as web services or one has to go through each RFC/BAPI and expose it explicitly?
2. Is there a comprehensive WSDL schema available anywhere for all the RFCs/BAPIs?
3. Are there any other web services (besides RFCs/BAPIs) that SAP Netweaver exposes? Where can I get more information?
Thank you in advance for your help.
Regards,
Pradeep

Darryl,
Thank you for your help or at least trying to help me. However, you left me with more questions than answers:-(.
1. "Old" does not mean "bad." Each RFC/BAPI serves a specific function. If some RFC is being obsoleted, there must be a replacement documented somewhere. Is there one?
2. I can look into SE80 (and other transactions) to see what is exposed. However, what I need to understand is what is SAP's stance on exposing standard web services.
Can others please share your thoughts?
Regards,
Pradeep

Serialization error while invoking a Java web service

Hi,
I've a requirement where I need to create a Java web service, which returns a collection (a set of records).
The way I've created a web service is by having a Java Class, which internally calls a Pl/sql package returning Ref cursors and a bean Class, which wraps the method of the Java Class, to return the collection. I could create the web service successfully and could invoke the end point. The end point looks like this: http://localhost:8988/MyJavaWebService-New_JWS-context-root/MyWebService_finalSoapHttpPort
The method exposed for the web service in my Java class is of type ArrayList, to fetch the collection element.
After giving the input at the end point, while I say invoke, for the web service, I get the following error:
<env:Envelope
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:ns0="http://mypkg/types/"
xmlns:ns1="http://www.oracle.com/webservices/internal/literal">
<env:Body>
<env:Fault>
<faultcode>env:Server</faultcode>
<faultstring>Internal Server Error (serialization error: no serializer is registered for (class mypkg.EmpBean, null))</faultstring>
</env:Fault>
</env:Body>
</env:Envelope>
I've tried making my exposed method of type Vector as well and re-generated the web service. But still I face the same issue at invocation.
Can anybody help me out and hint me on how I should proceed? I'm not sure if my approach is correct and so please correct me if I'm wrong.
Thanks in Advance,
Gayathri

Hi,
do you use 10.1.2 or 10.1.3?
Take a look at:
Re: How to create a web service with ArrayList or Collection

Security Error when trying to access web service

I have an app that connects over HTTPS to a web service on
our internal network. The interface to the web service was created
by using the WSDL Import function of the Flex IDE.
I can run the app and retrieve data without a problem when I
run from the debug-bin folder that the Flex IDE compiles to.
However, I cannot connect to the web service from anywhere else,
such as a different location on my own local drives, a network
drive, or another persons machine.
I've setup a local instance of Apache with mod_ssl so I could
host the app under an HTTPS connection itself, which the
documentation seemed to imply that would work. However, when I run
the app, I get:
[FaultEvent fault=[RPC Fault faultString="Security error
accessing url" faultCode="Channel.Security.Error"
faultDetail="Destination: DefaultHTTPS"] messageId=null
type="fault" bubbles=true cancelable=true eventPhase=2]
I am accessing the app by going to
https://mymachine.companydomain.com/myapp.html, and the web service
is being accessed through https://webservice.companydomain.com/.
Anybody have any thoughts on what I should be looking at?
I've been searching and trying things for a few days with no luck.
Any help would be appreciated. Thanks.

The SSL handshake works differently to a browser as it is making the connections automatically.
The browser asks every time if you want to trust an expired certificate, and it also recommends not to. Its impractical to manually check every service call to say do you trust the certificate so the functionality doesn't exist. I doubt any integration product does this. Therefore there isn't a option to ignore the certificate if it has expired.
This makes sence as the certificate is untrustworthy. The whole idea around SSL is trusting the site you are communicating with, all parties need to be trusted. This stops hackers from replicating their site and intercepting data.
If the administrator of the remote site is not willing to renew the certificate, are they really interested in SSL. I suggest they expose a non SSL service.
cheers
James

Getting error when trying to invoke web service - disable SSL

Hi
Please advise me how to disable the SSL for bpel.
The problem which am facing is as below
I am trying to invoke web service in another site, its showing me error as
javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateExpiredException:
Now i would like to disable the SSL for this handshake, so that it wont look for certificates and invokes the web service directly, right.
So please advise how to disable to SSL in bpel (10.1.2) now.
Thanks
Suneel Jakka

The SSL handshake works differently to a browser as it is making the connections automatically.
The browser asks every time if you want to trust an expired certificate, and it also recommends not to. Its impractical to manually check every service call to say do you trust the certificate so the functionality doesn't exist. I doubt any integration product does this. Therefore there isn't a option to ignore the certificate if it has expired.
This makes sence as the certificate is untrustworthy. The whole idea around SSL is trusting the site you are communicating with, all parties need to be trusted. This stops hackers from replicating their site and intercepting data.
If the administrator of the remote site is not willing to renew the certificate, are they really interested in SSL. I suggest they expose a non SSL service.
cheers
James

Error while invoking a external Web service

Hi all,
I am getting a error while invoking the webservice.
I have tested in soapUI its working there but in BPEL it gives me error.
Soap request:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<soap:Header>
<wsa:Action xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" bpel:priority="" bpel:completionPersistPolicy="" xmlns:bpel="http://schemas.oracle.com/bpel">http://www.lodestarcorp.com/ProcessPayloadString</wsa:Action>
<wsa:MessageID xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" bpel:priority="" bpel:completionPersistPolicy="" xmlns:bpel="http://schemas.oracle.com/bpel">uuid:058a8965-3bd3-4e29-8c2b-f96f74ccef7d</wsa:MessageID>
<wsa:To xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" bpel:priority="" bpel:completionPersistPolicy="" xmlns:bpel="http://schemas.oracle.com/bpel">http://mngktr51623/lodestar/platform/webservices/AdapterWS.asmx</wsa:To>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" soap:mustUnderstand="1">
<wsse:UsernameToken xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:Username>Divya_V</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">password1</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</soap:Header>
<soap:Body xmlns:ns1="http://www.lodestarcorp.com/">
<ns1:ProcessPayloadString>
<ns1:serviceID>WS_MDM_AVAILABILITY</ns1:serviceID>
<ns1:payload><![CDATA[<MDMREQUEST><METERACTIVE METERID="CON_METER_00"/></MDMREQUEST>]]></ns1:payload>
</ns1:ProcessPayloadString>
</soap:Body>
</soap:Envelope>
Error Message:
<remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
-<part name="code">
<code>Security
</code>
</part>
-<part name="summary">
<summary>
Header http://schemas.xmlsoap.org/ws/2004/08/addressing:Action for ultimate recipient is required but not present in the message.
</summary>
</part>
-<part name="detail">
<detail>null
</detail>
</part>
</remoteFault>
I have provided the Action header but still the same error message.
Kindly assist.
With Regards,
Divz

Hi,
do you use 10.1.2 or 10.1.3?
Take a look at:
Re: How to create a web service with ArrayList or Collection

Error when invoking pl/sql web service from bpel

Hi!
I have a simple 'Hello World' pl/sql web service. When i invoke it in asynchronous BPEL process, a local WSDL file is automatically generated for the parterlink used. The process even gets successfully deployed without any warning or error. But in the BPEL console when I create an instance, its alwaya being faulted and the audit give the following error at invoke:
"{http://schemas.oracle.com/bpel/extension}remoteFault" has been thrown. less
<remoteFault>
<part name="code" >
<code>Server.userException</code>
</part>
<part name="summary" >
<summary>when invoking endpointAddress 'null', java.net.UnknownHostException: www.proxy.us.oracle.com</summary>
</part>
<part name="detail" >
<detail>AxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException faultSubcode: faultString: java.net.UnknownHostException: www.proxy.us.oracle.com faultActor: faultNode: faultDetail: {http://xml.apache.org/axis/}stackTrace:java.net.UnknownHostException: www.proxy.us.oracle.com at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:153) at java.net.Socket.connect(Socket.java:452) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.collaxa.thirdparty.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:155) at org.collaxa.thirdparty.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:117) at org.collaxa.thirdparty.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:158) at org.collaxa.thirdparty.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:450) at org.collaxa.thirdparty.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:94) at org.collaxa.thirdparty.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32) at org.collaxa.thirdparty.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) at org.collaxa.thirdparty.apache.axis.SimpleChain.invoke(SimpleChain.java:83) at org.collaxa.thirdparty.apache.axis.client.AxisClient.invoke(AxisClient.java:147) at org.collaxa.thirdparty.apache.axis.client.Call.invokeEngine(Call.java:2732) at org.collaxa.thirdparty.apache.axis.client.Call.invoke(Call.java:2715) at org.collaxa.thirdparty.apache.axis.client.Call.invoke(Call.java:1737) at com.collaxa.cube.ws.wsif.providers.axis.WSIFOperation_ApacheAxis.invokeAXISMessaging(WSIFOperation_ApacheAxis.java:2113) at com.collaxa.cube.ws.wsif.providers.axis.WSIFOperation_ApacheAxis.invokeRequestResponseOperation(WSIFOperation_ApacheAxis.java:1611) at com.collaxa.cube.ws.wsif.providers.axis.WSIFOperation_ApacheAxis.executeRequestResponseOperation(WSIFOperation_ApacheAxis.java:1083) at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:452) at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:327) at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:189) at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:601) at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:317) at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:188) at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3408) at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1836) at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75) at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:166) at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:252) at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5438) at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1217) at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:511) at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:335) at ICubeDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(ICubeDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1796) at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:37) at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:125) at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70) at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86) at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123) at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755) at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928) at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186) at java.lang.Thread.run(Thread.java:534) {http://xml.apache.org/axis/}hostname:NewUser-lap </detail>
</part>
</remoteFault>
Can anybody please tell what could be the problem,
Thanking in advance,
Deepika.

www.proxy.us.oracle.com -> www-proxy.us.oracle.com - looks like set in the obsetenv.bat file

Getting error while deploying a simple web services

Hi
i am new to web services when i am deploying the web service using
deployment descriptor(WSDD) file using admin client i am getting the follwing error can any body help regarding this.
Mydeployment descriptor is
deploy.wsdd
<deployment xmlns="http://xml.apache.org/axis/wsdd/"
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
<service name="MyService" provider="java:RPC">
<parameter name="className" value="samples.userguide.example3.MyService"/>
<parameter name="allowedMethods" value="*"/>
</service>
</deployment>
I am getting exception as
C:\Program Files\Apache Software Foundation\Tomcat 5.5\webapps\axis\WEB-INF\clas
ses>java org.apache.axis.client.AdminClient deploy.wsdd
Feb 5, 2008 2:34:54 PM org.apache.axis.utils.JavaUtils isAttachmentSupported
WARNING: Unable to find required classes (javax.activation.DataHandler and javax
.mail.internet.MimeMultipart). Attachment support is disabled.
Processing file deploy.wsdd
Exception: AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.net.ConnectException: Connection refused: connect
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.net.ConnectException: Conne
ction refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:364)
at java.net.Socket.connect(Socket.java:507)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSoc
ketFactory.java:153)
at org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSoc
ketFactory.java:120)
at org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:1
91)
at org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.ja
va:404)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
y.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:1792)
at org.apache.axis.client.AdminClient.process(AdminClient.java:439)
at org.apache.axis.client.AdminClient.process(AdminClient.java:404)
at org.apache.axis.client.AdminClient.process(AdminClient.java:410)
at org.apache.axis.client.AdminClient.process(AdminClient.java:320)
at org.apache.axis.client.AdminClient.main(AdminClient.java:463)
{http://xml.apache.org/axis/}hostname:MUM-12016RS

Hi Jhansi,
Whether u create HRconnDS in ur Weblogic server
If not create it ...
If yes just check it out whether u gave a correct connection string for it......
Regards,
Suganth.G

401:Unauthorized error while consuming a MOSS web service

Hi, We are trying to cosume a Web Service from MOSS using Spring and Axis. The WSDL requires user name and password. We are passing the right credentials however we are getting the 401 error. The exact exception is provided below. Could any one advise how this can be resolved?
java.io.FileNotFoundException: Response: '401: Unauthorized' for url: 'https://ts2amr.accenture.com/_vti_bin/Search.asmx?wsdl'.
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'spWSClient' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'spWebService' while setting bean property 'service'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'spWebService' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Invocation of init method failed; nested exception is org.springframework.remoting.RemoteLookupFailureException: Failed to initialize service for JAX-RPC port [{urn:Microsoft.Search}QueryServiceSoap]; nested exception is javax.xml.rpc.ServiceException: Error processing WSDL document:
java.io.FileNotFoundException: Response: '401: Unauthorized' for url: 'https://ts2amr.accenture.com/_vti_bin/Search.asmx?wsdl'

I can't speak for MOSS for sure, but other Microsoft services such as MapPoint used to require Digest Authentication, which isn't quite as pervasive as Basic Authentication. You should doublecheck with the MOSS administrator about the proper credentials and access. You might even try a utility like SoapUI to see if things work from a test client before trying it on the application server.

Error while creating MBO with web service data source

Hi All,
I am trying to create MBO by selecting web service as a data source type in SMP 2.3. I am providing sharepoint webservice url of type wsdl with HTTP basic authentication. However, I am getting following error can anyone help me in that. Looking for detail explaination as this is new for me...
(For "define XSLT manually" I am using sample .xsl file)
Regards,
Harshada

Harshada Karane
Are you using any proxy in your browser? If yes, please set the proxy in workspace and then trHow to bypass proxy settings in SMP workspace for connecting any public Web Service within corporate Network
Rgrds
JK

Getting an error while building a sample web service

Hi,
I am beginner in web services and started working on a sample application in a web service tutorial.
Build is failing in build.xml file while building sample web service using ant tool.
antBuildfile: build.xml
clean:
setup:
[mkdir] Created dir: /tmp/output/WEB-INF/classes
[mkdir] Created dir: /tmp/client_classes
compile.server:
[javac] Compiling 1 source file to /tmp/output/WEB-INF/classes
webservice.build:
webss.build:
BUILD FAILED
Z:/JAVA-COBOL/sample1/tutorial/sample1/build.xml:43: The following error occurred while executing this line:
Z:/JAVA-COBOL/sample1/tutorial/sample1/build-webss.xml:10: Problem: failed to create task or type source2wsdd*_
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any <presetdef>/<macrodef> declarations have taken place.
Can anyone look into this and let me know if you have any idea on this?
Thanks,
SRoop.
Edited by: SRoop on Jun 20, 2008 9:11 AM
Edited by: SRoop on Jun 20, 2008 9:14 AM
Edited by: SRoop on Jun 21, 2008 5:51 AM

Hi,
I am beginner in web services and started working on a sample application in a web service tutorial.
Build is failing in build.xml file while building sample web service using ant tool.
antBuildfile: build.xml
clean:
setup:
[mkdir] Created dir: /tmp/output/WEB-INF/classes
[mkdir] Created dir: /tmp/client_classes
compile.server:
[javac] Compiling 1 source file to /tmp/output/WEB-INF/classes
webservice.build:
webss.build:
BUILD FAILED
Z:/JAVA-COBOL/sample1/tutorial/sample1/build.xml:43: The following error occurred while executing this line:
Z:/JAVA-COBOL/sample1/tutorial/sample1/build-webss.xml:10: Problem: failed to create task or type source2wsdd*_
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any <presetdef>/<macrodef> declarations have taken place.
Can anyone look into this and let me know if you have any idea on this?
Thanks,
SRoop.
Edited by: SRoop on Jun 20, 2008 9:11 AM
Edited by: SRoop on Jun 20, 2008 9:14 AM
Edited by: SRoop on Jun 21, 2008 5:51 AM

Error: BLS is exposed as Web Service

Similar Messages

Maybe you are looking for