Invoking a webservice using WSIF Binding

Hi All,
I have few queries regarding usage of WSIF Binding in BPEL
My understanding was it is useful for calling Java Classes from BPEL Process.
Can I use WSIF Binding for invoking the webservice ?
Or the use of WSIF Binding is limited to invoking Java classes.
If we can invoke web service , Can you please let me know how to do it?
you can mail your replies to [email protected]
Any help will be immensely appreciated..
Regards,
Bhanu

First of all thanks to Jens and clemens.
From both of your replies, i learnt that we can call webservice from BPEL process using WSIF binding .
Can you provide me a bpel sample where we're using wsif binding for invoking web service?
I have one more doubt:
"WSIF java binding means, which was used to call java classes. WSIF soap binding used to call web services"
Is my understanding correct?
Can you explain a bit on WSIF Java binding?
Regards,
Bhanu

Similar Messages

10.1.3.5 - Using WSIF binding in BPEL

Hi,
I'm trying to use WSIF binding for a java web service in my bpel process. I'm following the steps given at http://www.oracle.com/technology/pub/articles/bpel_cookbook/juric.html
I used Jdev to create wsdl for my java class and enabled WSIF bindings. I copied the generated wsdl to my bpel process and used it to create a partnerlink. Now I want to generate XML facade classes using schemac compiler. I modified the BPEL build.xml to call schemac for my generated wdl. The schemac errors out with following message:
[schemac] schemac> parsing schema file 'C:\share\jdevuserhome\home5\mywork\TestApps\TestWSIF3/bpel/WsifBindingDoc.wsdl' ...
[schemac] schemac> Loaded schemas from wsdl located at C:\share\jdevuserhome\home5\mywork\TestApps\TestWSIF3/bpel/WsifBindingDoc.wsdl
[schemac] warn: The W3C datatype 'base64Binary' is not currently supported by Collaxa schemac.
[schemac] warn: The W3C datatype 'hexBinary' is not currently supported by Collaxa schemac.
[schemac] warn: The W3C datatype 'time' is not currently supported by Collaxa schemac.
[schemac] schemac>WARNING: schemac tool has been deprecated, please use jaxb compliant compiler (e.g. oracle jaxb) to generate java classes from xml schema.
[schemac] schemac> generating XML business document ...
[schemac] schemac> compiling XML business documents ...
BUILD FAILED
C:\share\jdevuserhome\home5\mywork\TestApps\TestWSIF3\build.xml:41: Java compilation failed.
Failed to compile file(s) //list of files here...
Exception reported is: F:\Jdev10135\jdev\bin\schemac_1259228108484\src\org\xmlsoap\schemas\soap\encoding\ENTITIES.java:84: Incompatible type for constructor. Can't convert java.lang.String to org.w3c.dom.Element.
org.xmlsoap.schemas.soap.encoding.ENTITIES value = new org.xmlsoap.schemas.soap.encoding.ENTITIES(childValue);
^
F:\Jdev10135\jdev\bin\schemac_1259228108484\src\org\xmlsoap\schemas\soap\encoding\IDREFS.java:84: Incompatible type for constructor. Can't convert java.lang.String to org.w3c.dom.Element.
org.xmlsoap.schemas.soap.encoding.IDREFS value = new org.xmlsoap.schemas.soap.encoding.IDREFS(childValue);
^
F:\Jdev10135\jdev\bin\schemac_1259228108484\src\org\xmlsoap\schemas\soap\encoding\NMTOKENS.java:84: Incompatible type for constructor. Can't convert java.lang.String to org.w3c.dom.Element.
org.xmlsoap.schemas.soap.encoding.NMTOKENS value = new org.xmlsoap.schemas.soap.encoding.NMTOKENS(childValue);
^
F:\Jdev10135\jdev\bin\schemac_1259228108484\src\org\xmlsoap\schemas\soap\encoding\NOTATION.java:84: Undefined variable: childElement
javax.xml.namespace.QName value = super.getQNameValue(childElement,childValue);
^
F:\Jdev10135\jdev\bin\schemac_1259228108484\src\org\xmlsoap\schemas\soap\encoding\QName.java:84: Undefined variable: childElement
javax.xml.namespace.QName value = super.getQNameValue(childElement,childValue);
^
5 errors
Please verify that file /*list of files here */ is valid java file or if all required libraries are included in your classpath.
classpath: F:\Jdev10135\jdev\lib\ojc.jar;F:\Jdev10135\ant\lib\ant-oracle.jar;F:\Jdev10135\integration\lib\orabpel.jar;F:\Jdev10135\integration\lib\orabpel-ant.jar;F:\Jdev10135\integration\lib\orabpel-common.jar;F:\Jdev10135\integration\lib\orabpel-thirdparty.jar;F:\Jdev10135\webservices\lib\orawsdl.jar;F:\Jdev10135\lib\xmlparserv2.jar;F:\Jdev10135\lib\xml.jar;F:\Jdev10135\j2ee\home\lib\oc4j-internal.jar;F:\Jdev10135\j2ee\home\lib\adminclient.jar;F:\Jdev10135\integration\bpm\support\files;F:\Jdev10135\jdev\lib\jdev.jar;F:\Jdev10135\ant\lib\xml-apis.jar;F:\Jdev10135\ant\lib\xercesImpl.jar;F:\Jdev10135\ant\lib\jakarta-oro-2.0.8.jar;F:\Jdev10135\ant\lib\commons-net-1.3.0.jar;F:\Jdev10135\ant\lib\ant.jar;F:\Jdev10135\ant\lib\ant-xslp.jar;F:\Jdev10135\ant\lib\ant-xalan1.jar;F:\Jdev10135\ant\lib\ant-weblogic.jar;F:\Jdev10135\ant\lib\ant-vaj.jar;F:\Jdev10135\ant\lib\ant-trax.jar;F:\Jdev10135\ant\lib\ant-swing.jar;F:\Jdev10135\ant\lib\ant-stylebook.jar;F:\Jdev10135\ant\lib\ant-starteam.jar;F:\Jdev10135\ant\lib\ant-oracle-adfp.jar;F:\Jdev10135\ant\lib\ant-nodeps.jar;F:\Jdev10135\ant\lib\ant-netrexx.jar;F:\Jdev10135\ant\lib\ant-launcher.jar;F:\Jdev10135\ant\lib\ant-junit.jar;F:\Jdev10135\ant\lib\ant-jsch.jar;F:\Jdev10135\ant\lib\ant-jmf.jar;F:\Jdev10135\ant\lib\ant-jdepend.jar;F:\Jdev10135\ant\lib\ant-javamail.jar;F:\Jdev10135\ant\lib\ant-jai.jar;F:\Jdev10135\ant\lib\ant-icontract.jar;F:\Jdev10135\ant\lib\ant-commons-net.jar;F:\Jdev10135\ant\lib\ant-commons-logging.jar;F:\Jdev10135\ant\lib\ant-apache-resolver.jar;F:\Jdev10135\ant\lib\ant-apache-regexp.jar;F:\Jdev10135\ant\lib\ant-apache-oro.jar;F:\Jdev10135\ant\lib\ant-apache-log4j.jar;F:\Jdev10135\ant\lib\ant-apache-bsf.jar;F:\Jdev10135\ant\lib\ant-apache-bcel.jar;F:\Jdev10135\ant\lib\ant-antlr.jar;F:\Jdev10135\jdk\lib\tools.jar;F:\Jdev10135\jdev\bin
Any help on how to get rid of this error would be very useful.
thanks,
Mrityunjay
Edited by: mrityunjay_kant on Nov 26, 2009 1:51 AM

Did you check http://www.oracle.com/us/products/enterprise-manager/039537.pdf ?
and http://www.oracle.com/technetwork/oem/soa-mgmt/index.html
MANAGEMENT PACK FOR WEBCENTER SUITE
Regards
Rob
http://oemgc.wordpress.com

Error while trying to access WebService using WSIF

