Web Service Action Block

I'm attempting to call a web service that we have developed. I'm able to configure the webservice block without any problems. However, when I attempt to execute the block I get a "Internal server error" message. When I look in the general log I have the following message:
Classname: IntrospectionUtilities
Mesage: Generic Reflection error (Set): java.lang.NoSuchMethodException: com.lighthammer.xacute.actions.webservice.WebServiceAction.setSoapService(java.lang.String) -> setSoapService
Does anyone know what this message means ?
Thanks
Glenn

Glenn,
Unfortunately its not easy to tell why the Web Service call is failing without knowing what the Web Service is doing. But I can explaing what the SoapService is in xMII and maybe this will help....
The Soap Service to xMII is a helper class that parses the WSDL for the various ports and operations that are defined. It gets the transport URI of the service and also the SOAP Body to be used as a reference.
If your WebService fails to return these or they are malformed then the SoapService object will not create properly and cause this method to fail. My suggestion is to either examine your Web Service to make sure it meets proper W3 standards OR to use the POST action block to perform the HTTP operation.
Hope this helps.
-Sam

Similar Messages

Calling Enterprise Services through xMII Web Service action block

Hi All,
I'm calling some Enterprise Service through xMII Web Service action block.
After providing URL and user credentials, I'm getting error "SOAP Service could not be loaded: The element type 'p' must be terminated by the matching end-tag ''."
Can anyone point out what might be the reason ?
Thanks,
Sumit

If you haven't already, try using the browser from the xMII server machine rather than your own (client).
The error that you recieve usually means that instead of a WSDL an HTML is being returned when you use the WebService action block.
Possible reasons - as Jeremy pointed out - improper credentials or some error with the webservice itself.
Another thing you can possibly try out - use some web service analyser to access the webservice . There's one that goes by the name StrikeIron which is a freeware.Pretty neat tool.

Cannot see the elements in Web Service Action block

Hi,
When I use SoapUI I can see the elements of a Service but when I use Web Service Action block of MII, I can only see the first element (job). The children of job are not appearing in link editor. Any Idea?
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.ct.xxx.de" xmlns:xsd="http://data.xxx.de/xsd">
 <soapenv:Header/>
 <soapenv:Body>
 <ws:startJob>
 
 <ws:job>
 
 <xsd:a>?</xsd:a>
 
 <xsd:dir>?</xsd:dir>
 
 <xsd:dirR>?</xsd:dirR>
 
 <xsd:u>?</xsd:u>
 
 <xsd:g>?</xsd:g>
 
 <xsd:value>?</xsd:value>
 </ws:job>
 </ws:startJob>
 </soapenv:Body>
</soapenv:Envelope>

Anyone has any idea? I really appreciate any idea. Thanks

Passing Url dynamically in WEB SERVICE Action block

Hi All below is my requirement, kindly help
We have three environments 1. Development 2. Testing 3.Production
In one of the BLS i have used Web Service Action block by putting the web service url.
Whenever the BLS is moved from Testing environment or to Production i need to change the Url manually.
So, i want some generic method to by which i don have to change the Url whenever the code is moved to Testing or Production.
As far as i know that whenever i am putting the Url in the editor i need to press the next button to configure it but i want to get rid of this manual configuration.
But i guess while we configure Web Service action block by putting the Url in editor and pressing the Next button it congigures the Listener Port for configuration.
So is there any way by which this done done dynamically without configuring.
I mean i want to put the URL once in Development environment and if it is moved to Testing or production then also it should work.
A quick reply will be appreciated. I am using MII 12.0

Anyone has any idea? I really appreciate any idea. Thanks

MII 12.1.5 Web Service Action Block

Is there existing documentation on using the Web Service Action Block, specifically documenting the following Object Properties:
WSDLBaseUrl
Credential Alias:
I am trying to execute a Web Service Action block against a web service that uses http and basic authentication (User/Password). the WSDL loads just fine, the UserName and Password properties exposed through the WSDL are assigned valid values in Links Configuration, but according to the web service logs, the user name 'Guest' is being passed for the UserName. This same web service works in MII 12.1.1 Build 273.
Thanks in advance!

Steve,
The WSDLBaseURL property just prepends a string to the WSDL URL property so that you can abstract out the protocol, server and port values separately depending on the target system you wish to hit for the service call.
Regards,
Sam

Getting a error invoking web service action block

HI
I am first time using web service action block in xmii. I am using it for executing my transaction . But it is giving error stating that
Error invoking web service action block. I dont know please help me out?

