Documaker making web service calls

Hi, does anyone know if documaker and make web service calls to retrieve data
thanks

There are other products within the Oracle Documaker suite which have this capability, specifically Transall. Documaker server processes (gendata, etc) cannot natively call web services without customized implementations. Hope this helps!

Similar Messages

Occasional SOAP errors when making web service calls from C#

We have a C# application making web service calls to RFCs (non-NCO, SAP 4.7, WAS 6.40) and occasionally getting the following error:
The 'SOAP-ENV:Envelope' start tag on line '1' does not match the end tag of 'SOAP-ENV:Envel'. Line 1, position 34560.
This error happens randomly and can occur, not occur, and occur again for the exact same call (same data, same web service call). I anticipate that we might have a missing configuration on one of our application servers, but don't know where to tell BASIS to look. Any ideas or other help would be appreciated.

That's going to be difficult. The random nature of the error makes it impossible to reproduce (so far) in our Development and Test environments. Since the error is coming from the SAP side, I believe I would need a sniffer on each production application server in order to try to catch this and that would result in some very large log files. Is there any log file or other SAP transaction that might already be capturing these failures?

Making Web Service calls from a Form in the WorkSpace

I am getting conflicting information about this, so I hope someone here could clarify it. TIA.
This is what I want to do:
after a form is displayed/launched in the WorkSpace,
when the user Tabs out of a field (Exit event) on the form,
I want to make a Web Service call from the form,
get the result from the WebService,
and use the Result to populate another field on the form.
I know for certain that this works if I Reader-Extend the form,
and I set the JavaScript at the Exit event (to execute WebService call)
as "Run At Client".
The question is:
can I make the WebService calls without Reader-Extending the form???
I have been told that, yes you can,
but *only if* you let the JavaScript "Run At Server".
I tried that, but it caused the Reader to crash.
Some other people told me,
no you can not,
even if you "Run At Server", the form still needs to be Reader-Extended,
when using it in the WorkSpace environment.
So, what is the truth? can someon tell me?
Can I make WebServers calls from the Server-side at all?
Do I really need to Reader-Extend the form even if calling it from server side?
What exactly is it SUPPOSED to work?
thanks

yes, thank you both. I got the fix from Adobe Tech Support last week. It's working.
The fix I got included a rather complex looking "Submit Service" though. Makes me wonder how a regular user would know that he needs to write such a Submit Service?? and even if he knows that he needs a special Submit Service, would he know how to write it??? I found no documentation for this type of things either.
Shouldn't this solution be published somewhere in Adobe's website? Dev Lab perhaps?

Error while making Web service call

I have configured my webservice for https
i calling the web service from a j2me clieny application, i get the error
javax.xml.rpc.JAXRPCException: no HTTP reply header
at com.ibm.pvcws.jaxrpc.rpc.OperationImpl.invoke(OperationImpl.java:321)
Can somebody please help me with the error

Hello
You get the WebServiceME.jar by downloading an add-on by using the software manager, Help->Software Updates->Software Manager
Good luck

What stub code does APEX uses when making a web service call ?

What stub code does APEX uses when making a web service call (manual web service reference)
I am using APEX (which was part of the 11g installation).

Hi Steve,
Some options for the same issue:
web service time out
How to check for Web Srvice Timeout in ABAP Proxy call
Regards
Vijaya

Connection Reset while making http web service call to remote server

Hello guys,
Our environment details are as follows:
WebLogic version: 10.3.3
Cluster: yes
Database: Oracle
Web service server: Remote application
When our WebLogic server makes a http Web service call to another remote application which runs on IIS server for creating a record. The record gets created in remote application but WebLogic server log says java.net.SocketException: Connection reset and the same record doesn't get created in WebLogic application. We have confirmed that remote application is running and it is behaving as expected. Also, we installed web service client on our WebLogic machine just to isolate any network related issues, when we make a same request through this client it works fine and we get answer. At this point in time, it looks like it could be WebLogic or application which is behaving goofy. we are running out of ideas, it would be nice if someone have any thoughts on it like turning on any flags or any other troubleshooting steps. Please, let me know.
Here is the stack trace:
####<Sep 18, 2011 12:31:40 AM MDT> <Info> <com.blah.blah> <server1> <WLSserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Defaul
t (self-tuning)'> <user> <BEA1-69D606DA85BDB1A0A7D5> <> <1316327500388> <BEA-000000> <ERROR com.blah.blah - Error during creating a order remoteappja
va.net.SocketException: Connection reset
com.sun.jersey.api.client.ClientHandlerException: java.net.SocketException: Connection reset
at com.sun.jersey.api.client.Client.handle(Client.java:569)
at com.sun.jersey.api.client.WebResource.handle(WebResource.java:556)
at com.sun.jersey.api.client.WebResource.access$200(WebResource.java:69)
at com.sun.jersey.api.client.WebResource$Builder.get(WebResource.java:451)
Caused by: java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:173)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
at weblogic.net.http.MessageHeader.isHTTP(MessageHeader.java:220)
at weblogic.net.http.MessageHeader.parseHeader(MessageHeader.java:143)
at weblogic.net.http.HttpClient.parseHTTP(HttpClient.java:462)
at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:364)
at weblogic.net.http.SOAPHttpURLConnection.getInputStream(SOAPHttpURLConnection.java:37)
at weblogic.net.http.HttpURLConnection.getResponseCode(HttpURLConnection.java:952)
at com.sun.jersey.client.urlconnection.URLConnectionClientHandler._invoke(URLConnectionClientHandler.java:215)
at com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:126)
... 58 more
>
thanks a lot for your help in advance
Regards,