Hi All,
I am a new developer to WebServices. I read up information on how to create the WSDL and stubs using JDev 10g (10.1.2) using the wsa.jar that ships with the download. After creating my WSDL and the necessary proxies, when I try to run my client application (which runs in the same covatiner, standalone OC4j), I get the below error :
06/09/29 13:42:21 org.apache.wsif.WSIFException: org.apache.wsif.providers.ejb.WSIFOperation_EJB@15b0c83 : Could not invoke 'getOrderList'; nested exception is:
org.apache.wsif.WSIFException: Error while determining signature of method getOrderList : The meta information is not consistent.; nested exception is:
org.apache.wsif.WSIFException: parameters
06/09/29 13:42:21 at org.apache.wsif.providers.ejb.WSIFOperation_EJB.executeRequestResponseOperation(WSIFOperation_EJB.java:1259)
06/09/29 13:42:21 at org.apache.wsif.base.WSIFClientProxy.invoke(WSIFClientProxy.java:339)
06/09/29 13:42:21 at $Proxy3.getOrderList(Unknown Source)
I am trying to expose a Stateless Session EJB as a WebService, which contains a method called getOrderList(). This method returns an array of a complex type (Java Bean).
I am, however, able to succesfully access the WebService using the SOAP/HTTP protocol.
My client code is as follows:
WSIFServiceFactory factory = WSIFServiceFactory.newInstance();
WSIFService service = factory.getService("<path to wsdl>", null, null, "http://sample.com/", "OrderService");
orderService = (OrderService) service.getStub("WsifEjb", OrderService.class);
Not sure what am I missing here. If any further information is required in order to resolve this, please let me know.
Thanks,

You are trying to get 2 databases connected... so, you need to insure that FDEV can find and connect to ABCD.
So, from your FDEV database server, you can do 2 things (from command prompt):
1* tnsping ABCD (this will validate that the entry exists in your tnsnames.ora on your FDEV server, and that a valid listener can be found on remote server)
when above command succeeds:
2* sqlplus apps/appsdev@ABCD;
when you have established the connection, then you are SURE that your can connect ABCD database from FDEV database server. It will also validate the username / password combination, create session privilige, account not locked, etc.....
Please check the above, and post here the results.
HTH,
Thierry

Invalid security error when invoking secure webservice using SAML tokens

I have deployed a JAX-WS webservice using a stateless session bean to wl 10.3.2 that uses a custom policy. The service deploys fine, but weblogic returns an HTTP error 500 with a SOAP fault. The fault states wsse:InvalidSecurity. The webservice security policy reqires SAML holder of key assertions and attributes. I have tried everything from running weblogic with Metro 1.5 to configuring SAML Identity Asserter Providers, etc with no luck. I even tried using the built in SAML 2.0 assymetric holder of key policy. What am I doing wrong? The XML of interest is attached.
Thanks;
-Dave.
*[Sample message from client]*
<?xml version="1.0" encoding="UTF-8"?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion" xmlns:wsse11="http://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd" xmlns:exc14n="http://www.w3.org/2001/10/xml-exc-c14n#">
     <S:Header>
          <To xmlns="http://www.w3.org/2005/08/addressing">https://localhost:7002/NHINAdapterDocQuerySecured/AdapterDocQuerySecured</To>
          <Action xmlns="http://www.w3.org/2005/08/addressing">urn:gov:hhs:fha:nhinc:adapterdocquerysecured:RespondingGateway_CrossGatewayQueryRequestMessage</Action>
          <ReplyTo xmlns="http://www.w3.org/2005/08/addressing">
               <Address>http://www.w3.org/2005/08/addressing/anonymous</Address>
          </ReplyTo>
          <MessageID xmlns="http://www.w3.org/2005/08/addressing">uuid:fec656f8-a2be-4129-8412-34d9453e7cb2</MessageID>
          <wsse:Security S:mustUnderstand="1">
               <wsu:Timestamp xmlns:ns17="http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512" xmlns:ns16="http://www.w3.org/2003/05/soap-envelope" wsu:Id="_1">
                    <wsu:Created>2010-02-24T21:38:56Z</wsu:Created>
                    <wsu:Expires>2010-02-24T21:43:56Z</wsu:Expires>
               </wsu:Timestamp>
               <saml2:Assertion xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:exc14n="http://www.w3.org/2001/10/xml-exc-c14n#" xmlns:saml2="urn:oasis:names:tc:SAML:2.0:assertion" xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" xmlns:xs="http://www.w3.org/2001/XMLSchema" ID="96cdfb70-91a3-4baf-9da1-3ff07d249926" IssueInstant="2010-02-24T21:38:56.671Z" Version="2.0">
                    <saml2:Issuer Format="urn:oasis:names:tc:SAML:1.1:nameid-format:X509SubjectName">CN=SAML User,OU=SU,O=SAML User,L=Los Angeles,ST=CA,C=US</saml2:Issuer>
                    <saml2:Subject>
                         <saml2:NameID Format="urn:oasis:names:tc:SAML:1.1:nameid-format:X509SubjectName">UID=kskagerb*DoD</saml2:NameID>
                         <saml2:SubjectConfirmation Method="urn:oasis:names:tc:SAML:2.0:cm:holder-of-key">
                              <saml2:SubjectConfirmationData>
                                   <ds:KeyInfo>
                                        <ds:KeyValue>
                                             <ds:RSAKeyValue>
                                                  <ds:Modulus>iwGksKFK2ZYDxftMa093TajW7V9TwHW7NiyT6bJ2p38zBwpehwMJ1ZO9V0hFihcz/BZ2MvQ1WA1l0KhUBSR/bMiu6WmZ0bJPjvXx41ewGw5YzTL2RbT1U2XXBHtPHjbkH5jqK5zk67F/NM26v+hw0fSZiqM1BAFp9F73hMHsNrc=</ds:Modulus>
                                                  <ds:Exponent>AQAB</ds:Exponent>
                                             </ds:RSAKeyValue>
                                        </ds:KeyValue>
                                   </ds:KeyInfo>
                              </saml2:SubjectConfirmationData>
                         </saml2:SubjectConfirmation>
                    </saml2:Subject>
                    <saml2:AuthnStatement AuthnInstant="2009-04-16T13:15:39.000Z" SessionIndex="987">
                         <saml2:SubjectLocality Address="158.147.185.168" DNSName="cs.myharris.net"/>
                         <saml2:AuthnContext>
                              <saml2:AuthnContextClassRef>urn:oasis:names:tc:SAML:2.0:ac:classes:X509</saml2:AuthnContextClassRef>
                         </saml2:AuthnContext>
                    </saml2:AuthnStatement>
                    <saml2:AttributeStatement>
                         <saml2:Attribute Name="urn:oasis:names:tc:xspa:1.0:subject:subject-id">
                              <saml2:AttributeValue xmlns:ns6="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns7="http://www.w3.org/2001/XMLSchema" ns6:type="ns7:string">Karl S Skagerberg</saml2:AttributeValue>
                         </saml2:Attribute>
                         <saml2:Attribute Name="urn:oasis:names:tc:xspa:1.0:subject:organization">
                              <saml2:AttributeValue xmlns:ns6="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns7="http://www.w3.org/2001/XMLSchema" ns6:type="ns7:string">InternalTest2</saml2:AttributeValue>
                         </saml2:Attribute>
                         <saml2:Attribute Name="urn:oasis:names:tc:xspa:1.0:subject:organization-id">
                              <saml2:AttributeValue xmlns:ns6="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns7="http://www.w3.org/2001/XMLSchema" ns6:type="ns7:string">2.16.840.1.113883.4.349</saml2:AttributeValue>
                         </saml2:Attribute>
                         <saml2:Attribute Name="urn:nhin:names:saml:homeCommunityId">
                              <saml2:AttributeValue xmlns:ns6="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns7="http://www.w3.org/2001/XMLSchema" ns6:type="ns7:string">2.16.840.1.113883.4.349</saml2:AttributeValue>
                         </saml2:Attribute>
                         <saml2:Attribute Name="urn:oasis:names:tc:xacml:2.0:subject:role">
                              <saml2:AttributeValue>
                                   <hl7:Role xmlns:hl7="urn:hl7-org:v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" code="307969004" codeSystem="2.16.840.1.113883.6.96" codeSystemName="SNOMED_CT" displayName="Public Health" xsi:type="hl7:CE"/>
                              </saml2:AttributeValue>
                         </saml2:Attribute>
                         <saml2:Attribute Name="urn:oasis:names:tc:xspa:1.0:subject:purposeofuse">
                              <saml2:AttributeValue>
                                   <hl7:PurposeForUse xmlns:hl7="urn:hl7-org:v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" code="TREATMENT" codeSystem="2.16.840.1.113883.3.18.7.1" codeSystemName="nhin-purpose" displayName="Use or disclosure of Psychotherapy Notes" xsi:type="hl7:CE"/>
                              </saml2:AttributeValue>
                         </saml2:Attribute>
                         <saml2:Attribute Name="urn:oasis:names:tc:xacml:2.0:resource:resource-id">
                              <saml2:AttributeValue xmlns:ns6="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns7="http://www.w3.org/2001/XMLSchema" ns6:type="ns7:string">500000000^^^&1.1&ISO</saml2:AttributeValue>
                         </saml2:Attribute>
                    </saml2:AttributeStatement>
                    <saml2:AuthzDecisionStatement Decision="Permit" Resource="https://158.147.185.168:8181/SamlReceiveService/SamlProcessWS">
                         <saml2:Action Namespace="urn:nhin:names:hl7:rbac:4.00:operation">EXECUTE</saml2:Action>
                         <saml2:Evidence>
                              <saml2:Assertion ID="40df7c0a-ff3e-4b26-baeb-f2910f6d05a9" IssueInstant="2009-04-16T13:10:39.093Z" Version="2.0">
                                   <saml2:Issuer Format="urn:oasis:names:tc:SAML:1.1:nameid-format:X509SubjectName">CN=SAML User,OU=Harris,O=HITS,L=Melbourne,ST=FL,C=US</saml2:Issuer>
                                   <saml2:Conditions NotBefore="2009-04-16T13:10:39.093Z" NotOnOrAfter="2010-12-31T12:00:00.000Z"/>
                                   <saml2:AttributeStatement>
                                        <saml2:Attribute Name="AccessConsentPolicy" NameFormat="http://www.hhs.gov/healthit/nhin">
                                             <saml2:AttributeValue xmlns:ns6="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns7="http://www.w3.org/2001/XMLSchema" ns6:type="ns7:string">Claim-Ref-1234</saml2:AttributeValue>
                                        </saml2:Attribute>
                                        <saml2:Attribute Name="InstanceAccessConsentPolicy" NameFormat="http://www.hhs.gov/healthit/nhin">
                                             <saml2:AttributeValue xmlns:ns6="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns7="http://www.w3.org/2001/XMLSchema" ns6:type="ns7:string">Claim-Instance-1</saml2:AttributeValue>
                                        </saml2:Attribute>
                                   </saml2:AttributeStatement>
                              </saml2:Assertion>
                         </saml2:Evidence>
                    </saml2:AuthzDecisionStatement>
                    <ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
                         <ds:SignedInfo>
                              <ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
                              <ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
                              <ds:Reference URI="#96cdfb70-91a3-4baf-9da1-3ff07d249926">
                                   <ds:Transforms>
                                        <ds:Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>
                                        <ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
                                   </ds:Transforms>
                                   <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
                                   <ds:DigestValue>VnukKqb4Bt1KWDKfy8SDfk1Hp2s=</ds:DigestValue>
                              </ds:Reference>
                         </ds:SignedInfo>
                         <ds:SignatureValue>DUwjh/H3XSfUG250rTlLdihstDXY1+qkY9GaY81Iu7Ag4MgoGvGBrGjZOJ7YnssPdrqUGiURxf6k