Hi Mike,
I am using xMII - 11.5 version and with java 1.6.0_07. In My system i have installed service pack 3. When ever i use webservice action block and execute it, It gives error stating .
[INFO ]: Execution Started At: 11:07:16
[DEBUG]: 00000.01600 Begin Transaction 'TMP83E3D064-F6E8-4E3D-647F-6CE6B41C9E83'
[DEBUG]: 00000.01600 Begin Sequence Sequence : ()
[DEBUG]: 00000.01600 Begin Action WebService_0 : ()
[ERROR]: Error Invoking Web Service Action: null
[ERROR]: ACTION FAILED: End Action WebService_0 : ()
[DEBUG]: 00001.42200 Begin Sequence Sequence_0 : ()
[DEBUG]: 00001.42200 Begin Action Tracer_0 : ()
[INFO ]: <?xml version="1.0" encoding="UTF-8"?><XacuteResponse xmlns="http://www.lighthammer.com/Xacute"><Rowsets DateCreated="2000-01-01T00:00:00" EndDate="2000-01-01T00:00:00" StartDate="2000-01-01T00:00:00" Version=""><FatalError/><Messages><Message/></Messages><Rowset><Columns><Column Description="" MaxRange="0.00" MinRange="0.00" Name="" SQLDataType="0" SourceColumn=""/></Columns><Row><Output/></Row></Rowset></Rowsets></XacuteResponse>
[DEBUG]: 00001.43700 End Action Tracer_0 : ()
[DEBUG]: 00001.43700 End Sequence Sequence_0 : ()
[DEBUG]: 00001.43700 End Sequence Sequence : ()
[DEBUG]: 00001.43700 End Transaction 'TMP83E3D064-F6E8-4E3D-647F-6CE6B41C9E83'
[INFO ]: Execution Completed At: 11:07:17 Elapsed Time was 1421 mS
please help me out .

Web Service Action Block in MII 12.0

Hi All,
We are trying to understand the functionality of web services action block in MII 12.0 with a third party application.
Can anyone share the complete procedure of the configuration to understand the data flow between webservice block with third party application.
Thanks
Rajesh S

Rajesh,
let's take your example. An external web service has been created with C or .NET or other tools. The creator of the web service also have created a URL that you can use to call the web service. The web service may accept input and responses output. The input / output parameters (among other settings) are defined in the WSDL.
Now you want to call the external web service in MII. You create a BLT with the web service action. After you have entered the URL and press enter the web service configuration wizard calls the URL and retrieves the WSDL data (if the URL is correct). That's what I have described above.
In the link editor MII displays the XML structure of the web service. There you can link data to the input parameter of the web service, e.g. the contents of a file. If the web service action is processed, the web service is called using the linked values, and the file contents is submitted.
The external party can also call any MII BLT as a web service using the MII WSDLGen service. In the BLT, you also define Transaction Properties as input and output parameters. WSDLGen will build a xml structure using these parameters. If the external party want to send the file contents, it calls the MII web service with the file contents in the Transaction input property.
You can easily test a MII web service. You just need two BLTs, one calling the other to see if the file contents is sent correctly.
Does this explanation help? I do not see a difference between a URL and WSDL URL. The file contents is passed inside the web call, not stored in a location.
Michael

Web Service Action block throws Internal Server Error 500

Please forgive the lengthy message!
Web service Action block authenticates the user as confirmed from the web service logs. Now I get an Internal Server Error 500. Is this a bug in MII? The WS does execute correctly from a .Net Client.
Here is the Message from the error in MII NetWeaver log:
SOAP Invoke Error. Status: 500 Message: Internal Server Error
[EXCEPTION]
java.lang.Exception: Status (500): Internal Server Error
at com.sap.lhcommon.webservice.SoapClient.invoke(SoapClient.java:81)
at com.sap.xmii.bls.executables.actions.webservice.WebServiceActions.callWebService(WebServiceActions.java:319)
at com.sap.xmii.bls.executables.actions.webservice.WebServiceActions.webService(WebServiceActions.java:408)
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:585)
at com.sap.xmii.bls.engine.DataBufferPayload.execute(DataBufferPayload.java:157)
at com.sap.xmii.bls.engine.ReflectiveAction.doExecute(ReflectiveAction.java:629)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:195)
at com.sap.xmii.bls.engine.BaseAction.execute(BaseAction.java:75)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runAction(ProductionRunner.java:121)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:50)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:102)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:59)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:102)
at com.sap.xmii.bls.executables.sequences.RootNode.execute(RootNode.java:39)
at com.sap.xmii.bls.engine.TransactionInstance.execute(TransactionInstance.java:879)
at com.sap.xmii.bls.engine.TransactionInstance.run(TransactionInstance.java:586)
at com.sap.xmii.bls.engine.TransactionExecuter.runTransactionInstance(TransactionExecuter.java:613)
at com.sap.xmii.bls.engine.TransactionExecuter.executeFromHttpRequest(TransactionExecuter.java:258)
at com.sap.xmii.servlet.Runner.service(Runner.java:81)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.sap.xmii.servlet.ServletRunner.run(ServletRunner.java:80)
at com.sap.xmii.common.LocalServiceConnection.post(LocalServiceConnection.java:137)
at com.sap.xmii.xacute.common.ClientCatalogUtilities.postServiceConnection(ClientCatalogUtilities.java:1946)
at com.sap.xmii.xacute.transaction.TransactionUtilities.ExecuteTransaction(TransactionUtilities.java:432)
at com.sap.xmii.servlet.Catalog.handleExecuteTempTrx(Catalog.java:254)
at com.sap.xmii.servlet.Catalog.service(Catalog.java:210)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:162)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:81)
at com.sap.xmii.system.SecurityFilter.doFilter(SecurityFilter.java:96)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:441)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:291)
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:240)
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:425)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:250)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
--Steve

Steve,
The 500 error is what we get back from the target server.
This is probably not a bug since I don't think that MII has ever supported the SOAP-Fault node to build the response XML.
Sam
PS: For those of you reading this we had an offline discussion about this.

Error when using Web service Action Block.

Hi All
I am calling recursive function in my transaction.Means same transaction i am calling inside a transaction.I have used the Webservice Action block to call the transaction.
I have passed the parameters whatever is requied.
But I am getting error when i am executing the transaction:
"Error invoking Webservice Action: Status(500):Internal Server Error".
Please suggest me on this.
Thanks in advance.
Regards,
Manisha

Hi Vishal
This transaction is trying to achieve the recursive function.
I want to call the same transaction within a transaction.So i have used WebService action block to call the transaction.
I have passed the input parameters whatever required.I have given loginName and password as my server login name and password.But when i am executing the transaction, I am getting the following error:
"Internal Server Error"
If any idea please suugest me.
Thanks,
Manisha

Web Service Action in Block in SAP MII has a problem.?

Hi Experts,
I am trying to consume Primavera web service from SAP MII 12.1
Getting the following error
[INFO] [Tracer_0]An error was discovered processing the <wsse:Security> header
I am using web logic server 10.3 as my App Server and Primavera p6 PPM,trying to connect to primavera web services through MII
Web Service:http://localhost/p6ws/services/BaselineProjectService?wsdlAny Updates to be applied on SAP Netweaver,I applied patches too but no luck
I am able to get default port when I Authenticate using Credential Alias Attribute of Web Service Action Block
I am getting the same default port when I dont use the credential alias also
But My Final response from the server is an Error,
I thought its an authentication error,but not sure how to proceed to solve the error.
Please help.

Hi Subhanim,
As of my knowledge, you need to specifies Credential Alias as it automatic appears in Configure object and in the mean time you need to set configure link for User Credentials map.
I think this will solve your error.
Thanks,
Kind Regards,
Praveen Reddy M

Error While generating Web Service Proxy using Web Service Action in MII 12

