You can plan to develop and implement Web services based
on a variety of Java™ programming models.
Before you begin
The Samples Gallery includes
Samples that demonstrate JAX-WS-based Web services. The JAX-WS Web
services 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), which you can use to
complete 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).
About this task
Best practice: IBM® WebSphere® Application Server supports the Java API for XML-Based Web Services (JAX-WS)
programming model and the Java API
for XML-based RPC (JAX-RPC) programming model. JAX-WS is the next
generation Web services programming model extending the foundation
provided by the 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
You
must re-write existing JAX-RPC applications if you want to take advantage
of the features of the JAX-WS programming model.
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 optimal security, 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 onto WebSphere Application Server.
Development and deployment are based on a variety of Java programming models.
- 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 the application server. For detailed
information on installing the application server, read about installing
your application serving environment.
- Review Web services Samples.
Results
You have a design plan for implementing Web services applications
into your business architecture.