Chapter 8. Router solutions using Web Services Gateway 165
For example, if you use the clustering feature of WebSphere Application Server
for to enhance the Web Services Gateway performance and availability, take
similar measures for the filter application.
Don’t create filters that do a lot of tasks. Instead, create multiple filters that each
perform one simple task (for example, logging, transforming content, routing,
etc.). Then, associate all the filters to the service you need. This facilitates the
development, reduces the complexity of the filters, and promotes the reuse.
8.5 System design overview
After considering the design guidelines, ITSO Electronics decided to implement
and test the solution in the following three stages.
8.5.1 Stage 1: Basic integration
In the first stage, the Retail and Wholesale departments are all internal to ITSO
Electronics. The Retail system is aware of which Wholesale department is
supplying each part and codes the request appropriately. The Router provides
transport protocol conversion and simple logging. It also provides a layer of
abstraction between the systems that allows the Wholesale services to change
or move without affecting the Retail systems.
The solution using WebSphere Web Services Gateway in this stage is shown in
Figure 8-10.
Figure 8-10 Web Services Gateway implementation, stage 1
Wholesale1
Wholesale2
SOAP/
HTTP
SOAP/
JMS
Web Services Gateway (Router)
Retail
Service:
InventoryWholesale1
SOAP/HTTP
Channel 1
UDDI Registry
WSDL
WSDL
Service:
InventoryWholesale2
Target
Service
Target
Service
2
1
3
4
SOAP/
HTTP
5
6