IBH7vaeXk24XvXP3F85WP9nBm+2M4BvGTplgOmAo0yuwze+90FvwILzFNmmX/tvy3QKTDHlh1rEx
/Jqfm6q/56WW1suAbRY=</ds:SignatureValue>
                         <ds:KeyInfo>
                              <ds:KeyValue>
                                   <ds:RSAKeyValue>
                                        <ds:Modulus>iwGksKFK2ZYDxftMa093TajW7V9TwHW7NiyT6bJ2p38zBwpehwMJ1ZO9V0hFihcz/BZ2MvQ1WA1l
0KhUBSR/bMiu6WmZ0bJPjvXx41ewGw5YzTL2RbT1U2XXBHtPHjbkH5jqK5zk67F/NM26v+hw0fSZ
iqM1BAFp9F73hMHsNrc=</ds:Modulus>
                                        <ds:Exponent>AQAB</ds:Exponent>
                                   </ds:RSAKeyValue>
                              </ds:KeyValue>
                         </ds:KeyInfo>
                    </ds:Signature>
               </saml2:Assertion>
               <ds:Signature xmlns:ns17="http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512" xmlns:ns16="http://www.w3.org/2003/05/soap-envelope" Id="_2">
                    <ds:SignedInfo>
                         <ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#">
                              <exc14n:InclusiveNamespaces PrefixList="wsse S"/>
                         </ds:CanonicalizationMethod>
                         <ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
                         <ds:Reference URI="#_1">
                              <ds:Transforms>
                                   <ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#">
                                        <exc14n:InclusiveNamespaces PrefixList="wsu wsse S"/>
                                   </ds:Transform>
                              </ds:Transforms>
                              <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
                              <ds:DigestValue>oo99UrPhAcwla4Qbkdd9jAPn0cE=</ds:DigestValue>
                         </ds:Reference>
                    </ds:SignedInfo>
                    <ds:SignatureValue>ds4vqts8uCdJcNGo0uTPzId5UBX+GVrdztQPv823c1Zy9ZZGSfQC/GsBPM/EMbFInDPFsyT4e1QYZMCzmqLYnifWHlDQJb7oMJBokafavAqZda1B55Zzh3TSm6BqKWtB/DX17d6rLx/HPiLNZ9qsBfuGn3aTlUCpNsYA8ObBtp8=</ds:SignatureValue>
                    <ds:KeyInfo>
                         <wsse:SecurityTokenReference wsse11:TokenType="http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV2.0">
                              <wsse:KeyIdentifier ValueType="http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLID">96cdfb70-91a3-4baf-9da1-3ff07d249926</wsse:KeyIdentifier>
                         </wsse:SecurityTokenReference>
                    </ds:KeyInfo>
               </ds:Signature>
          </wsse:Security>
     </S:Header>
     <S:Body>
          <ns3:AdhocQueryRequest xmlns:ns2="urn:gov:hhs:fha:nhinc:gateway:samltokendata" xmlns:ns3="urn:oasis:names:tc:ebxml-regrep:xsd:query:3.0" xmlns:ns4="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0" xmlns:ns5="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0" xmlns:ns6="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:3.0" maxResults="-1" startIndex="0" federated="false">
               <ns3:ResponseOption returnComposedObjects="true" returnType="LeafClass"/>
               <ns4:AdhocQuery home="urn:oid:2.16.840.1.113883.4.349" id="urn:uuid:14d4debf-8f97-4251-9a74-a90016b0af0d">
                    <ns4:Slot name="$XDSDocumentEntryStatus">
                         <ns4:ValueList>
                              <ns4:Value>('urn:oasis:names:tc:ebxml-regrep:StatusType:Approved')</ns4:Value>
                         </ns4:ValueList>
                    </ns4:Slot>
                    <ns4:Slot name="$XDSDocumentEntryPatientId">
                         <ns4:ValueList>
                              <ns4:Value>'1012581676V377802^^^&2.16.840.1.113883.4.349&ISO'</ns4:Value>
                         </ns4:ValueList>
                    </ns4:Slot>
               </ns4:AdhocQuery>
          </ns3:AdhocQueryRequest>
     </S:Body>
</S:Envelope>
*[Response from server:]*
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
     <env:Body>
          <env:Fault xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
               <faultcode>wsse:InvalidSecurity</faultcode>
               <faultstring>weblogic.xml.crypto.api.MarshalException: weblogic.xml.dom.marshal.MarshalException: Failed to unmarshal {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}SecurityTokenReference, no SecurityTokenReference factory found for {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}KeyIdentifier ValueType: http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLID</faultstring>
          </env:Fault>
     </env:Body>
</env:Envelope>
*[webservice WSDL]*
<?xml version="1.0" encoding="UTF-8"?>

<definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="urn:gov:hhs:fha:nhinc:adapterdocquerysecured"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:query="urn:oasis:names:tc:ebxml-regrep:xsd:query:3.0"
xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype"
xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"
xmlns:wsaws="http://www.w3.org/2005/08/addressing"
xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"
xmlns:sc="http://schemas.sun.com/2006/03/wss/server"
xmlns:wspp="http://java.sun.com/xml/ns/wsit/policy"
xmlns:vprop="http://docs.oasis-open.org/wsbpel/2.0/varprop"
xmlns:sxnmp="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/NMProperty"
name="AdapterDocQuerySecured"
targetNamespace="urn:gov:hhs:fha:nhinc:adapterdocquerysecured">
<documentation>Adapter Document Query</documentation>
<types>
<xsd:schema>
<xsd:import namespace="urn:oasis:names:tc:ebxml-regrep:xsd:query:3.0"
schemaLocation="../schemas/ebRS/query.xsd"/>
<xsd:import namespace="urn:gov:hhs:fha:nhinc:gateway:samltokendata"
schemaLocation="../schemas/nhinc/gateway/SamlTokenData.xsd"/>
</xsd:schema>
</types>
<message name="RespondingGateway_CrossGatewayQueryRequestMessage">
<part name="body"
element="query:AdhocQueryRequest"/>
</message>
<message name="RespondingGateway_CrossGatewayQueryResponseMessage">
<part name="body"
element="query:AdhocQueryResponse"/>
</message>
<portType name="AdapterDocQuerySecuredPortType">
<operation name="RespondingGateway_CrossGatewayQuery">
<input name="RespondingGateway_CrossGatewayQueryRequest"
message="tns:RespondingGateway_CrossGatewayQueryRequestMessage"
wsaw:Action="urn:gov:hhs:fha:nhinc:adapterdocquerysecured:RespondingGateway_CrossGatewayQueryRequestMessage"/>
<output name="RespondingGateway_CrossGatewayQueryResponse"
message="tns:RespondingGateway_CrossGatewayQueryResponseMessage"
wsaw:Action="urn:gov:hhs:fha:nhinc:adapterdocquerysecured:RespondingGateway_CrossGatewayQueryResponseMessage"/>
</operation>
</portType>
<binding name="AdapterDocQuerySecuredBindingSoap11" type="tns:AdapterDocQuerySecuredPortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsp:PolicyReference URI="#RespondingGateway_Query_Binding_SoapPolicy"/>
<operation name="RespondingGateway_CrossGatewayQuery">
<soap:operation soapAction="urn:RespondingGateway_CrossGatewayQuery"/>
<input name="RespondingGateway_CrossGatewayQueryRequest">
<soap:body use="literal"/>
<wsp:PolicyReference URI="#RespondingGateway_Query_Binding_Soap_Input_Policy"/>
</input>
<output name="RespondingGateway_CrossGatewayQueryResponse">
<soap:body use="literal"/>
<wsp:PolicyReference URI="#RespondingGateway_Query_Binding_Soap_Output_Policy"/>
</output>
</operation>
</binding>
<service name="AdapterDocQuerySecured">
<port name="AdapterDocQuerySecuredPortSoap11"
binding="tns:AdapterDocQuerySecuredBindingSoap11">
<soap:address
location="https://localhost:7002/NHINAdapterDocQuerySecured" />
</port>
</service>

<vprop:property name="action" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:action"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>action</vprop:query>
</vprop:propertyAlias>

<vprop:property name="resource" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:resource"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>resource</vprop:query>
</vprop:propertyAlias>

<vprop:property name="purposeForUseRoleCode" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:purposeForUseRoleCode"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>purposeForUseRoleCode</vprop:query>
</vprop:propertyAlias>

<vprop:property name="purposeForUseCodeSystem" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:purposeForUseCodeSystem"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>purposeForUseCodeSystem</vprop:query>
</vprop:propertyAlias>

<vprop:property name="purposeForUseCodeSystemName" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:purposeForUseCodeSystemName"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>purposeForUseCodeSystemName</vprop:query>
</vprop:propertyAlias>

<vprop:property name="purposeForUseDisplayName" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:purposeForUseDisplayName"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>purposeForUseDisplayName</vprop:query>
</vprop:propertyAlias>

<vprop:property name="userFirstName" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:userFirstName"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>userFirstName</vprop:query>
</vprop:propertyAlias>

<vprop:property name="userMiddleName" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:userMiddleName"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>userMiddleName</vprop:query>
</vprop:propertyAlias>

<vprop:property name="userLastName" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:userLastName"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>userLastName</vprop:query>
</vprop:propertyAlias>

<vprop:property name="userName" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:userName"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>userName</vprop:query>
</vprop:propertyAlias>

<vprop:property name="userOrganization" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:userOrganization"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>userOrganization</vprop:query>
</vprop:propertyAlias>

<vprop:property name="userRoleCode" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:userRoleCode"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>userRoleCode</vprop:query>
</vprop:propertyAlias>

<vprop:property name="userRoleCodeSystem" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:userRoleCodeSystem"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>userRoleCodeSystem</vprop:query>
</vprop:propertyAlias>

<vprop:property name="userRoleCodeSystemName" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:userRoleCodeSystemName"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>userRoleCodeSystemName</vprop:query>
</vprop:propertyAlias>

<vprop:property name="userRoleCodeDisplayName" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:userRoleCodeDisplayName"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>userRoleCodeDisplayName</vprop:query>
</vprop:propertyAlias>

<vprop:property name="expirationDate" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:expirationDate"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>expirationDate</vprop:query>
</vprop:propertyAlias>

<vprop:property name="signDate" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:signDate"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>signDate</vprop:query>
</vprop:propertyAlias>

<vprop:property name="contentReference" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:contentReference"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>contentReference</vprop:query>
</vprop:propertyAlias>

<vprop:property name="content" type="xsd:base64Binary"/>
<vprop:propertyAlias propertyName="tns:content"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>content</vprop:query>
</vprop:propertyAlias>
<wsp:Policy wsu:Id="RespondingGateway_Query_Binding_SoapPolicy">
<wsp:ExactlyOne>
<wsp:All>
<wsaws:UsingAddressing xmlns:wsaws="http://www.w3.org/2006/05/addressing/wsdl"/>
<sc:KeyStore wspp:visibility="private"
aliasSelector="gov.hhs.fha.nhinc.callback.KeyStoreServerAliasSelector"
callbackHandler="gov.hhs.fha.nhinc.callback.KeyStoreCallbackHandler"/>
<sc:TrustStore wspp:visibility="private"
callbackHandler="gov.hhs.fha.nhinc.callback.TrustStoreCallbackHandler"/>
<sp:TransportBinding>
<wsp:Policy>
<sp:TransportToken>
<wsp:Policy>
<sp:HttpsToken>
<wsp:Policy>
<sp:RequireClientCertificate/>
</wsp:Policy>
</sp:HttpsToken>
</wsp:Policy>
</sp:TransportToken>
<sp:Layout>
<wsp:Policy>
<sp:Strict/>
</wsp:Policy>
</sp:Layout>
<sp:IncludeTimestamp/>
<sp:AlgorithmSuite>
<wsp:Policy>
<sp:Basic128/>
</wsp:Policy>
</sp:AlgorithmSuite>
</wsp:Policy>
</sp:TransportBinding>
<sp:EndorsingSupportingTokens>
<wsp:Policy>
<sp:SamlToken
sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">
<wsp:Policy>
<sp:WssSamlV20Token11/>
</wsp:Policy>
</sp:SamlToken>
</wsp:Policy>
</sp:EndorsingSupportingTokens>
<sp:Wss11>
<wsp:Policy>
<sp:MustSupportRefKeyIdentifier/>
<sp:MustSupportRefIssuerSerial/>
<sp:RequireSignatureConfirmation/>
</wsp:Policy>
</sp:Wss11>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
<wsp:Policy wsu:Id="RespondingGateway_Query_Binding_Soap_Input_Policy">
<wsp:ExactlyOne>
<wsp:All>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
<wsp:Policy wsu:Id="RespondingGateway_Query_Binding_Soap_Output_Policy">
<wsp:ExactlyOne>
<wsp:All>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
<plnk:partnerLinkType name="AdapterDocQuerySecured">