Here's what the issue was for us:
When the web service was initializing, Weblogic? was trying to retrieve the WSDL first before initializing the service.
Though the web service URL was proper, the WSDL itself was unresolvable. This led to this strange connection reset error.
So, if you're experiencing this consistently, check your WSDL URL.
We used "strace" to discover this problem by running it for a brief time while the web service initialization was attempted - and it very clearly showed that the code was attempting to laod something from a bogus address / IP

Configuring SSL to make a HTTPS web Service call from XI

Hi All,
We are making a https web service call using soap adapter from XI. Looking at the various posts and SAP help links, we are configuring SSL for the same.
The procedure given in SAP help has been followed to configure SSL but with no luck. If someone had done this could you please give a step by step procedure to configure SSL, we might have missed out on something.
Also are there are any other settings apart from SSL to be done to make a https web service call using soap adapter from XI.
Cheers,
Chandra

user13046122 wrote:
I have an old pl/sql "helper" package, originally written to make SOAP Web Service calls from the database - it uses UTL_HTTP to invoke the target services.
I now need to make SOAP Web Service calls - from an 8.1.7.4 database
But the version of UTL_HTTP inside 8.1.7.4 does not contain the functions needed in the helper package
Can anybody suggest a means of making SOAP Web Service calls from an 8.1.7.4 database ?I think you'll be very lucky to find anyone here who still has access to a version of Oracle that is that old.... I mean... that's like what? 15 years old at least? I'm surprised you've still got hardware that can run that.
It would probably help if you could post what code you've got and explain which function(s) it's complaining about, as I doubt people will want to guess.

Web service call from a ReadWriteBackingMap

We are thinking of making a web service call from a ReadWriteBackingMap
<cachestore-scheme>
<class-scheme>
<class-name>
We will extend ReadWriteBackingMap class and override load() method to make a call to a web service.
This cache will be read only data and will hold relatively static data like list of c
ountries.
We expect to use Spring framework/JDK 1.5/WS security to make this web service call. We hope to
have the jar/config files available in server classpath when we start coherence servers.
1. Do you see any issues with this approach?
2. Any best practices?
3. Server resources(memory etc) will be shared between the server java process and this call to
web services, getting the xml, parsing the data etc. Any issues with that?

Hi,
I would recommend implementing the web-service callout logic in a custom cachestore/cacheloader (see the CacheLoader.load() method) and configure your rwbm with your cachestore implementation.
While subclassing RWBM and overriding functionality can be done, the CacheLoader interface is the intended method designed to accomplish this kind of task. RWBM internal implementations may perform other internal bookkeeping and may vary over time.
See also:
http://download.oracle.com/otn_hosted_doc/coherence/351/com/tangosol/net/cache/CacheLoader.html
http://wiki.tangosol.com/display/COH35UG/cachestore-scheme
http://wiki.tangosol.com/display/COH35UG/Sample+CacheStores
thanks,
-Rob

Weblogic app server wsdl web service call with SSL Validation error = 16

Weblogic app server wsdl web service call with SSL Validation error = 16
I need to make wsdl web service call in my weblogic app server. The web service is provided by a 3rd party vendor. I keep getting error
Cannot complete the certificate chain: No trusted cert found
Certificate chain received from ws-eq.demo.xxx.com - xx.xxx.xxx.156 was not trusted causing SSL handshake failure
Validation error = 16
From the SSL debug log, I can see 3 verisign hierarchy certs are correctly loaded (see 3 lines in the log message starting with “adding as trusted cert”). But somehow after first handshake, I got error “Cannot complete the certificate chain: No trusted cert found”.
Here is how I load trustStore and keyStore in my java program:
 System.setProperty("javax.net.ssl.trustStore",”cacerts”);
 System.setProperty("javax.net.ssl.trustStorePassword", trustKeyPasswd);
 System.setProperty("javax.net.ssl.trustStoreType","JKS");
