WebSphere WebSphere Application Server Network Deployment, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Tuning SIBus Web services

You can use the administrative console or a Jacl script to tune performance settings for the Web services enablement of the service integration bus (SIBus).

Why and when to perform this task

SIBus Web services dynamically selects 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 SIBus Web services functionality. This fast-path route through the bus is used if the following criteria are met:

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.

To improve the performance of SIBus Web services you can tune the following parameters:

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 SIBus Web services, complete one of the following two steps: If you have mediations that act on SOAP headers, also complete the following step:

Related concepts
Guidance for tuning mediations for performance

Task topic

Terms of Use | Feedback

Last updated: 15 Mar 2007
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\tasks\tjw_tune.html

© Copyright IBM Corporation 2004, 2007. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)