<plnk:role name="AdapterDocQuerySecuredPortTypeRole"
portType="tns:AdapterDocQuerySecuredPortType"/>
</plnk:partnerLinkType>
</definitions>
Edited by: dvazquez1027 on Feb 25, 2010 5:10 PM
Edited by: dvazquez1027 on Feb 25, 2010 5:22 PM

Hi
yes, I had the same issue and I found a solution.
You need to request a patch for BUG 9212862 (already corrected in WLS 10.3.3) and do the follwing:
javax.xml.ws.BindingProvider provider = (javax.xml.ws.BindingProvider)port;
java.util.Map context = provider.getRequestContext();
context.put(weblogic.wsee.jaxrpc.WLStub.POLICY_COMPATIBILITY_PREFERENCE, weblogic.wsee.jaxrpc.WLStub.POLICY_COMPATIBILITY_MSFT);
This will cause the SecurityMessageArchitect class of WLS to not send the SecurityTokenReference in the Soap security header.
Please note that is evidently a non-comformity to the specs of microsoft:
Please give a look at
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf (8.3 Signing Tokens)
and also at:
http://www.oasis-open.org/committees/download.php/16768/wss-v1.1-spec-os-SAMLTokenProfile.pdf
(3.4 Identifying and Referencing Security Tokens)
A SAML key identifier reference MUST be used for all (local and remote) references to SAML 1.1
assertions. [...]
All conformant implementations MUST be able to process SAML assertion references occurring in a
<wsse:Security> header or in a header element other than a signature to acquire the corresponding
assertion. A conformant implementation MUST be able to process any such reference independent of the
confirmation method of the referenced assertion.
It follows that the .NET 3.5 is a non conformat implementation: I would gladly know which is the position of Microsoft on that.
ciao
carlo

Invoking Session EJB (with WSIF binding) from a BPEL process

Hi,
I am invoking a stateless session bean from a bpel process. The bpel process is throwing:
Failed to lookup EJB home using JNDI name 'ejb/visilient/BPELHelper'; nested exception is:
java.lang.NullPointerException
I can see the ejb jndi name under 'default' app.
Any ideas?
TIA

It is a lovely sample... However, it doesn't cover Complex Types and Exception handling. It would be nice if each example was thorough. Would be a great help.
What I was hoping to achieve is this:
1) Have an EJB deployed
2) Use WSIF for BPEL Processes.
3) Use Web Service interface for AJAX calls etc.
I was hoping that this would be the exact code base and that only a single EJB would be deployed.
So far, it looks like JDeveloper will only support Java WSIF bindings. No EJB Bindings. It also looks like JAXRPC is the best supported WS interface. With that in mind, it deploys a seperate subset of the EJB. Thus causing two seperate deployments. I am working on trying all this out over the next couple days. See where I get.
Anyways, do you have any recommendation for accomplishing what I am wanting to do? 1 deployed EJB, with a WS interface and allowing WSIF bindings. Any other references for me to look at? Should I not be thinking about using JDeveloper for any of the WSDL generation and do all this manually for now?
Thanks,
BradW

Error while invoking a webservice using Axis deployed in tomacat from Bpel

Hi,
I am trying to invoke a Axis webservice(from Java class to WSDL- bottom up java bean webservice approach) developed in Exclipse IDE, deployed in Tomcat.
When i am trying to invoke the service, from Bpel from Jdeveloper it is throwing error as such :
Invoke_1 (faulted)
[2009/05/22 14:32:18] Faulted while invoking operation "storeLoanData" on provider "LoanDataPersist".less
-<messages>
-<input>
-<Invoke_1_storeLoanData_InputVariable>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="p_request">
-<p_request xmlns="" xmlns:def="http://dtos.demo.com" xsi:type="def:LoanDataPersistRequest" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<customerName>wew
</customerName>
<netIncome>12
</netIncome>
<loanAmount>12
</loanAmount>
<realEstateAddress>wew
</realEstateAddress>
<customerID/>
</p_request>
</part>
</Invoke_1_storeLoanData_InputVariable>
</input>
-<fault>
-<remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
-<part name="summary">
<summary>exception on JaxRpc invoke: trailing block elements must have an id attribute
</summary>
</part>
</remoteFault>
</fault>
</messages>
I may add that, the WSDL generated is using "soap:enc:array ", rpc style.
Can anyone tell me the reason and suggest .

