Chapter 8. Router solutions using Web Services Gateway 215
8.7.3 Standards compliance
By utilizing open standards, Web services can, in theory, enable any two
software components to communicate regardless of what technologies or
platforms are used to create or deploy them. Interoperability across
heterogeneous platforms is one of the key value propositions of Web services.
WS-I Profile
The Web Services Interoperability Organization is an open industry effort
chartered to promote Web services interoperability across platforms,
applications, and programming languages. Web services for J2EE intends to
conform to the WS-I Basic Profile 1.0, and should interoperate with any other
vendor conforming to this specification.
WS-Security
You can configure the gateway for secure transmission of SOAP messages
using tokens, keys, signatures and encryption in accordance with the Web
Services Security (WS-Security) draft recommendation.
Interoperability through firewalls
The Web Services Gateway is entirely based on Web services, which when
implemented using HTTP as SOAP transport protocol, are totally firewall friendly.
8.7.4 Autonomic
Log and trace facilities are important for fault monitoring and isolation.
WebSphere Application Server provides a number of log files. JVM logs are
located in the <WAS_HOME>/logs/<applicationServerName> directory, and by
default are named SystemOut.log and SystemErr.log.
The Diagnostic Trace Service can be used to enable tracing of application server
components. The following trace specification can be used when diagnosing
Web Services Gateway problems:
com.ibm.wsgw.*=all=enabled:
org.apache.wsif.*=all=enabled:
com.ibm.ws.webservices.*=all=enabled
Note: In certain circumstances, the gateway also creates and sends its own
messages (for example for WSDL retrieval). In these cases, the gateway
always supplies its own credentials to the authenticating proxy. So even if you
enable proxy authentication and specify requester-supplied credentials, you
must still supply credentials for the gateway.