Quantcast

Howto: BPEL Invoke https WebS - tutor request

classic Classic list List threaded Threaded
25 messages Options
12
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Howto: BPEL Invoke https WebS - tutor request

szdezso
Hello There!

I'm looking for a step by step tutorial about how create a bpel process that communicate a https WebService from OSB BPEL process.

For ex.: call this: https://secure.telemessage.com/services/telemessage 

Soap sample (from SoapUI):

<soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sch="http://telemessage.com/soap/schemas">
   <soapenv:Header/>
   <soapenv:Body>
      <sch:queryStatus soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
         <loginDetails xsi:type="sch:AuthenticationDetails">
            <password xsi:type="xsd:string">asa</password>
            <username xsi:type="xsd:string">asas</username>
         </loginDetails>
         <message_id xsi:type="xsd:long">1</message_id>
         <messageKey xsi:type="xsd:string">a</messageKey>
      </sch:queryStatus>
   </soapenv:Body>
</soapenv:Envelope>

It's catch a good response from WebS (but authentication failed).

Can you help me?

Thanks in dvance.

Rgds.

D.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Howto: BPEL Invoke https WebS - tutor request

Stefan Müller-Wilken
Hi there,

there is a 'classic' tutorial by Tom Barrett called 'A gentle introduction to BPEL' that should provide all necessary information to consume (or provide) web services like the one you referenced. You can find this tutorial (and many others) on the openesb website: www.open-esb.net

Cheers
 Stefan.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Howto: BPEL Invoke https WebS - tutor request

szdezso
Hello Stefan,

Thx the quick response, I know the BPEL.
Maybe my question was wrong.
I have to communicate a https ! webservice from OSB.
The http communication is works.
I need the Casa editor: how setup the Invoked https webs client in Casa?

I give a sample/public https webs that somebody bind this webs in a sample Bpel and Casa project.
Or give me a working tutor.

Rgds.

D.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Howto: BPEL Invoke https WebS - tutor request

Stefan Müller-Wilken
So, where exactly lies the problem? Switching an OpenESB service assembly to call services via HTTPS? Or how to consume SOAP services? Or how to authenticate (i.e. fill the username and password elements in your example?

Cheers
 Stefan
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Howto: BPEL Invoke https WebS - tutor request

szdezso
This:  "Switching an OpenESB service assembly to call services via HTTPS"
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Howto: BPEL Invoke https WebS - tutor request

szdezso
In reply to this post by Stefan Müller-Wilken
OpenESB call a Https WebS
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Howto: BPEL Invoke https WebS - tutor request

Stefan Müller-Wilken
But where exactly is the problem? When you consume the external WSDL behind a HTTPS address in OpenESB, you get a WSDL file in your project that you can drag to the right hand side of your BPEL designer and invoke just the same way you would with a non secured destination. No magic about that. So: just do as you usually would and you should be fine.

Cheers
 Stefan
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Howto: BPEL Invoke https WebS - tutor request

szdezso
Hello,

I have followed you, but I have an exception:

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP-ENV:Body>
      <SOAP-ENV:Fault>
         <faultcode>SOAP-ENV:Server</faultcode>
         <faultstring>
<![CDATA[BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;jbi:message xmlns:sxeh=&quot;http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling&quot; type=&quot;sxeh:faultMessage&quot; version=&quot;1.0&quot; xmlns:jbi=&quot;http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper&quot;&gt;&lt;jbi:part&gt;HTTP transport error: java.net.SocketException: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext)&lt;/jbi:part&gt;&lt;/jbi:message&gt;. Sending errors for the pending requests in the process scope before terminating the process instance]]>
</faultstring>
         <faultactor>sun-bpel-engine</faultactor>
         <detail>
            <detailText>
<![CDATA[BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;jbi:message xmlns:sxeh=&quot;http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling&quot; type=&quot;sxeh:faultMessage&quot; version=&quot;1.0&quot; xmlns:jbi=&quot;http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper&quot;&gt;&lt;jbi:part&gt;HTTP transport error: java.net.SocketException: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext)&lt;/jbi:part&gt;&lt;/jbi:message&gt;. Sending errors for the pending requests in the process scope before terminating the process instance
   Caused by: BPCOR-6131: An Error status was received while doing an invoke (partnerLink=PartnerLink3, portType={http://tempuri.org/}IIAPIInterfacebinding, operation=getSession)
BPCOR-6129: Line Number is 38
BPCOR-6130: Activity Name is Invoke1
   Caused by: HTTP transport error: java.net.SocketException: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext)
   Caused by: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext)
   Caused by: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext)
   Caused by: null
   Caused by: E:\develop\OpenESB-SE-3.0.5\OE-Instance\keystore.jks (A rendszer nem találja a megadott fájlt)]]>
</detailText>
         </detail>
      </SOAP-ENV:Fault>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

?

Thx.

Rgds.

D.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Howto: BPEL Invoke https WebS - tutor request