System.setProperty("javax.net.ssl.keyStoreType","JKS");
System.setProperty("javax.net.ssl.keyStore", keyStoreName);
 System.setProperty("javax.net.ssl.keyStorePassword",clientCertPwd); System.setProperty("com.sun.xml.ws.transport.http.client.HttpTransportPipe.dump","true");
Here is how I create cacerts using verisign hierarchy certs (in this order)
1.6.0_29/jre/bin/keytool -import -trustcacerts -keystore cacerts -storepass changeit -file VerisignClass3G5PCA3Root.txt -alias "Verisign Class3 G5P CA3 Root"
1.6.0_29/jre/bin/keytool -import -trustcacerts -keystore cacerts -storepass changeit -file VerisignC3G5IntermediatePrimary.txt -alias "Verisign C3 G5 Intermediate Primary"
1.6.0_29/jre/bin/keytool -import -trustcacerts -keystore cacerts -storepass changeit -file VerisignC3G5IntermediateSecondary.txt -alias "Verisign C3 G5 Intermediate Secondary"
Because my program is a weblogic app server, when I start the program, I have java command line options set as:
-Dweblogic.security.SSL.trustedCAKeyStore=SSLTrust.jks
-Dweblogic.security.SSL.ignoreHostnameVerification=true
-Dweblogic.security.SSL.enforceConstraints=strong
That SSLTrust.jks is the trust certificate from our web server which sits on a different box. In our config.xml file, we also refer to the SSLTrust.jks file when we bring up the weblogic app server.
In addition, we have working logic to use some other wsdl web services from the same vendor on the same SOAP server. In the working web service call flows, we use clientgen to create client stub, and use SSLContext and WLSSLAdapter to load trustStore and keyStore, and then bind the SSLContext and WLSSLAdapter objects to the webSerive client object and make the webservie call. For the new wsdl file, I am told to use wsimport to create client stub. In the client code created, I don’t see any way that I can bind SSLContext and WLSSLAdapter objects to the client object, so I have to load certs by settting system pramaters. Here I attached the the wsdl file.
I have read many articles. It seems as long as I can install the verisign certs correctly to web logic server, I should have fixed the problem. Now the questions are:
1. Do I create “cacerts” the correct order with right keeltool options?
2. Since command line option “-Dweblogic.security.SSL.trustedCAKeyStore” is used for web server jks certificate, will that cause any problem for me?
3. Is it possible to use wsimport to generate client stub that I can bind SSLContext and WLSSLAdapter objects to it?
4. Do I need to put the “cacerts” to some specific weblogic directory?
---------------------------------wsdl file
<wsdl:definitions name="TokenServices" targetNamespace="http://tempuri.org/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:tns="http://tempuri.org/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:wsa10="http://www.w3.org/2005/08/addressing" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata">
 <wsp:Policy wsu:Id="TokenServices_policy">
 <wsp:ExactlyOne>
 <wsp:All>
 <sp:TransportBinding xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
 <wsp:Policy>
 <sp:TransportToken>
 <wsp:Policy>
 <sp:HttpsToken RequireClientCertificate="true"/>
 </wsp:Policy>
 </sp:TransportToken>
 <sp:AlgorithmSuite>
 <wsp:Policy>
 <sp:Basic256/>
 </wsp:Policy>
 </sp:AlgorithmSuite>
 <sp:Layout>
 <wsp:Policy>
 <sp:Strict/>
 </wsp:Policy>
 </sp:Layout>
 </wsp:Policy>
 </sp:TransportBinding>
 <wsaw:UsingAddressing/>
 </wsp:All>
 </wsp:ExactlyOne>
 </wsp:Policy>
 <wsdl:types>
 <xsd:schema targetNamespace="http://tempuri.org/Imports">
 <xsd:import schemaLocation="xsd0.xsd" namespace="http://tempuri.org/"/>
 <xsd:import schemaLocation="xsd1.xsd" namespace="http://schemas.microsoft.com/2003/10/Serialization/"/>
 </xsd:schema>
 </wsdl:types>
 <wsdl:message name="ITokenServices_GetUserToken_InputMessage">
 <wsdl:part name="parameters" element="tns:GetUserToken"/>
 </wsdl:message>
 <wsdl:message name="ITokenServices_GetUserToken_OutputMessage">
 <wsdl:part name="parameters" element="tns:GetUserTokenResponse"/>
 </wsdl:message>
 <wsdl:message name="ITokenServices_GetSSOUserToken_InputMessage">
 <wsdl:part name="parameters" element="tns:GetSSOUserToken"/>
 </wsdl:message>
 <wsdl:message name="ITokenServices_GetSSOUserToken_OutputMessage">
 <wsdl:part name="parameters" element="tns:GetSSOUserTokenResponse"/>
 </wsdl:message>
 <wsdl:portType name="ITokenServices">
 <wsdl:operation name="GetUserToken">
 <wsdl:input wsaw:Action="http://tempuri.org/ITokenServices/GetUserToken" message="tns:ITokenServices_GetUserToken_InputMessage"/>
 <wsdl:output wsaw:Action="http://tempuri.org/ITokenServices/GetUserTokenResponse" message="tns:ITokenServices_GetUserToken_OutputMessage"/>
 </wsdl:operation>
 <wsdl:operation name="GetSSOUserToken">
 <wsdl:input wsaw:Action="http://tempuri.org/ITokenServices/GetSSOUserToken" message="tns:ITokenServices_GetSSOUserToken_InputMessage"/>
 <wsdl:output wsaw:Action="http://tempuri.org/ITokenServices/GetSSOUserTokenResponse" message="tns:ITokenServices_GetSSOUserToken_OutputMessage"/>
 </wsdl:operation>
 </wsdl:portType>
 <wsdl:binding name="TokenServices" type="tns:ITokenServices">
 <wsp:PolicyReference URI="#TokenServices_policy"/>
 <soap12:binding transport="http://schemas.xmlsoap.org/soap/http"/>
 <wsdl:operation name="GetUserToken">
 <soap12:operation soapAction="http://tempuri.org/ITokenServices/GetUserToken" style="document"/>
 <wsdl:input>
 <soap12:body use="literal"/>
 </wsdl:input>
 <wsdl:output>
 <soap12:body use="literal"/>
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="GetSSOUserToken">
 <soap12:operation soapAction="http://tempuri.org/ITokenServices/GetSSOUserToken" style="document"/>
 <wsdl:input>
 <soap12:body use="literal"/>
 </wsdl:input>
 <wsdl:output>
 <soap12:body use="literal"/>
 </wsdl:output>
 </wsdl:operation>
 </wsdl:binding>
 <wsdl:service name="TokenServices">
 <wsdl:port name="TokenServices" binding="tns:TokenServices">
 <soap12:address location="https://ws-eq.demo.i-deal.com/PhxEquity/TokenServices.svc"/>
 <wsa10:EndpointReference>
 <wsa10:Address>https://ws-eq.demo.xxx.com/PhxEquity/TokenServices.svc</wsa10:Address>
 </wsa10:EndpointReference>
 </wsdl:port>
 </wsdl:service>