Hi All,
We are using the Web Service action block in BLS transaction to call a web service from an external legacy system. When we provide the WSDL in the action block configuration and click Next we can see the Port and Operation of the web service which we have selected and finally clicked on Finish. On clicking Finish it is giving an error "[Fatal Error] :-1:-1: Premature end of file." and no web service request/response structures are being generated.
The WSDL file is attached herwith. Please check and provide the solution. We are using MII 12.2 SP02 with latest patch.
An error message is also added to the NetWeaver log as below:
XmlProxy Error: Premature end of file.
[EXCEPTION]
org.xml.sax.SAXParseException: Premature end of file.
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.lhcommon.schema.XmlHelper.loadDocument(XmlHelper.java:38)
at com.sap.lhcommon.schema.XmlHelper.loadDocumentNS(XmlHelper.java:28)
at com.sap.lhcommon.webservice.SoapMessage.getExampleXmlAsBytes(SoapMessage.java:103)
at com.sap.xmii.servlet.XmlProxy.service(XmlProxy.java:204)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:162)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:81)
at com.sap.xmii.system.SecurityFilter.doFilter(SecurityFilter.java:96)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
at com.sap.xsrf.filter.XSRFProtectorFilter.doFilter(XSRFProtectorFilter.java:62)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:468)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:399)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:388)
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:84)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:244)
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:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327)
The wsdl file is as follows:
<wsdl:definitions
targetNamespace="urn:cat.cis.mesassembly.server.service.pod"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://pod.service.server.mesassembly.cis.cat"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:intf="urn:cat.cis.mesassembly.server.service.pod"
xmlns:impl="urn:cat.cis.mesassembly.server.service.pod"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding"
>
<wsdl:types>
 <schema targetNamespace="http://pod.service.server.mesassembly.cis.cat"
 xmlns="http://www.w3.org/2001/XMLSchema">
 <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
 <complexType name="ProductionOrderDetailsInput">
 <sequence>
 <element name="detailsString" type="xsd:base64Binary"/>
 <element name="productionOrderNumber" nillable ="true" type="xsd:string"/>
 <element name="fullExplosionFlag" type="xsd:string"/>
 </sequence>
 </complexType>
 <complexType name="ProductionOrderDetailsReceipt">
 <sequence>
 <element name="errorMessage" nillable="true" type="xsd:string"/>
 <element name="valid" type="xsd:boolean"/>
 </sequence>
 </complexType>
 </schema>
</wsdl:types>
<wsdl:message name="processOrderDetailsResponse">
<wsdl:part name="podReturn" type="tns:ProductionOrderDetailsReceipt" />
</wsdl:message>
<wsdl:message name="processOrderDetailsRequest">
<wsdl:part name="input" type="tns:ProductionOrderDetailsInput" />
</wsdl:message>
<wsdl:portType name="PodService">
 <wsdl:operation name="ProcessOrderDetails" parameterOrder="input">
 <wsdl:input message="impl:processOrderDetailsRequest"
 name="processOrderDetailsRequest"/>
 <wsdl:output message="impl:processOrderDetailsResponse"
 name="processOrderDetailsResponse"/>
 </wsdl:operation>
</wsdl:portType>
<wsdl:binding name="ProdOrderDetailsSoapBinding" type="impl:PodService">
 <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
 <wsdl:operation name="ProcessOrderDetails">
 <soap:operation soapAction="http://pod.service.server.mesassembly.cis.cat/NewOperation"/>
 <wsdl:input name="processOrderDetailsRequest">
 <soap:body use="literal" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:cat.cis.mesassembly.server.service.pod" />
 </wsdl:input>
 <wsdl:output name="processOrderDetailsResponse">
 <soap:body use="literal" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:cat.cis.mesassembly.server.service.pod" />
 </wsdl:output>
 </wsdl:operation>
</wsdl:binding>
<wsdl:service name="PodService_Service">
 <wsdl:port binding="impl:ProdOrderDetailsSoapBinding" name="ProdOrderDetails">
 <soap:address location="http:/localhost:8080/MESAssembly/services/ProdOrderDetails"/>
 </wsdl:port>
</wsdl:service>
</wsdl:definitions>

The WSDL file is as follows:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions
targetNamespace="urn:cat.cis.mesassembly.server.service.pod"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://pod.service.server.mesassembly.cis.cat"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:intf="urn:cat.cis.mesassembly.server.service.pod"
xmlns:impl="urn:cat.cis.mesassembly.server.service.pod"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding"
>
<wsdl:types>
 <schema targetNamespace="http://pod.service.server.mesassembly.cis.cat"
 xmlns="http://www.w3.org/2001/XMLSchema">
 <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
 <complexType name="ProductionOrderDetailsInput">
 <sequence>
 <element name="detailsString" type="xsd:base64Binary"/>
 <element name="productionOrderNumber" nillable ="true" type="xsd:string"/>
 <element name="fullExplosionFlag" type="xsd:string"/>
 </sequence>
 </complexType>
 <complexType name="ProductionOrderDetailsReceipt">
 <sequence>
 <element name="errorMessage" nillable="true" type="xsd:string"/>
 <element name="valid" type="xsd:boolean"/>
 </sequence>
 </complexType>
 </schema>
</wsdl:types>
<wsdl:message name="processOrderDetailsResponse">
<wsdl:part name="podReturn" type="tns:ProductionOrderDetailsReceipt" />
</wsdl:message>
<wsdl:message name="processOrderDetailsRequest">
<wsdl:part name="input" type="tns:ProductionOrderDetailsInput" />
</wsdl:message>
<wsdl:portType name="PodService">
 <wsdl:operation name="ProcessOrderDetails" parameterOrder="input">
 <wsdl:input message="impl:processOrderDetailsRequest"
 name="processOrderDetailsRequest"/>
 <wsdl:output message="impl:processOrderDetailsResponse"
 name="processOrderDetailsResponse"/>
 </wsdl:operation>
</wsdl:portType>
<wsdl:binding name="ProdOrderDetailsSoapBinding" type="impl:PodService">
 <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
 <wsdl:operation name="ProcessOrderDetails">
 <soap:operation soapAction="http://pod.service.server.mesassembly.cis.cat/NewOperation"/>
 <wsdl:input name="processOrderDetailsRequest">
 <soap:body use="literal" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:cat.cis.mesassembly.server.service.pod" />
 </wsdl:input>
 <wsdl:output name="processOrderDetailsResponse">
 <soap:body use="literal" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:cat.cis.mesassembly.server.service.pod" />
 </wsdl:output>
 </wsdl:operation>
</wsdl:binding>
<wsdl:service name="PodService_Service">
 <wsdl:port binding="impl:ProdOrderDetailsSoapBinding" name="ProdOrderDetails">
 <soap:address location="http:/localhost:8080/MESAssembly/services/ProdOrderDetails"/>
 </wsdl:port>
</wsdl:service>
</wsdl:definitions>

Error Invoking Web Service Action: Status (500): null

Hi forum
I am getting an "Invoking Web Service Action: Status (500): null" error when invoking a web service action block . The BLS transaction used as a web service outputs a text string which I tested using an xacute query . while executing the transaction as a web service the tracer tells me that there is no output .
Best regards,
Antonio
I am using an xMII 11.5 installation .
[INFO ]: Execution Started At: 04:17:46
[DEBUG]: 00000.01600 Begin Transaction 'TMP45B360D9-0E02-2CF7-C4B4-F3C0B41C29E0'
[DEBUG]: 00000.01600 Begin Sequence Sequence : ()
[DEBUG]: 00000.01600 Begin Action WebService_0 : ()
[ERROR]: Error Invoking Web Service Action: Status (500): null
[ERROR]: ACTION FAILED: End Action WebService_0 : ()
[DEBUG]: 00000.11000 Begin Sequence Sequence_0 : ()
[DEBUG]: 00000.11000 Begin Action Tracer_0 : ()
[INFO ]:
[DEBUG]: 00000.11000 End Action Tracer_0 : ()
[DEBUG]: 00000.11000 End Sequence Sequence_0 : ()
[DEBUG]: 00000.11000 End Sequence Sequence : ()
[DEBUG]: 00000.11000 End Transaction 'TMP45B360D9-0E02-2CF7-C4B4-F3C0B41C29E0'
[INFO ]: Execution Completed At: 04:17:46 Elapsed Time was 94 mS

Jamie,
Yes Indeed, I was calling inside a web service action another BLS transaction . Now , I am using a call to the transaction using the runner . It worked fine .
Thanks,

Run Web Service Action

Can someone point me to any documentation for the Run Web Service action? I'm looking for simple field level syntax. I'm able to begin a session but can't seem to use it for anything. The XML-RPC provider requires login and key (password) and need to know how to format that in the parameters field.

This is not for the action itself, but the underlying AppleScript support is documented here.

Error Invoking Web Service Action: null

I am using the WEBSERVICE action in the BLS to access a third party system. I am getting an error during execution: [ERROR]: Error Invoking Web Service Action: null. I cannot find any messages in any of the logs. Even though the action fails, the remote WebService processes properly. My basis guy seems to think that it is related to SOAP incompatibilities/versions. Any other ideas floating around out there? Any other methods to troubleshoot? The external application uses Document-Literal Style web services and conforms to WS-I Basic Profile.