Hi Marc,
Thanks for the guidancer. But sir, i am unable to detect at which place i have to do the required changes.I found p_request as a parameter in the method only in the interface only.
As bcos ultimately , i am generating the tomcat /axis web service (WSDL) from the java class, which is using 2 Request and response java bean, in which they are doing someing like this:
private static org.apache.axis.description.TypeDesc typeDesc =
new org.apache.axis.description.TypeDesc(LoanDataPersistRequest.class, true);
static {
typeDesc.setXmlType(new javax.xml.namespace.QName("http://dtos.demo.com", "LoanDataPersistRequest"));
org.apache.axis.description.ElementDesc elemField = new org.apache.axis.description.ElementDesc();
elemField.setFieldName("customerName");
elemField.setXmlName(new javax.xml.namespace.QName("", "customerName"));
elemField.setXmlType(new javax.xml.namespace.QName("", "string"));
elemField.setNillable(true);
etc etc...................}
And second thing is when the WSDL is generated, from that the stubs and skeletons is generated to test the service.
There in the Stub i found out "p_request" in this place:
private static void _initOperationDesc1(){
org.apache.axis.description.OperationDesc oper;
org.apache.axis.description.ParameterDesc param;
oper = new org.apache.axis.description.OperationDesc();
oper.setName("storeLoanData");
param = new org.apache.axis.description.ParameterDesc(*new javax.xml.namespace.QName("", "p_request")*, org.apache.axis.description.ParameterDesc.IN, new javax.xml.namespace.QName("http://dtos.demo.com", "LoanDataPersistRequest"), com.demo.dtos.LoanDataPersistRequest.class, false, false);
oper.addParameter(param);
oper.setReturnType(new javax.xml.namespace.QName("http://dtos.demo.com", "LoanDataPersistResponse"));
oper.setReturnClass(com.demo.dtos.LoanDataPersistResponse.class);
oper.setReturnQName(new javax.xml.namespace.QName("", "storeLoanDataReturn"));
oper.setStyle(org.apache.axis.constants.Style.RPC);
oper.setUse(org.apache.axis.constants.Use.ENCODED);
_operations[0] = oper;
And in skeleton :
static {
org.apache.axis.description.OperationDesc _oper;
org.apache.axis.description.FaultDesc _fault;
org.apache.axis.description.ParameterDesc [] _params;
_params = new org.apache.axis.description.ParameterDesc [] {
new org.apache.axis.description.ParameterDesc(*new javax.xml.namespace.QName("", "p_request")*, org.apache.axis.description.ParameterDesc.IN, new javax.xml.namespace.QName("http://dtos.demo.com", "LoanDataPersistRequest"), com.demo.dtos.LoanDataPersistRequest.class, false, false),
oper = new org.apache.axis.description.OperationDesc("storeLoanData", params, new javax.xml.namespace.QName("", "storeLoanDataReturn"));
_oper.setReturnType(new javax.xml.namespace.QName("http://dtos.demo.com", "LoanDataPersistResponse"));
_oper.setElementQName(new javax.xml.namespace.QName("urn:com.demo.service", "storeLoanData"));
_oper.setSoapAction("");
myOperationsList.add(oper);
if (_myOperations.get("storeLoanData") == null) {
_myOperations.put("storeLoanData", new java.util.ArrayList());
((java.util.List)_myOperations.get("storeLoanData")).add(_oper);
PLease suggest if i make some changes in stub and skeleton how it would reflect the WSDL... or else please suggest where shud i do the required changes.

Defect while invoking a Webservice using WSDL

Hi all,
I am trying to invoke a web service by creating a web service data source using the wsdl of the web service.
I dragged the web service data control on to my jspx page as ADF Parameter form. The web service, once gets
invoked should insert a row in the data base using the pay load that we send with the request.
The application is running with out any errors but when I submit the data it is getting inserted 2 times into the database
where the web service should insert only once. I tried sending the payload to the webservice manually then it inserted
only once. I am unable to find the problem.. Kindly help me on this.
Thanks & Regards,
Phani.

Hi Frank,
I did that but still the problem persists. Actually what I did was like this.
I have created a webservice proxy and a datasource using the wsdl of the proxy which has a metod "*CreateReference*" in it.
inside this create reference there is a "*parameters*" folder in which I have all the payload parameters and
a "*return*" method which has a table with statuscode and statusmessage attrubutes that gives the result
which would be a "Success" or a "Fault".
I have created a jspx page with three layout and on First layout I have dragged all the fields that are there
in the parameters folder as ADF Inputtext with Lable and I have dragged the CreateReference method from the data source as a ADF Button.
I have dragged the table that is there in the result on to the second half of the jspx page.
when I run this and click on the button after entering the info into the lables it should create a row in the database.
in my case it is creating row twice where it should create only once.
In my page definition I have default(deferred) as the refresh for all the iterators.???
Can you kindly help me on this...
Thanks,
Phani.
Edited by: 887737 on Jan 2, 2012 2:00 AM

Invokation of Webservices using HTTP

Can I invoke webservices in SAP using HTTP instead of SOAP? If so How?

Hi Vijay,
yes we can do it with HTTP
Configuring the Receiver Plain HTTP Adapter
Use
The plain HTTP outbound channel is a service provided by the Integration Engine. The system is addressed when technical routing determines a corresponding communication channel for the logical receiver from logical routing. The system sends the payload of the message to an HTTP address using HTTP, without being enhanced with an envelope.
Integration
You configure the adapter on the Parameters tab page during the definition of a communication channel in the Integration Server.
Activities
The plain HTTP adapter gives the receiver system the following specifications:
Transport Protocol
HTTP 1.0
Message Protocol
XI payload in HTTP body
Adapter Engine
Integration Server
Addressing Type
URL Address
HTTP Destination
Specify the target host, service number, and path prefix including query string:
http://<hostname:port>/<path>?<query-string>
You can identify the target host (HTTP port) of a SAP Web Application Server using the ICM monitor.
Host and port of the HTTP proxy (optional if there is a firewall between the plain HTTP adapter and the receiver system)
Authentication data for the receiver system, see also: transaction Display and Maintain RFC Destinations (SM59)
Specify the RFC destination.
Parameters from the Communication Channel for Technical Routing
●      Content type (the entry text/XML is expected as default)
Specifies the content format (payload) that the message should have.
●      (Optional) header fields for the receiver-specific protocol
●      Select Additional Query String Attributes:
○       Sender party
○       Sender service
○       Receiver interface
○       Message ID
○       Quality of service
○       Queue ID
The queue ID is only required if the quality of service is EOIO.
●      Specifications for payload manipulation
○       XML code (default UTF-8)
Specifies the character set.
○       URL escaping
Presents the XML in a URL-enabled format.
Special characters that could be interpreted as control characters are replaced with escape characters (masked).
○       Prolog
Enhances the payload for particular servers (optional, see below).
○       Epilog
Enhances the payload for particular servers (optional, see below).
Adapter-Specific Message Attributes
●      To evaluate adapter attributes in the message header of the XI message, select Set Adapter-Specific Message Attributes.
●      If you want missing message attributes to trigger an error message, select Fail If Adapter-Specific Message Attributes Missing.
If the indicator is set and the header for adapter-specific message attributes or one of the set attributes is missing from the message, this leads to a system error (red flag).
If you do not set the indicator, and message attributes are missing, the adapter accesses information from the adapter configuration.
●      If you want to use an HTTP destination or URL set by the mapping, select URL orHTTP Destination.
(The indicator displayed depends on the Addressing Type you selected above). If you set the indicator, the URL or HTTP destination set dynamically is called by HTTP.
If the message header does not contain the URL or the HTTP destination, and you have set the Fail If Adapter-Specific Message Attributes Missingindicator, the XI message is set to status System Error.
If you do not set the indicator, the URL or HTTP destination defined statically in the communication channel is used.
The technical names of the fields are:
○       URL: TargetURL
○       HTTP Destination: HTTPDest
●      If you want to use HTTP header fields, select Apply HTTP Header Fields and enter the fields in Field 1 to Field 6.
The fields are embedded in the HTTP request under the names you enter here.
The technical names of the fields are HeaderFieldOne, .... HeaderFieldSix.
●      If you want to use URL parameters, select Apply URL Parameters and enter the parameters in the fields Parameter 1 to Parameter 6.
The parameters are included in the HTTP request under the names specified here.
The technical names of the fields are URLParamOne, u2026, URLParamSix.
●      If you want to save HTTP header fields from the synchronous response in the XI message header, choose HTTP Header Fields (Synchronous Response) and enter the fields in the fields Field 1 to Field 6.
The fields must have the same names as the fields that are also to be sent in the HTTP response.
The technical names of the fields are HeaderFieldOne,...,HeaderFieldSix.
●      The attribute namespace for the adapter is http://sap.com/xi/XI/System/HTTP.

Invoking a Webservice using a SOAP adapter

Hi,
I have the following scenario.
SAP ABAP outbound proxy <-> SAP XI <--> External webservice.
The above call is a synchronous call from SAP R/3 and a receiver soap adapter is configured for the Webservice.
I am getting the following error messages when I try to run the scenario.
1)ADAPTER.SOAP_EXCEPTION.
2)<SAP:AdditionalText>
soap fault: Server did not recognize the value of HTTPHeaderSOAPAction
</SAP:AdditionalText>
What could be the possible reasons for the error message?
In the target URL of the soap adapter I am specifying the path till .asmx.
Thanks,
Leo

Hi,
There are 2 pieces of data that must be provided in the SOAP receiver adapter. Both of them can be obtained from the WSDL of the soap service provider.
1. Target URL, which can be obtain from the attribute "location" of the "address" element in the WSDL.
2. SOAP Action, which can be obtain from the "soapAction" attibute of the "operation" element in the WSDL.
Regards,
Bill

Invoking a webservice from a servlet

Hi,
I am able to invoke a webservice using a Standalone java program. I am using the below command to invoke the web service.
java com.javasrc.webservices.age.AgeServiceClient -lhttp://localhost:8080/axis/services/AgeService "Siva" 33
Now if I write the whole code in a method I am not able to retreive the values into the servlet. Can any please suggest me how to invoke a web service from a servlet/JSP. Please tell if there any sites for this.
Here is my Client code:
import org.apache.axis.client.Call;
import org.apache.axis.client.Service;
import org.apache.axis.encoding.XMLType;
import org.apache.axis.utils.Options;
import javax.xml.namespace.QName;
import javax.xml.rpc.ParameterMode;
public class AgeServiceClient
public static void main(String [] args)
try
     Options options = new Options(args);
     String endpointURL = options.getURL();
     String name;
     Integer age;
     args = options.getRemainingArgs();
     if ((args == null) || (args.length < 2))
          name = "NoName";
          age = new Integer( 0 );
     else
          name = args[ 0 ];
          age = new Integer( args[ 1 ] );
          Service service = new Service();
          Call call = (Call) service.createCall();
          call.setTargetEndpointAddress( new java.net.URL(endpointURL) );
          call.setOperationName( new QName("http://age.webservices.javasrc.com", "age") );
          call.addParameter( "arg1", XMLType.XSD_STRING,ParameterMode.IN);
          call.addParameter( "arg2", XMLType.XSD_INT, ParameterMode.IN);
          call.setReturnType( org.apache.axis.encoding.XMLType.XSD_STRING);
          String ret = (String) call.invoke( new Object[]{name,age});
          System.out.println("Age result : " + ret);
     catch (Exception e)
          System.err.println(e.toString());
Thanks in advance
Prashanth

This is very simple maybe you don't have servlet experience.
Simply you create a servlet and put your client main method in another one (not static method) + importing jar of your client and other associated jar files in WEB_INF\lib folder of servlet.
check for helloworld servlet then you can implement servlet for your client.

Soap layer error when trying to invoke a webservice.

Hi,
I am new to Weblogic.
I have an issue while invoking the webservice of a webmethods application.
I am invoking that webservice using rpc call (call.invoke() method of javax.xml.rpc api).
Please find error description occured in the Server logs of weblogic server.
Exception while invoking the service call Message is :failed to invoke operation '__incidentReqInput' due to an error in the soap layer(SAAJ);
nested exception is: Message[Found SOAPElement
[<m:payload xmlns:m="http://www.abc.com/gs/solutions/message"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:nil="true">
</m:payload>]. But was not able to find a Part that is registered with this Message which corresponds to this SOAPElement. Th
e name of the element should be one of these[__bea_noname_result]]StackTrace[
javax.xml.soap.SOAPException: Found SOAPElement [<m:payload xmlns:m="http://www.abc.com/gs/solutions/message"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:nil="true">
</m:payload>]. But was not able to find a Part that is registered with this Message which corresponds to this SOAPElement. Th
e name of the element should be one of these[__bea_noname_result]
at weblogic.webservice.core.DefaultMessage.toJava(DefaultMessage.java:478)
at weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:325)
at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:144)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:443)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:566)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:419)
at com.gs.customerbonding.hub.httpHandler.WSResponseSenderImpl.sendResponse(WSResponseSenderImpl.jcs:370)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371)
at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:423)
at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
at com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:381)
at $Proxy106.sendResponse(Unknown Source)
Any help is highly appreciated.
Regards
Nag

