| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| SOA implmentation using WMB v6.1 |
« View previous topic :: View next topic » |
| Author |
Message
|
| bprasana |
 Posted: Thu Apr 08, 2010 12:49 pm Post subject: SOA implmentation using WMB v6.1 |
 |
|
Disciple
Joined: 18 Apr 2005
Posts: 179
|
If I were to expose some of my WMB implementation(not existing but new) as services, what steps do i need to take.
Suppose I have identified services and operations, which look something like this:
1. CustomerInquiryService
1.1 searchCustomerByNameAndAddress
1.2 searchCustomerById
1.3 searchcustomerByxyZ
2.CustomerManagementService
2.1 UpdateCustomer
2.2 DeleteCustomer
2.3 abcCustomer
3..4..5..
If I were to transfer this to WMB language,
1 is a WebService, so I use SOAP node to create a WMB main Flow. And 1.x becomes probably a function/operation and use subflow or just another node in the main service
similarly,
2 is a MQ Serivce,(transaction managed) , so I create a WMB main flow for it and 2.x as individual functions/procedures
is much approach correct, Or is there a better way of doing it?
How does individual operation gets invoked inside a single Service? Does Soap header contain operation name so that i can route it to correct operation, or should I implement this in payload.?
thanks
bprasana |
|
| Back to top |
|
 |
| munnster |
| Posted: Thu Apr 08, 2010 7:28 pm Post subject: |
|
|
Newbie
Joined: 10 Mar 2010
Posts: 5
|
That's a good approach for new stuff.
You should look at the SOAP samples, and also look at what is generated if you drag & drop WSDL into a message flow.
For document literal WSDL (which is what you should use) the top level element in the SOAP Body has to be different for every operation, so it's easy to determine the operation from the message payload.
You can use the same pattern for XML over MQ style services. So in a non-SOAP-wrapped MQ service, the document root can be used to identify the operation. This means that you can have a simple, consistent pattern to expose the same service as SOAP/HTTP, XML/MQ or both. |
|
| Back to top |
|
|
| bprasana |
| Posted: Fri Apr 09, 2010 3:29 pm Post subject: Ws-Security |
|
|
Disciple
Joined: 18 Apr 2005
Posts: 179
|
So, How do i implement the Webservices Security on top of this?
We are thinking of username token.
Do I need to include that as part of the WSDL header? or SOAP header? |
|
| Back to top |
|
|
| goffinf |
| Posted: Wed Apr 14, 2010 3:10 pm Post subject: Re: Ws-Security |
|
|
Chevalier
Joined: 05 Nov 2005
Posts: 401
|
| bprasana wrote: |
So, How do i implement the Webservices Security on top of this?
We are thinking of username token.
Do I need to include that as part of the WSDL header? or SOAP header? |
WS-Security is a SOAP header, but can appear in your WSDL under the <binding> section for <input> and/or <output>.
AFAIK Broker doesn't automatically consume a WSDL constructed this way. See 'Policy Sets' in the docs.
Fraser. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