</wsdl:definitions>
----------------------------------application log
adding as trusted cert:
Subject: CN=VeriSign Class 3 International Server CA - G3, OU=Terms of use at https://www.verisign.com/rpa (c)10, OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
Issuer: CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
Algorithm: RSA; Serial number: 0x641be820ce020813f32d4d2d95d67e67
Valid from Sun Feb 07 19:00:00 EST 2010 until Fri Feb 07 18:59:59 EST 2020
adding as trusted cert:
Subject: OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
Issuer: OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
Algorithm: RSA; Serial number: 0x3c9131cb1ff6d01b0e9ab8d044bf12be
Valid from Sun Jan 28 19:00:00 EST 1996 until Wed Aug 02 19:59:59 EDT 2028
adding as trusted cert:
Subject: CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
Issuer: OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
Algorithm: RSA; Serial number: 0x250ce8e030612e9f2b89f7054d7cf8fd
Valid from Tue Nov 07 19:00:00 EST 2006 until Sun Nov 07 18:59:59 EST 2021
<Mar 7, 2013 6:59:21 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Ignoring not supported JCE Cipher: SunPKCS11-Solaris version 1.6 for algorithm DESede/CBC/NoPadding>
<Mar 7, 2013 6:59:21 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Will use default Cipher for algorithm DESede>
<Mar 7, 2013 6:59:21 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Using JCE Cipher: SunJCE version 1.6 for algorithm RSA/ECB/NoPadding>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLSetup: loading trusted CA certificates>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Filtering JSSE SSLSocket>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.addContext(ctx): 28395435>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLSocket will be Muxing>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write HANDSHAKE, offset = 0, length = 115>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <25779276 SSL3/TLS MAC>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <25779276 received HANDSHAKE>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: ServerHello>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: Certificate>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Cannot complete the certificate chain: No trusted cert found>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 0 in the chain: Serial number: 2400410601231772600606506698552332774
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
Not Valid Before:Tue Dec 18 19:00:00 EST 2012
Not Valid After:Wed Jan 07 18:59:59 EST 2015
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 1 in the chain: Serial number: 133067699711757643302127248541276864103
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Not Valid Before:Sun Feb 07 19:00:00 EST 2010
Not Valid After:Fri Feb 07 18:59:59 EST 2020
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <validationCallback: validateErr = 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[0] = Serial number: 2400410601231772600606506698552332774
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
Not Valid Before:Tue Dec 18 19:00:00 EST 2012
Not Valid After:Wed Jan 07 18:59:59 EST 2015
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[1] = Serial number: 133067699711757643302127248541276864103
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Not Valid Before:Sun Feb 07 19:00:00 EST 2010
Not Valid After:Fri Feb 07 18:59:59 EST 2020
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <weblogic user specified trustmanager validation status 16>
<Mar 7, 2013 6:59:22 PM EST> <Warning> <Security> <BEA-090477> <Certificate chain received from ws-eq.demo.xxx.com - xx.xxx.xxx.156 was not trusted causing SSL handshake failure.>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validation error = 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Certificate chain is untrusted>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLTrustValidator returns: 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Trust status (16): CERT_CHAIN_UNTRUSTED>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <NEW ALERT with Severity: FATAL, Type: 42
java.lang.Exception: New alert stack
 at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
 at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source)
 at com.certicom.tls.record.handshake.ClientStateReceivedServerHello.handle(Unknown Source)
 at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown Source)
 at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown Source)
 at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
 at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
 at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
 at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
 at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
 at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
 at com.certicom.tls.record.WriteHandler.write(Unknown Source)
 at com.certicom.io.OutputSSLIOStreamWrapper.write(Unknown Source)
 at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
 at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
 at java.io.FilterOutputStream.flush(FilterOutputStream.java:123)
 at weblogic.net.http.HttpURLConnection.writeRequests(HttpURLConnection.java:154)
 at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:358)
 at weblogic.net.http.SOAPHttpsURLConnection.getInputStream(SOAPHttpsURLConnection.java:37)
 at weblogic.wsee.util.is.InputSourceUtil.loadURL(InputSourceUtil.java:100)
 at weblogic.wsee.util.dom.DOMParser.getWebLogicDocumentImpl(DOMParser.java:118)
 at weblogic.wsee.util.dom.DOMParser.getDocument(DOMParser.java:65)
 at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:311)
 at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:305)
 at weblogic.wsee.jaxws.spi.WLSProvider.readWSDL(WLSProvider.java:296)
 at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:77)
 at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:62)
 at javax.xml.ws.Service.<init>(Service.java:56)
 at ideal.ws2j.eqtoken.TokenServices.<init>(TokenServices.java:64)
 at com.citi.ilrouter.util.IpreoEQSSOClient.invokeRpcPortalToken(IpreoEQSSOClient.java:165)
 at com.citi.ilrouter.servlets.T3LinkServlet.doPost(T3LinkServlet.java:168)
 at com.citi.ilrouter.servlets.T3LinkServlet.doGet(T3LinkServlet.java:206)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
 at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(Unknown Source)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(Unknown Source)
 at weblogic.servlet.internal.WebAppServletContext.securedExecute(Unknown Source)
 at weblogic.servlet.internal.WebAppServletContext.execute(Unknown Source)
 at weblogic.servlet.internal.ServletRequestImpl.run(Unknown Source)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write ALERT, offset = 0, length = 2>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <close(): 6457753>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <close(): 6457753>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.removeContext(ctx): 22803607>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Filtering JSSE SSLSocket>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.addContext(ctx): 14640403>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLSocket will be Muxing>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write HANDSHAKE, offset = 0, length = 115>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <23376797 SSL3/TLS MAC>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <23376797 received HANDSHAKE>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: ServerHello>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: Certificate>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Cannot complete the certificate chain: No trusted cert found>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 0 in the chain: Serial number: 2400410601231772600606506698552332774
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
Not Valid Before:Tue Dec 18 19:00:00 EST 2012
Not Valid After:Wed Jan 07 18:59:59 EST 2015
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 1 in the chain: Serial number: 133067699711757643302127248541276864103
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Not Valid Before:Sun Feb 07 19:00:00 EST 2010
Not Valid After:Fri Feb 07 18:59:59 EST 2020
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <validationCallback: validateErr = 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[0] = Serial number: 2400410601231772600606506698552332774
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
Not Valid Before:Tue Dec 18 19:00:00 EST 2012
Not Valid After:Wed Jan 07 18:59:59 EST 2015
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[1] = Serial number: 133067699711757643302127248541276864103
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Not Valid Before:Sun Feb 07 19:00:00 EST 2010
Not Valid After:Fri Feb 07 18:59:59 EST 2020
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <weblogic user specified trustmanager validation status 16>
<Mar 7, 2013 6:59:22 PM EST> <Warning> <Security> <BEA-090477> <Certificate chain received from ws-eq.demo.xxx.com - 12.29.210.156 was not trusted causing SSL handshake failure.>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validation error = 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Certificate chain is untrusted>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLTrustValidator returns: 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Trust status (16): CERT_CHAIN_UNTRUSTED>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <NEW ALERT with Severity: FATAL, Type: 42
java.lang.Exception: New alert stack
 at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
 at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source)
 at com.certicom.tls.record.handshake.ClientStateReceivedServerHello.handle(Unknown Source)
 at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown Source)
 at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown Source)
 at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
 at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
 at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
 at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
 at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
 at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
 at com.certicom.tls.record.WriteHandler.write(Unknown Source)
 at com.certicom.io.OutputSSLIOStreamWrapper.write(Unknown Source)
 at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
 at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
 at java.io.FilterOutputStream.flush(FilterOutputStream.java:123)
 at weblogic.net.http.HttpURLConnection.writeRequests(HttpURLConnection.java:154)
 at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:358)
 at weblogic.net.http.SOAPHttpsURLConnection.getInputStream(SOAPHttpsURLConnection.java:37)
 at weblogic.wsee.util.is.InputSourceUtil.loadURL(InputSourceUtil.java:100)
 at weblogic.wsee.util.dom.DOMParser.getWebLogicDocumentImpl(DOMParser.java:118)
 at weblogic.wsee.util.dom.DOMParser.getDocument(DOMParser.java:65)
 at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:311)
 at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:305)
 at weblogic.wsee.jaxws.spi.WLSProvider.readWSDL(WLSProvider.java:296)
 at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:77)
 at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:62)
 at javax.xml.ws.Service.<init>(Service.java:56)
 at ideal.ws2j.eqtoken.TokenServices.<init>(TokenServices.java:64)
 at com.citi.ilrouter.util.IpreoEQSSOClient.invokeRpcPortalToken(IpreoEQSSOClient.java:165)
 at com.citi.ilrouter.servlets.T3LinkServlet.doPost(T3LinkServlet.java:168)
 at com.citi.ilrouter.servlets.T3LinkServlet.doGet(T3LinkServlet.java:206)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
 at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(Unknown Source)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(Unknown Source)
 at weblogic.servlet.internal.WebAppServletContext.securedExecute(Unknown Source)
 at weblogic.servlet.internal.WebAppServletContext.execute(Unknown Source)
 at weblogic.servlet.internal.ServletRequestImpl.run(Unknown Source)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write ALERT, offset = 0, length = 2>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <close(): 16189141>