I am not using any wsdl file. I'm trying to invoke a webservice that is at client's end (using RPC call). Mine is a generic server program. When i'm calling other clients using the same method, im not facing any issues. Only for 1 particular end-point i'm getting the above exception. Any suggestions?

Unable to invoke Java WSIF Binding process

Hi,
I am using BPEL 10.1.3.1 version.
- I created Greeting.java, then from JDev generate WebService for class but did not publish or deploy as web service
- in BPEL created one partner link using same wsdl file from local file system
- put invoke activity to call this partner link
- deployed process
- copied all class file with package folder inside $ORACLE_HOME/bpel/system/classes folder
When i initiate the process i get error
Failed get wsdl service definition.
Failed to get a WSDL service that support the portType "{http://BusinessProcess/}Greeting" in WSDL definition "{http://BusinessProcess/}Greeting".
Please verify that WSDL portType "{http://BusinessProcess/}Greeting" is supported by a service in WSDL file.
Please help.

Hi Jack
Does your WSDL have the "binding" and "service" section? I do not use JDev or anything else to create the WSDL for me, I create it by hand so I don´t know how to help you in JDev, but it seens that JDev does not generate this sections and you must set then in order to use WSIF Bindings to Java or EJB.
Regards
Marcelo

Unable to invoke Java WSIF Binding wsdl from BPEL

Hi,
I am using BPEL 10.1.3.1 version.
- I created Greeting.java, then from JDev generate WebService for class but did not publish or deploy as web service
- in BPEL created one partner link using same wsdl file from local file system
- put invoke activity to call this partner link
- deployed process
- copied all class file with package folder inside $ORACLE_HOME/bpel/system/classes folder
When i initiate the process i get error
Failed get wsdl service definition.
Failed to get a WSDL service that support the portType "{http://BusinessProcess/}Greeting" in WSDL definition "{http://BusinessProcess/}Greeting".
Please verify that WSDL portType "{http://BusinessProcess/}Greeting" is supported by a service in WSDL file.
Please help.

Hi Jack
Does your WSDL have the "binding" and "service" section? I do not use JDev or anything else to create the WSDL for me, I create it by hand so I don´t know how to help you in JDev, but it seens that JDev does not generate this sections and you must set then in order to use WSIF Bindings to Java or EJB.
Regards
Marcelo

WSIF Binding Error while invoking HTTP Service

Hi,
I am getting a WSIF binding error when invoking an HTTP service. I was able to successfully invoke another HTTP service on the same server. However, while invoking some of the others services, we are getting errors. The wsdl binding declaration is:
<binding name="JACADACustMaintBinding" type="tns:JACADACustMaintPortType">
<http:binding verb="POST"/>
<operation name="PostData">
<http:operation location="/custmaint.cfg"/>
<input>
<mime:mimeXml part="CustMaintInput"/>
<mime:content type="text/xml"/>
</input>
<output>
<mime:mimeXml part="CustMaintOutput"/>
<mime:content type="text/xml"/>
</output>
</operation>
</binding>
The error we are getting is as follows:
com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.oracle.com/bpel/extension}bindingFault}
messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage}
parts: {{summary=[email protected] : Could not invoke 'PostData'; nested exception is:
     java.lang.Exception: Error in HTTP Post: Status 500: Unable to invoke service method: com.jacada.ea.jclient3.JClient3Exception: com.jacada.ea.jclient3.JClient3Exception:Negative response from server, response code: 110. Message from server: com.jacada.ea.jservice.JServiceException: Could not set input parameter: InVar_0: <html><head><title>Apache Tomcat/4.1.18 - Error report</title><STYLE></STYLE> </head><body><h1>HTTP Status 500 - Unable to invoke service method: com.jacada.ea.jclient3.JClient3Exception: com.jacada.ea.jclient3.JClient3Exception:Negative response from server, response code: 110. Message from server: com.jacada.ea.jservice.JServiceException: Could not set input parameter: InVar_0</h1><HR size="1" noshade><p><b>type</b> Status report</p><p><b>message</b> <u>Unable to invoke service method: com.jacada.ea.jclient3.JClient3Exception: com.jacada.ea.jclient3.JClient3Exception:Negative response from server, response code: 110. Message from server: com.jacada.ea.jservice.JServiceException: Could not set input parameter: InVar_0</u></p><p><b>description</b> <u>The server encountered an internal error (Unable to invoke service method: com.jacada.ea.jclient3.JClient3Exception: com.jacada.ea.jclient3.JClient3Exception:Negative response from server, response code: 110. Message from server: com.jacada.ea.jservice.JServiceException: Could not set input parameter: InVar_0) that prevented it from fulfilling this request.</u></p><HR size="1" noshade><h3>Apache Tomcat/4.1.18</h3></body></html>
,detail=java.lang.Exception: Error in HTTP Post: Status 500: Unable to invoke service method: com.jacada.ea.jclient3.JClient3Exception: com.jacada.ea.jclient3.JClient3Exception:Negative response from server, response code: 110. Message from server: com.jacada.ea.jservice.JServiceException: Could not set input parameter: InVar_0: <html><head><title>Apache Tomcat/4.1.18 - Error report</title><STYLE></STYLE> </head><body><h1>HTTP Status 500 - Unable to invoke service method: com.jacada.ea.jclient3.JClient3Exception: com.jacada.ea.jclient3.JClient3Exception:Negative response from server, response code: 110. Message from server: com.jacada.ea.jservice.JServiceException: Could not set input parameter: InVar_0</h1><HR size="1" noshade><p><b>type</b> Status report</p><p><b>message</b> <u>Unable to invoke service method: com.jacada.ea.jclient3.JClient3Exception: com.jacada.ea.jclient3.JClient3Exception:Negative response from server, response code: 110. Message from server: com.jacada.ea.jservice.JServiceException: Could not set input parameter: InVar_0</u></p><p><b>description</b> <u>The server encountered an internal error (Unable to invoke service method: com.jacada.ea.jclient3.JClient3Exception: com.jacada.ea.jclient3.JClient3Exception:Negative response from server, response code: 110. Message from server: com.jacada.ea.jservice.JServiceException: Could not set input parameter: InVar_0) that prevented it from fulfilling this request.</u></p><HR size="1" noshade><h3>Apache Tomcat/4.1.18</h3></body></html>
     at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:617)
     at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:437)
     at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:251)
     at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:826)
     at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:402)
     at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:199)
     at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3698)
     at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1655)
     at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:217)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:314)
     at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5765)
     at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1087)
     at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.createAndInvoke(CubeEngineBean.java:133)
     at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.syncCreateAndInvoke(CubeEngineBean.java:162)
     at sun.reflect.GeneratedMethodAccessor86.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
     at com.evermind.server.ThreadState.runAs(ThreadState.java:693)
     at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.TxRequiresNewInterceptor.invoke(TxRequiresNewInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
     at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
     at CubeEngineBean_LocalProxy_4bin6i8.syncCreateAndInvoke(Unknown Source)
     at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequestAnyType(DeliveryHandler.java:547)
     at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequest(DeliveryHandler.java:464)
     at com.collaxa.cube.engine.delivery.DeliveryHandler.request(DeliveryHandler.java:133)
     at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java:95)
     at sun.reflect.GeneratedMethodAccessor85.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
     at com.evermind.server.ThreadState.runAs(ThreadState.java:693)
     at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
     at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
     at DeliveryBean_RemoteProxy_4bin6i8.request(Unknown Source)
     at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processNormalOperation(SOAPRequestProvider.java:451)
     at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processBPELMessage(SOAPRequestProvider.java:274)
     at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processMessage(SOAPRequestProvider.java:120)
     at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:956)
     at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349)
     at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:466)
     at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114)
     at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:96)
     at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:194)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
     at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:400)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
     at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:414)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:623)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:313)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)
