This topic discusses how to plan your use of Web
services that are developed and implemented based on a variety of Java programming
models.
Before you begin
Read the Web
services scenario: Overview which tells the story of a fictional online
garden supply retailer named Plants by WebSphere and how this retailer incorporated
the Web services concept. You can also review the Samples Gallery for Web services samples. These Samples
demonstrate Enterprise JavaBeans (EJBs) and JavaBeans components that are
available as Web services.
newfeatThe
Feature Pack for Web Services provides Samples that demonstrate JAX-WS-based
Web services using many of the new functions and standards supported in this
Feature Pack. The Feature Pack for Web Services Samples are available with
installation of the Feature Pack. The Samples demonstrate the simple message
exchange patterns using both synchronous and asynchronous invocation of Web
services in SOAP 1.1 and SOAP 1.2 environments. The Samples are composed with
Web service standards such as WS-Addressing (WS-A) , WS-Reliable Messaging
(WS-RM), and WS-Secure Conversation (WS-SC), and enable you to perform a broad
range of interoperability tests. The samples demonstrate the use of JavaBeans
artifacts and static service endpoints and proxy-based clients. Additionally,
a Sample is provided that demonstrates Message Transmission Optimization Mechanism
(MTOM). To learn more about these Samples, see the Samples readme located
in the app_server_root/samples/lib/WebServicesSamples directory.
Read about installing the Samples using the administration console to learn
how to install these Samples onto an application server that has been augmented
with a Web services profile.
About this task
newfeat
Best practice: The WebSphere® Application Server Version 6.1
Feature Pack for Web Services extends the capabilities of this product
to introduce support for the Java API for XML-Based Web Services (JAX-WS) 2.0 programming model.
JAX-WS is the next generation Web services programming model complimenting
the foundation provided by the Java API for XML-based RPC (JAX-RPC) programming model. Using the strategic
JAX-WS programming model, development of Web services and clients
is simplified through support of a standards-based annotations model.
Although the JAX-RPC programming model and applications are still
supported, take advantage of the easy-to-implement JAX-WS programming
model to develop new Web services applications and clients. bprac
Existing
JAX-RPC applications wanting to use JAX-WS features will need to be rewritten
using the JAX-WS programming model.
newfeat
Supported configurations: The Feature Pack for Web Services does not
support Java Message Service
(JMS) transports or enterprise beans. This product only supports an
HTTP transport and hosting JavaBeans endpoints within the Web container for JAX-WS Web services applications.
To develop enterprise beans hosted as Web services, you must use the
JAX-RPC programming model. This product does allow JAX-WS clients
to issue requests from any of the Java Platform, Enterprise Edition (Java EE) containers along with the client Java 2 Standard Edition (J2SE) environment.sptcfg
Web
services reflect the service-oriented architecture approach to programming.
This approach is based on the idea of building applications by discovering
and implementing network-available services, or by invoking the available
applications to accomplish a task. Web services deliver interoperability,
for example, Web services applications provide a way for components created
in different programming languages to work together as if they were created
using the same language. Web services rely on existing transport technologies,
such as HTTP, and standard data encoding techniques, such as Extensible Markup
Language (XML), for invoking the implementation.
Procedure
- Identify your goals and design Web services to fit your e-business
solution. Consider what you want to accomplish by using Web services.
Decide how Web services fit into your current topology, applications and programming
model. Determine how the Web services process requests on the server and how
the clients manage and use the Web service.
- Design your Web services for reliability, availability, manageability
and security. For example, you want your Web services to process
a transaction in a reasonable time at all hours of the day and provide users
with good security characteristics, such as authentication for buyers. Planning
to use Web services to work with WebSphere Application Server helps to meet
these requirements.
- Review the standards used in developing and deploying Web services
into WebSphere Application Server. Development and deployment are based on
a variety of Java programming models. There
are extensions to these standards that are also important to review. See Extensions to the JAX-RPC and Web Services
for J2EE programming models for more information.
- Decide what development and implementation tools to use.
You can use a variety of manual development and implementation tasks.
Whether you have an existing Web service to implement or you want to develop
your own from a JavaBeans implementation or from an Enterprise JavaBeans (EJB)
module, you can choose different tasks respective to your resources. You can
also use assembly tools to complete development and implementation tasks.
- Install WebSphere Application Server.
See Install WebSphere Application Server.
See Install WebSphere
Application Server.
See Install WebSphere Application Server.
- Review Web services
Samples.
Results
You have a design plan for implementing Web services applications
into your business architecture.