Stefan Müller-Wilken
Hi there - and sorry, for the rant, BUT: have you ever wondered, what OpenESB (or the jJava runtime) want's to tell you by saying "A rendszer nem találja a megadott fájlt"? And this even more so when written in a single line as

Caused by: E:\develop\OpenESB-SE-3.0.5\OE-Instance\keystore.jks (A rendszer nem találja a megadott fájlt)]]>

So, the first thing I'd suggest is to check if your keystore.jks is available and filled with reasonable values. What is the output of the command

keytool -list -keystore E:\develop\OpenESB-SE-3.0.5\OE-Instance\keystore.jks

Cheers
 Stefan
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Howto: BPEL Invoke https WebS - tutor request

szdezso
Hello

"A rendszer ne mtalalja a megadott fajlt" eq "File not found".
And yes it's a Soapui side sopaenvelope, but the essence: keystore,jks not found.

Ok I will check the command.
But how can I create a keystore.jks, how do I fill it?

Rgds.

D.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Howto: BPEL Invoke https WebS - tutor request

Stefan Müller-Wilken
Nothing easier than that: http://lmgtfy.com/?q=create+a+keystore.jks...
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Howto: BPEL Invoke https WebS - tutor request

szdezso
The cmd result is:

keytool error: java.lang.Exception: Keystore file does not exist: E:\develop\OpenESB-SE-3.0.5\OE-Instance\keystore.jks

D.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Howto: BPEL Invoke https WebS - tutor request

Stefan Müller-Wilken
... and the cmd is?
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Howto: BPEL Invoke https WebS - tutor request

szdezso
keytool.exe is exists.

This command is enough for keystore.jks?

keytool -genkey -alias mykey -keyalg RSA -keypass changeit -keystore keystore.jks
-storepass changeit

then I copy the generated keystore.jks to OSB instance folder?

or I have to do plus steps too?

Thx.

D.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Howto: BPEL Invoke https WebS - tutor request

Stefan Müller-Wilken
It depends on the revision and if you also intend to do client authentication (in which case you need to make sure you pick the appropriate key alias). But for a first test this should suffice...

Cheers
 Stefan
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Howto: BPEL Invoke https WebS - tutor request

szdezso
So, I have followed this instructions:

https://docs.oracle.com/cd/E19509-01/820-3503/cnfg_ssl-em_t/index.html

keytool -genkey -alias mykey -keyalg RSA -keypass changeit -keystore keystore.jks -storepass changeit

keytool -export -alias mykey -file mykey.cer -keystore keystore.jks -storepass changeit

keytool -import -v -trustcacerts -alias mykey -keypass changeit -file mykey.cer -keystore cacerts.jks -storepass changeit

Then I have copied the keystore.jks and cacerts.jks and mykey.cer files to
e:\develop\OpenESB-SE-3.0.5\OE-Instance\

then I have updated the openesb.bat in the following line:

"%JAVA_HOME%\bin\java" "-Dcom.atomikos.icatch.file=%OPENESB_HOME%/tm/jta.properties" "-Djava.util.logging.config.file=%OPENESB_HOME%/config/logger.properties" -Djava.util.logging.manager=net.openesb.standalone.logging.LogManager -cp "%filename%;%OPENESB_HOME%/lib/ext/jansi-1.11.jar" "-Djavax.net.ssl.keyStore=%OPENESB_HOME%/keystore.jks" "-Djavax.net.ssl.trustStore=%OPENESB_HOME%/cacerts.jks" -Djavax.net.ssl.keyStorePassword=changeit -Djavax.net.ssl.trustStorePassword=changeit -Djmx.invoke.getters=true "-Dopenesb.home=%OPENESB_HOME%" net.openesb.standalone.startup.Bootstrap %*

added this: -Djavax.net.ssl.trustStorePassword=changeit

Rerun the Soap request:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP-ENV:Body>
      <SOAP-ENV:Fault>
         <faultcode>SOAP-ENV:Server</faultcode>
         <faultstring>
<![CDATA[BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;jbi:message xmlns:sxeh=&quot;http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling&quot; type=&quot;sxeh:faultMessage&quot; version=&quot;1.0&quot; xmlns:jbi=&quot;http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper&quot;&gt;&lt;jbi:part&gt;HTTP transport error: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target&lt;/jbi:part&gt;&lt;/jbi:message&gt;. Sending errors for the pending requests in the process scope before terminating the process instance]]>
</faultstring>
         <faultactor>sun-bpel-engine</faultactor>
         <detail>
            <detailText>
