Distributed nonce caching enables you to distribute the cache for
a nonce to different servers in a cluster.
Before you begin
Before configuring distributed nonce caching, configure cache replication.
For more information,
see
Configuring cache replication.
Important: When you configure the cache replication, do not use the
default value of a single replica for the Number of replicas for dynamic cache
replication domains. Instead, use a full group replica for any replication
domains that you configure for dynamic cache. If you cannot select the option,
verify your cache replication configuration.
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
In
previous releases of WebSphere Application Server, the nonce was cached locally.
To use this feature, you must complete the following actions:
Procedure
- Verify that you created an appropriate domain setting when you
form a cluster.
For
more information, see Creating clusters.
- Verify that replication domain is properly secured. The
nonce cache is crucial to the integrity of the nonce validation process. If
the nonce cache is compromised, then you cannot trust the result of the validation
process.
- In
the administrative console for the cell level, select the Distribute nonce
caching option. You can enable the option by completing the
following steps:
- Click Servers > Application servers > server_name.
- Under Security, click Web services: Default bindings for
Web services security.
- Select the Distribute nonce caching option.
- Verify
that the dynamic cache service is enabled for each one of the application
servers in your cluster. To access the dynamic cache service through
the administrative console, complete the following steps:
- Click Servers > Application servers > server_name.
- Under Container settings, click Container services > Dynamic
cache service.
- Confirm that the Enable service at server startup option
is selected.
- In the administrative console for the server level, select the Distribute
nonce caching option. You can enable the option by completing
the following steps:
- Click Security > Web services.
- Select the Distribute nonce caching option.
- Restart the servers within your cluster.
Results
When you select the Distribute nonce caching option in the
administrative console, the nonce is propagated to other servers in your environment.
However, the nonce might be subject to a one-second delay in propagation and
subject to any network congestion.