| Author |
Message
|
| ntwmb |
 Posted: Wed May 27, 2009 3:04 am Post subject: Message broker web/application server |
 |
|
Apprentice
Joined: 18 Sep 2008
Posts: 34
|
Hi
Will the broker runtime defaultly have web server or application server to deploy the java code developed in toolkit?
Any ideas?
Thanks.. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed May 27, 2009 3:11 am Post subject: Re: Message broker web/application server |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ntwmb wrote: |
Will the broker runtime defaultly have web server or application server to deploy the java code developed in toolkit?
|
If the java code is running inside a Java Compute node, the broker will deal with it.
If you've built a flow so as to expose this code as a web service (e.g. an HTTPInput node) the broker will deal with it.
After that, it won't. Generally speaking.
What would the broker be doing with app server functionality? 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ntwmb |
| Posted: Wed May 27, 2009 3:18 am Post subject: |
|
|
Apprentice
Joined: 18 Sep 2008
Posts: 34
|
Hi Vitor
Many Thanks for your reply.
I need to develop WSDL in toolkit and I need to provide this wsdl copy to other application to connect to message broker, which would send SOAP messages using this WSDL.
I can create WSDL manually in toolkit, but I need to publish it to server, this is the reason I asked about app server in broker runtime. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed May 27, 2009 3:34 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ntwmb wrote: |
| I need to develop WSDL in toolkit and I need to provide this wsdl copy to other application to connect to message broker, which would send SOAP messages using this WSDL. |
Fair point.
| ntwmb wrote: |
| I can create WSDL manually in toolkit, but I need to publish it to server, this is the reason I asked about app server in broker runtime. |
Again, fair point. AFAIK (and it's not that far) WMB doesn't provide WSRR facilities for WSDL. So you'd need to publish it elsewhere.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ntwmb |
| Posted: Wed May 27, 2009 4:37 am Post subject: |
|
|
Apprentice
Joined: 18 Sep 2008
Posts: 34
|
Hi Vitor
It is given in message broker help contents, that webservices can be published to UDDI in toolkit.
What I want to do is create sample WSDL, and provide it to the other application team.
For this, I have created WSDL manually, I'm confused how to proceed from here. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed May 27, 2009 4:46 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
By "publish it to a server", do you mean "Make it available via HTTP from the broker with a ?wsdl in the URL"?
Broker doesn't do that right now - look for previous posts from mgk on the subject of ?wsdl - but you can export the WSDL from the Toolkit and do anything you want with it, and in theory you can even dig into the internal HTTP listener in broker and mangle the config in unsupported ways so that you can drop the WSDL file onto the broker file system.
You likely want to do anything other than that last one, though. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed May 27, 2009 4:49 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ntwmb wrote: |
| It is given in message broker help contents, that webservices can be published to UDDI in toolkit. |
There's a difference between Toolkit publishing to UDDI (which I didn't know it could do & would welcome the link) and broker providing UDDI.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed May 27, 2009 4:52 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ntwmb wrote: |
| What I want to do is create sample WSDL, and provide it to the other application team. |
There's always email.... 
(Web services not exactly my thing. When I've built web services I've not has WSDL in an external respository, UDDI, WSRR, etc, etc)
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ntwmb |
| Posted: Wed May 27, 2009 5:26 am Post subject: |
|
|
Apprentice
Joined: 18 Sep 2008
Posts: 34
|
Hi mqjeff/Vitor
Your answers are really helpful.
I'm using various terms - developing webservices, publish to server;
because as a Java developer we would develop webservices, deploy it to app server in WSAD(Websphere application developer)
(I used same terminology in broker also, which might not suit the correct termilnology I should use in broker.)
My understanding was develop webservices in broker toolkit using java code(perspective), deploy webservcies to app server in broker, create wsdl, give wsdl copy to other team. I strongly believe that wsdl should reside in a namespace where we can see the wsdl by typing the URL in browser. (If app server is not available then namespace will not come into picture?)
Can you please suggest any possible approach I can develop WSDL in toolkit? |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed May 27, 2009 5:30 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ntwmb wrote: |
| Can you please suggest any possible approach I can develop WSDL in toolkit? |
Please see above my comments on my level of experience with web services, and read my comments in that light.
Where I've developed web services within WMB, I've used Toolkit to import the WSDL, incorporated the details into a flow (using namespaces as appropriate) and using ESQL because I don't do Java. This seems to work fine. The same WSDL is used by the service comsumers to do their thing (note use of highly technical term ).
Other methods are undoubtably available and could well be better.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ntwmb |
| Posted: Wed May 27, 2009 5:36 am Post subject: |
|
|
Apprentice
Joined: 18 Sep 2008
Posts: 34
|
Hi Vitor
I used the same approach as told by you for my other projects, where I got WSDL from other team which I have used in my message flow for SOAP nodes and written ESQL to process/transform the messages. Till now I never used Java in broker toolkit.(I'm from Java background, can work on both ESQL and Java)
If I have the WSDL with me, then I can easily go for this approach. But the problem here is I need to provide the WSDL to other team, and use the same for SOAP nodes in toolkit... |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed May 27, 2009 5:41 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ntwmb wrote: |
| But the problem here is I need to provide the WSDL to other team, and use the same for SOAP nodes in toolkit... |
I'm not sure I see your problem. Find out how the other team want the WSDL provided/published and give it to them would be my policy, which is so obvious you must have thought of it and proves I don't get the issue!
If you could rephrase....?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ntwmb |
| Posted: Wed May 27, 2009 6:16 am Post subject: |
|
|
Apprentice
Joined: 18 Sep 2008
Posts: 34
|
Hi Vitor
Sorry, if my query is not in an explainable format.
The application that has to connect to message broker will send SOAP messages, by using a WSDL copy installed in their system. Message broker team has to create the wsdl and provide the same to them.
But to create this wsdl, we should know the targetnamespace, porttype, binding operation details. So I can't create wsdl manually in toolkit to provide just the WSDL.
I think I need to write code to create webservices thereby wsdl, so that wsdl can be accessible using URL, We can use same WSDL in soapnodes, after attaching this wsdl to soapinput node, we can provide (HTTP Transport tab) URL to other application to send soap messages.
Is this data helpful to understand the problem? |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed May 27, 2009 6:26 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ntwmb wrote: |
| Sorry, if my query is not in an explainable format. |
I'm sorry I'm being dimmer than usual. 
| ntwmb wrote: |
| The application that has to connect to message broker will send SOAP messages, by using a WSDL copy installed in their system. Message broker team has to create the wsdl and provide the same to them. |
Got that.
| ntwmb wrote: |
| But to create this wsdl, we should know the targetnamespace, porttype, binding operation details. So I can't create wsdl manually in toolkit to provide just the WSDL. |
No? Why?
| ntwmb wrote: |
| I think I need to write code to create webservices thereby wsdl, so that wsdl can be accessible using URL, We can use same WSDL in soapnodes, after attaching this wsdl to soapinput node, we can provide (HTTP Transport tab) URL to other application to send soap messages. |
Obviously.
| ntwmb wrote: |
| Is this data helpful to understand the problem? |
Not really. It all seems straightforward, apart from the point I highlighted above. It's very likely I can't see the wood for all these trees.....
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ntwmb |
| Posted: Wed May 27, 2009 6:52 am Post subject: |
|
|
Apprentice
Joined: 18 Sep 2008
Posts: 34
|
Well, if I have to develop the code and deploy it, I need to know the server details to which I can deploy the code in broker. (which is my main query)
Thanks for your answers Vitor. |
|
| Back to top |
|
|
|
|