Request you all to provide inputs.
Thanks and Regards.
John

Hi,
Using the exact same wsdl i was able to get a response from the HTTP service using OSB. I created a business service targeting this wsdl. Then created a proxy service to route the xml to the business service.
I was able to successfully invoke and get response from the HTTP service without making any change to the wsdl.
Could this be a bug in BPEL PM? Should I raise an SR?

Need Help: Not able to invoke fusion crm webservice using SOAP UI

Hi,
I am trying to invoke fusion crm webservice by using SOAP UI, but I am getting Invalid seccurity tocken exception.
I have followed below steps specified in the oracle support document.
In Soap UI, Go to File>Preferences ,select the "HTTP Settings' tab on the lower left panel, then select the checkbox 'Authenticate Preemtively'.
2. From the wsdl extract the content from above wsdl between the tag/elements <dsig:X509Certificate> and </dsig:X509Certificate>
3. Create a file called certificate.cer ( in local Drive) with above encrypted data enclosed between -----BEGIN CERTIFICATE-----   and -----END CERTIFICATE-----, file content shown below ( note: encrypted data
    for example
    -----BEGIN CERTIFICATE-----
MIICCzCCAXSgAwIBAgIETy
    -----END CERTIFICATE-----
4. Identifiy the java.home of SOAP UI , navigation (Help – System Properties) ,example ( it may be something like D:\SOAP UI download\soapui-4.5.1\jre)
5. Find the location of cacert file in SOAP UI ( example D:\SOAP UI download\soapui-4.5.1\jre\lib\security\cacert)
6. Use following keytool command to add the certificate file certificate.cer into keystore cacert , sample command given below for reference
   keytool -importcert -alias rcpt-key-alias -file "D:\certificate.cer" -keystore "D:\SOAP UI download\soapui-4.5.1\jre\lib\security\cacerts"
   at command prompt when prompted enter password as changeit
7. Restart SOAP UI and create a new project with https version of WSDL of organizationService
8. In SOAP UI , in Auth tab , provide the user name and password.
9. Invoke the Webservice
I have used following request XML in SOAP UI
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://xmlns.oracle.com/apps/sales/opptyMgmt/opportunities/opportunityService/types/" xmlns:opp="http://xmlns.oracle.com/apps/sales/opptyMgmt/opportunities/opportunityService/" xmlns:rev="http://xmlns.oracle.com/apps/sales/opptyMgmt/revenues/revenueService/" xmlns:not="http://xmlns.oracle.com/apps/crmCommon/notes/noteService" xmlns:not1="http://xmlns.oracle.com/apps/crmCommon/notes/flex/noteDff/" xmlns:rev1="http://xmlns.oracle.com/oracle/apps/sales/opptyMgmt/revenues/revenueService/" xmlns:act="http://xmlns.oracle.com/apps/crmCommon/activities/activitiesService/" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:soap="soap" xmlns:ns1="http://xmlns.oracle.com/apps/fnd/soaprovider/plsql/fnd_user_pkg/">
   <soapenv:Header>
      <fmw-context xmlns="http://xmlns.oracle.com/fmw/context/1.0"/>
      <wsse:Security soap:mustUnderstand="1">
         <wsse:UsernameToken>
            <wsse:Username>userName</wsse:Username>
            <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">Password</wsse:Password>
         </wsse:UsernameToken>
      </wsse:Security>
   </soapenv:Header>
   <soapenv:Body>
      <typ:createOpportunity>
         <typ:opportunity>
            <opp:BudgetedFlag>1</opp:BudgetedFlag>
         </typ:opportunity>
      </typ:createOpportunity>
   </soapenv:Body>
</soapenv:Envelope>
It would be great help if someone guide me on this...
Thanks & Regards
Samanta Mishra

For reference here is an example of a SOAP envelope I commonly use with SOAP UI to "query" employee data from HCM:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://xmlns.oracle.com/apps/hcm/employment/core/workerService/types/" xmlns:typ1="http://xmlns.oracle.com/adf/svc/types/">
    <soapenv:Header>
        <wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
            <wsse:UsernameToken wsu:Id="UsernameToken-2" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
                <wsse:Username>username</wsse:Username>
                <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">password</wsse:Password>
                <wsse:Nonce EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">jwCzGGijT90Wml6eZe4cxg==</wsse:Nonce>
                <wsu:Created>2012-07-04T06:49:48.981Z</wsu:Created>
            </wsse:UsernameToken>
        </wsse:Security>
    </soapenv:Header>
    <soapenv:Body>
        <typ:findWorker>
            <typ:findCriteria>
                <typ1:fetchStart>0</typ1:fetchStart>
                <typ1:fetchSize>1</typ1:fetchSize>
                <typ1:filter>
                    <typ1:conjunction>And</typ1:conjunction>
                    <typ1:group>
                        <typ1:conjunction>And</typ1:conjunction>
                        <typ1:upperCaseCompare>false</typ1:upperCaseCompare>
                        <typ1:item>
                            <typ1:conjunction>And</typ1:conjunction>
                            <typ1:upperCaseCompare>false</typ1:upperCaseCompare>
                            <typ1:attribute>PersonNumber</typ1:attribute>
                            <typ1:operator>=</typ1:operator>
                            <typ1:value>123456</typ1:value>
                        </typ1:item>
                    </typ1:group>
                </typ1:filter>
            </typ:findCriteria>
            <typ:findControl>
                <typ1:retrieveAllTranslations>false</typ1:retrieveAllTranslations>
            </typ:findControl>
        </typ:findWorker>
    </soapenv:Body>
</soapenv:Envelope>
This example works fine for our Fusion Applications Cloud test instance, without any SSL setup or setting credentials on the request properties as the target service supports policy without message protection.
Based on the your steps your service has message protection policy, so the above will not work rather you need to do additional configuration. Please check the policy on your service to confirm how the call needs to be made. Here are few links and documents:
"How to invoke Fusion Application TCA webservice from SOAP UI (Doc ID 1496071.1)" documents how a service with message protection can be called from SOAP UI. Your steps seem identical so presumably they are based on this document.
"Oracle Fusion Sales Cloud Web Services (Doc ID 1354841.1)" contains information about the CRM web services including examples on the certificate import and sample payloads.
Please provide:
The security policies defined on the service (check the wsdl)
The exact error message the you get
Jani Rautiainen
Fusion Applications Developer Relations
https://blogs.oracle.com/fadevrel/

Invoking a webservice using WSIF Binding

Similar Messages

Maybe you are looking for