how to use dynamic partner link in BPEL ?

[mithun_jhonny]

Hi,

I need to call web services dynamically from BPEL (I want to give the location of web service as inputs)

i.e I need to make use of dynamic partner link . Can any one point me to any tutorial for that ?

thanks,
Mithun

[Kiran Bhumana-2]

Hello Mithun,
 You can find information on this on open-esb wiki pages (BPEL-SE).
FYReference,
http://wiki.open-esb.java.net/Wiki.jsp?page=UsingDynamicPartnerLinks.

thanks,
Kiran.

mithun_jhonny wrote:

> Hi,
>
> I need to call web services dynamically from BPEL (I want to give the
> location of web service as inputs)
>
> i.e I need to make use of dynamic partner link . Can any one point me to any
> tutorial for that ?
>
> thanks,
> Mithun
>
>
>
>  

--
Kiran Bhumana
Open ESB Community (http://open-esb.org)

[mithun_jhonny]

Hi,

I tried the example given there . But when I pass a different web service address (other than the one already used in on the main BPEL ). It gives me a error saying

   Caused by: BPJBI-6019:unable to resolve the service endpoint dynamically for the document fragment

Can anyone please help me with this . Please find the files attached.
 

thanks,
Mithun


netbeansoproj.zip

Kiran Bhumana-2 wrote:

Hello Mithun,
 You can find information on this on open-esb wiki pages (BPEL-SE).
FYReference,
http://wiki.open-esb.java.net/Wiki.jsp?page=UsingDynamicPartnerLinks.

thanks,
Kiran.

mithun_jhonny wrote:
> Hi,
>
> I need to call web services dynamically from BPEL (I want to give the
> location of web service as inputs)
>
> i.e I need to make use of dynamic partner link . Can any one point me to any
> tutorial for that ?
>
> thanks,
> Mithun
>
>
>
>  

--
Kiran Bhumana
Open ESB Community (http://open-esb.org)

[mithun_jhonny]

hi,

Just to update . I have 2 echo  web services which have same targetnamespace and same operation name . I am extracting the end-point by  wrap with service reference in the main bpel. I am trying to call one of these echo services dynamically.

But I get the following error (   Caused by: BPJBI-6019:unable to resolve the service endpoint dynamically for the document fragment )

Please find the update project files attachd. It will be great if someone can look at this and guide me .

NetBeansProjects.zip







Hi,

I tried the example given there . But when I pass a different web service address (other than the one already used in on the main BPEL ). It gives me a error saying

   Caused by: BPJBI-6019:unable to resolve the service endpoint dynamically for the document fragment

Can anyone please help me with this . Please find the files attached.
 

thanks,
Mithun


netbeansoproj.zip

Kiran Bhumana-2 wrote:

Hello Mithun,
 You can find information on this on open-esb wiki pages (BPEL-SE).
FYReference,
http://wiki.open-esb.java.net/Wiki.jsp?page=UsingDynamicPartnerLinks.

thanks,
Kiran.

mithun_jhonny wrote:
> Hi,
>
> I need to call web services dynamically from BPEL (I want to give the
> location of web service as inputs)
>
> i.e I need to make use of dynamic partner link . Can any one point me to any
> tutorial for that ?
>
> thanks,
> Mithun
>
>
>
>  

--
Kiran Bhumana
Open ESB Community (http://open-esb.org)

[Kiran Bhumana-2]

Hello Mithun,

I looked at your project. What you can change is the address, not the service and port. We are working on improving HTTP BC so that you can change the service and port as well. But for now, take it that the HTTP-BC needs to know that the service and port that you are providing so that it can format the message according to the right binding.

What you did is very good, except that you didn't need the echo3WSDL at all! Your echo and echo3 WSDLs are exactly the same. Since echo WSDL is already deployed in BC, by changing just the address it should work.
I couldn't reach http://10.60.141.107:9009/echo3/echo3Service, hence I think even after the changes it failed on my machine.

Attached is a project that I worked on to provide as a sample in NB, so users can reuse these BPELs to construct the Dynamic endpoint structure. Let me know if that helps in any way.

Thanks,
Kiran B.

mithun_jhonny wrote:

Hi,

I tried the example given there . But when I pass a different web service
address (other than the one already used in on the main BPEL ). It gives me
a error saying 

   Caused by: BPJBI-6019:unable to resolve the service endpoint dynamically
for the document fragment 

Can anyone please help me with this . Please find the files attached.
 

thanks,
Mithun


http://www.nabble.com/file/p18437106/netbeansoproj.zip netbeansoproj.zip 
Kiran Bhumana-2 wrote:
  

Hello Mithun,
 You can find information on this on open-esb wiki pages (BPEL-SE). 
FYReference, 
http://wiki.open-esb.java.net/Wiki.jsp?page=UsingDynamicPartnerLinks.

thanks,
Kiran.

mithun_jhonny wrote:
    

Hi,

I need to call web services dynamically from BPEL (I want to give the
location of web service as inputs)

i.e I need to make use of dynamic partner link . Can any one point me to
any
tutorial for that ? 

thanks,
Mithun



  
      

-- 
Kiran Bhumana
Open ESB Community (http://open-esb.org)



    

[mithun_jhonny]

thanks for the reply Kiran. It did help.
I have a question . I understand that in order for the dynamic partner link to work the partner links must have the same portname, targetnamespace etc and also the partner links must be mapped to a EPR in mapper.

Is it possible to have to 2 partner links mapped in the mapper ? and does the netbeans differentiate this  ?


thanks,
Mithun

Kiran Bhumana-2 wrote:

Hello Mithun,

I looked at your project. What you can change is the address, not the
service and port. We are working on improving HTTP BC so that you can
change the service and port as well. But for now, take it that the
HTTP-BC needs to know that the service and port that you are providing
so that it can format the message according to the right binding.

What you did is very good, except that you didn't need the echo3WSDL at
all! Your echo and echo3 WSDLs are exactly the same. Since echo WSDL is
already deployed in BC, by changing just the address it should work.
I couldn't reach http://10.60.141.107:9009/echo3/echo3Service, hence I
think even after the changes it failed on my machine.

Attached is a project that I worked on to provide as a sample in NB, so
users can reuse these BPELs to construct the Dynamic endpoint structure.
Let me know if that helps in any way.

Thanks,
Kiran B.

mithun_jhonny wrote:
> Hi,
>
> I tried the example given there . But when I pass a different web service
> address (other than the one already used in on the main BPEL ). It gives me
> a error saying
>
>    Caused by: BPJBI-6019:unable to resolve the service endpoint dynamically
> for the document fragment
>
> Can anyone please help me with this . Please find the files attached.
>  
>
> thanks,
> Mithun
>
>
> http://www.nabble.com/file/p18437106/netbeansoproj.zip netbeansoproj.zip
> Kiran Bhumana-2 wrote:
>  
>> Hello Mithun,
>>  You can find information on this on open-esb wiki pages (BPEL-SE).
>> FYReference,
>> http://wiki.open-esb.java.net/Wiki.jsp?page=UsingDynamicPartnerLinks.
>>
>> thanks,
>> Kiran.
>>
>> mithun_jhonny wrote:
>>    
>>> Hi,
>>>
>>> I need to call web services dynamically from BPEL (I want to give the
>>> location of web service as inputs)
>>>
>>> i.e I need to make use of dynamic partner link . Can any one point me to
>>> any
>>> tutorial for that ?
>>>
>>> thanks,
>>> Mithun
>>>
>>>
>>>
>>>  
>>>      
>> --
>> Kiran Bhumana
>> Open ESB Community (http://open-esb.org)
>>
>>
>>
>>    
>
>  

 

[Kiran Bhumana-2]

Mithun,
 Glad it worked. I don't quite understand your question below. Can you please elaborate?

-Kiran B.

mithun_jhonny wrote:

thanks for the reply Kiran. It did help. 
I have a question . I understand that in order for the dynamic partner link
to work the partner links must have the same portname, targetnamespace etc
and also the partner links must be mapped to a EPR in mapper. 

Is it possible to have to 2 partner links mapped in the mapper ? and does
the netbeans differentiate this  ?


thanks,
Mithun 





Kiran Bhumana-2 wrote:
  

Hello Mithun,

I looked at your project. What you can change is the address, not the 
service and port. We are working on improving HTTP BC so that you can 
change the service and port as well. But for now, take it that the 
HTTP-BC needs to know that the service and port that you are providing 
so that it can format the message according to the right binding.

What you did is very good, except that you didn't need the echo3WSDL at 
all! Your echo and echo3 WSDLs are exactly the same. Since echo WSDL is 
already deployed in BC, by changing just the address it should work.
I couldn't reach http://10.60.141.107:9009/echo3/echo3Service, hence I 
think even after the changes it failed on my machine.

Attached is a project that I worked on to provide as a sample in NB, so 
users can reuse these BPELs to construct the Dynamic endpoint structure. 
Let me know if that helps in any way.

Thanks,
Kiran B.

mithun_jhonny wrote:
    

Hi,

I tried the example given there . But when I pass a different web service
address (other than the one already used in on the main BPEL ). It gives
me
a error saying 

   Caused by: BPJBI-6019:unable to resolve the service endpoint
dynamically
for the document fragment 

Can anyone please help me with this . Please find the files attached.
 

thanks,
Mithun


http://www.nabble.com/file/p18437106/netbeansoproj.zip netbeansoproj.zip 
Kiran Bhumana-2 wrote:
  
      

Hello Mithun,
 You can find information on this on open-esb wiki pages (BPEL-SE). 
FYReference, 
http://wiki.open-esb.java.net/Wiki.jsp?page=UsingDynamicPartnerLinks.

thanks,
Kiran.

mithun_jhonny wrote:
    
        

Hi,

I need to call web services dynamically from BPEL (I want to give the
location of web service as inputs)

i.e I need to make use of dynamic partner link . Can any one point me
to
any
tutorial for that ? 

thanks,
Mithun



  
      
          

-- 
Kiran Bhumana
Open ESB Community (http://open-esb.org)



    
        

[mithun_jhonny]

Hi Kiran,

My question is if I have 2 partner links (different service name and portname) which I have to use in the single bpel process dynamically. Can I map the EPR (endpoint-referece) to two partner links in the mapper?

basically I want a way to dynamically identify two different partner links in a bpel process ? Can you please provide me your inputs on the same ?

Mithun



 

Kiran Bhumana-2 wrote:

Mithun,
 Glad it worked. I don't quite understand your question below. Can you
please elaborate?

-Kiran B.

mithun_jhonny wrote:
> thanks for the reply Kiran. It did help.
> I have a question . I understand that in order for the dynamic partner link
> to work the partner links must have the same portname, targetnamespace etc
> and also the partner links must be mapped to a EPR in mapper.
>
> Is it possible to have to 2 partner links mapped in the mapper ? and does
> the netbeans differentiate this  ?
>
>
> thanks,
> Mithun
>
>
>
>
>
> Kiran Bhumana-2 wrote:
>  
>> Hello Mithun,
>>
>> I looked at your project. What you can change is the address, not the
>> service and port. We are working on improving HTTP BC so that you can
>> change the service and port as well. But for now, take it that the
>> HTTP-BC needs to know that the service and port that you are providing
>> so that it can format the message according to the right binding.
>>
>> What you did is very good, except that you didn't need the echo3WSDL at
>> all! Your echo and echo3 WSDLs are exactly the same. Since echo WSDL is
>> already deployed in BC, by changing just the address it should work.
>> I couldn't reach http://10.60.141.107:9009/echo3/echo3Service, hence I
>> think even after the changes it failed on my machine.
>>
>> Attached is a project that I worked on to provide as a sample in NB, so
>> users can reuse these BPELs to construct the Dynamic endpoint structure.
>> Let me know if that helps in any way.
>>
>> Thanks,
>> Kiran B.
>>
>> mithun_jhonny wrote:
>>    
>>> Hi,
>>>
>>> I tried the example given there . But when I pass a different web service
>>> address (other than the one already used in on the main BPEL ). It gives
>>> me
>>> a error saying
>>>
>>>    Caused by: BPJBI-6019:unable to resolve the service endpoint
>>> dynamically
>>> for the document fragment
>>>
>>> Can anyone please help me with this . Please find the files attached.
>>>  
>>>
>>> thanks,
>>> Mithun
>>>
>>>
>>> http://www.nabble.com/file/p18437106/netbeansoproj.zip netbeansoproj.zip
>>> Kiran Bhumana-2 wrote:
>>>  
>>>      
>>>> Hello Mithun,
>>>>  You can find information on this on open-esb wiki pages (BPEL-SE).
>>>> FYReference,
>>>> http://wiki.open-esb.java.net/Wiki.jsp?page=UsingDynamicPartnerLinks.
>>>>
>>>> thanks,
>>>> Kiran.
>>>>
>>>> mithun_jhonny wrote:
>>>>    
>>>>        
>>>>> Hi,
>>>>>
>>>>> I need to call web services dynamically from BPEL (I want to give the
>>>>> location of web service as inputs)
>>>>>
>>>>> i.e I need to make use of dynamic partner link . Can any one point me
>>>>> to
>>>>> any
>>>>> tutorial for that ?
>>>>>
>>>>> thanks,
>>>>> Mithun
>>>>>
>>>>>
>>>>>
>>>>>  
>>>>>      
>>>>>          
>>>> --
>>>> Kiran Bhumana
>>>> Open ESB Community (http://open-esb.org)
>>>>
>>>>
>>>>
>>>>    
>>>>        
>>>  
>>>      
>>  
>>
>>    
>
>  

--
Kiran Bhumana
Open ESB Community (http://open-esb.org)

[Kiran Bhumana-2]

Yes it is possible. Did you check this example?
https://open-jbi-components.dev.java.net/source/browse/open-jbi-components/driver-tests/bpelse/dynamicpartnerlink/dynamicPartnerLinkJBI/

Also be aware that in your case the WSDL needs to be also available by the HTTPBC.

HTH,
Kiran B

mithun_jhonny wrote:

Hi Kiran,

My question is if I have 2 partner links (different service name and
portname) which I have to use in the single bpel process dynamically. Can I
map the EPR (endpoint-referece) to two partner links in the mapper?

basically I want a way to dynamically identify two different partner links
in a bpel process ? Can you please provide me your inputs on the same ?

Mithun



 





Kiran Bhumana-2 wrote:
  

Mithun,
 Glad it worked. I don't quite understand your question below. Can you 
please elaborate?

-Kiran B.

mithun_jhonny wrote:
    

thanks for the reply Kiran. It did help. 
I have a question . I understand that in order for the dynamic partner
link
to work the partner links must have the same portname, targetnamespace
etc
and also the partner links must be mapped to a EPR in mapper. 

Is it possible to have to 2 partner links mapped in the mapper ? and does
the netbeans differentiate this  ?


thanks,
Mithun 





Kiran Bhumana-2 wrote:
  
      

Hello Mithun,

I looked at your project. What you can change is the address, not the 
service and port. We are working on improving HTTP BC so that you can 
change the service and port as well. But for now, take it that the 
HTTP-BC needs to know that the service and port that you are providing 
so that it can format the message according to the right binding.

What you did is very good, except that you didn't need the echo3WSDL at 
all! Your echo and echo3 WSDLs are exactly the same. Since echo WSDL is 
already deployed in BC, by changing just the address it should work.
I couldn't reach http://10.60.141.107:9009/echo3/echo3Service, hence I 
think even after the changes it failed on my machine.

Attached is a project that I worked on to provide as a sample in NB, so 
users can reuse these BPELs to construct the Dynamic endpoint structure. 
Let me know if that helps in any way.

Thanks,
Kiran B.

mithun_jhonny wrote:
    
        

Hi,

I tried the example given there . But when I pass a different web
service
address (other than the one already used in on the main BPEL ). It
gives
me
a error saying 

   Caused by: BPJBI-6019:unable to resolve the service endpoint
dynamically
for the document fragment 

Can anyone please help me with this . Please find the files attached.
 

thanks,
Mithun


http://www.nabble.com/file/p18437106/netbeansoproj.zip
netbeansoproj.zip 
Kiran Bhumana-2 wrote:
  
      
          

Hello Mithun,
 You can find information on this on open-esb wiki pages (BPEL-SE). 
FYReference, 
http://wiki.open-esb.java.net/Wiki.jsp?page=UsingDynamicPartnerLinks.

thanks,
Kiran.

mithun_jhonny wrote:
    
        
            

Hi,

I need to call web services dynamically from BPEL (I want to give the
location of web service as inputs)

i.e I need to make use of dynamic partner link . Can any one point me
to
any
tutorial for that ? 

thanks,
Mithun



  
      
          
              

-- 
Kiran Bhumana
Open ESB Community (http://open-esb.org)



    
        
            

-- 
Kiran Bhumana
Open ESB Community (http://open-esb.org)



    

[jsexton0]

Hello -

I downloaded the attached, loaded it up into my server (fresh install) and ran the test case.  I got a 404.  The output is below.  Did I miss something?  Thanks

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/">
  <SOAP-ENV:Body>
    <SOAP-ENV:Fault>
      <faultcode xmlns="">SOAP-ENV:Server</faultcode>
      <faultstring xmlns="">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 Status-Code 404: Not Found - Not Found&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 xmlns="">sun-bpel-engine</faultactor>
      <detail xmlns="">
        <detailText>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 Status-Code 404: Not Found - Not Found&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://j2ee.netbeans.org/wsdl/PartnerWSDL}PartnerWSDLPortType, operation=PartnerWSDLOperation)
BPCOR-6129:Line Number is 59
BPCOR-6130:Activity Name is Invoke2
   Caused by: HTTP Status-Code 404: Not Found - Not Found</detailText>
      </detail>
    </SOAP-ENV:Fault>
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Kiran Bhumana-2 wrote:

Hello Mithun,

I looked at your project. What you can change is the address, not the
service and port. We are working on improving HTTP BC so that you can
change the service and port as well. But for now, take it that the
HTTP-BC needs to know that the service and port that you are providing
so that it can format the message according to the right binding.

What you did is very good, except that you didn't need the echo3WSDL at
all! Your echo and echo3 WSDLs are exactly the same. Since echo WSDL is
already deployed in BC, by changing just the address it should work.
I couldn't reach http://10.60.141.107:9009/echo3/echo3Service, hence I
think even after the changes it failed on my machine.

Attached is a project that I worked on to provide as a sample in NB, so
users can reuse these BPELs to construct the Dynamic endpoint structure.
Let me know if that helps in any way.

Thanks,
Kiran B.

 

[Kiran Bhumana-2]

Probably your server ports were different from mine. Mine are default values. Error below sort of indicates that HTTP BC was not able to reach the service being called by BPEL's invoke.

-Kiran.

jsexton0 wrote:

Hello -

I downloaded the attached, loaded it up into my server (fresh install) and
ran the test case.  I got a 404.  The output is below.  Did I miss
something?  Thanks

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/
http://schemas.xmlsoap.org/soap/envelope/">
  <SOAP-ENV:Body>
    <SOAP-ENV:Fault>
      <faultcode xmlns="">SOAP-ENV:Server</faultcode>
      <faultstring xmlns="">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 &amp;lt;?xml version=&amp;quot;1.0&amp;quot;
encoding=&amp;quot;UTF-8&amp;quot;?&amp;gt;&amp;lt;jbi:message
xmlns:sxeh=&amp;quot;http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling&amp;quot;
type=&amp;quot;sxeh:faultMessage&amp;quot; version=&amp;quot;1.0&amp;quot;
xmlns:jbi=&amp;quot;http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper&amp;quot;&amp;gt;&amp;lt;jbi:part&amp;gt;HTTP
Status-Code 404: Not Found - Not
Found&amp;lt;/jbi:part&amp;gt;&amp;lt;/jbi:message&amp;gt;. Sending errors
for the pending requests in the process scope before terminating the process
instance</faultstring>
      <faultactor xmlns="">sun-bpel-engine</faultactor>
      <detail xmlns="">
        <detailText>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 &amp;lt;?xml version=&amp;quot;1.0&amp;quot;
encoding=&amp;quot;UTF-8&amp;quot;?&amp;gt;&amp;lt;jbi:message
xmlns:sxeh=&amp;quot;http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling&amp;quot;
type=&amp;quot;sxeh:faultMessage&amp;quot; version=&amp;quot;1.0&amp;quot;
xmlns:jbi=&amp;quot;http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper&amp;quot;&amp;gt;&amp;lt;jbi:part&amp;gt;HTTP
Status-Code 404: Not Found - Not
Found&amp;lt;/jbi:part&amp;gt;&amp;lt;/jbi:message&amp;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://j2ee.netbeans.org/wsdl/PartnerWSDL}PartnerWSDLPortType,
operation=PartnerWSDLOperation)
BPCOR-6129:Line Number is 59
BPCOR-6130:Activity Name is Invoke2
   Caused by: HTTP Status-Code 404: Not Found - Not Found</detailText>
      </detail>
    </SOAP-ENV:Fault>
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>



Kiran Bhumana-2 wrote:
  

Hello Mithun,

I looked at your project. What you can change is the address, not the 
service and port. We are working on improving HTTP BC so that you can 
change the service and port as well. But for now, take it that the 
HTTP-BC needs to know that the service and port that you are providing 
so that it can format the message according to the right binding.

What you did is very good, except that you didn't need the echo3WSDL at 
all! Your echo and echo3 WSDLs are exactly the same. Since echo WSDL is 
already deployed in BC, by changing just the address it should work.
I couldn't reach http://10.60.141.107:9009/echo3/echo3Service, hence I 
think even after the changes it failed on my machine.

Attached is a project that I worked on to provide as a sample in NB, so 
users can reuse these BPELs to construct the Dynamic endpoint structure. 
Let me know if that helps in any way.

Thanks,
Kiran B.

 

    

[jsexton0]

Hello -
It would seem so, but this is a brand new install.  I've changed nothing, other than loading up these projects.  I had been using ServiceMix, but we're switching to OpenESB.  I need dynamic PLs so your example is very interesting to me (using ServiceMix I had done these using the Java client API).

The ports listed in my start messages are as follows:

JBIFW0010: JBI framework ready to accept requests.
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 8080
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 8181
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 4848

The SA deploys without error.  The address line in the dynamic test input is:

<address>http://localhost:8080/PartnerWSDLService/DynamicPartner</address>

When I use a browser, http://localhost:8080/PartnerWSDLService/DynamicPartner yields a 404 error.
Is there a diagnostic that will list the PL URIs a running server thinks are available?

Thanks

Kiran Bhumana-2 wrote:

Probably your server ports were different from mine. Mine are default
values. Error below sort of indicates that HTTP BC was not able to reach
the service being called by BPEL's invoke.

-Kiran.

jsexton0 wrote:
> Hello -
>
> I downloaded the attached, loaded it up into my server (fresh install) and
> ran the test case.  I got a 404.  The output is below.  Did I miss
> something?  Thanks
>
> <?xml version="1.0" encoding="UTF-8"?>
> <SOAP-ENV:Envelope
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/
> http://schemas.xmlsoap.org/soap/envelope/">
>   <SOAP-ENV:Body>
>     <SOAP-ENV:Fault>
>       <faultcode xmlns="">SOAP-ENV:Server</faultcode>
>       <faultstring xmlns="">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
> Status-Code 404: Not Found - Not
> Found&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 xmlns="">sun-bpel-engine</faultactor>
>       <detail xmlns="">
>         <detailText>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
> Status-Code 404: Not Found - Not
> Found&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://j2ee.netbeans.org/wsdl/PartnerWSDL}PartnerWSDLPortType,
> operation=PartnerWSDLOperation)
> BPCOR-6129:Line Number is 59
> BPCOR-6130:Activity Name is Invoke2
>    Caused by: HTTP Status-Code 404: Not Found - Not Found</detailText>
>       </detail>
>     </SOAP-ENV:Fault>
>   </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
>
>
>
> Kiran Bhumana-2 wrote:
>  
>> Hello Mithun,
>>
>> I looked at your project. What you can change is the address, not the
>> service and port. We are working on improving HTTP BC so that you can
>> change the service and port as well. But for now, take it that the
>> HTTP-BC needs to know that the service and port that you are providing
>> so that it can format the message according to the right binding.
>>
>> What you did is very good, except that you didn't need the echo3WSDL at
>> all! Your echo and echo3 WSDLs are exactly the same. Since echo WSDL is
>> already deployed in BC, by changing just the address it should work.
>> I couldn't reach http://10.60.141.107:9009/echo3/echo3Service, hence I
>> think even after the changes it failed on my machine.
>>
>> Attached is a project that I worked on to provide as a sample in NB, so
>> users can reuse these BPELs to construct the Dynamic endpoint structure.
>> Let me know if that helps in any way.
>>
>> Thanks,
>> Kiran B.
>>
>>  
>>
>>    
>
>  

--
Kiran Bhumana
Open ESB Community (http://open-esb.org)

[jsexton0]

Hi, again -

I just started over from the top and undeployed, re-opened and re-built all the projects, re-deployed, and it seems to have worked!

Thanks


Hello -
It would seem so, but this is a brand new install.  I've changed nothing, other than loading up these projects.  I had been using ServiceMix, but we're switching to OpenESB.  I need dynamic PLs so your example is very interesting to me (using ServiceMix I had done these using the Java client API).

The ports listed in my start messages are as follows:

JBIFW0010: JBI framework ready to accept requests.
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 8080
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 8181
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 4848

The SA deploys without error.  The address line in the dynamic test input is:

<address>http://localhost:8080/PartnerWSDLService/DynamicPartner</address>

When I use a browser, http://localhost:8080/PartnerWSDLService/DynamicPartner yields a 404 error.
Is there a diagnostic that will list the PL URIs a running server thinks are available?

Thanks

Kiran Bhumana-2 wrote:

Probably your server ports were different from mine. Mine are default
values. Error below sort of indicates that HTTP BC was not able to reach
the service being called by BPEL's invoke.

-Kiran.

jsexton0 wrote:
> Hello -
>
> I downloaded the attached, loaded it up into my server (fresh install) and
> ran the test case.  I got a 404.  The output is below.  Did I miss
> something?  Thanks
>
> <?xml version="1.0" encoding="UTF-8"?>
> <SOAP-ENV:Envelope
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/
> http://schemas.xmlsoap.org/soap/envelope/">
>   <SOAP-ENV:Body>
>     <SOAP-ENV:Fault>
>       <faultcode xmlns="">SOAP-ENV:Server</faultcode>
>       <faultstring xmlns="">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
> Status-Code 404: Not Found - Not
> Found&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 xmlns="">sun-bpel-engine</faultactor>
>       <detail xmlns="">
>         <detailText>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
> Status-Code 404: Not Found - Not
> Found&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://j2ee.netbeans.org/wsdl/PartnerWSDL}PartnerWSDLPortType,
> operation=PartnerWSDLOperation)
> BPCOR-6129:Line Number is 59
> BPCOR-6130:Activity Name is Invoke2
>    Caused by: HTTP Status-Code 404: Not Found - Not Found</detailText>
>       </detail>
>     </SOAP-ENV:Fault>
>   </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
>
>
>
> Kiran Bhumana-2 wrote:
>  
>> Hello Mithun,
>>
>> I looked at your project. What you can change is the address, not the
>> service and port. We are working on improving HTTP BC so that you can
>> change the service and port as well. But for now, take it that the
>> HTTP-BC needs to know that the service and port that you are providing
>> so that it can format the message according to the right binding.
>>
>> What you did is very good, except that you didn't need the echo3WSDL at
>> all! Your echo and echo3 WSDLs are exactly the same. Since echo WSDL is
>> already deployed in BC, by changing just the address it should work.
>> I couldn't reach http://10.60.141.107:9009/echo3/echo3Service, hence I
>> think even after the changes it failed on my machine.
>>
>> Attached is a project that I worked on to provide as a sample in NB, so
>> users can reuse these BPELs to construct the Dynamic endpoint structure.
>> Let me know if that helps in any way.
>>
>> Thanks,
>> Kiran B.
>>
>>  
>>
>>    
>
>  

--
Kiran Bhumana
Open ESB Community (http://open-esb.org)

[Kiran Bhumana-2]

Did you deploy all the projects? CompApp and the EJB project?
I don't know how to get a list of URIs that a server is hosting, but the following should provide the WSDL when you enter it in your browser.

http://localhost:8080/PartnerWSDLService/DynamicPartner?wsdl

If you didn't get the WSDL by typing the above, then your server is not hosting it. The address tag doesn't change, no need for the ?wsdl.

-Kiran.

jsexton0 wrote:

Hello -
It would seem so, but this is a brand new install.  I've changed nothing,
other than loading up these projects.  I had been using ServiceMix, but
we're switching to OpenESB.  I need dynamic PLs so your example is very
interesting to me (using ServiceMix I had done these using the Java client
API).

The ports listed in my start messages are as follows:

JBIFW0010: JBI framework ready to accept requests.
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 8080
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 8181
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 4848

The SA deploys without error.  The address line in the dynamic test input
is:

<address>http://localhost:8080/PartnerWSDLService/DynamicPartner</address>

When I use a browser,
http://localhost:8080/PartnerWSDLService/DynamicPartner yields a 404 error. 
Is there a diagnostic that will list the PL URIs a running server thinks are
available?

Thanks


Kiran Bhumana-2 wrote:
  

Probably your server ports were different from mine. Mine are default 
values. Error below sort of indicates that HTTP BC was not able to reach 
the service being called by BPEL's invoke.

-Kiran.

jsexton0 wrote:
    

Hello -

I downloaded the attached, loaded it up into my server (fresh install)
and
ran the test case.  I got a 404.  The output is below.  Did I miss
something?  Thanks

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/
http://schemas.xmlsoap.org/soap/envelope/">
  <SOAP-ENV:Body>
    <SOAP-ENV:Fault>
      <faultcode xmlns="">SOAP-ENV:Server</faultcode>
      <faultstring xmlns="">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 &amp;lt;?xml version=&amp;quot;1.0&amp;quot;
encoding=&amp;quot;UTF-8&amp;quot;?&amp;gt;&amp;lt;jbi:message
xmlns:sxeh=&amp;quot;http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling&amp;quot;
type=&amp;quot;sxeh:faultMessage&amp;quot;
version=&amp;quot;1.0&amp;quot;
xmlns:jbi=&amp;quot;http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper&amp;quot;&amp;gt;&amp;lt;jbi:part&amp;gt;HTTP
Status-Code 404: Not Found - Not
Found&amp;lt;/jbi:part&amp;gt;&amp;lt;/jbi:message&amp;gt;. Sending
errors
for the pending requests in the process scope before terminating the
process
instance</faultstring>
      <faultactor xmlns="">sun-bpel-engine</faultactor>
      <detail xmlns="">
        <detailText>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 &amp;lt;?xml version=&amp;quot;1.0&amp;quot;
encoding=&amp;quot;UTF-8&amp;quot;?&amp;gt;&amp;lt;jbi:message
xmlns:sxeh=&amp;quot;http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling&amp;quot;
type=&amp;quot;sxeh:faultMessage&amp;quot;
version=&amp;quot;1.0&amp;quot;
xmlns:jbi=&amp;quot;http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper&amp;quot;&amp;gt;&amp;lt;jbi:part&amp;gt;HTTP
Status-Code 404: Not Found - Not
Found&amp;lt;/jbi:part&amp;gt;&amp;lt;/jbi:message&amp;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://j2ee.netbeans.org/wsdl/PartnerWSDL}PartnerWSDLPortType,
operation=PartnerWSDLOperation)
BPCOR-6129:Line Number is 59
BPCOR-6130:Activity Name is Invoke2
   Caused by: HTTP Status-Code 404: Not Found - Not Found</detailText>
      </detail>
    </SOAP-ENV:Fault>
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>



Kiran Bhumana-2 wrote:
  
      

Hello Mithun,

I looked at your project. What you can change is the address, not the 
service and port. We are working on improving HTTP BC so that you can 
change the service and port as well. But for now, take it that the 
HTTP-BC needs to know that the service and port that you are providing 
so that it can format the message according to the right binding.

What you did is very good, except that you didn't need the echo3WSDL at 
all! Your echo and echo3 WSDLs are exactly the same. Since echo WSDL is 
already deployed in BC, by changing just the address it should work.
I couldn't reach http://10.60.141.107:9009/echo3/echo3Service, hence I 
think even after the changes it failed on my machine.

Attached is a project that I worked on to provide as a sample in NB, so 
users can reuse these BPELs to construct the Dynamic endpoint structure. 
Let me know if that helps in any way.

Thanks,
Kiran B.

 

    
        

-- 
Kiran Bhumana
Open ESB Community (http://open-esb.org)