Draft comment: This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15
The static service gateway provides a single access point for many service requesters and
service providers.
The available service types are static and cannot be changed after the module has been deployed
to the runtime. It is possible to override the endpoint that the service exposes by using a service
registry or database. The benefit of using this gateway pattern, is that the message body can be
changed easily within the module. The static service gateway pattern can be used with either HTTP,
JMS, MQ or web services. Figure 1 shows the common pattern
used for a static service gateway. Figure 1. Static service gateway pattern
To create a web service client, you retrieve the WSDL file for the service provider, and pass it
into the web service tool to generate a client stub. For a static service gateway the creation of
this WSDL file is a manual process, where you must download the target service provider WSDL,
replace any policy information with that attached to the service gateway export and then override
the endpoint to that of the service gateway.
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15