I received a workaround by an internal message.
The how to guide is :
-Download the wsdl file (with bindings, not the one from ESR)
-Correct it in order that the schema corresponds to the answer (remove minOccurs or other things like this)
-Deploy the wsdl file on you a server (java web project for exemple). you can deploy on your local
-Create a new logicial destination that point to the wsdl file modified
-Change the metadata destination in your web dynpro project for the corresponding model and keep the execution desitnation as before.
Then the received data is check by the metadata logical destination but the data is retrieved from the correct server.

How can I use web service call for edit a report with SSRS in Java Struts2 web application

Hello im new in SSRS technologie and I would like make web service call at my SSRS server. Is sombody can help me ?
- What API should I import in my project ? I use Maven can I found this API on Maven repository ?
- I would like have an sample of code which initialize the ReportingService, do the call and process result.
We use the SQL Server ReportingService 2008 R2 and currently we made HTTP call like this : http://<ssr_server>/ReportServer/Pages/ReportViewer.aspx?%2fSSRS_OMB%2fMyReport&rs:Command=Render&MyParam=<value>
Regards

Hi ombinte,
SQL Server Reporting Services provides access to the full functionality of the report server through the Report Server Web service. Because the Report Server Web service is an XML Web service which uses Simple Object Access Protocol (SOAP) over Hypertext Transfer
Protocol (HTTP), any SOAP-aware application or development tool can communicate with the SSRS web service.
There are three primary ways to develop Reporting Services applications based on the Web service, please see:
Develop applications using Microsoft Visual Studio and the Microsoft .NET Framework SDK.
Develop applications using the rs utility (RS.exe), the Reporting Services script environment.
Develop applications using any SOAP-enabled set of development tools.
For more information about Report Server Web Service, you can refer to the following document:
http://technet.microsoft.com/en-us/library/ms152787.aspx
Hope this helps.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Error while calling SPML web service call in OIM 11g