All -
Here is a trace. My remote web service returns an empty SOAP body upon success (SOAP envelope only). Is this causing the Null Pointer Exception??
PS - I am also getting a lot of "WARNING: received an illegal cookie" messages. Is this a problem.
[Wed Mar 19 16:38:08 EDT 2008] <?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope ...xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body> ...blah, blah...</soap:Body>
</soap:Envelope>
[Wed Mar 19 16:39:09 EDT 2008] java.lang.NullPointerException
[Wed Mar 19 16:39:09 EDT 2008] at org.apache.commons.httpclient.HttpMethodBase.getStatusCode(HttpMethodBase.java:590)
[Wed Mar 19 16:39:09 EDT 2008] at com.lighthammer.webservice.SoapClient.invoke(Unknown Source)
[Wed Mar 19 16:39:09 EDT 2008] at com.lighthammer.xacute.actions.webservice.WebServiceAction.RawInvoke(Unknown Source)
[Wed Mar 19 16:39:09 EDT 2008] at com.lighthammer.xacute.actions.webservice.WebServiceAction.Invoke(Unknown Source)
[Wed Mar 19 16:39:09 EDT 2008] at com.lighthammer.xacute.core.Action.Process(Unknown Source)
[Wed Mar 19 16:39:09 EDT 2008] at com.lighthammer.xacute.engine.TransactionEngine.Process(Unknown Source)
[Wed Mar 19 16:39:09 EDT 2008] at com.lighthammer.xacute.core.ActionSequence.Process(Unknown Source)
[Wed Mar 19 16:39:09 EDT 2008] at com.lighthammer.xacute.engine.TransactionEngine.Process(Unknown Source)
[Wed Mar 19 16:39:09 EDT 2008] at com.lighthammer.xacute.core.ActionSequence.Process(Unknown Source)
[Wed Mar 19 16:39:09 EDT 2008] at com.lighthammer.xacute.engine.TransactionEngine.Process(Unknown Source)
[Wed Mar 19 16:39:09 EDT 2008] at com.lighthammer.xacute.core.ActionSequence.Process(Unknown Source)
[Wed Mar 19 16:39:09 EDT 2008] at com.lighthammer.xacute.engine.TransactionEngine.Process(Unknown Source)
[Wed Mar 19 16:39:09 EDT 2008] at com.lighthammer.xacute.engine.TransactionEngine.Execute(Unknown Source)
[Wed Mar 19 16:39:09 EDT 2008] at com.lighthammer.xacute.services.Runner.doGet(Unknown Source)
[Wed Mar 19 16:39:09 EDT 2008] at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
[Wed Mar 19 16:39:09 EDT 2008] at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
[Wed Mar 19 16:39:09 EDT 2008] at com.newatlanta.servletexec.SERequestDispatcher.forwardServlet(SERequestDispatcher.java:638)
[Wed Mar 19 16:39:09 EDT 2008] at com.newatlanta.servletexec.SERequestDispatcher.forward(SERequestDispatcher.java:236)
[Wed Mar 19 16:39:09 EDT 2008] at com.newatlanta.servletexec.SERequestDispatcher.internalForward(SERequestDispatcher.java:283)
[Wed Mar 19 16:39:09 EDT 2008] at com.newatlanta.servletexec.SEFilterChain.doFilter(SEFilterChain.java:96)
[Wed Mar 19 16:39:09 EDT 2008] at com.lighthammer.cms.system.CMSFilter.doFilter(Unknown Source)
[Wed Mar 19 16:39:09 EDT 2008] at com.newatlanta.servletexec.SEFilterChain.doFilter(SEFilterChain.java:60)
[Wed Mar 19 16:39:09 EDT 2008] at com.newatlanta.servletexec.ApplicationInfo.filterApplRequest(ApplicationInfo.java:2159)
[Wed Mar 19 16:39:09 EDT 2008] at com.newatlanta.servletexec.ApplicationInfo.processApplRequest(ApplicationInfo.java:1823)
[Wed Mar 19 16:39:09 EDT 2008] at com.newatlanta.servletexec.ServerHostInfo.processApplRequest(ServerHostInfo.java:937)
[Wed Mar 19 16:39:09 EDT 2008] at com.newatlanta.servletexec.ServletExec.ProcessRequest(ServletExec.java:1091)
[Wed Mar 19 16:39:09 EDT 2008] at com.newatlanta.servletexec.ServletExec.ProcessRequest(ServletExec.java:973)
[Wed Mar 19 16:39:09 EDT 2008] at com.newatlanta.servletexec.ServletExecService.processServletRequest(ServletExecService.java:167)
[Wed Mar 19 16:39:09 EDT 2008] at com.newatlanta.servletexec.ServletExecService.Run(ServletExecService.java:204)
[Wed Mar 19 16:39:09 EDT 2008] at com.newatlanta.servletexec.HttpServerRequest.run(HttpServerRequest.java:487)
[Wed Mar 19 16:39:10 EDT 2008] WARNING: received an illegal cookie name: $Version
[Wed Mar 19 16:39:10 EDT 2008] Cookie: $Version=0; JSESSIONID=mZrFUwEbv-vJKx8dds2Swq6k9k; $Path=/Lighthammer, $Version=0; JSESSIONPROXY=mZrFUwEbv-vJKx8dds2Swq6k9k; $Path=/
[Wed Mar 19 16:39:10 EDT 2008] User-Agent: Jakarta Commons-HttpClient/2.0.2
[Wed Mar 19 16:39:10 EDT 2008] WARNING: received an illegal cookie name: $Path
[Wed Mar 19 16:39:10 EDT 2008] Cookie: $Version=0; JSESSIONID=mZrFUwEbv-vJKx8dds2Swq6k9k; $Path=/Lighthammer, $Version=0; JSESSIONPROXY=mZrFUwEbv-vJKx8dds2Swq6k9k; $Path=/
[Wed Mar 19 16:39:10 EDT 2008] User-Agent: Jakarta Commons-HttpClient/2.0.2
[Wed Mar 19 16:39:10 EDT 2008] WARNING: received an illegal cookie name: $Path
[Wed Mar 19 16:39:10 EDT 2008] Cookie: $Version=0; JSESSIONID=mZrFUwEbv-vJKx8dds2Swq6k9k; $Path=/Lighthammer, $Version=0; JSESSIONPROXY=mZrFUwEbv-vJKx8dds2Swq6k9k; $Path=/
[Wed Mar 19 16:39:10 EDT 2008] User-Agent: Jakarta Commons-HttpClient/2.0.2

