Hi Bharathi,
In the riftsaw.sar/bpel.properties file if you set the following
properties to true is will be doing runtime lookups of bpel endpoints:
# if set to true will self-register BPEL endpoints upon deployment to a
UDDI.
# this uses the juddi-client-3.0.x and the uddi client config can be set
in the uddi.xml
# file
bpel.uddi.registration=true
# if set to true will lookup BPEL endpoints in a UDDI Registry.
# this uses the juddi-client-3.0.x and the uddi client config can be set
in the uddi.xml
# file
bpel.uddi.lookup=true
You should try the Dynamic Partner quickstart, both with the default
settings as well as setting the above mentioned properties to 'true'. If
this works then you are halfway there.
The next step is that you want to lookup an BPEL endpoint yourself in
the registry?
Cheers,
--Kurt
On 3/5/12 6:41 AM, [email protected] wrote:
Hi Kurt,
Sorry for disturbing you. Because I don’t have any other options so
please help me.
Regards,
Bharathi S.
*From:*S, Bharathi (Cognizant)
*Sent:* Friday, March 02, 2012 9:40 AM
*To:* 'Kurt T Stam'
*Cc:* [email protected]; [email protected]
*Subject:* RE: Need you help to read service url from jboss jUDDI from
BPEL or ESB
Hi Kurt,
Thanks for your reply. I have already placed in jboss rifsaw developer
forum,but I did not get much info.
Could you please help me for the below mail.
I am using JBoss SOA Suite 5.2, with that riftsaw is build-in. if you
explain the step by step approach to implement the dynamic lookup from
bpel process is very useful.
Because past one month I am trying the same. Now I am in critical
situation.
Kindly help me.
Regards,
Bharahti S.
Note:
I am very new to this jboss components. So please help me.
*From:*Kurt T Stam [mailto:[email protected]]
*Sent:* Thursday, March 01, 2012 9:35 PM
*To:* S, Bharathi (Cognizant)
*Cc:* [email protected]; [email protected]
*Subject:* Re: Need you help to read service url from jboss jUDDI from
BPEL or ESB
Hi Bharathi,
The jUDDI user forum is probably the right place for this discussion.
What version of RiftSaw are you using? If it is recent you can turn on
the 'dynamic lookup' feature, which I think is what you mention you
are using. If so, the BPEL process will lookup the bindings in jUDDI
already, and -if found- use this information by substituting it in the
WSDL for the EndPoint info. I worked on this code, but I'm sorry that
it's lacking full documentation (on my todo list). Anyway, if I
remember correctly it only works looking up EndPoints on other BPEL
processeses. If you want it to lookup regular webservices you need to
make sure they are registered in UDDI, you can use the UDDI
annotations for that.
Please sign up for the juddi user list if you haven't already and lets
see if we can get you going.
Cheers,
--Kurt
On 3/1/12 7:21 AM, [email protected]
<mailto:[email protected]> wrote:
Hi All,
I have take your ids from the below link,
http://mail-archives.apache.org/mod_mbox/juddi-user/201103.mbox/%[email protected]%3E
Sorry for disturbing you all.
I am looking some more information in jUDDI and i will exlpain below
what i am looking for in jUDDI,
I am using riftsaw bpel process. In that i have seen , they have
mentioned one feature like below,
· UDDI registration of BPEL endpoints, and Runtime UDDI Endpoint
lookup as preview
feature.
So what i am looking is i wand to read the service url info from jUDDI
from BPEL process or through the jboss ESB.
I am trying to do dynamic partnerlink using jUDDI.So please let me
know if you guys knew any other way to achive this.
Kindly help me how to do this.
Regards,
Bharathi S.
This e-mail and any files transmitted with it are for the sole use of the
intended recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient(s), please reply to the sender and
destroy all copies of the original message. Any unauthorized review, use,
disclosure, dissemination, forwarding, printing or copying of this email,
and/or any action taken in reliance on the contents of this e-mail is strictly
prohibited and may be unlawful.
This e-mail and any files transmitted with it are for the sole use of the
intended recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient(s), please reply to the sender and
destroy all copies of the original message. Any unauthorized review, use,
disclosure, dissemination, forwarding, printing or copying of this email,
and/or any action taken in reliance on the contents of this e-mail is strictly
prohibited and may be unlawful.
