29.01.2013 Views

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

These intermediary nodes might handle quality of service and infrastructure<br />

functions that are non-application specific. Examples include message logging,<br />

routing, prioritization, and security. In general, intermediaries should not alter the<br />

meaning of the message body.<br />

A typical situation where you need to use intermediary SOAP nodes is where you<br />

have an existing internal Web service implementation within your enterprise that<br />

you now want to expose externally. There might be new requirements associated<br />

with requests originating from outside of your organization, such as additional<br />

interoperability requirements, increased security requirements, auditability of<br />

requests, or contractual service-level agreements. These requirements can be<br />

implemented using an intermediary SOAP node, or a Web service gateway.<br />

Web service gateways<br />

A Web service gateway is a middleware component that bridges the gap between<br />

Internet and intranet environments during Web service invocations. It can be<br />

used internally to provide the SOAP node functions as described previously. It<br />

can also be used at the network boundary of the organization. Regardless of<br />

where it is placed, it can provide some or all of the following functions:<br />

► Automatic publishing of WSDL files to an external UDDI or WSIL registry<br />

► Automatic protocol/transport mappings<br />

► Security functions<br />

► Mediation of message structure<br />

► Proxy server for Web service communications through a firewall<br />

► Auditing of SOAP messages<br />

► Operational management and reporting of published interfaces<br />

► Web service threat detection and defense<br />

11.5 Support for Web services in <strong>WebSphere</strong><br />

<strong>Application</strong> <strong>Server</strong><br />

<strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> <strong>V7.0</strong> implements the Java EE 5 and Java SE 6<br />

standards, and therefore it provides support for SOAP and for XML. The support<br />

for Web services in <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> can also be combined with<br />

the capabilities of an Enterprise Service Bus (ESB) product such as <strong>WebSphere</strong><br />

Enterprise Service Bus or <strong>WebSphere</strong> Message Broker.<br />

This section addresses how <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> <strong>V7.0</strong> supports a<br />

Web services architecture.<br />

Chapter 11. Web services 371

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!