Hi,
While testing the SPML web service call, I am getting the "failure in security check" errors.
And I have attached the request and responce .
Request:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header xmlns:ns1="urn:names:spml:ws:header">
<ns1:ServiceHeader>
<ns1:serviceId/>
</ns1:ServiceHeader>
<wsse:Security soap:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:UsernameToken>
<wsse:Username>xelsysadm</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">XXXXXXXX</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</soap:Header>
<soap:Body xmlns:ns2="http://xmlns.oracle.com/idm/identity/spmlv2custom/Username">
<ns2:validateUsernameRequest xmlns:ns3="urn:oasis:names:tc:SPML:2:0" requestID="12345" executionMode="synchronous" locale="en" policyURI="http://www.sample.com/string/string">
<ns2:capabilityData mustUnderstand="true" capabilityURI="urn:oasis:names:tc:SPML:2:0:reference"/>
<ns2:username>TCS1000</ns2:username>
</ns2:validateUsernameRequest>
</soap:Body>
</soap:Envelope
Response:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<env:Fault xmlns:ns0="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<faultcode>ns0:FailedCheck</faultcode>
<faultstring>FailedCheck : failure in security check</faultstring>
<faultactor/>
</env:Fault>
</env:Body>
</env:Envelope>
I have attached the log file from OIM
####<Apr 26, 2012 10:27:13 AM EDT> <Error> <oracle.wsm.resources.enforcement> <corwloimhd01> <dev-oim_oim_server01> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <214014dca901f288:-460ab67b:136eeab0662:-7ffd-0000000000000838> <1335450433058> <WSM-07501> <Failure in Oracle WSM Agent processRequest, category=security, function=agent.function.service, application=spml-xsd, composite=null, modelObj=SPMLService, policy=oracle/wss11_saml_or_username_token_with_message_protection_service_policy, policyVersion=1, assertionName={http://schemas.oracle.com/ws/2006/01/securitypolicy}wss11-username-with-certificates.>
####<Apr 26, 2012 10:27:13 AM EDT> <Notice> <Stdout> <corwloimhd01> <dev-oim_oim_server01> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <214014dca901f288:-460ab67b:136eeab0662:-7ffd-000000000000083d> <1335450433058> <BEA-000000> <<Apr 26, 2012 10:27:13 AM EDT> <Error> <oracle.wsm.resources.enforcement> <WSM-07501> <Failure in Oracle WSM Agent processRequest, category=security, function=agent.function.service, application=spml-xsd, composite=null, modelObj=SPMLService, policy=oracle/wss11_saml_or_username_token_with_message_protection_service_policy, policyVersion=1, assertionName={http://schemas.oracle.com/ws/2006/01/securitypolicy}wss11-username-with-certificates.>>
Please help me how to solve this issue.
Thanks in advance
Siva

Your business logic has to be implemented by using OIM APIS. oimclient.jar..
you can then expose these business functions accordingly using a webservice or rest ...
for business logic refer:-
http://docs.oracle.com/cd/E27559_01/dev.1112/e27150/apis.htm#OMDEV734
You will basicsally have to deal with UserManager class for managing users.
java API:
http://docs.oracle.com/cd/E27559_01/apirefs.1112/e28159/toc.htm

Setting the attachment name in web service call scheduleReport

Hi there,
I searched the forum for this, found lots of threads but no useful solution...
I am using BI Publisher 10.1.3.4.1 and I need to send a PDF report by email using its web service functionality. This works fine but the report is attached as "attachment.pdf" which is far from ideal. Is it possible to specify what the attachment should be called (e.g. "veryimportantreport.pdf")
See below an example of the web service call I am doing.
Thanks
Luis
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
 xmlns:pub="http://xmlns.oracle.com/oxp/service/v11/PublicReportService"
 xmlns:pub1="http://xmlns.oracle.com/oxp/service/PublicReportService">
 <soapenv:Header/>
 <soapenv:Body>
 <pub:scheduleReport>
 <pub:scheduleRequest>
 <pub:cronExpression></pub:cronExpression>
 <pub:deliveryRequest>
 <pub:contentType>pdf</pub:contentType>
 <pub:documentData></pub:documentData>
 <pub:emailOption>
 <pub:emailBody>Message body</pub:emailBody>
 <pub:emailFrom>[email protected]</pub:emailFrom>
 <pub:emailReplyTo>[email protected]</pub:emailReplyTo>
 <pub:emailServerName>emailserver</pub:emailServerName>
 <pub:emailSubject>Subject</pub:emailSubject>
 <pub:emailTo>[email protected]</pub:emailTo>
 </pub:emailOption>
 </pub:deliveryRequest>
 <pub:reportRequest>
 <pub:reportAbsolutePath>/Order/Order.xdo</pub:reportAbsolutePath>
 <pub:attributeFormat>pdf</pub:attributeFormat>
 <pub:parameterNameValues>
 <pub:item>
 <pub:name>P_ORDER_ID</pub:name>
 <multiValuesAllowed>false</multiValuesAllowed>
 <pub:values>
 <pub1:item>123</pub1:item>
 </pub:values>
 </pub:item>
 </pub:parameterNameValues>
 </pub:reportRequest>
 </pub:scheduleRequest>
 <pub:userID>luis</pub:userID>
 <pub:password>luis</pub:password>
 </pub:scheduleReport>
 </soapenv:Body>
</soapenv:Envelope>

mdonohue wrote:
Sorry, product currently does not provide a way to name the attachment. I have entered an enhancement request to get that into a future release.That is a bit disappointing but thanks for letting me know!
We are using BIP to generate reports from Apex and it works very well, except for this small detail.
By the way, you sound very sure; are you related to Oracle in any way (I mean, is this an "official" answer)? I can't tell from your profile...
Cheers
Luis

