You can use the administrative console or a Jacl script
to tune performance settings for the Web services enablement of the
service integration bus.
About this task
Bus-enabled Web services dynamically select an optimized
route through the code where possible.
If you
migrate Web services from the WebSphere® Application
Server Version 5 Web services gateway, and you do not use mediations
to support previous Gateway filter applications, then your messages
avoid being routed through the internal infrastructure that enables
additional bus-enabled Web services functionality. This fast-path
route through the bus is used if the following criteria are met:
- The inbound port and outbound port for the service are on the
same server.
- There are no mediations on the path from the inbound port to the
outbound port.
Further optimizations can be made,
if your configuration meets the previous two criteria, and also meets
the following criteria:
- The inbound template WSDL URI is the same location as the Outbound
Target Service WSDL location URI.
- The inbound service template WSDL service name matches the outbound
WSDL service name.
- The inbound service template port name matches the outbound WSDL
port name.
- The mapping of the namespaces is disabled (that is, you have set
the inbound service property com.ibm.websphere.wsgw.mapSoapBodyNamespace to false).
- Operation-level security is not enabled on the outbound service.
If your Web services use the fast-path route, you need
not tune mediations or the service integration bus. However it is
good practise to do so, because a typical environment will have at
least one non-fast-path (for example, mediated) service.
If you have mediations that act on SOAP headers, you can
improve performance by inserting the associated header schemas (.xsd files)
into the SDO repository.
To tune bus-enabled Web services, complete
one of the following two steps:
If you have mediations that act on SOAP headers, also complete
the following step: