2. Use the certificates to invoke
the secured Web service
to display the extrapolated
amount of the bid:
a. Make sure the AuctionApp
we opened previously is
up and running. If it is not,
right-click the AuctionApp
node and choose Deploy.
b. Expand the Web Service
References node of the
AuctionAppWebService-
Client project and right-
click the AuctionApp
SOAPws node; then
select Edit Web Service
Attributes.
c. Under the Quality Of
Service tab, expand the
Security section.
d. Select the Use develop
ment defaults option, as
shown in Figure 8.
e. Click OK.
f. Right-click the AuctionApp
WebServiceClient project
and choose Clean and
Build.
g. Right-click the
AuctionAppWebService
Client project again and
choose Run.
The list of all entries is dis-
played, as shown in Figure 5.
h. Click the Show all Bid
Items link to display the list
of bid entries, as shown in
Figure 6.
i. Click the View link for the
bidder named Vals to see
the newly extrapolated
amount of the Vals bid, as
shown in Figure 9.
Conclusion
In this article, we have seen how
easy it is to configure security
and reliability into an existing
Web service and set up default
credentials to access the service.
The bundled GlassFish keystore
and truststore files were very
useful. We used NetBeans and
Metro to automatically update
these files and use them immediately for development.
In Part 2 of this series, we
will focus on importing specific
certificates into the GlassFish
keystore and truststore so that
they can be used in a production
environment. </article>
JAVA IN ACTION
REGISTER NOW
Save $200 by Sept. 28th
Register at
oracle.com/javaone
ABOUT US
Silver Sponsor
Bronze Sponsors
LEARN MORE
•;NetBeans Advanced Web Service
Interoperability manual
•;Metro User Guide
•;GlassFish resources
Copyright © 2012, Oracle and/or its affiliates. All rights reserved.
Oracle and Java are registered trademarks of Oracle and/or its affiliates.
Other names may be trademarks of their respective owners.