How to see http response from an axis web service call (Eclipse)

Hello,
I would like to see the raw http response which is returned from web service calls. I have a dynamic web project in Eclipse which uses a local instance of Tomcat 6. I'm using all of the default setting for a top-down web service generated from a WSDL file. I've generated the client using the built-in "generate client" using default settings.
I've tried using the Eclipse plugin TCP/IP monitor and apache's TCPMON, but I am only able to see the http request, not the http response returned from the web server I am querying.
I've seen some sparse documentation outlining how to use logging handlers and a client-config.wsdd file, but I haven't been able to get that working.
So to recap, I'm looking for a way to view raw http responses using a web service client and server generated from a WSDL file in eclipse. I don't mind creating a new project using different code-generating libraries if someone has an easy way to do this using a different configuration.
Thanks very much,
Craig

908794 wrote:
Hello,
I would like to see the raw http response which is returned from web service calls.Why the HTTP response? Isn't the soap message body enough? If it is, you probably want to check out SoapUI.
A simple google query for "apache axis2 http response" also return this article:
http://blogs.cocoondev.org/dims/archives/004668.html
And finally, you did go through the Axis2 website right? It has a wiki with a rather staggering amount of articles in there.
http://wiki.apache.org/ws/FrontPage/Axis2/

Newscale Custom Code - AJAX Libraries - Web Service calls during ordering moment

Authentication issues calling webservice that requires credentials to be passed. NTLM authentication. Web service we are calling works from Service Link with HTTPIWA2 adapter.This is on Windows environment. When in the ordering moment, i am being presented with a popup box asking for credentials.
We are implementing a custom Newscale solution for Web Service calls during the ordering moment. I've installed and got the basic example working on our Windows based system. However, I'm trying to implement a more complex web service call that includes supplying credentials- domain userid password encrypted in the xdsproperties file. The web service we are calling has been successfully called by the service link HTTPIWA2 adapter, and independently using SOAP Sonar, so i don't feel the problem is with the web service.
We are on a windows based server and the web service we are calling is on windows as well. In the ordering moment the web service is being called, but I'm being presented with popups asking for credentials for the server that Request Center is on.
Has anyone successfully used this AJAX solution calling a web service using NTLM authentication? I'd like to compare configurations to see what is missing. You can email me directly at [email protected] Newscale PSG is on the case, but i was hoping to touch base with any other customers currently using this.
thanks!

A newer version of the Configuration Manager Client is installed. Cannot continue installing this version of the management point.
Action ended 20:50:23: SmsDetectColocationDowngrade. Return value 3.
Action ended 20:50:23: INSTALL. Return value 3.
The installer certainly thinks that you still have a previous ConfigMgr client installed. Perhaps you haven't completely removed it. Use ccmclean.exe from the SMS 2003 tool kit.
If that fails, why not just rebuild the server - you've said that this is a fresh install. I don't like too much messing at the beginning. This can be difficult enough - you need to start with a clean installation of the product.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Asynchronous web service call doesn't work

Hi,
I'm trying to convert a synchronous web service call into an asynchronous call. (Folder-level Javascript, Acrobat Professional 8.1, Windows XP).
Everything works fine when I call Soap.Request as a synchronous call. It calls the web service and gets the expected result. However, when I try to convert Soap.Request into an asynchronous call by adding the OAsync property, as described on pp. 198-199 of "Developing Acrobat Applications Using JavaScript," NONE of the various OAsync functions (i.e. result, response, wait) are ever called. IOW, the Javascript code continues executing after the Soap.Request call and doesn't wait for my web service call to return. Indeed, the web service method on the server doesn't even BEGIN to execute by the time the Javascript code runs to completion. (I can confirm this by watching my ASP.Net code execute in the Visual Studio debugger. In fact, the Javascript code runs to completion even before the Global.asax Session_Start code begins to execute, much less the web service method itself.) So, the problem is not with the web service, which works fine when Soap.Request is called as a synchronous method.
To reiterate, my Javascript code is identical to the code on pp. 198-199 of "Developing Acrobat Applications Using JavaScript." In troubleshooting this, I've tried calling the OAsync functions (mySync.wait(), mySync.result(), mySync.response()) after calling the Soap.Request, but nothing works.
Is there something else that I must add to my Javascript code (e.g. an additional Soap.Request property, or something after calling Soap.Request) to force the Javascript to wait until the web service method returns?
Thanks,
Bill

Hi Lukasz,
you can also define namespace the later in the operation GetOpenOrders itself, e.g.:
<tem:GetOpenOrders xmlns:tem=u201Dhttp://tempuri.org/u201D>
It does not need to be part of the Envelope element.
Best regards
Bastian

Documaker making web service calls

Similar Messages

Maybe you are looking for