Ansync Web Service is Blocking

Hello,
I have build an asynchronous web service and have implemented a polling
interface for my Java client to access it. Here is the call sequence:
1. Client calls "start" method which is buffered and also starts a
conversation.
2. Client calls "isReady" which returns true|false depending on the status
of the service completion
3. Client calls "getInfo" which returns the result of the service
If the "start" method processing takes over 30 seconds the following
exception is genreated when calling "isReady":
####<Sep 15, 2003 9:57:51 AM PDT> <Error> <WLW> <OKCOMPUTER> <ssa_admin>
<ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<anonymous>>
<BEA1-001F36642240> <000000>
<Failure=javax.ejb.TransactionRolledbackLocalException: [EJB:010107]The lock
request from EJB:PersistentContainer with primary
key:192.168.1.101-1556d12.f7a62f4472.-8000 timed-out after waiting 30,000
ms. The transaction or thread requesting the lock was:Name=[EJB
com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.
core.request.Request)],Xid=BEA1-001F36642240(27960095),Status=Active,numRepl
iesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=30,seconds
left=270,activeThread=Thread[ExecuteThread: '13' for queue:
'weblogic.kernel.Default',5,Thread Group for Queue:
'weblogic.kernel.Default'],SCInfo[domain_ssa+ssa_admin]=(state=active),prope
rties=({weblogic.transaction.name=[EJB
com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.
core.request.Request)]}),OwnerTransactionManager=ServerTM[ServerCoordinatorD
escriptor=(CoordinatorURL=ssa_admin+192.168.1.101:7001+domain_ssa+t3+,
XAResources={JMS_FileStore, weblogic.jdbc.wrapper.JTSXAResourceImpl,
JMS_cgJMSStore},NonXAResources={})]).; nested exception is:
weblogic.ejb20.locks.LockTimedOutException: [EJB:010107]The lock request
from EJB:PersistentContainer with primary
key:192.168.1.101-1556d12.f7a62f4472.-8000 timed-out after waiting 30,000
ms. The transaction or thread requesting the lock was:Name=[EJB
com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.
core.request.Request)],Xid=BEA1-001F36642240(27960095),Status=Active,numRepl
iesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=30,seconds
left=270,activeThread=Thread[ExecuteThread: '13' for queue:
'weblogic.kernel.Default',5,Thread Group for Queue:
'weblogic.kernel.Default'],SCInfo[domain_ssa+ssa_admin]=(state=active),prope
rties=({weblogic.transaction.name=[EJB
com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.
core.request.Request)]}),OwnerTransactionManager=ServerTM[ServerCoordinatorD
escriptor=(CoordinatorURL=ssa_admin+192.168.1.101:7001+domain_ssa+t3+,
XAResources={JMS_FileStore, weblogic.jdbc.wrapper.JTSXAResourceImpl,
JMS_cgJMSStore},NonXAResources={})]). [ServiceException]>
There are several things to note in this error message:
1. The the timeout occurred after 30,000 ms
2. The "seconds since begin" is equal to 30
3. The "seconds left" is equal to 270
If seems that if the "seconds since begin" is less than "seconds left" then
the exception should not occurr until the condition is false.
Also, the client call to "isReady" seems to be blocking based on the
exception and some debug/tracing I did. The server log confirms that the
when the client class "isReady" and the "start" method is still executing it
will wait until "start" is completed before letting the "isReady" call
continue.
A couple of questions:
1. Is this how an async Web service is supposed to behave when using
polling?
2. Where are the time out values specified that are displayed in the
stacktrace above?
-Joe