<![CDATA[BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;jbi:message xmlns:sxeh=&quot;http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling&quot; type=&quot;sxeh:faultMessage&quot; version=&quot;1.0&quot; xmlns:jbi=&quot;http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper&quot;&gt;&lt;jbi:part&gt;HTTP transport error: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target&lt;/jbi:part&gt;&lt;/jbi:message&gt;. Sending errors for the pending requests in the process scope before terminating the process instance
   Caused by: BPCOR-6131: An Error status was received while doing an invoke (partnerLink=PartnerLink3, portType={http://tempuri.org/}IIAPIInterfacebinding, operation=getSession)
BPCOR-6129: Line Number is 38
BPCOR-6130: Activity Name is Invoke1
   Caused by: HTTP transport error: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
   Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
   Caused by: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
   Caused by: unable to find valid certification path to requested target]]>
</detailText>
         </detail>
      </SOAP-ENV:Fault>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

and the in log:

2017-03-01T10:22:19.887+0100 WARNING [com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.BPELProcessInstanceImpl] (sun-bpel-engine-thread-9) BPCOR-6151: The process instance has been terminated because a fault was not handled; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>HTTP transport error: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target</jbi:part></jbi:message>
com.sun.jbi.engine.bpel.core.bpel.exception.SystemException: BPCOR-6131: An Error status was received while doing an invoke (partnerLink=PartnerLink3, portType={http://tempuri.org/}IIAPIInterfacebinding, operation=getSession)
BPCOR-6129: Line Number is 38
BPCOR-6130: Activity Name is Invoke1
        at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.processStatus(InvokeUnitImpl.java:969)
        at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.process(InvokeUnitImpl.java:566)
        at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.doAction(InvokeUnitImpl.java:185)
        at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:163)
        at com.sun.jbi.engine.bpel.core.bpel.engine.BusinessProcessInstanceThread.execute(BusinessProcessInstanceThread.java:98)
        at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.process(BPELProcessManagerImpl.java:1088)
        at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:280)
        at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:1338)
        at com.sun.jbi.engine.bpel.BPELSEInOutThread.processStatus(BPELSEInOutThread.java:384)
        at com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:241)
        at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:193)
Caused by: com.sun.xml.ws.client.ClientTransportException: HTTP transport error: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
        at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:131)
        at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:219)
        at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:143)
        at com.sun.xml.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:139)
        at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:961)
        at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:910)
        at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:873)
        at com.sun.xml.ws.api.pipe.Fiber.run(Fiber.java:717)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)
Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
        at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
        at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1904)
        at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:279)
        at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:273)
        at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1446)
        at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:209)
        at sun.security.ssl.Handshaker.processLoop(Handshaker.java:901)
        at sun.security.ssl.Handshaker.process_record(Handshaker.java:837)
        at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1023)
        at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1332)
        at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1359)
        at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1343)
        at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:563)
        at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185)
        at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1092)
        at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:250)
        at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:119)
        ... 10 more
Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
        at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:385)
        at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:292)
        at sun.security.validator.Validator.validate(Validator.java:260)
        at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:326)
        at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:231)
        at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:126)
        at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1428)
        ... 22 more
Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
        at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:196)
        at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:268)
        at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:380)
        ... 28 more

What's missing?

D.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Howto: BPEL Invoke https WebS - tutor request

Stefan Müller-Wilken
This can have at least two reasons. One is connected to the misleading name of keytool, that, for some reason, is not capable of handling keys - apart from creating them. You can especially not export them! Please make a test and use keytool to list the contents of your keystore (keytool -list -keystore keystore.jks). If you have the following, then you're safe:

mykey, Mar 1, 2017, PrivateKeyEntry,
Certificate fingerprint (SHA1): ...

The important part here is the PrivateKeyEntry, which indicates that this is not just a certificate but also a key. You'll need that!

The other thing is to make sure that your destinations signing authority needs to be part of your trusted certificates store. Is it?

Cheers
 Stefan
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Howto: BPEL Invoke https WebS - tutor request

szdezso
Hello!

I have use this:

keytool -list -keystore E:\develop\OpenESB-SE-3.0.5\OE-Instance\keystore.jks

and the result is:

c:\Program Files\Java\jdk1.7.0_75\bin>keytool -list -keystore E:\develop\OpenESB-SE-3.0.5\OE-Instance\keystore.jks
Enter keystore password:

*****************  WARNING WARNING WARNING  *****************
* The integrity of the information stored in your keystore  *
* has NOT been verified!  In order to verify its integrity, *
* you must provide your keystore password.                  *
*****************  WARNING WARNING WARNING  *****************

Keystore type: JKS
Keystore provider: SUN

Your keystore contains 1 entry

mykey, 2017.03.01., PrivateKeyEntry,
Certificate fingerprint (SHA1): 2E:05:0F:CD:A3:DC:EC:3B:40:84:8A:0E:95:3C:2C:86:DF:C0:29:55

Rgds.

D.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Howto: BPEL Invoke https WebS - tutor request

szdezso
I use the WebS at first from SoapUI, from this tool the WebS works without problem.
Without any plus interaction.

I have to use the WebS cert in OSB?

Rgds.

D.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Howto: BPEL Invoke https WebS - tutor request

Stefan Müller-Wilken
Well, you will at least have to add it to your trusted certificates. That's why I suggested checking if it is in the list already...
12
Loading...