Hi,
Could you please try this>?
In the wlw-config.xml Configuration File please change
<ejb-concurrency-strategy> to Database.
Also please try this
How to set txn timeout in JWS files?
You should also be able to set this via a -D on the command line or through
the jws-config.properties. The property you want to set is
"weblogic.jws.TransactionTimeout". Give it some integer value corresponding
to the number of seconds you want the txn timeout value to be:
-Dweblogic.jws.TransactionTimeout=72000
would timeout transactions after 20 hours
Now, since this value gets cooked into deployment descriptors, you need to
have this property set when you deploy (in debug) or when you build your
production ear.
Vimala
"Joe Chavez" <[email protected]> wrote in message
news:[email protected]...
Hello,
I have build an asynchronous web service and have implemented a polling
interface for my Java client to access it. Here is the call sequence:
1. Client calls "start" method which is buffered and also starts a
conversation.
2. Client calls "isReady" which returns true|false depending on the status
of the service completion
3. Client calls "getInfo" which returns the result of the service
If the "start" method processing takes over 30 seconds the following
exception is genreated when calling "isReady":
####<Sep 15, 2003 9:57:51 AM PDT> <Error> <WLW> <OKCOMPUTER> <ssa_admin>
<ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<anonymous>>
<BEA1-001F36642240> <000000>
<Failure=javax.ejb.TransactionRolledbackLocalException: [EJB:010107]Thelock
request from EJB:PersistentContainer with primary
key:192.168.1.101-1556d12.f7a62f4472.-8000 timed-out after waiting 30,000
ms. The transaction or thread requesting the lock was:Name=[EJB
com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.
>
core.request.Request)],Xid=BEA1-001F36642240(27960095),Status=Active,numRepl
iesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=30,seconds
left=270,activeThread=Thread[ExecuteThread: '13' for queue:
'weblogic.kernel.Default',5,Thread Group for Queue:
'weblogic.kernel.Default',SCInfo[domain_ssa+ssa_admin]=(state=active),prope
rties=({weblogic.transaction.name=[EJB
com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.
>
core.request.Request)]}),OwnerTransactionManager=ServerTM[ServerCoordinatorD
escriptor=(CoordinatorURL=ssa_admin+192.168.1.101:7001+domain_ssa+t3+,
XAResources={JMS_FileStore, weblogic.jdbc.wrapper.JTSXAResourceImpl,
JMS_cgJMSStore},NonXAResources={})]).; nested exception is:
weblogic.ejb20.locks.LockTimedOutException: [EJB:010107]The lock request
from EJB:PersistentContainer with primary
key:192.168.1.101-1556d12.f7a62f4472.-8000 timed-out after waiting 30,000
ms. The transaction or thread requesting the lock was:Name=[EJB
com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.
>
core.request.Request)],Xid=BEA1-001F36642240(27960095),Status=Active,numRepl
iesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=30,seconds
left=270,activeThread=Thread[ExecuteThread: '13' for queue:
'weblogic.kernel.Default',5,Thread Group for Queue:
'weblogic.kernel.Default',SCInfo[domain_ssa+ssa_admin]=(state=active),prope
rties=({weblogic.transaction.name=[EJB
com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.
>
core.request.Request)]}),OwnerTransactionManager=ServerTM[ServerCoordinatorD
escriptor=(CoordinatorURL=ssa_admin+192.168.1.101:7001+domain_ssa+t3+,
XAResources={JMS_FileStore, weblogic.jdbc.wrapper.JTSXAResourceImpl,
JMS_cgJMSStore},NonXAResources={})]). [ServiceException]>
There are several things to note in this error message:
1. The the timeout occurred after 30,000 ms
2. The "seconds since begin" is equal to 30
3. The "seconds left" is equal to 270
If seems that if the "seconds since begin" is less than "seconds left"then
the exception should not occurr until the condition is false.
Also, the client call to "isReady" seems to be blocking based on the
exception and some debug/tracing I did. The server log confirms that the
when the client class "isReady" and the "start" method is still executingit
will wait until "start" is completed before letting the "isReady" call
continue.
A couple of questions:
1. Is this how an async Web service is supposed to behave when using
polling?
2. Where are the time out values specified that are displayed in the
stacktrace above?
-Joe

Web Service Action Block

Similar Messages

Maybe you are looking for